From: Francesco Potorti` <pot@gnu.org>
Cc: emacs-devel@gnu.org (Emacs developers), storm@cua.dk (Kim F. Storm)
Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)
Date: Fri, 22 Feb 2002 15:08:36 +0100 [thread overview]
Message-ID: <E16eGNI-0005bB-00@pot.cnuce.cnr.it> (raw)
In-Reply-To: <200202211621.g1LGLEt01092@kogs46.informatik.uni-hamburg.de> (utcke@kogs1.informatik.uni-hamburg.de)
> However, this will often NOT be the case when #line directives are
> found in files generated by other programs (there may be a 1:100 or a
> 100:1 correspondance) -- but you don't know. So etags will have to
> put the #line directive's line number directly into TAGS.
I do not think this is correct. The program generating the #line
directives can, I think, be assumed to output a new #line directive
whenever there is no 1:1 correspondence.
I do believe that Sven is right. That's the precise purpose of the
#line directive.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-22 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200202211303.g1LD3ar29903@kogs46.informatik.uni-hamburg.de>
2002-02-21 14:43 ` Bug Report (Feature request?) etags (GNU Emacs 21.1) Francesco Potorti`
2002-02-21 15:51 ` Kim F. Storm
2002-02-21 16:21 ` Sven Utcke
2002-02-22 14:08 ` Francesco Potorti` [this message]
[not found] ` <200202220433.g1M4XAt14047@aztec.santafe.edu>
2002-02-22 11:48 ` Sven Utcke
2002-02-22 14:29 ` Francesco Potorti`
2002-02-22 14:56 ` Sven Utcke
2002-02-23 20:19 ` Richard Stallman
[not found] ` <200202220433.g1M4X3f14032@aztec.santafe.edu>
2002-02-22 14:10 ` Francesco Potorti`
2002-02-22 15:02 ` Sven Utcke
2002-02-22 16:27 ` Stefan Monnier
[not found] <200202220433.g1M4XCj14050@aztec.santafe.edu>
2002-02-22 11:37 ` Sven Utcke
2002-02-23 20:19 ` Richard Stallman
[not found] <200202141816.g1EIGWQ19766@kogs12.informatik.uni-hamburg.de>
[not found] ` <871yfjhgk7.fsf@pot.cnuce.cnr.it>
[not found] ` <5xg03zg0hc.fsf@kfs2.cua.dk>
[not found] ` <vd0bsenf432.fsf@kogs12.informatik.uni-hamburg.de>
[not found] ` <5xu1sfq8t9.fsf@kfs2.cua.dk>
[not found] ` <Pine.SUN.3.91.1020218153612.5449D-100000@is>
[not found] ` <87n0y6emxz.fsf@pot.cnuce.cnr.it>
[not found] ` <uofimd4mp.fsf@synopsys.com>
[not found] ` <87lmdq7cwm.fsf@creche.redhat.com>
[not found] ` <87eljie7ty.fsf@pot.cnuce.cnr.it>
[not found] ` <200202192131.g1JLVp413268@aztec.santafe.edu>
2002-03-05 12:15 ` Francesco Potorti`
2002-03-05 13:11 ` Sven Utcke
2002-03-06 5:57 ` Eli Zaretskii
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=E16eGNI-0005bB-00@pot.cnuce.cnr.it \
--to=pot@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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.