unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: storm@cua.dk, pot@gnu.org, utcke@kogs1.informatik.uni-hamburg.de,
	emacs-devel@gnu.org
Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)
Date: Sat, 23 Feb 2002 13:19:52 -0700 (MST)	[thread overview]
Message-ID: <200202232019.g1NKJq114644@aztec.santafe.edu> (raw)
In-Reply-To: <874rk9a8uk.fsf@pot.cnuce.cnr.it> (message from Francesco Potorti` on 22 Feb 2002 15:29:07 +0100)

    Using C-u M-. one can search for more tags.  We (not me, please!) can
    change find-tag so that, before looking in the TAGS buffer for more
    tags, the current buffer is searched backwards from point for a #line
    directive.  If that is found, jump to the correponding location in the
    file referenced by #line. 

    Etags is left unchanged.

This might be the right way to handle #line for this case, where the
#line refers to a real source file which etags cannot or did not scan.
Although I think it should go straight to the real source file;
it should not "find" any tags in the generated file at all.

However, for the .c and .y case, it should be etags that recognizes
that it should not scan the .c file if the .y file is going to
be scanned.

Please consider this question decided.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-02-23 20:19 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`
     [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 [this message]
     [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

  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=200202232019.g1NKJq114644@aztec.santafe.edu \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pot@gnu.org \
    --cc=storm@cua.dk \
    --cc=utcke@kogs1.informatik.uni-hamburg.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).