Issue 1277 in dactyl: All multi-key commands (gg,go,gn,<Leader>-X,etc.) don't work.

5 views
Skip to first unread message

dac...@googlecode.com

unread,
Feb 25, 2015, 1:03:04 PM2/25/15
to dacty...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Project-Pentadactyl

New issue 1277 by cherac...@gmail.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

1. Default install of latest nightly build (as of 20150215).
2. Firefox 36.0
3. Any attempt at a multiple key command (gg,go,gn,<Leader>-X,etc.) does
not register the first key.

If I type <Leader>-r it does the "r" operation rather than the "<Leader>-r"
operation. If it type "gg" it shows that it has registered a single g
(i.e. waiting for me to type something more) without ever scrolling the
page. If I type "go" it thinks I have typed "o".

Single letter commands (like "G") seem to work fine.

Pentadactyl hg7149 (created 2015/02/24 04:23:22) running on:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:36.0) Gecko/20100101
Firefox/36.0



Apologies if this is a dupe. I searched "multiple,multi,leader,keys"
without seeing any tickets that matched.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

dac...@googlecode.com

unread,
Feb 25, 2015, 1:06:47 PM2/25/15
to dacty...@googlegroups.com

Comment #1 on issue 1277 by cherac...@gmail.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

For a bit more color:

I opened Firefox from a terminal and this is the stack trace when I try to
input the command "gg":



pentadactyl: TypeError:
iter(...)[Symbol.iterator](...).next(...).value[Symbol.iterator] is not a
function
pentadactyl: TypeError:
iter(...)[Symbol.iterator](...).next(...).value[Symbol.iterator] is not a
function::
pentadactyl: stack: hasNativeKey@resource://dactyl-content/events.js:478:29
pentadactyl: execute@resource://dactyl-content/key-processors.js:106:63
pentadactyl: process@resource://dactyl-content/key-processors.js:216:16
pentadactyl: onKeyPress@resource://dactyl-content/events.js:770:22
pentadactyl: wrappedListener@resource://dactyl-content/events.js:225:17
pentadactyl: toString: function () /* use strict */ String(error)

pentadactyl: TypeError:
iter(...)[Symbol.iterator](...).next(...).value[Symbol.iterator] is not a
function
pentadactyl: TypeError:
iter(...)[Symbol.iterator](...).next(...).value[Symbol.iterator] is not a
function::
pentadactyl: stack: hasNativeKey@resource://dactyl-content/events.js:478:29
pentadactyl: execute@resource://dactyl-content/key-processors.js:106:63
pentadactyl: process@resource://dactyl-content/key-processors.js:216:16
pentadactyl: onKeyPress@resource://dactyl-content/events.js:770:22
pentadactyl: wrappedListener@resource://dactyl-content/events.js:225:17
pentadactyl: toString: function () /* use strict */ String(error)

dac...@googlecode.com

unread,
Feb 25, 2015, 1:11:32 PM2/25/15
to dacty...@googlegroups.com

Comment #2 on issue 1277 by cherac...@gmail.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

Finally, and this appears to be a website bug as opposed to pentadactyl,
I'm getting an access denied error when I try to download the previous
nightly build (20150222.) I don't have any issues downloading the others
(latest,20150223,20141011).

Also, just want to say that I love this extension and appreciate the work
you guys put into it. Just wanted to make that clear since so far this
ticket is nothing but complaints ;).

dac...@googlecode.com

unread,
Feb 25, 2015, 10:58:01 PM2/25/15
to dacty...@googlegroups.com

Comment #3 on issue 1277 by mattle...@gmail.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

I confirmed this also fails with the previous two releases, 20150223 and
20150222. Even earlier versions fail of course thanks to
Firefox's "awesome" numbering scheme.

Manually fixing 20141011's install.rdf to include Firefox 36.0 doesn't help
- I guess the Chrome actually did change, since it successfully installs
but doesn't do anything. This was a fresh 36.0 image (OSX) with no other
plugins.

More worringly - I can't get the XPI to work from the hg tip, or any recent
hg revisions. Am I missing something about how to build the extension
manually?

dac...@googlecode.com

unread,
Feb 25, 2015, 11:55:44 PM2/25/15
to dacty...@googlegroups.com

Comment #4 on issue 1277 by mattle...@gmail.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

Actually, I tried again building from the master branch at Github -
https://github.com/5digits/dactyl

It seems to work now, which is great. In order to build I had to edit
common/make_jars.sh:

diff --git i/common/make_jar.sh w/common/make_jar.sh
index 37159ab..349aa34 100644
--- i/common/make_jar.sh
+++ w/common/make_jar.sh
@@ -42,7 +42,7 @@ mungeliterals=$(cat <<'!'
$_ = <>;
s{(?<!function )\bliteral\((?:function \(\) )?/\*(.*?)\*/\$?\)}{
my $s = $1;
- $s =~ s/[\\']/\\$&/g;
+ $s =~ s/[\\\']/\\$&/g;
$s =~ s/\n/\\n\\$&/g;
"/* Preprocessors FTW. */ '$s'";
}ges;

I.e., add an extra \ to the \\' line. I recall there's a patch for this but
it's not in master I suppose.

dac...@googlecode.com

unread,
Mar 3, 2015, 3:27:02 PM3/3/15
to dacty...@googlegroups.com

Comment #5 on issue 1277 by phil-goo...@hands.com: All multi-key commands
(gg,go,gn,<Leader>-X,etc.) don't work.
https://code.google.com/p/dactyl/issues/detail?id=1277

I have had this "no multi-key commands" behavior for quite a while (years
I'd guess), across many versions of Iceweasel and pentadactyl -- in fact I
had gained the impression that this just didn't work at all, and had
learned to avoid all such commands without really noticing. This has even
been carried across from an old laptop to my current one (I copied the
profile from the old to the new).

It was only when asking on IRC that I confirmed that they really ought to
work.

I since have discovered that by creating a new profile I fixed the problem.

I still have the old profile, which still exhibits the problem, so if there
are any tests I can do to track down the problem, feel free to ask.

Cheers, Phil.
Reply all
Reply to author
Forward
0 new messages