On Mon, Dec 20, 2010 at 1:21 PM, Leo Alekseyev wrote:
> 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.
>
> ;;
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
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- from S-, and if that is too difficult, then (b) get
rid of outline manipulation altogether. I use S- in windmove
orders of magnitude more often than I mess with m
On Thu, Dec 16, 2010 at 2:24 PM, Leo Alekseyev 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
As per the docs, I have (add-hook 'org-shiftup-final-hook
'windmove-up) and similar hooks set. That way, shift-arrow keys work
as they do in windmove (that is, they switch between windows) _unless_
I am on an org heading.
I would like to make that behavior universal -- I want to disable any
sort
