From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: next-error refactoring
Date: Thu, 01 Jul 2004 08:47:08 +0300 [thread overview]
Message-ID: <87n02kl1in.fsf@mail.jurta.org> (raw)
In-Reply-To: <4nzn6kc2fg.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 30 Jun 2004 14:42:59 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Can I get a list of suggested modes that might benefit from next-error
> support? Everyone, please send me your suggestions.
>
> So far we have:
>
> compilation-mode
> grep (which uses compilation-mode)
> occur-mode
>
> Other possibilities:
>
> emerge
> diff-mode
AFAICS, diff-mode belongs to the "what we have" category since it
already supports `next-error'.
> (please add your suggestions)
I think existing modes are enough to create an unified set of key
bindings. These modes are quite heterogeneous by their functionality,
so you can get good coverage of needs for key bindings.
If you want to add next-error support for more modes, you might consider
etags, dired-do-search, find-grep-dired.
> When I have a list of modes I can look at the key binding problems
> between them all.
Please take into account conclusions from the discussion started from
http://lists.gnu.org/archive/html/emacs-devel/2004-05/msg01452.html
http://lists.gnu.org/archive/html/emacs-devel/2004-06/msg00023.html
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-07-01 5:47 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 5:29 compilation-highlight-duration Tak Ota
2004-05-01 17:51 ` compilation-highlight-duration Richard Stallman
2004-05-02 16:47 ` compilation-highlight-duration Tak Ota
2004-05-03 14:03 ` compilation-highlight-duration Richard Stallman
2004-05-03 14:13 ` compilation-highlight-duration Tak Ota
2004-05-04 7:43 ` compilation-highlight-duration Richard Stallman
2004-05-04 14:54 ` compilation-highlight-duration Tak Ota
2004-05-04 16:55 ` compilation-highlight-duration Juri Linkov
2004-05-04 17:20 ` compilation-highlight-duration Kim F. Storm
2004-05-04 20:01 ` compilation-highlight-duration Juri Linkov
2004-05-04 21:30 ` compilation-highlight-duration Kim F. Storm
2004-05-04 20:32 ` compilation-highlight-duration Drew Adams
2004-05-04 19:15 ` compilation-highlight-duration Tak Ota
2004-05-04 21:35 ` compilation-highlight-duration Tak Ota
2004-05-05 17:33 ` compilation-highlight-duration Stefan Monnier
2004-05-05 18:05 ` compilation-highlight-duration Tak Ota
2004-05-05 20:20 ` compilation-highlight-duration Richard Stallman
2004-05-05 20:59 ` compilation-highlight-duration Tak Ota
2004-05-05 22:47 ` compilation-highlight-duration Thien-Thi Nguyen
2004-05-05 21:22 ` compilation-highlight-duration Stefan Monnier
2004-05-06 5:58 ` compilation-highlight-duration Kim F. Storm
2004-05-06 9:23 ` compilation-highlight-duration Juri Linkov
2004-05-06 7:48 ` compilation-highlight-duration Kim F. Storm
2004-05-06 10:34 ` compilation-highlight-duration David Kastrup
2004-05-06 10:22 ` compilation-highlight-duration Kim F. Storm
2004-05-07 0:29 ` compilation-highlight-duration Richard Stallman
2004-05-07 0:29 ` compilation-highlight-duration Richard Stallman
2004-05-09 1:03 ` compilation-highlight-duration Juri Linkov
2004-05-09 18:48 ` compilation-highlight-duration Richard Stallman
2004-05-09 19:12 ` compilation-highlight-duration Kim F. Storm
2004-05-10 7:17 ` compilation-highlight-duration Eli Zaretskii
2004-05-10 20:30 ` compilation-highlight-duration Stefan Daschek
2004-05-28 11:19 ` compilation-highlight-duration Juri Linkov
2004-05-28 11:42 ` compilation-highlight-duration Kim F. Storm
2004-05-28 15:45 ` next-error refactoring (was: compilation-highlight-duration) Ted Zlatanov
2004-05-28 18:14 ` next-error refactoring Juri Linkov
2004-05-29 3:54 ` Ted Zlatanov
2004-05-29 17:03 ` next-error refactoring (was: compilation-highlight-duration) Richard Stallman
2004-06-01 17:55 ` next-error refactoring Ted Zlatanov
2004-06-02 17:36 ` Richard Stallman
2004-06-03 15:23 ` Ted Zlatanov
2004-06-07 21:27 ` Juri Linkov
2004-06-09 19:52 ` Richard Stallman
2004-06-02 17:36 ` Richard Stallman
2004-06-03 15:30 ` Ted Zlatanov
2004-06-03 23:33 ` Juri Linkov
2004-06-07 16:14 ` Ted Zlatanov
2004-06-04 2:03 ` Richard Stallman
2004-06-07 16:11 ` Ted Zlatanov
2004-06-07 17:01 ` Tak Ota
2004-06-08 20:31 ` Richard Stallman
2004-06-11 18:39 ` Ted Zlatanov
2004-06-12 9:44 ` Richard Stallman
2004-06-30 18:42 ` Ted Zlatanov
2004-07-01 5:47 ` Juri Linkov [this message]
2004-09-13 18:56 ` Ted Zlatanov
2004-09-14 10:28 ` Kim F. Storm
2004-09-15 18:08 ` Ted Zlatanov
2004-06-09 9:53 ` Stefan Monnier
2004-06-09 20:19 ` Juri Linkov
2004-06-10 23:01 ` Richard Stallman
2004-05-29 17:02 ` compilation-highlight-duration Richard Stallman
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=87n02kl1in.fsf@mail.jurta.org \
--to=juri@jurta.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 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).