all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Allow compilation-next-error-function to leave code line highlighted until next command is typed
Date: Tue, 13 Jul 2004 20:16:58 -0400	[thread overview]
Message-ID: <E1BkXSE-0005rN-7M@fencepost.gnu.org> (raw)
In-Reply-To: <4nllhpqk3w.fsf@lifelogs.com> (message from Ted Zlatanov on Mon,  12 Jul 2004 12:13:39 -0400)

    > The first 4 nodes in building.texi need to be thoroughly reviewed
    > for obsolete statements and for other important things that should
    > be added.  Can someone thoroughly familiar with the new compilation
    > code volunteer to do that?

    Sorry, I thought "new compilation code" referred to the other major
    changes in compile.el that were put in CVS.

    I will look at building.texi and see if the next-error changes I did
    affect anything.

All the changes in compile.el, including Daniel Pfeiffer's, could
require changes in the manual.  If you reread the NEWS and you're
familiar with the code as it stands now, you could probably
recognize whatever errors there may be in the manual.  That would
be quite useful.

  reply	other threads:[~2004-07-14  0:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 19:26 [PATCH] Allow compilation-next-error-function to leave code line highlighted until next command is typed Francis Litterio
2004-06-22 23:19 ` Juri Linkov
2004-06-23  4:50 ` Eli Zaretskii
2004-06-28 14:58 ` Richard Stallman
2004-06-29  1:32   ` Juri Linkov
2004-06-30  3:02     ` Richard Stallman
2004-07-01  5:46       ` Juri Linkov
2004-07-02 10:12         ` Richard Stallman
2004-07-10 22:41         ` Richard Stallman
2004-07-12 16:13           ` Ted Zlatanov
2004-07-14  0:16             ` Richard Stallman [this message]
2004-09-13 17:58               ` Ted Zlatanov
2004-09-17  9:36                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1BkXSE-0005rN-7M@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.