unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: bug in save-some-buffers or diff.el?
Date: 23 Oct 2003 08:06:39 +0200	[thread overview]
Message-ID: <ufzhka3o0.fsf@elta.co.il> (raw)
In-Reply-To: <874qy08shp.fsf@mail.jurta.org> (message from Juri Linkov on 23 Oct 2003 07:53:22 +0300)

> From: Juri Linkov <juri@jurta.org>
> Date: 23 Oct 2003 07:53:22 +0300
> 
> Anyhow, I'm just trying to find the solution to the real problem about
> warnings that go unnoticed because they become overwritten by the
> new messages in the minibuffer.

My personal imperfect solution is to watch closely the echo area, and
if I see any message(s) flash by that I didn't expect, I look them up
later in the *Messages* buffer.

For messages about *.el files being newer than the corresponding .elc,
perhaps we could add an option to sit-for 2 seconds after displaying
each such message.  It should be off by default, of course.

  reply	other threads:[~2003-10-23  6:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22  0:07 bug in save-some-buffers or diff.el? David Abrahams
2003-10-22  8:38 ` Juri Linkov
2003-10-22  9:35   ` David Abrahams
2003-10-22 12:52     ` Stefan Monnier
2003-10-22 15:22       ` David Abrahams
2003-10-22 14:35     ` Juri Linkov
2003-10-22 16:28       ` David Abrahams
2003-10-22 16:34       ` Kevin Rodgers
2003-10-22 17:52         ` Eli Zaretskii
2003-10-23  4:53           ` Juri Linkov
2003-10-23  6:06             ` Eli Zaretskii [this message]
2003-10-23  8:00               ` Juri Linkov
2003-10-24 14:52                 ` Eli Zaretskii
2003-10-23 18:38       ` Richard Stallman
2003-10-23 19:47         ` David Abrahams
2003-10-24 10:41           ` Richard Stallman
2003-10-27 17:44             ` emacshear (was: bug in save-some-buffers or diff.el?) Juri Linkov

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=ufzhka3o0.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --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 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).