all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 14 Jun 2018 16:18:56 +0300	[thread overview]
Message-ID: <83po0t33r3.fsf@gnu.org> (raw)
In-Reply-To: <4cce0ca1-f9d1-41cb-a2a2-e54464aa2626@default> (message from Drew Adams on Wed, 13 Jun 2018 10:31:00 -0700 (PDT))

> Date: Wed, 13 Jun 2018 10:31:00 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> 
> 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?





  reply	other threads:[~2018-06-14 13:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 17:31 bug#31815: 27.0; Inappropriate use of curly quotes in `info.el' Drew Adams
2018-06-14 13:18 ` Eli Zaretskii [this message]
     [not found] <<4cce0ca1-f9d1-41cb-a2a2-e54464aa2626@default>
     [not found] ` <<83po0t33r3.fsf@gnu.org>
2018-07-13 15:57   ` 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
2018-07-13 17:51       ` Drew Adams
2018-07-13 18:44         ` 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=83po0t33r3.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.