unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 7565@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#7565: 24.0.50; "Buffer ... modified; kill anyway?" doesn't end up in *Messages*
Date: Mon, 14 Oct 2019 03:19:14 +0200	[thread overview]
Message-ID: <87eezgt97x.fsf@gnus.org> (raw)
In-Reply-To: <m34nuiykfi.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 22 Feb 2012 16:09:05 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Glenn Morris <rgm@gnu.org> writes:
>
>> It is an interactive query. Did you type "yes" without reading it?
>
> I sometimes forget.  And then I look in the *Messages* buffer, and am
> disappointed that it's not there...

I wondered where the yes-or-no-p prompt happened, and it's in the bowels
of read_minibuf, and it's this:

    /* Insert the prompt, record where it ends.  */
    Finsert (1, &minibuf_prompt);

So if we want to do this, it probably makes sense to put absolutely all
minibuffer prompts into the *Messages* buffer.

And that's actually something I can see the charm in doing, but I'm not
quite sure that the use case is compelling.  Dan mentions

> Probably so one has a way of putting the message into a bug report if needed.

but you can do that by just going to the beginning of the minibuffer and
copying the text there.

Does anybody have an opinion here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-14  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 16:17 bug#7565: 24.0.50; "Buffer ... modified; kill anyway?" doesn't end up in *Messages* jidanni
2012-02-22  4:09 ` Glenn Morris
2012-02-22 15:09   ` Lars Magne Ingebrigtsen
2019-10-14  1:19     ` Lars Ingebrigtsen [this message]
2020-08-07 10:40       ` Lars Ingebrigtsen
2020-08-09  5:56         ` 積丹尼 Dan Jacobson
2012-02-22  4:16 ` jidanni

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=87eezgt97x.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=7565@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=rgm@gnu.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://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).