unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 11138@debbugs.gnu.org, dpchiesa@hotmail.com
Subject: bug#11138: 23.3; on Windows, message-box does not display line breaks in the message
Date: Sat, 31 Mar 2012 14:29:31 -0700	[thread overview]
Message-ID: <D14976F3A53B48BF8EBEA1226D5D52CC@us.oracle.com> (raw)
In-Reply-To: <83d37sk1wa.fsf@gnu.org>

> What I mean is that message-box on Windows eventually calls
> x-popup-menu.  So whatever you do for multi-line messages inside
> x-popup-menu will also affect x-popup-menu calls that want to display
> menus as well.

I would not suggest changing `x-popup-menu'.  My suggestion was to have
`message-box' call `x-popup-menu' (or other code to create the menu) passing
multiple menu lines, all of which, except the last one ("OK"), are
non-selectable.

The multiple lines come from splitting, at each \n, the result of applying
FORMAT-STRING to ARGS.

(BTW, I do not have the Emacs 24 C code, but in Emacs 23.3 it looks like
`message-box' calls `x-popup-dialog', not `x-popup-menu'.  Same idea, anyway.)






  reply	other threads:[~2012-03-31 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 14:53 bug#11138: 23.3; on Windows, message-box does not display line breaks in the message Dino Chiesa
2012-03-31 15:26 ` Drew Adams
2012-03-31 18:06   ` Eli Zaretskii
2012-03-31 18:14     ` Drew Adams
2012-03-31 18:30       ` Eli Zaretskii
2012-03-31 18:37         ` Drew Adams
2012-03-31 18:58           ` Eli Zaretskii
2012-03-31 19:19             ` Drew Adams
2012-03-31 19:26               ` Eli Zaretskii
2012-03-31 21:29                 ` Drew Adams [this message]
2012-04-01  3:00                   ` Eli Zaretskii
2012-03-31 19:10     ` Stefan Monnier
2012-03-31 19:19       ` Drew Adams
2012-03-31 21:36     ` Juanma Barranquero
2012-04-01 16:58       ` 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

  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=D14976F3A53B48BF8EBEA1226D5D52CC@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=11138@debbugs.gnu.org \
    --cc=dpchiesa@hotmail.com \
    --cc=eliz@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).