unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 15 Jul 2018 15:09:25 -0700 (PDT)	[thread overview]
Message-ID: <4f6094d3-9054-4ba2-a35e-c12c68bd9edf@default> (raw)
In-Reply-To: <878t6c9ojp.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'.
> 
> In the OP you said
>     They were all changed from this text:
>       Index for `%s'
>     The latter text should be restored.
> 
> Which would affect the text in Info buffers (because it's the argument
> to an `insert' call which is evaluated in an Info buffer).  I'm not sure
> if you are just ignoring the effect of the change you propose, or you
> have some additional changes in mind.

I've said multiple times, very clearly, that the _bug_, the
problem for users that is reported, is the presences of
curly quotes in Lisp source code.  It can make it difficult
for users who copy+paste such Lisp code.  And that statement
too is about curly quotes in Lisp source code.

The point is to not have those quotes in the Lisp source
code.  That does not imply that they cannot appear in Info.

Yes, technically, if "the latter text" is simply "restored"
then the Info text would be affected.

But that's not the point of the bug, as the context and the
several other mails in the thread all make clear, repeatedly.

There are other ways to get the effect of curly quotes in
Info than to insert that literal text.  It is clear from
the context that I was not proposing that only restoring
the exact same text in the Lisp code is an acceptable fix.

The point of a bug report is to state the problem, not to
prescribe a particular solution, and certainly not to claim
that there is only one possible solution.

The point of that text, which I think you should (and do?)
realize, is that the curly quotes should be removed from
the Lisp code.  Nothing more, nothing less.

I corrected a misinterpretation more than once in this
thread.  It's simply not about curly quotes in Info.
And it could not be, given that it has been stated that
Emacs has no control over the appearance of curly quotes
in Info (alas).

> > 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.
> 
> Okay.

Not okay; too bad.





  reply	other threads:[~2018-07-15 22:09 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 [this message]
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=4f6094d3-9054-4ba2-a35e-c12c68bd9edf@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).