From: Andreas Schwab <schwab@linux-m68k.org>
To: npostavs@users.sourceforge.net
Cc: 354@debbugs.gnu.org, eggert@cs.ucla.edu, kb1vqh@gmail.com
Subject: bug#354: "Added (how many lines, bytes?!) to file.txt"
Date: Sun, 02 Apr 2017 08:16:02 +0200 [thread overview]
Message-ID: <871stb1gil.fsf@linux-m68k.org> (raw)
In-Reply-To: <87shlrxy2e.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Sat, 01 Apr 2017 23:55:53 -0400")
On Apr 01 2017, npostavs@users.sourceforge.net wrote:
> diff --git a/src/xdisp.c b/src/xdisp.c
> index 9ecfb86401..8ff291affb 100644
> --- a/src/xdisp.c
> +++ b/src/xdisp.c
> @@ -10470,9 +10470,12 @@ message_with_string (const char *m, Lisp_Object string, bool log)
> /* Dump an informative message to the minibuf. If M is 0, clear out
> any existing message, and let the mini-buffer text show through.
>
> - The message must be safe ASCII and the format must not contain ` or
> - '. If your message and format do not fit into this category,
> - convert your arguments to Lisp objects and use Fmessage instead. */
> + The message must be safe ASCII (because when Emacs is
> + non-interactive the message is sent straight to stderr without
> + encoding first) and the format must not contain ` or ' (because
> + this function does not account for `text-quoting-style'. If your
> + message and format do not fit into this category, convert your
> + arguments to Lisp objects and use Fmessage instead. */
Missing a close paren.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-04-02 6:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 18:37 bug#354: "Added (how many lines, bytes?!) to file.txt" jidanni
2008-06-03 21:07 ` Stefan Monnier
2008-06-06 4:02 ` Kevin Rodgers
2008-06-06 14:56 ` Drew Adams
2015-02-27 7:21 ` Paul Eggert
2015-02-27 13:52 ` Jeff Clough
2017-03-14 0:58 ` npostavs
2017-03-14 15:55 ` Eli Zaretskii
2017-04-01 4:27 ` npostavs
2017-04-01 6:09 ` Eli Zaretskii
2017-04-02 3:55 ` npostavs
2017-04-02 6:16 ` Andreas Schwab [this message]
2017-04-02 16:10 ` npostavs
2017-04-02 15:52 ` Eli Zaretskii
2017-04-02 18:24 ` Paul Eggert
2017-04-02 18:40 ` npostavs
2017-04-02 18:44 ` Paul Eggert
2017-04-02 19:09 ` npostavs
2017-04-07 2:27 ` npostavs
2017-04-10 2:17 ` npostavs
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=871stb1gil.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=354@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=kb1vqh@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).