From: David Bremner <david@tethera.net>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH v3] emacs: Use the minibuffer for CLI error reporting
Date: Sun, 06 Jan 2013 22:54:16 -0400 [thread overview]
Message-ID: <87ip79r9d3.fsf@zancas.localnet> (raw)
In-Reply-To: <1357249669-9706-1-git-send-email-amdragon@mit.edu>
Austin Clements <amdragon@MIT.EDU> writes:
> We recently switched to popping up a buffer to report CLI errors, but
> this was too intrusive, especially for transient errors and especially
> since we made fewer things ignore errors. This patch changes this to
> display a basic error message in the minibuffer (using Emacs' usual
> error handling path) and, if there are additional details, to log
> these to a separate error buffer and reference the error buffer from
> the minibuffer message. This is more in line with how Emacs typically
> handles errors, but makes the details available to the user without
> flooding them with the details.
pushed.
d
prev parent reply other threads:[~2013-01-07 2:54 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
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 [this message]
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=87ip79r9d3.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=amdragon@MIT.EDU \
--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).