From: Daniel Brockman <daniel@brockman.se>
To: emacs-devel@gnu.org
Subject: Re: bind next-error and previous-error in Occur mode? read-only?
Date: Thu, 01 Feb 2007 03:53:21 +0100 [thread overview]
Message-ID: <87veimio66.fsf@wigwam.brockman.se> (raw)
In-Reply-To: EIENLHALHGIMHGDOLMIMAEHHCOAA.drew.adams@oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
> I also just noticed `occur-next', bound to `M-n' in *Occur*.
> It's good to have a binding that does this, but wouldn't `C-n'
> be more logical? IOW, wouldn't it make sense to have `C-n'
> be `occur-next' and have `next-error-follow-minor-mode'
> use `M-n' instead of `C-n'? Is there a reason to keep `C-n'
> as `next-line'?
Yes. In fact, there is a very good reason: That binding
is standard throughout all of Emacs. I always use `C-n'
to move to the next line, and I would be confused if that
binding was changed in the *Occur* buffer --- even though
the command `occur-next' is similar to `next-line'.
Why do you think `C-n' is more logical than `M-n' here?
To me, it makes sense to rebind `C-n' only when moving by
lines in the usual manner does not itself make any sense.
After all, `next-line' is a pretty useful command.
--
Daniel Brockman <daniel@brockman.se>
prev parent reply other threads:[~2007-02-01 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 20:59 bind next-error and previous-error in Occur mode? read-only? Drew Adams
2007-01-26 3:09 ` Richard Stallman
2007-01-26 5:36 ` Masatake YAMATO
2007-01-26 9:42 ` Eli Zaretskii
2007-01-26 10:27 ` Masatake YAMATO
2007-01-26 14:43 ` Eli Zaretskii
2007-01-26 15:55 ` Ted Zlatanov
2007-01-26 16:21 ` Drew Adams
2007-01-26 19:05 ` Ted Zlatanov
2007-01-26 19:15 ` Drew Adams
2007-02-01 2:53 ` Daniel Brockman [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87veimio66.fsf@wigwam.brockman.se \
--to=daniel@brockman.se \
--cc=emacs-devel@gnu.org \
/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.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).