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 12:19:03 -0700 [thread overview]
Message-ID: <0ECB696350BF4BF189E9B1F3ABF29572@us.oracle.com> (raw)
In-Reply-To: <83ehs8k364.fsf@gnu.org>
> > > > wouldn't it be possible to just use multiple menu lines...
> > >
> > > Not if we reuse the normal menu-creation code...
> >
> > It certainly would be possible (trivial) in Lisp: just
> > split the string at each \n and create a separate
> > (non-selectable) menu item for each.
>
> But the same code is used for a real menu, where we don't want to
> create two separate menu items for a line with embedded newline.
Sorry, I don't follow you - don't know what you mean.
What I'm saying is that (in Lisp, at least) it would be possible to create a
menu here that had one non-selectable menu item (line) for each line of the
multiline input (as split by \n), plus a selectable final line for the `OK'
action.
Not sure what you intend by a "real" menu, but it is certainly possible (in Lisp
at least) to create a menu with N non-selectable menu items followed by one
selectable item. Such a menu is as real as any other I've come across.
next prev parent reply other threads:[~2012-03-31 19:19 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 [this message]
2012-03-31 19:26 ` Eli Zaretskii
2012-03-31 21:29 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0ECB696350BF4BF189E9B1F3ABF29572@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 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.