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: Sat, 14 Jul 2018 18:36:45 -0700 (PDT) [thread overview]
Message-ID: <35a57007-ee1d-41c3-b7e5-be20a3c735ec@default> (raw)
In-Reply-To: <87k1pxam2a.fsf@gmail.com>
> > I didn't suggest restoring the quotes to non-curly in Info.
>
> If you rephrase your suggestion as a patch, then we won't have to play
> guessing games.
What's to guess? I said clearly in _each_ of my posts
to this bug thread, starting with the report itself,
that it's about the use of such chars in the Lisp source
files - in particular in `info.el'.
I mentioned that I tried to `grep' to see if other Lisp
files were similarly affected, and that it seemed that
`info.el' was the only one affected at the top level
of the source-code tree, at least.
Each time, I spoke of Lisp files and of `info.el'
specifically. At no time did I talk about the presence
of curly quotes in Info buffers (we've been down that
dead-end road before).
That someone could misunderstand my message here is
not so simple, I think, but it is understandable - it
happens. But to come back after it has been made
doubly clear and suggest that I somehow made you guess
what the problem is seems a bit unfair.
I don't know what kind of patch is needed. And anyway
Eli has said that he doesn't see any reason to care
about users copy+pasting our Lisp source code. Won't
fix.
next prev parent reply other threads:[~2018-07-15 1:36 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
2018-07-14 15:12 ` Noam Postavsky
2018-07-15 1:36 ` Drew Adams [this message]
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=35a57007-ee1d-41c3-b7e5-be20a3c735ec@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).