From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 31815@debbugs.gnu.org
Subject: bug#31815: 27.0; Inappropriate use of curly quotes in `info.el'
Date: Fri, 13 Jul 2018 08:57:03 -0700 (PDT) [thread overview]
Message-ID: <80f28e80-65fa-439e-b313-5ad616ef0dbd@default> (raw)
In-Reply-To: <<83po0t33r3.fsf@gnu.org>>
> > In `info.el' there are three occurrences of this (these are curly
> > quotes, in case that doesn't come through in the bug-report system):
> >
> > Index for '%s'
> >
> > They were all changed from this text:
> >
> > Index for `%s'
> >
> > The latter text should be restored.
>
> I don't understand what's so special in these 3 occurrences.
> Info
^^^^
> buffers are full of curly quotes; the commands that use the above
> generate Info buffers from portions of other Info buffers, and add a
> header line. So why should the header lines use different style of
> quotes from the rest of the buffer?
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.)
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.
I don't know an easy way to find all such occurrences in the
Lisp sources, since such chars cannot be searched for using
the `grep' I have. There may well be other occurrences,
in subdirs of dir `lisp/'.
Bug #31807 has additional information about why this is
problematic: in some contexts one cannot easily copy+paste
source code that contains such chars. In bug #31807 I
describe how I was bitten by this when trying to submit
a bug report.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31807#20
next parent reply other threads:[~2018-07-13 15:57 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 ` Drew Adams [this message]
2018-07-13 16:15 ` bug#31815: 27.0; Inappropriate use of curly quotes in `info.el' Noam Postavsky
2018-07-13 16:28 ` Drew Adams
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=80f28e80-65fa-439e-b313-5ad616ef0dbd@default \
--to=drew.adams@oracle.com \
--cc=31815@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).