From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Propertizing the minor-mode-alist
Date: Tue, 21 Sep 2004 14:31:23 -0400 [thread overview]
Message-ID: <E1C9pQB-0005J9-Jl@fencepost.gnu.org> (raw)
In-Reply-To: <1095647396.7357.281.camel@pineapple.bkk.thaiopensource.com> (message from James Clark on Mon, 20 Sep 2004 09:29:56 +0700)
I misspoke earlier: there's a keystroke for goto to next error, but not
for goto first error.
C-u C-x ` goes to the first error. C-x ` goes to the first error
when you have not visited any errors.
If this can be made to do the job, I would definitely prefer it.
However, I take your point about moving point being a strange thing for
a mode-line click to do. The underlying idea is that clicking on the
invalidity indicator ought to give information about the invalidity.
Moving point to the location of the first error was an easy way to do
this, but perhaps a better way would be to pop up a buffer giving a
summary of all the errors in the buffer. Do you think that would be
better?
I would rather avoid ad-hoc mode line interfaces.
next prev parent reply other threads:[~2004-09-21 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 11:57 Propertizing the minor-mode-alist James Clark
2004-09-16 14:00 ` Stefan
2004-09-17 2:32 ` James Clark
2004-09-17 3:46 ` Stefan
2004-09-17 21:52 ` Kim F. Storm
2004-09-18 19:07 ` Richard Stallman
2004-09-17 23:23 ` Richard Stallman
2004-09-18 2:50 ` James Clark
2004-09-18 22:55 ` Richard Stallman
2004-09-19 6:07 ` David Kastrup
2004-09-19 6:35 ` James Clark
2004-09-20 0:05 ` Richard Stallman
2004-09-20 2:29 ` James Clark
2004-09-20 10:56 ` Kai Grossjohann
2004-09-21 18:31 ` Richard Stallman [this message]
2004-09-22 7:30 ` James Clark
2004-09-22 13:23 ` Stefan Monnier
2004-09-22 14:02 ` James Clark
2004-09-22 16:31 ` Stefan Monnier
2004-09-23 9:29 ` Richard Stallman
2004-09-23 13:15 ` James Clark
2004-09-24 12:08 ` Richard Stallman
2004-09-18 10:52 ` James Clark
2004-09-18 21:06 ` Stefan
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=E1C9pQB-0005J9-Jl@fencepost.gnu.org \
--to=rms@gnu.org \
--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 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.