From: Thorsten <firstname.lastname@example.org>
Subject: Re: org-replace-disputed-keys not working
Date: Tue, 27 Mar 2012 12:35:35 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
suvayu ali <firstname.lastname@example.org> writes:
> On Tue, Mar 27, 2012 at 00:08, Thorsten <email@example.com> wrote:
>> I started the emacs-daemon with that option, but it did not help
>> unfortunately. But it seems windmove.el only works in X11 anyway, not in
>> console sessions? At least for me the shift character is ignored in a
>> console session and doing C-h k for S-<right> gives:
> That is an issue with your terminal emulator. I have faced that too but
> haven't had time to look into it in detail.
> I also use windmove but with the meta (M, Alt on linux) key. This
> however has the disadvantage of conflicting even more with org. So I use
> the shift key with org. So in the end windmove works in all modes
> (except org) for all sessions (X and terminal), it works with hiccups
> with org only in an X session.
M-<arrow> is somehow used by Archlinux itself it seems, they change
tty's on my sytem and don't get through to the application.
> These are my relevant settings:
> ;; navigate thru windows using M-<arrow>
> (windmove-default-keybindings 'meta)
> ;; Make windmove work in org-mode with 'shift as modifier:
> (add-hook 'org-shiftup-final-hook 'windmove-up)
> (add-hook 'org-shiftleft-final-hook 'windmove-left)
> (add-hook 'org-shiftdown-final-hook 'windmove-down)
> (add-hook 'org-shiftright-final-hook 'windmove-right)
> Hope this will help.
Thanks, that looks like a straight-forward solution. I'll check it out.
next prev parent reply other threads:[~2012-03-27 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 12:59 org-replace-disputed-keys not working Thorsten
2012-03-26 17:17 ` Bastien
2012-03-26 22:08 ` Thorsten
2012-03-26 22:29 ` suvayu ali
2012-03-27 10:35 ` Thorsten [this message]
2012-03-27 8:20 ` Bastien
2012-03-27 10:28 ` Thorsten
2012-03-27 8:44 ` Gregor Zattler
2012-03-27 10:44 ` Thorsten
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).