From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
<21@emacsbugs.donarmstrong.com>
Cc: emacs-devel@gnu.org
Subject: bug#21: Scrolling occasionally stops in *compilation*
Date: Tue, 10 Jun 2008 12:47:55 -0700 [thread overview]
Message-ID: <006d01c8cb32$e0d073e0$0200a8c0__795.238643377338$1213128504$gmane$org@us.oracle.com> (raw)
In-Reply-To: <jwvej75ru6o.fsf-monnier+emacsbugreports@gnu.org>
I think this is the kind of thing Richard was trying to say should not be sent
to the entire universe.
This mail, like many others that are similar, means nothing to me. I didn't file
this bug. I wasn't even aware of it. I'm still not aware of it, by mail - except
for this cryptic message.
Please try to focus the send list for this kind of thing.
> From: Stefan Monnier
> Sent: Tuesday, June 10, 2008 12:02 PM
> To: 21@emacsbugs.donarmstrong.com
> Subject: bug#21: Scrolling occasionally stops in *compilation*
>
> If you can try the Emacs-CVS trunk, I've installed a change there that
> might have fixed your problem.
>
>
> Stefan
next prev parent reply other threads:[~2008-06-10 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:02 bug#21: Scrolling occasionally stops in *compilation* Stefan Monnier
2008-06-10 19:47 ` Drew Adams [this message]
[not found] ` <mailman.13010.1213128432.18990.bug-gnu-emacs@gnu.org>
2008-06-11 10:23 ` Joe Wells
2008-06-11 13:28 ` Drew Adams
2008-06-11 17:45 ` Richard M Stallman
2008-06-11 18:50 ` Don Armstrong
2008-06-11 19:14 ` which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Joe Wells
2008-06-11 21:42 ` which bug messages should be sent where? Jason Rumney
2008-06-15 17:55 ` bug#388: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Richard M Stallman
2010-03-17 16:12 ` bug#21: Scrolling occasionally stops in *compilation* Glenn Morris
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='006d01c8cb32$e0d073e0$0200a8c0__795.238643377338$1213128504$gmane$org@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=21@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).