From: Eli Zaretskii <eliz@gnu.org>
To: 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 20:27:04 +0300 [thread overview]
Message-ID: <83d0vrcahj.fsf@gnu.org> (raw)
In-Reply-To: <80f28e80-65fa-439e-b313-5ad616ef0dbd@default> (message from Drew Adams on Fri, 13 Jul 2018 08:57:03 -0700 (PDT))
> Date: Fri, 13 Jul 2018 08:57:03 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 31815@debbugs.gnu.org
>
> 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.
Why do you care about what is in the Lisp sources? The Lisp sources
do whatever they need to do to produce appropriate contents in the
buffer they create.
> 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
Using these characters does have its downsides, so we use them as
little as possible in the sources.
next prev parent reply other threads:[~2018-07-13 17:27 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d0vrcahj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31815@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.