From: Chong Yidong <cyd@stupidchicken.com>
To: "Marshall\, Simon" <Simon.Marshall@misys.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: [21.1.90]: point put at point-min in *compilation*
Date: Mon, 04 Feb 2008 10:40:11 -0500 [thread overview]
Message-ID: <87hcgoloh0.fsf@stupidchicken.com> (raw)
In-Reply-To: <6EE216E1AA959543A555C60FF34FB76702CD2B19@maileube01.misys.global.ad> (Simon Marshall's message of "Mon\, 4 Feb 2008 14\:49\:58 -0000")
"Marshall, Simon" <Simon.Marshall@misys.com> writes:
> In 21.1, if you run Compile | Compile... RET or Compile | Recompile in a
> *compilation* buffer, point is initially placed at point-max, which
> means that point stays at point-max as compilation output is inserted
> into the buffer and Emacs scrolls the window to keep the latest output
> visible. Very convenient.
>
> In 21.1.90, point is placed at point-min, so that you have to actively
> scroll the window to see compilation output. I really don't like it!
I think this is due to the following change:
2007-12-27 Richard Stallman <rms@gnu.org>
* progmodes/compile.el (compilation-start): Set initial visible
point properly even when compilation buffer already current.
Which was meant to address this complaint:
From: Drew Adams Sent: Monday, December 11, 2006 3:21 PM
Previously in Emacs 22, as well as in previous releases, , repeating
grep in the *grep* buffer would put you at the top of the buffer. This
was true at least as late as a build from 2006-07-19.
Now, it puts you at the end of the buffer, so you must do M-< to get
back to the beginning. Quite annoying.
next prev parent reply other threads:[~2008-02-04 15:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 14:49 [21.1.90]: point put at point-min in *compilation* Marshall, Simon
2008-02-04 15:14 ` Chong Yidong
2008-02-04 15:55 ` Marshall, Simon
2008-02-04 16:37 ` Drew Adams
2008-02-04 17:29 ` Marshall, Simon
2008-02-04 15:40 ` Chong Yidong [this message]
2008-02-04 20:50 ` Glenn Morris
2008-02-05 1:24 ` Richard Stallman
2008-02-05 9:19 ` Marshall, Simon
2008-02-05 16:15 ` Stefan Monnier
2008-02-06 16:11 ` Richard Stallman
2008-02-06 16:17 ` David Kastrup
2008-02-06 17:03 ` Marshall, Simon
2008-02-07 0:44 ` Richard Stallman
2008-02-07 2:41 ` Stefan Monnier
2008-02-07 19:52 ` Richard Stallman
2008-02-07 9:55 ` Marshall, Simon
2008-02-07 9:59 ` Miles Bader
2008-02-07 10:02 ` David Kastrup
2008-02-07 15:10 ` Marshall, Simon
2008-02-07 15:29 ` David Kastrup
2008-02-07 15:50 ` Marshall, Simon
2008-02-07 16:09 ` David Kastrup
2008-02-07 16:35 ` Marshall, Simon
2008-02-07 15:28 ` Stefan Monnier
2008-02-07 19:59 ` Juri Linkov
2008-02-08 4:16 ` Richard Stallman
2008-02-06 17:14 ` Stefan Monnier
2008-02-07 1:57 ` Juri Linkov
2008-02-07 3:30 ` Stefan Monnier
2008-02-07 19:57 ` Juri Linkov
2008-02-08 9:22 ` Marshall, Simon
2008-02-08 14:46 ` Stefan Monnier
2008-02-06 21:10 ` Stephen J. Turnbull
2008-02-06 22:09 ` Stefan Monnier
2008-02-07 19:52 ` Richard Stallman
2008-02-07 21:13 ` Stephen J. Turnbull
2008-02-08 4:15 ` 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=87hcgoloh0.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=Simon.Marshall@misys.com \
--cc=emacs-pretest-bug@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).