emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Alekseyev <dnquark@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Windmove keybindings pass-through
Date: Mon, 20 Dec 2010 13:21:29 -0800	[thread overview]
Message-ID: <AANLkTimBv_gm2rEyFmikyJoondqysp89nto2CDm3xW7Q@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinX7x+8qZqB-rYVvQ2xieksGY-h-4MnbX83S3NK@mail.gmail.com>

To answer my own question: here's how you avoid clobbering the
windmove commands.  This method should probably be added to the org
manual section which discusses the (add-hook 'org-shiftup-final-hook
'windmove-up), etc commands.

;; don't clobber windmove bindings: code must be placed _before_ org
loads
;; also, the (add-hook 'org-shiftup-final-hook 'windmove-up), etc
lines don't seem to do squat
;; default disputed keys remap so that windowmove commands aren't
overridden
(setq org-disputed-keys '(([(shift up)] . [(meta p)])
                          ([(shift down)] . [(meta n)])
                          ([(shift left)] . [(meta -)])
                          ([(shift right)] . [(meta +)])
                          ([(meta return)] . [(control meta return)])
                          ([(control shift right)] . [(meta shift +)])
                          ([(control shift left)] . [(meta shift -)])))
(setq org-replace-disputed-keys t)


On Mon, Dec 20, 2010 at 12:37 PM, Leo Alekseyev <dnquark@gmail.com> wrote:
> Thanks for the suggestion, but this is a non-solution.  My preference
> would be to (a) in org-mode, move outline manipulation to e.g.
> C-<arrows> from S-<arrows>, and if that is too difficult, then (b) get
> rid of outline manipulation altogether.  I use S-<arrows> in windmove
> orders of magnitude more often than I mess with my org outlines.
> Surely there must be a way to customize org keybindings without having
> to source-dive?..
>
> --Leo
>
> On Thu, Dec 16, 2010 at 3:20 PM, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>> On Thu, Dec 16, 2010 at 2:24 PM, Leo Alekseyev <dnquark@gmail.com> wrote:
>>> Optionally, it would be nice
>>> if I can map the shift-arrow functionality to something like M-arrows
>>> or C-arrows or C-M-arrows (whichever might be not taken / less
>>> useful).  However, getting rid of org-mode's stealing shift-arrows is
>>> a priority.  Any help is appreciated :)
>>
>> I would recommend (windmove-default-keybindings 'control) for
>> `C-<arrow>'. That seems to be the modifier key least used by org-mode
>> and least likely to be overridden.
>>
>> --
>> Suvayu
>>
>> Open source is the future. It sets us free.
>>
>

  reply	other threads:[~2010-12-20 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 22:24 Windmove keybindings pass-through Leo Alekseyev
2010-12-16 23:20 ` suvayu ali
2010-12-20 20:37   ` Leo Alekseyev
2010-12-20 21:21     ` Leo Alekseyev [this message]
2010-12-20 21:43       ` suvayu ali

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimBv_gm2rEyFmikyJoondqysp89nto2CDm3xW7Q@mail.gmail.com \
    --to=dnquark@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).