all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 38645@debbugs.gnu.org
Subject: bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown
Date: Fri, 27 Dec 2019 12:29:56 +0200	[thread overview]
Message-ID: <83k16ioycb.fsf@gnu.org> (raw)
In-Reply-To: <f1bdec72-3091-1ba0-dcd6-641afecde81b@gmx.at> (message from martin rudalics on Fri, 27 Dec 2019 10:46:57 +0100)

> Cc: ynyaaa@gmail.com, 38645@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Fri, 27 Dec 2019 10:46:57 +0100
> 
>  >> martin, who just noted that the recently added (to master)
>  >>
>  >>         Lisp_Object str = build_string ("Command attempted to use minibuffer"
>  >>                                         "while in minibuffer");
>  >>
>  >> produces
>  >>
>  >> "Command attempted to use minibufferwhile in minibuffer"
>  >
>  > Hope you've already fixed it.
> 
> I cannot reliably push these days.

OK, pushed.





  reply	other threads:[~2019-12-27 10:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  6:49 bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown ynyaaa
2019-12-17  7:41 ` Eli Zaretskii
2019-12-17 11:55 ` ynyaaa
2019-12-17 12:07   ` Eli Zaretskii
2019-12-18 10:52     ` ynyaaa
2019-12-18 16:31       ` Eli Zaretskii
2019-12-20  2:16         ` ynyaaa
2019-12-26 20:49           ` Eli Zaretskii
2019-12-27  9:12             ` martin rudalics
2019-12-27  9:21               ` Eli Zaretskii
2019-12-27  9:46                 ` martin rudalics
2019-12-27 10:29                   ` Eli Zaretskii [this message]
2019-12-29 14:15               ` Eli Zaretskii
2019-12-29 18:33                 ` martin rudalics
2019-12-29 18:50                   ` Eli Zaretskii
2019-12-29 19:30                     ` martin rudalics
2019-12-30 16:07                       ` Eli Zaretskii

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=83k16ioycb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38645@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.