unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Harald Maier <harald@maierh.de>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: compilation-scroll-output broken
Date: Wed, 21 Jan 2004 08:52:33 +0100	[thread overview]
Message-ID: <m3n08h91ry.fsf@ate.maierh> (raw)
In-Reply-To: <jewu7m9mcs.fsf@sykes.suse.de> (Andreas Schwab's message of "Wed, 21 Jan 2004 01:28:03 +0100")

Andreas Schwab <schwab@suse.de> writes:

> Richard Stallman <rms@gnu.org> writes:
>
>>     what was the motivation for this change?
>>
>>     2004-01-03  Richard M. Stallman  <rms@gnu.org>
>>
>>          * progmodes/compile.el (compile-internal): Use point, not point-min,
>>          for set-window-point.
>>
>> It fixed a bug where the actual output was not visible
>> because it was inserted in the buffer before the window start.
>> This occurred when the buffer was already displayed in another window.
>
> Do you have a simple way to reproduce?  I can't remember having seen this
> problem myself, and ignoring compilation-scroll-output looks like the more
> serious bug.

I want to second this.

I am using for '*compilation*' 'special-display-buffer-names' (frame
height 20 lines) and I also have set 'compilation-scroll-output' set
to 't' but with my very long compile command line (7628 characters)
the buffer moves _not_ to the end and so I am not able to see whether
the compilation has finished. It moves to the end only for the first
time. Also without 'special-display-buffer-names' it looks better.

Harald

PS: Last check out was on 2004-01-19.

  reply	other threads:[~2004-01-21  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 15:50 compilation-scroll-output broken Andreas Schwab
2004-01-13 21:14 ` Richard Stallman
2004-01-21  0:28   ` Andreas Schwab
2004-01-21  7:52     ` Harald Maier [this message]
2004-01-21 21:09     ` 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=m3n08h91ry.fsf@ate.maierh \
    --to=harald@maierh.de \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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).