From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14730-done@debbugs.gnu.org
Subject: bug#14730: 24.3.50; post-command-hook errors no longer in *Messages*
Date: Thu, 27 Jun 2013 09:46:15 -0700 (PDT) [thread overview]
Message-ID: <bf7f7fb5-4496-4a70-8074-b6c18b551b8d@default> (raw)
In-Reply-To: <jwva9mb5xe3.fsf-monnier+emacs@gnu.org>
> > I am not sure, but it seems like there has been a change so that errors
> > in post-command-hook no longer get logged in *Messages*.
>
> Not that I know.
Does you mean that you think such errors do get logged to *Messages*
or that they have never been logged there? Which kind of "no change"
do you mean?
prev parent reply other threads:[~2013-06-27 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:20 bug#14730: 24.3.50; post-command-hook errors no longer in *Messages* Drew Adams
2013-06-27 16:31 ` Stefan Monnier
2013-06-27 16:46 ` Drew Adams [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://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=bf7f7fb5-4496-4a70-8074-b6c18b551b8d@default \
--to=drew.adams@oracle.com \
--cc=14730-done@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).