From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: luangruo@yahoo.com, 20481@debbugs.gnu.org
Subject: bug#20481: 24.5; , Newlines in message-box output don't work on Windows
Date: Sat, 14 Sep 2024 14:00:46 +0300 [thread overview]
Message-ID: <86bk0qh541.fsf@gnu.org> (raw)
In-Reply-To: <9256c296-a719-4147-b994-f6b6427e8671@imayhem.com> (message from Cecilio Pardo on Thu, 12 Sep 2024 15:33:23 +0200)
> Date: Thu, 12 Sep 2024 15:33:23 +0200
> From: Cecilio Pardo <cpardo@imayhem.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 20481@debbugs.gnu.org
>
> On 12/09/2024 4:49, Po Lu wrote:
> > Thanks. Following are a number of minor stylistic comments.
>
> Sorry I missed those. They are corrected in the attached patch.
Thanks, now installed on the master branch (which will become Emacs 31).
FTR, I needed some additions because mingw.org's MinGW lacks some
stuff in its headers that the code used. Please see that the result
still compiles with MinGW64.
next prev parent reply other threads:[~2024-09-14 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 3:18 bug#20481: 24.5; Newlines in message-box output don't work on Windows Adam Connor
2015-05-01 7:19 ` Eli Zaretskii
[not found] ` <CAC_vAoGvLFr--qNihU+MDpyZPhZEysz02hCOOWVE4otubmRJWg@mail.gmail.com>
2015-05-02 6:33 ` Eli Zaretskii
2024-08-19 16:13 ` bug#20481: 24.5; , " Cecilio Pardo
2024-08-19 17:44 ` Eli Zaretskii
2024-08-19 19:20 ` Cecilio Pardo
2024-09-11 13:44 ` Cecilio Pardo
2024-09-12 2:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-12 13:33 ` Cecilio Pardo
2024-09-14 11:00 ` Eli Zaretskii [this message]
[not found] ` <28906c5b-0ff1-49a7-990b-50ad95235be2@imayhem.com>
2024-09-14 15:19 ` Eli Zaretskii
2024-09-14 12:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 12:17 ` Eli Zaretskii
2024-09-14 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 14:14 ` 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=86bk0qh541.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20481@debbugs.gnu.org \
--cc=cpardo@imayhem.com \
--cc=luangruo@yahoo.com \
/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.