unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 35202@debbugs.gnu.org
Subject: bug#35202: 27.0.50; Info-quoted false positives and false negatives
Date: Tue, 09 Apr 2019 09:18:44 +0300	[thread overview]
Message-ID: <83sgur7lbv.fsf@gnu.org> (raw)
In-Reply-To: <CABczVwf_Axh_L58mM0spA4f=VRQtW=aVFsd8y-yQxhPYbKFEug@mail.gmail.com> (message from Mauro Aranda on Mon, 8 Apr 2019 20:30:19 -0300)

> From: Mauro Aranda <maurooaranda@gmail.com>
> Date: Mon, 8 Apr 2019 20:30:19 -0300
> 
> diff --git a/lisp/info.el b/lisp/info.el
> index f3b413a..268ecd8 100644
> --- a/lisp/info.el
> +++ b/lisp/info.el
> @@ -4269,7 +4269,7 @@ Info-quoted
>  ;; the former can be done much more reliably, i.e. without risking
>  ;; false positives.
>  (defvar Info-mode-font-lock-keywords
> -  '(("‘\\([^’]*\\)’" (1 'Info-quoted))))
> +  '(("‘\\([‘’]?\\|[^‘’]*\\)’" (1 'Info-quoted))))

Thanks, but I'm worried how we will be able to make sure this change
doesn't break display in some other places.  Would it make sense to
search all our Info files for the new regexp, and examine the display
of all the places that match?  Or did you already do that?





  reply	other threads:[~2019-04-09  6:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 22:42 bug#35202: 27.0.50; Info-quoted false positives and false negatives Mauro Aranda
2019-04-08 23:30 ` Mauro Aranda
2019-04-09  6:18   ` Eli Zaretskii [this message]
2019-04-09 17:40     ` Mauro Aranda
2019-04-09 18:23       ` Eli Zaretskii
2019-04-11  0:19         ` Mauro Aranda
2019-04-13  8:30           ` Eli Zaretskii
2019-04-13 13:26             ` Mauro Aranda
2019-04-21 12:02               ` Eli Zaretskii
2019-04-21 14:17                 ` Mauro Aranda
2019-04-09 11:35   ` Noam Postavsky
2019-04-09 17:43     ` Mauro Aranda

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=83sgur7lbv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35202@debbugs.gnu.org \
    --cc=maurooaranda@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).