unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Clark <jjc@auth-only.jclark.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Propertizing the minor-mode-alist
Date: Wed, 22 Sep 2004 21:02:27 +0700	[thread overview]
Message-ID: <1095861747.7357.491.camel@pineapple.bkk.thaiopensource.com> (raw)
In-Reply-To: <jwvisa64eww.fsf-monnier+emacs@gnu.org>

On Wed, 2004-09-22 at 20:23, Stefan Monnier wrote:
> > I like the idea of using a C-u prefix to make the next error command go
> > to the first error.  I can definitely use that.
> 
> > I don't see a good way to make it work with C-x `.  nxml-mode presents
> > errors using a very different style of UI from compile.el.  It's more
> 
> M-x next-error is now "independent" from compile.el.
> Of course, this is specific to Emacs-CVS, but you could use this new feature
> by providing a next-error-function (that's the name of the new var
> introduced to decouple next-error from compile.el).

This looks great.  Let me just check my understanding here.

The doc string talks about "the next error in the current buffer".  This
means the next error following the error that was last found my the
next-error-function, not the next error after point.  So to support the
next-error-function I need to maintain an additional bit of state saying
which error in my buffer, if any, is the current error for the purposes
of next error function; if my next-error-function is called with a
non-nil RESET, I change the current error to be the first error in the
buffer.  

If the user wanted to use next-error to run through the errors from an
XSLT processor, say, instead from nxml-mode, then they would make the
compilation buffer be the only one displayed in the frame before calling
next-error.

Have I misunderstood anything?

James

  reply	other threads:[~2004-09-22 14:02 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
2004-09-22  7:30                   ` James Clark
2004-09-22 13:23                     ` Stefan Monnier
2004-09-22 14:02                       ` James Clark [this message]
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

  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=1095861747.7357.491.camel@pineapple.bkk.thaiopensource.com \
    --to=jjc@auth-only.jclark.com \
    --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).