From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: Lute.Kamstra@cwi.nl, eliz@elta.co.il, bug-texinfo@gnu.org,
emacs-devel@gnu.org
Subject: Re: Double hyphens in variable names.
Date: Thu, 2 Oct 2003 21:13:36 -0500 (CDT) [thread overview]
Message-ID: <200310030213.h932DaJ12512@raven.dms.auburn.edu> (raw)
In-Reply-To: <200310030150.h931oQ312488@raven.dms.auburn.edu> (message from Luc Teirlinck on Thu, 2 Oct 2003 20:50:26 -0500 (CDT))
>From my previous message:
I changed my mind on this, since @verb in isolation seems to work
perfectly, in all situations you describe. It apparently is not
supposed to be called from within other environments such as @code.
But then again, @verb _does_ work within @code in as far as the Info
output is concerned. It works from within other environments in
LaTeX. The Texinfo documentation does not explicitly say whether
@verb is supposed to work from within @code. I will let Karl decide
whether the fact that @verb does not work (in all situations) from
within @code is a bug or not. Andreas pointed out the reason for the
problem, assuming it is one.
It seems that `imenu@verb{|--|}index-alist' sometimes get treated as
implicitly inside an @code (@verb does not work) and sometimes not
(@verb works). Of course, this is inconsistent.
I should have said "would be inconsistent" (if my impression would be
correct).
Sincerely,
Luc.
next prev parent reply other threads:[~2003-10-03 2:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 13:53 Double hyphens in variable names Lute Kamstra
2003-10-02 5:55 ` Eli Zaretskii
2003-10-02 8:43 ` Lute Kamstra
2003-10-02 13:18 ` Luc Teirlinck
2003-10-02 15:11 ` Lute Kamstra
2003-10-02 16:00 ` Luc Teirlinck
2003-10-02 16:14 ` Lute Kamstra
2003-10-02 16:54 ` Andreas Schwab
2003-10-02 17:25 ` Luc Teirlinck
2003-10-03 1:50 ` Luc Teirlinck
2003-10-03 2:13 ` Luc Teirlinck [this message]
2003-10-03 3:45 ` Luc Teirlinck
2003-10-02 19:04 ` Oliver Scholz
2003-10-03 8:39 ` Lute Kamstra
2003-10-03 16:18 ` Luc Teirlinck
2003-10-03 19:37 ` Lute Kamstra
2003-10-03 18:33 ` Luc Teirlinck
2003-10-03 18:42 ` Luc Teirlinck
2003-10-03 19:46 ` Lute Kamstra
2003-10-04 10:47 ` David Ponce
2003-10-06 7:11 ` Lute Kamstra
2003-10-06 23:19 ` Juri Linkov
2003-10-07 9:08 ` Lute Kamstra
2003-10-03 19:42 ` Richard Stallman
2003-10-03 21:19 ` Juri Linkov
2003-10-02 14:07 ` Luc Teirlinck
2003-10-02 19:15 ` Richard Stallman
2003-10-02 18:56 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2003-10-04 1:03 Karl Berry
2003-10-04 22:35 ` Richard Stallman
2003-10-05 0:53 ` Miles Bader
2003-10-05 10:36 ` Stepan Kasal
2003-10-05 8:34 ` Werner LEMBERG
2003-10-04 1:03 Karl Berry
2003-10-04 3:51 ` Luc Teirlinck
2003-10-06 9:06 David PONCE
2003-10-06 9:18 ` Lute Kamstra
2003-10-07 5:32 ` Richard Stallman
2003-10-07 6:57 ` Lute Kamstra
2003-10-06 9:26 David PONCE
2003-10-07 7:57 David PONCE
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=200310030213.h932DaJ12512@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=Lute.Kamstra@cwi.nl \
--cc=bug-texinfo@gnu.org \
--cc=eliz@elta.co.il \
--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).