Open GoogleCodeExporter opened 9 years ago
i'd also love to see this standardized. Ideally, i think most of these keys
should be
at the OS level. I think there are some problems to actually have Apple
incorporate
it into OS X or MS for Windows. Because, basically it means a major change to
all the
shortcuts. Technically, there are also some problems to get it to work in OSX
at
least.
personally, i havn't tried to rely on OS wide such change either because there
are
several practical issues. On OS X for example, it simply won't work because it
conflict with too many Mac's standard shortcuts in all apps with the Cmd key.
If on
goes with the ergoemacs binding, then one has to remap lots of Cmd shortcuts
individually for each app (besides the few standards cmd bindings across os).
The OS
X's keybinding system is not able to do this completely or smoothly either,
because
some keys are bind at very low level that bypass the keybind system. On
Windows, the
situation is similar but i know the detail well. Don't know what's the
situation with
Linux or X11.
in practice, what i do is to always switch to emacs for text editing, than copy
paste
back to whatever app.
i do hope there's some movement on this... i think a key is to start with
popularising this, getting more people to be aware of this, have more linux
apps
starting to use this. As awareness spread, then more and more app will adopt,
tech
will come to fix any existing problems, and possibly this ergonomic binding
become
standadized on word processor related apps as a input system.
Original comment by xah...@gmail.com
on 15 Jul 2009 at 1:32
[deleted comment]
[deleted comment]
[deleted comment]
I am using xmonad quite a while now and I have to say I works perfectly fine
with
ErgoEmacs keybindings as long as you remap the 'Mod' key from Meta to somewhere
else,
for instance the windows-logo key (sometimes called 'Super'). This way I have
everything from the WM in 'Super-Space' and everything from ErgoEmacs in
'Meta-Space', leaving the pinky-straining 'Ctrl-Space' to only a few, sparsely
used
shortcuts. I think this is pretty much standard (at least among the xmond users
i
know), however xmonad, as emacs, is all about customization and I do not see
any form
of "official" standadization happening anywhere in the near future.
see
http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#Rebinding_the_m
od_key_.28Alt_conflicts_with_other_apps.3B_I_want_the_____key.21.29
For the terminal, I suggest having a look at ~/.inputrc or if it does not exist
/usr/share/readline/inputrc, since bash as many other programs in the unix
world make
use of the readline libraries, check it out there are plenty of tutorials and
dotfiles to rip from on the 'net. Alternatively, use zsh instead of bash, ZLE,
the
zsh line editor beats the pants of readline at lenght.
I am currently playing with the thought of implementing global ergo-emacs like
shortcuts for windows in AHK or 'hoekey'. It should not be that hard, and I
already
got (dvorak here) Alt-e and Alt-u for foreward and backward delete aswell as
Alt-chtn
for arrow keys in hoekey overriding the menubar-activating Alt key... but I
might not
find the time to produce something for the public (also: for qwerty users) in
the
next few weeks.
greets,
Milan
Original comment by milan.santosi@gmail.com
on 24 Sep 2009 at 4:21
Interesting. I'd love to see OS X level integration as well. As for conflicts
with the CMD key bindings, I notice that
many of Ergoemacs' bindings use the Alt key as the modifier. I am no OS X
expert but it's conceivable that you
could use the option key instead. As a modifier in OS X the option key is only
used to produce special characters.
You could keep some of the relevant CMD-key bindings such as copy/paste/undo,
but then use the option key to
bind to emacs commands such as word-forward or delete-word. At present, the
option key is used in
combination with the directional keys to move forward by words, or delete whole
words. However, it'd be great to
not have to move off of the home row.
Original comment by aspicL...@gmail.com
on 2 Jun 2010 at 8:25
Original issue reported on code.google.com by
ville.w...@gmail.com
on 24 Mar 2009 at 12:37