From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Stephan Stahl <stl@isogmbh.de>
Subject: Re: Idea for compilation mode
Date: 04 Jun 2003 18:37:44 +0900 [thread overview]
Message-ID: <buor86aw5cn.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <E19NU1k-0005mk-3r@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> I've always use the old gosmacs binding for this -- `C-x C-n' -- which I
> find very nice (even on a normal ascii keyboard, C-x ` is rather awkward
> to type).
>
> I didn't put it there because I carried forward the original Emacs
> meaning of C-x C-n. However, it could well be that next-error is
> used more than set-goal-column. So perhaps that binding should be changed.
>
> However, if next-error is C-x C-n, previous-error can't be C-x C-p.
> It would be better to find a good pair of keys for next-error and
> previous-error.
Hmm, well I of course use `C-x C-p' for previous-error, but I see that the
default binding is `mark-page'; is that a widely used command (I don't
think I use any page commands at all, except for forward/backward-page)?
I think that next/previous-error are quite widely used (not just
compilation, but grep, etc. also), and so deserve rather easy-to-type
bindings.
-Miles
--
80% of success is just showing up. --Woody Allen
next prev parent reply other threads:[~2003-06-04 9:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 22:41 Idea for compilation mode Richard Stallman
2003-06-03 7:42 ` Stephan Stahl
2003-06-03 8:01 ` David Kastrup
2003-06-03 10:20 ` Miles Bader
2003-06-03 16:14 ` Kevin Rodgers
2003-06-03 12:11 ` Frank Schmitt
2003-06-03 11:24 ` Kai Großjohann
2003-06-03 13:14 ` Stephan Stahl
2003-06-03 13:42 ` Kai Großjohann
2003-06-03 14:08 ` Stephan Stahl
2003-06-03 14:16 ` Stefan Monnier
2003-06-05 0:07 ` Richard Stallman
2003-06-05 0:07 ` Richard Stallman
2003-06-04 8:53 ` Richard Stallman
2003-06-04 9:37 ` Miles Bader [this message]
2003-06-04 10:23 ` David Kastrup
2003-06-04 10:27 ` Stephan Stahl
2003-06-04 15:19 ` Andreas Schwab
2003-06-05 6:25 ` Stephan Stahl
2003-06-05 13:07 ` Andreas Schwab
2003-06-05 13:31 ` Stephan Stahl
2003-06-05 13:37 ` Stefan Monnier
2003-06-05 14:00 ` Lute Kamstra
2003-06-05 23:02 ` Miles Bader
2003-06-05 23:08 ` Stefan Monnier
2003-06-07 12:01 ` Kai Großjohann
2003-06-05 10:57 ` Richard Stallman
2003-06-06 1:45 ` Miles Bader
2003-06-06 6:11 ` David Kastrup
2003-06-06 8:58 ` Stephan Stahl
2003-06-06 9:49 ` David Kastrup
2003-06-06 12:01 ` Stephan Stahl
2003-06-06 12:41 ` Juanma Barranquero
2003-06-06 13:40 ` Stephan Stahl
2003-06-06 17:55 ` Juanma Barranquero
2003-06-11 8:22 ` Stephan Stahl
2003-06-06 21:35 ` Frank Schmitt
2003-06-08 1:09 ` Richard Stallman
2003-06-08 2:38 ` David Kastrup
2003-06-09 17:12 ` Juanma Barranquero
2003-06-11 8:36 ` Stephan Stahl
2003-06-11 8:51 ` David Kastrup
2003-06-12 7:42 ` Juanma Barranquero
2003-06-06 15:40 ` David Kastrup
2003-06-06 16:49 ` Stephan Stahl
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=buor86aw5cn.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=miles@gnu.org \
--cc=stl@isogmbh.de \
/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).