From: "Steffen DETTMER" <Steffen.DETTMER@ingenico.com>
To: <bug-gnu-emacs@gnu.org>
Cc: steffen@dett.de
Subject: etags (GNU Emacs 21.4.20): identifier omitted situation in TAGS (minor bug)
Date: Mon, 14 May 2007 10:25:23 +0200 [thread overview]
Message-ID: <20070514082523.GB12890@elberon.bln.de.ingenico.com> (raw)
Hi,
I think I found a bug in etags (GNU Emacs 21.4.20), at least on
cygwin happening in a special combination (see below). Finally I
found a small file to reproduce it.
It may happen that a "blank space identifier" is written
instead of the element name. It seems to happen for the last
element of an enum, if additionally a multi-line comment is given
behind and if there is no whitespace between element identifier
and comment block (it seems, all of those conditions must be meet
to trigger the problem).
Here an example (etagsbug.h):
------------------------------------------------------------------->8=======
typedef enum
{
ELEM_1, /**< Comment Element 1
Second comment line. */
ELEM_2, /**< Comment Element 2
Second comment line. */
ELEM_I /**< Comment Element i
Second comment line. */
} Works_t;
typedef enum
{
ELEM_1, /**< Comment Element 1
Second comment line. */
ELEM_2, /**< Comment Element 2
Second comment line. */
ELEM_I/**< Comment Element i
Second comment line. */
} Fails_t;
=======8<-------------------------------------------------------------------
I would expect the "same" for Works_t and Fails_t, because the
declarations differ in comments/whitespace only, however, ELEM_I
of Fails_t does not go into the created TAGS file.
The resulting TAGS file is something like
------------------------------------------------------------------->8=======
^L
etagsbug.h,154
ELEM_1,^?3,15
ELEM_2,^?5,89
ELEM_I ^?7,163
} Works_t;^?Works_t^A9,237
ELEM_1,^?13,264
ELEM_2,^?15,338
^?18,444
} Fails_t;^?Fails_t^A19,482
=======8<-------------------------------------------------------------------
(^L, ^? and ^A are one-character control chars in the file of course)
In line 9, there should be " ELEM_I ^?18,444". With vim 7.0
(1-122) this leads to a parse error (I don't know for Emacs, but
at least the identifier will be missing).
I hope this little description helps a bit.
well, thanks for reading this! :) Best greetings from Germany! :)
oki,
Steffen
About Ingenico Throughout the world businesses rely on Ingenico for secure and expedient electronic transaction acceptance. Ingenico products leverage proven technology, established standards and unparalleled ergonomics to provide optimal reliability, versatility and usability. This comprehensive range of products is complemented by a global array of services and partnerships, enabling businesses in a number of vertical sectors to accept transactions anywhere their business takes them.
www.ingenico.com This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
About Ingenico Throughout the world businesses rely on Ingenico for secure and expedient electronic transaction acceptance. Ingenico products leverage proven technology, established standards and unparalleled ergonomics to provide optimal reliability, versatility and usability. This comprehensive range of products is complemented by a global array of services and partnerships, enabling businesses in a number of vertical sectors to accept transactions anywhere their business takes them.
www.ingenico.com This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
About Ingenico Throughout the world businesses rely on Ingenico for secure and expedient electronic transaction acceptance. Ingenico products leverage proven technology, established standards and unparalleled ergonomics to provide optimal reliability, versatility and usability. This comprehensive range of products is complemented by a global array of services and partnerships, enabling businesses in a number of vertical sectors to accept transactions anywhere their business takes them.
www.ingenico.com This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
next reply other threads:[~2007-05-14 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 8:25 Steffen DETTMER [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-17 14:53 etags (GNU Emacs 21.4.20): identifier omitted situation in TAGS (minor bug) Francesco Potorti`
2007-05-18 9:00 Francesco Potorti`
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=20070514082523.GB12890@elberon.bln.de.ingenico.com \
--to=steffen.dettmer@ingenico.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=steffen@dett.de \
/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).