From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31815@debbugs.gnu.org
Subject: bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'
Date: Fri, 13 Jul 2018 09:28:31 -0700 (PDT) [thread overview]
Message-ID: <d85071fb-1d33-4066-9122-269995475885@default> (raw)
In-Reply-To: <CAM-tV-_cz_j=aTy9EPxyh8dCjT5UR-wbNXvmT6SezWAcx1HJuA@mail.gmail.com>
> > I just got a copy of the control msg for this bug, saying
> > that it has been closed (I haven't received the usual help
> > msg for the bug filer saying that it was closed, however.)
>
> Perhaps you misread the control message? I set the bug to severity
> minor and tagged it notabug (to summarize Eli's response, which I
> basically agree with), but I didn't close it, and looking at...,
> it is not closed.
I see; thanks. I didn't (still don't) understand the difference
between `notabug' and `closed'. Is it wrong to assume that it
will be closed if it is not a bug?
> > The bug report was about the occurrence of such curly quotes
> > in the Lisp sources (`info.el'), not about their appearance
> > in Info files. So your reply does not make sense to me.
>
> The curly quotes in the source are there to produce curly quotes in
> Info buffers. We want to produce curly quotes in info buffers to match
> the rest of the buffer content which comes from Info files which have
> curly quotes in them. Your suggestion to restore the ascii quotes
> would produce a buffer of mixed quoting styles.
I didn't suggest restoring the quotes to non-curly in Info.
[Though I would like it for users to be able to control
whether Info uses curly quotes. We've been through that
before: Apparently Texinfo doesn't give us a choice here,
so, for example, option ` text-quoting-style' has no
effect on Info. Too bad, but not everything is as
flexible for users as is Emacs.]
I suggested restoring them in the Lisp source files, not
in Info buffers. The source files need not use the chars
literally to produce them for Info, AFAIK.
---
To be clear: I'm not even sure just what copy+paste gotcha
I stumbled upon, when trying to report bug #31807. I think
that other times I've been able to copy+paste such chars
into bug reports, without a problem of any kind of unexpected
conversion. See that bug thread for more info, maybe.
next prev parent reply other threads:[~2018-07-13 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4cce0ca1-f9d1-41cb-a2a2-e54464aa2626@default>
[not found] ` <<83po0t33r3.fsf@gnu.org>
2018-07-13 15:57 ` bug#31815: 27.0; Inappropriate use of curly quotes in `info.el' Drew Adams
2018-07-13 16:15 ` Noam Postavsky
2018-07-13 16:28 ` Drew Adams [this message]
2018-07-14 15:12 ` Noam Postavsky
2018-07-15 1:36 ` Drew Adams
2018-07-15 21:28 ` Noam Postavsky
2018-07-15 22:09 ` Drew Adams
2018-07-16 14:03 ` Noam Postavsky
2018-07-16 14:12 ` Drew Adams
2018-07-13 17:27 ` Eli Zaretskii
2018-07-13 17:51 ` Drew Adams
2018-07-13 18:44 ` Eli Zaretskii
2018-06-13 17:31 Drew Adams
2018-06-14 13:18 ` 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=d85071fb-1d33-4066-9122-269995475885@default \
--to=drew.adams@oracle.com \
--cc=31815@debbugs.gnu.org \
--cc=npostavs@gmail.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 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).