From: David Bremner <david@tethera.net>
To: Mark Walters <markwalters1009@gmail.com>,
Austin Clements <amdragon@MIT.EDU>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: tweak error buffer handling
Date: Fri, 28 Dec 2012 08:44:43 -0400 [thread overview]
Message-ID: <87wqw2pcqs.fsf@zancas.localnet> (raw)
In-Reply-To: <87ip7my2er.fsf@qmul.ac.uk>
Mark Walters <markwalters1009@gmail.com> writes:
> Austin Clements <amdragon@MIT.EDU> writes:
>> How about showing all errors in the minibuffer (which could simply
>> mean calling (error ...) and letting the Emacs top-level show it in
>> the mini-buffer)? We could log the verbose error details (like
>> stdout) to some other buffer that we don't automatically show, but
>> instead simply reference from the minibuffer message
>
> That sounds great. In an ideal world we could behave slightly
> differently for fatal errors but the common errors are likely to be
> transient (locked database errors) so getting these right (which this
> would do) seems the important step.
>
> My view is that we should push a fix like the above for 0.15. What do
> other people think?
Sounds reasonable. I have to admit the new reporting is a bit annoying
for transient messages.
d
next prev parent reply other threads:[~2012-12-28 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 20:49 [PATCH] emacs: tweak error buffer handling Mark Walters
2012-12-25 21:05 ` Tomi Ollila
2012-12-26 22:27 ` Mark Walters
2012-12-27 23:04 ` Austin Clements
2012-12-28 9:03 ` Mark Walters
2012-12-28 12:44 ` David Bremner [this message]
2012-12-28 19:48 ` [PATCH] emacs: Use the minibuffer for CLI error reporting Austin Clements
2012-12-29 18:00 ` Mark Walters
2013-01-03 0:44 ` Austin Clements
2013-01-03 23:21 ` David Bremner
2013-01-03 0:50 ` [PATCH v2] " Austin Clements
2013-01-03 21:47 ` [PATCH v3] " Austin Clements
2013-01-03 22:48 ` Mark Walters
2013-01-06 21:12 ` Austin Clements
2013-01-05 21:33 ` Tomi Ollila
2013-01-07 2:54 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqw2pcqs.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=amdragon@MIT.EDU \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).