all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Ryde <user42_kevin@yahoo.com.au>
Cc: 19900@debbugs.gnu.org
Subject: bug#19900: 24.4; info-look.el quotes from makeinfo @item
Date: Thu, 19 Feb 2015 08:11:19 +0200	[thread overview]
Message-ID: <83oaoq4eig.fsf@gnu.org> (raw)
In-Reply-To: <873862zcf4.fsf@blah.blah>

> From: Kevin Ryde <user42_kevin@yahoo.com.au>
> Date: Thu, 19 Feb 2015 16:40:47 +1100
> 
> Recent makeinfo on @item generates forward quote 'foo' rather than
> backquote `foo' which it used to.  info-look.el doesn't match the
> forward 'foo' in various places which are @table (as opposed to @defun
> etc).

These two characters are actually customizable in the latest Texinfo
(although I doubt that many people use that feature).  So perhaps
there should be a defcustom for them, so users could use other
characters if needed.

> 2015-02-19  Kevin Ryde  <user42_kevin@yahoo.com.au>
> 
> 	* info-look.el (c-mode, bison-mode, makefile-mode)
> 	(makefile-automake-mode, texinfo-mode, autoconf-mode, awk-mode)
> 	(latex-mode, emacs-lisp-mode, sh-mode, cfengine-mode): Match both
> 	`foo' and 'foo' for @item and similar.
> 	(emacs-lisp-mode): U+2018,U+2019 in emacs.info and elisp.info too.
> 	(latex-mode): Match multi-arg \frac{num}{den} or \sqrt[root]{n} in
> 	suffix regexp

Why do you confine U+2018 and U+2019 to Emacs manuals?  AFAIK, they
will appear in any manual that has its @documentencoding set to UTF-8.
So I think you can see that in any manual any time.

Thanks.





  reply	other threads:[~2015-02-19  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  5:40 bug#19900: 24.4; info-look.el quotes from makeinfo @item Kevin Ryde
2015-02-19  6:11 ` Eli Zaretskii [this message]
2015-03-13 18:17 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83oaoq4eig.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19900@debbugs.gnu.org \
    --cc=user42_kevin@yahoo.com.au \
    /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.