GNU bug report logs - #24786
25.1; Misleading documentation/news for text-quoting-style

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24786 in the body.
You can then email your comments to 24786 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.1; Misleading documentation/news for text-quoting-style
Date: Mon, 24 Oct 2016 21:33:12 +0200

I've just fixed a complex Emacs Lisp program using `error' in batch mode
where messages of the "Exception: 'foo'" kind were turned into
"Exception: ‘foo’", leading to a crash in the test rig written in as it
did not expect non-ASCII output.  I find this inacceptable behavior.
Why should printing one thing print something entirely different from
what has been specified?

I've learned that there is a `text-quoting-style' variable that controls
this behavior, however both its docstring and the corresponding news
entry suggest that there is no way to disable the post-processing.  On
top of that they don't mention that the simplest way to make things look
like they previously did is to set it to `grave`.  Is there any reason
this is not documented?  More importantly, if that is the truth, why is
there no flag to disable that post-processing?

Message #8 received at 24786 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
Cc: 24786 <at> debbugs.gnu.org
Subject: Re: bug#24786: 25.1;
 Misleading documentation/news for text-quoting-style
Date: Mon, 24 Oct 2016 23:13:42 +0300

> From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
> Date: Mon, 24 Oct 2016 21:33:12 +0200
> 
> I've just fixed a complex Emacs Lisp program using `error' in batch mode
> where messages of the "Exception: 'foo'" kind were turned into
> "Exception: ‘foo’", leading to a crash in the test rig written in as it
> did not expect non-ASCII output.  I find this inacceptable behavior.
> Why should printing one thing print something entirely different from
> what has been specified?
> 
> I've learned that there is a `text-quoting-style' variable that controls
> this behavior, however both its docstring and the corresponding news
> entry suggest that there is no way to disable the post-processing.  On
> top of that they don't mention that the simplest way to make things look
> like they previously did is to set it to `grave`.  Is there any reason
> this is not documented?  More importantly, if that is the truth, why is
> there no flag to disable that post-processing?

Did you look at the state of affairs on the emacs-25 branch?  If not,
please do: I think at least some of these problems were fixed there.
If they are still not fixed, or you cannot figure out how to fix them,
please tell the details: where did you read or saw behavior that
disallows turning off the conversion of quotes.  FWIW, I see this in
the doc string:

  ‘grave’ means quote with grave accent and apostrophe `like this'.

which seems to be what you want, no?

Message #13 received at 24786-done <at> debbugs.gnu.org (full text, mbox):

From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 24786-done <at> debbugs.gnu.org
Subject: Re: bug#24786: 25.1; Misleading documentation/news for
 text-quoting-style
Date: Mon, 24 Oct 2016 23:30:31 +0200

> Did you look at the state of affairs on the emacs-25 branch?  If not,
> please do: I think at least some of these problems were fixed there.
> If they are still not fixed, or you cannot figure out how to fix them,
> please tell the details: where did you read or saw behavior that
> disallows turning off the conversion of quotes.

Thanks for the hint, I'm on Emacs 25.1 where the behavior is as
described.  As you've pointed out, 25.2 does not take
`text-quoting-style' into account for both `message' and
`format-message', additionally to that the (incompatible) change has
been documented and the docstring updated to clarify that `grave` is the
setting to disable post-processing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.