From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Sebastian Wiesner <lunaryorn@gmail.com>
Cc: emacs-devel@gnu.org
Subject: RE: Inhibit "Wrote foo" from write-region
Date: Tue, 21 Jan 2014 09:59:16 -0800 (PST) [thread overview]
Message-ID: <43c90265-e456-416e-b5f1-1e29e9d9a54e@default> (raw)
In-Reply-To: <<834n4xgu3z.fsf@gnu.org>>
> I think the conclusion was that we can add a variable that Lisp
> programs could bind, which will force write-region use 'message'.
> Then you could override that in Lisp.
That seems pretty crude. Sounds like all or nothing. Giving the
user the black & white choice, "Do you want eight zillion useless
messages or no messages at all?" sounds like a cop-out.
Why not do what we do for Dired, when you operate on marked files?
You get *one* message telling you there were errors (if any), and
if you then hit `?' a buffer pops up with all of the details. [1]
IOW, (1) inform the user if there were problems and then (2) let
the user get all the nitty gritty about those individual problems
on demand. Those details are logged separately, not in *Messages*.
Logging such information to an Emacs buffer seems like the Emacs
way, no?
[1] Yes, I know that for some Dired operations the individual
operation also logs its own little messages to *Messages*. But
for other Dired operations it does not.
next prev parent reply other threads:[~2014-01-21 17:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 12:32 Inhibit "Wrote foo" from write-region Sebastian Wiesner
2014-01-21 12:38 ` Sebastian Wiesner
2014-01-21 15:57 ` Eli Zaretskii
2014-01-21 16:31 ` Sebastian Wiesner
2014-01-21 16:47 ` Eli Zaretskii
2014-01-22 12:35 ` Sebastian Wiesner
2014-01-22 15:11 ` Stefan Monnier
2014-01-22 17:00 ` Sebastian Wiesner
[not found] ` <<834n4xgu3z.fsf@gnu.org>
2014-01-21 17:59 ` Drew Adams [this message]
2014-01-21 18:26 ` Eli Zaretskii
2014-01-22 8:05 ` Juri Linkov
2014-01-21 16:42 ` Tom Tromey
2014-01-22 12:37 ` Sebastian Wiesner
2014-01-22 15:09 ` Stefan Monnier
2014-01-22 17:08 ` Sebastian Wiesner
2014-01-22 19:20 ` Stefan Monnier
2014-01-23 9:35 ` Sebastian Wiesner
2014-01-23 13:50 ` Stefan Monnier
2014-01-23 14:24 ` Sebastian Wiesner
2014-01-23 15:18 ` Stefan Monnier
2014-01-23 16:15 ` Sebastian Wiesner
2014-01-23 16:29 ` Eli Zaretskii
2014-01-23 17:31 ` Sebastian Wiesner
2014-01-23 18:04 ` Eli Zaretskii
2014-01-24 20:14 ` Sebastian Wiesner
2014-01-23 16:25 ` Eli Zaretskii
2014-01-23 17:37 ` Sebastian Wiesner
2014-01-23 18:07 ` Eli Zaretskii
2014-01-24 13:34 ` Johan Andersson
2014-01-24 13:48 ` Stefan Monnier
2014-01-24 14:25 ` Eli Zaretskii
[not found] <"<m2r481o6rh.fsf"@lunaryorn-air.fritz.box>
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43c90265-e456-416e-b5f1-1e29e9d9a54e@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lunaryorn@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.