unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Gutov <dgutov@yandex.ru>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 9d35bb8: Fix minor quoting problems in doc strings
Date: Tue, 19 May 2015 19:49:01 -0700	[thread overview]
Message-ID: <555BF61D.40202@cs.ucla.edu> (raw)
In-Reply-To: <555BF326.1060504@yandex.ru>

>>    This is like `(let ((v ,EXP)) ,EXPS) except that `v' is a new generated

> If we're sure that quotes will be paired

Although the quotes that we want to curl are paired, there are other stray grave 
accents and apostrophes that we shouldn't curl.

> the above example is simply missing a ' after the closing paren.

Are you sure?  The first grave accent looks like a quasiquote, so there 
shouldn't be a closing apostrophe.  Those commas are clues that it's a quasiquote.

Here's my current draft regexp to catch the quotations we want to curl:

   `\\([^[:space:]'`‘’][^'`‘’]*\\)?'

A bit tricky, but could be worse.  Newlines are allowed, as some doc strings 
break these quotes across line boundaries (e.g., info node references).



  parent reply	other threads:[~2015-05-20  2:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150519220123.30678.22605@vcs.savannah.gnu.org>
     [not found] ` <E1YupZj-000803-T3@vcs.savannah.gnu.org>
2015-05-19 22:30   ` [Emacs-diffs] master 9d35bb8: Fix minor quoting problems in doc strings Dmitry Gutov
2015-05-19 23:18     ` Paul Eggert
2015-05-20  1:16       ` Dmitry Gutov
2015-05-20  2:14         ` Paul Eggert
2015-05-20  2:36           ` Dmitry Gutov
2015-05-20  2:45             ` Dmitry Gutov
2015-05-20  2:49             ` Paul Eggert [this message]
2015-05-20 12:25               ` Dmitry Gutov
2015-05-20 12:50           ` Stefan Monnier
2015-05-21  7:36             ` Paul Eggert
2015-05-21 10:05               ` Dmitry Gutov
2015-05-21 14:44                 ` Paul Eggert
2015-05-20  4:23     ` Yuri Khan
2015-05-20 15:36   ` Glenn Morris
2015-05-21  5:18     ` Paul Eggert

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=555BF61D.40202@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@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).