From: "Davis Herring" <herring@lanl.gov>
To: rms@gnu.org
Cc: emacs-devel@gnu.org, roland.winkler@physik.uni-erlangen.de
Subject: Re: messages override minibuffer input
Date: Wed, 12 Sep 2007 15:32:04 -0700 (PDT) [thread overview]
Message-ID: <43404.128.165.123.18.1189636324.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <E1IVCNc-0000eU-J4@fencepost.gnu.org>
> Can you look for places in the sources where it would be right to use
> `optional-message'? If you find many, then the function would be a good
> feature.
Places where `optional-message' might be useful:
autorevert.el, in `auto-revert-handler'
desktop.el, in `desktop-idle-create-buffers'
help-at-pt.el: see approximate reimplementation in `help-at-pt-maybe-display'
speedbar.el, in `speedbar-timer-fn'
emacs-lisp/eldoc.el, in `eldoc-message', perhaps to replace
`eldoc-display-message-no-interference-p'
perhaps erc/erc-backend.el, in the PRIVMSG response handler
perhaps erc/erc-notify.el, in `erc-notify-timer'
gnus/mm-decode.el, in the process sentinels in `mm-display-external'
gnus/nntp.el, in `nntp-accept-process-output'
progmodes/cperl-mode.el, in `cperl-get-help'
progmodes/idlwave.el, in `idlwave-load-rinfo-next-step'
progmodes/vhdl-mode.el, in `vhdl-print-warnings'
textmodes/reftex-dcr.el: see approximate reimplementation in
`reftex-view-crossref-when-idle'
emacs-lock.el, in `emacs-lock-clear-sentinel'
find-dired.el, in `find-dired-sentinel'
man.el, in `Man-notify-when-ready'
pcvs.el, in `cvs-sentinel'
vc-arch.el, in the lambdas created in `vc-arch-trim-make-sentinel'
eshell/esh-proc.el, in `eshell-remove-process-entry'
progmodes/sql.el, in `sql-stop'
perhaps progmodes/xscheme.el, in `xscheme-process-sentinel'
url/url.el: see approximate reimplementation in `url-lazy-message'
I just checked lisp/; I do not think very much asynchronous messaging
occurs in src/.
> You can write Lisp code to do the same things now done at C level. We
> could also turn that C code into a subr, if that is useful.
True, but how should client code request it? I can't add an optional
argument to `optional-message' and have it work like `message' now, of
course.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2007-09-12 22:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 4:23 messages override minibuffer input Roland Winkler
2007-09-08 14:48 ` Stefan Monnier
2007-09-10 21:41 ` Davis Herring
2007-09-11 20:30 ` Richard Stallman
2007-09-12 22:32 ` Davis Herring [this message]
2007-09-13 3:23 ` Luc Teirlinck
2007-09-13 4:23 ` Davis Herring
2007-09-14 7:05 ` Richard Stallman
2007-09-12 9:25 ` Johannes Weiner
2007-09-12 10:24 ` Johannes Weiner
2007-09-12 16:25 ` Davis Herring
2007-09-12 16:28 ` Davis Herring
[not found] ` <E1IUCJ9-0000VV-9H@fencepost.gnu.org>
2007-09-16 3:23 ` Roland Winkler
2007-09-17 0:20 ` Richard Stallman
2007-09-17 14:49 ` Roland Winkler
2007-09-17 22:24 ` Richard Stallman
2007-09-22 15:18 ` Roland Winkler
2007-09-23 9:07 ` Richard Stallman
2007-09-23 15:08 ` Roland Winkler
2007-09-23 21:54 ` Richard Stallman
2007-09-23 23:33 ` Roland Winkler
2007-09-24 18:19 ` Richard Stallman
2007-09-25 1:06 ` Roland Winkler
2007-09-24 0:24 ` Drew Adams
2007-09-24 1:28 ` Roland Winkler
2007-09-24 2:02 ` Drew Adams
2007-09-24 3:20 ` Roland Winkler
2007-09-24 10:36 ` Robert J. Chassell
2007-09-24 15:08 ` Drew Adams
2007-09-24 16:11 ` Robert J. Chassell
2007-09-24 16:53 ` Drew Adams
2007-09-24 10:43 ` Johannes Weiner
2007-09-24 11:12 ` David Kastrup
2007-09-24 13:19 ` Johannes Weiner
2007-09-24 14:48 ` Roland Winkler
2007-09-25 10:44 ` Richard Stallman
2007-09-24 15:13 ` Drew Adams
2007-09-25 10:43 ` Richard Stallman
2007-09-17 22:31 ` Davis Herring
2007-09-18 0:53 ` Stefan Monnier
2007-09-23 21:55 ` Richard Stallman
2007-09-24 8:30 ` Stefan Monnier
2007-09-24 17:16 ` Davis Herring
2007-09-24 17:24 ` Drew Adams
2007-09-25 10:44 ` 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=43404.128.165.123.18.1189636324.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=roland.winkler@physik.uni-erlangen.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).