From: Kaushal Modi <kaushal.modi@gmail.com>
To: Adam Porter <adam@alphapapa.net>,
emacs-orgmode@gnu.org, lists@wilkesley.net
Subject: Re: Problems with M-<up> on Emacs 25.
Date: Mon, 18 Apr 2016 03:14:37 +0000 [thread overview]
Message-ID: <CAFyQvY2UL+GekE_VnE=gqykFTX1dDe_uwFqchZM8rdReRm7fWg@mail.gmail.com> (raw)
In-Reply-To: <87ega3pzev.fsf@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hi Ian,
> On my computer running 24.5.1 M<up> works as expected. However, on emacs
25.1.50.1 I get ...
First of all, it is important to know in which major mode you are trying to
use the M-<up>/<down> bindings. They are undefined by defined and are
defined in org-mode-map.
It is also important to know in which minor/major mode maps you are binding
those in your config. I would guess that the problem you see does not occur
in an emacs -Q session?
It's also important to know that a key can be bound to different command in
different minor/major mode maps and in global maps.
Here's the priority:
1. Minor mode map (last enabled minor mode)
2. Major mode map (e.g. org-mode-map)
3. Global map
So even if M-<up> is bound to org-metaup in org-mode-map, if foo-mode-map
(some minor mode map) as that key bound to a function 'bar' and if foo-mode
is enabled in an org-mode buffer, M-<up> will now call 'bar' instead of
'org-metaup'. So it is important to understand the consequences when making
new bindings to minor mode maps (or understand the maps of the minor modes
you enable).
> but emacs thinks that M-<up> is bound to scroll other window.
Emacs does not bind M-<up> by default to anything. So my guess is that
somewhere in your config, you are binding that key to scroll other window.
(I myself have been guilty of stepping over org-mode-map bindings in the
past. Now I have learnt when to bind keys in global-map vs my own minor
mode map which I use when I want my bindings to override everything else).
--
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2316 bytes --]
prev parent reply other threads:[~2016-04-18 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 9:57 Problems with M-<up> on Emacs 25 Ian Barton
2016-04-17 23:51 ` Adam Porter
2016-04-18 3:14 ` Kaushal Modi [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY2UL+GekE_VnE=gqykFTX1dDe_uwFqchZM8rdReRm7fWg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=lists@wilkesley.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.