From: David Kastrup <dak@gnu.org>
To: rms@gnu.org
Cc: emacs-pretest-bug@gnu.org, Simon.Marshall@misys.com,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: [21.1.90]: point put at point-min in *compilation*
Date: Wed, 06 Feb 2008 17:17:28 +0100 [thread overview]
Message-ID: <86y79yrrdz.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <E1JMmsA-00047i-7k@fencepost.gnu.org> (Richard Stallman's message of "Wed, 06 Feb 2008 11:11:42 -0500")
Richard Stallman <rms@gnu.org> writes:
> > I would guess that a default of t for compilation-scroll-output would be
> > better that the current default of nil, but YMMV. When I'm compiling, I
> > generally want to see progress, so I generally want Emacs to scroll the
> > window for me.
>
> Agreed,
>
> I disagree. I find that I can't read the output of compilation if it
> scrolls. Compilers are too fast these days! Now, if we could slow them
> down, maybe it would be ok to scroll the output. Any ideas?
It is frequently said that GCC is doing a good job at slowing down
compilation. I also think that at least on some platforms
process-adaptive-read-buffering has some helpful effects (it did for
tramp until tramp put in some special code temporarily nilling it).
And people say that Emacs redisplay is also getting increasingly more
helpful here.
--
David Kastrup
next prev parent reply other threads:[~2008-02-06 16:17 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
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 [this message]
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=86y79yrrdz.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=Simon.Marshall@misys.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=rms@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).