all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: emacs-devel@gnu.org
Subject: Changes to emacs/doc/emacs/building.texi,v
Date: Mon, 17 Nov 2008 01:57:31 +0200	[thread overview]
Message-ID: <87y6zjkyvo.fsf@jurta.org> (raw)

In the 2008-10-31 commit of building.texi I noticed the following change:

   @findex compile-goto-error
  +@vindex compilation-auto-jump-to-first-error
     You can visit the source for any particular error message by moving
   point in the @samp{*compilation*} buffer to that error message and
   typing @key{RET} (@code{compile-goto-error}).  Alternatively, you can
   click @kbd{Mouse-2} on the error message; you need not switch to the
  - <at> samp{*compilation*} buffer first.
  +@samp{*compilation*} buffer first.  If you set the variable
  +@code{compilation-auto-jump-to-first-error} to a non-@code{nil} value,
  +Emacs automatically jumps to the first error (if any exists) once
  +compilation finishes.

Actually it jumps to the first error immediately after it occurs.

Perhaps this is caused by the inaccuracy in the doc string of
`compilation-auto-jump-to-first-error' that says:

  If non-nil, automatically jump to the first error after `compile'.

A better variant would be:

  If non-nil, automatically jump to the first error during `compile'.

BTW, maybe a new option `first-error' of `compilation-scroll-output'
should be documented in the manual too?

-- 
Juri Linkov
http://www.jurta.org/emacs/




             reply	other threads:[~2008-11-16 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 23:57 Juri Linkov [this message]
2008-11-17  1:53 ` Changes to emacs/doc/emacs/building.texi,v Chong Yidong
2008-11-17  4:25 ` Stefan Monnier
2008-11-17 22:35   ` Juri Linkov
2008-11-17 22:49     ` martin rudalics

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=87y6zjkyvo.fsf@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 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.