unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: next-error refactoring
Date: Thu, 03 Jun 2004 11:30:14 -0400	[thread overview]
Message-ID: <4n3c5c64mx.fsf@lifelogs.com> (raw)
In-Reply-To: E1BVZfW-0006T6-OW@fencepost.gnu.org

On Wed, 02 Jun 2004, rms@gnu.org wrote:

	>> Is it time to make next-error a minor mode with its own next-error.el
>     >     file?
>     > 
>     > We already have a minor mode for this: compilation-minor-mode.
> 
>     Yes, but the name "compilation-minor-mode" hardly addresses the DWIM
>     nature of next-error as it stands now, and the compilation-minor-mode
>     has other side effects (fontification, for instance).
> 
> Those go together because they are used together.
> 
> Introducing unnecessary levels of abstraction for small things
> creates clutter.  

I'm trying to make next-error a universal "next DWIM" interface, and
being tied to compilation-minor-mode will hamper that effort.  For
instance, it would look very strange if compilation-minor-mode was on
in a mail article summary, even though next-error (or some sensibly
named alias) could make sense for moving to the next article.  It
would be easier to name hooks for next-error, as well, if it had its
own mode.  I would like to create hooks that developers can easily use
to register their next-error capability, instead of the current
situation where next-error mode has to be enabled by magically setting
a variable, and discovering next-error buffers is an error-prone
algorithm.

I'm thinking of next-error-register and next-error-unregister
functions a developer would call in a buffer; to register a
next-error-function has to be provided (plus other things, probably)
and in return the buffer is registered as a next-error capable buffer.

Also, users will be less confused if next-error has its own minor
mode.

> We do not want a separate mode for next-error parsing alone,
> distinct from the rest of error handling.

Understood.  I would like to make next-error more than that.

Ted

  reply	other threads:[~2004-06-03 15:30 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 [this message]
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
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=4n3c5c64mx.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    /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).