unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>,
	"'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 3312@debbugs.gnu.org
Subject: bug#3312: 23.0.93; Use punctuation syntax for apostrophe in Info
Date: Sat, 17 Sep 2011 07:41:23 -0700	[thread overview]
Message-ID: <8A73A99C9B5B4324A7561AF5CB0D3875@us.oracle.com> (raw)
In-Reply-To: <87d3ezic3v.fsf@mail.jurta.org>

> I see that Gnus solves this problem by modifying syntax of ' and `
> to whitespace...
> So I'm not sure what is better for Info buffers:
> whitespace syntax (" ") or punctuation (".")?

Either is probably OK.  I would vote for punctuation syntax for ` and ',
especially since they are used not only for `...' but also in Lisp code, and
since they are, in English, punctuation.

[We do have embedded spaces in `...' in the manuals (e.g., search for regexp
`\([a-zA-Z]+ \)+[a-zA-Z]+' in (elisp)).  But either whitespace or punctuation
syntax for `' would be OK for that, since you could in either case get all of
the text easily by clicking the mouse (e.g. double-click mouse-1, then click
mouse-3).]






  reply	other threads:[~2011-09-17 14:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 22:02 bug#3312: 23.0.93; Use punctuation syntax for apostrophe in Info Drew Adams
2009-05-17 14:50 ` Kevin Rodgers
2009-05-17 15:59   ` Drew Adams
2009-05-17 18:59 ` Juri Linkov
2009-05-17 20:01   ` Eli Zaretskii
2009-05-17 20:03   ` Drew Adams
2009-05-17 19:29 ` Stefan Monnier
2009-05-17 20:08   ` Drew Adams
2009-05-19  0:47   ` Juri Linkov
2009-05-19  3:09     ` Drew Adams
2009-06-08 17:34       ` Drew Adams
2011-09-16 21:12     ` Lars Magne Ingebrigtsen
2011-09-17 12:31       ` Juri Linkov
2011-09-17 14:41         ` Drew Adams [this message]
2011-09-18  7:51         ` Lars Magne Ingebrigtsen
2011-09-18 19:57   ` Juri Linkov

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=8A73A99C9B5B4324A7561AF5CB0D3875@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=3312@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=larsi@gnus.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).