all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sven Utcke <utcke@kogs1.informatik.uni-hamburg.de>
Cc: storm@cua.dk, pot@gnu.org, emacs-devel@gnu.org
Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)
Date: Fri, 22 Feb 2002 12:37:35 +0100 (CET)	[thread overview]
Message-ID: <200202221137.g1MBbZk02551@kogs46.informatik.uni-hamburg.de> (raw)
In-Reply-To: <200202220433.g1M4XCj14050@aztec.santafe.edu> from "Richard Stallman" at Feb 21, 2002 09:33:12 PM

Hello Richard, hello all,

>     It has been mentioned before to put dual references into TAGS:
>     one for the actual file, and one for the file from the #line
>     directive.  This is simple.
> 
> Having both files in the TAGS table is what we want to AVOID.
> It is wasteful.

Not in the case to which the sentence above was alluding.  There you
would have a line

FUNC f::x(a,b) { a /?/ b }

in the .ylag file, but a line

_YLfunc_x__f_(_YLp *a, _YLp *b)

in the generated .c file.  I believe the only way to reasonably handle
this would be _four_ references altogether:  One for each file, and
one for each functionname.  So looking up f::a would get you to the
*.ylag file first, and to the *.c file next (Ok, this would probably
be hard to implement :-), while looking up _YLfunc_x__f_ (why would
anybody want to do that?) would get you to the *.c file first and to
the *.ylag next.  

I guess.  But then, I have no clue about ylag, only web.  And for the
latter _one_ reference (to the *.web) would certainly be enough...

Sven
-- 
 _  __                     The Cognitive Systems Group
| |/ /___  __ _ ___                                       University of Hamburg
| ' </ _ \/ _` (_-<  phone:    +49 (0)40 42883-2576      Vogt-Koelln-Strasse 30
|_|\_\___/\__, /__/  fax  :    +49 (0)40 42883-2572             D-22527 Hamburg
          |___/ http://kogs-www.informatik.uni-hamburg.de/~utcke/home.html

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


       reply	other threads:[~2002-02-22 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200202220433.g1M4XCj14050@aztec.santafe.edu>
2002-02-22 11:37 ` Sven Utcke [this message]
2002-02-23 20:19   ` Bug Report (Feature request?) etags (GNU Emacs 21.1) 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
     [not found] <200202211303.g1LD3ar29903@kogs46.informatik.uni-hamburg.de>
2002-02-21 14:43 ` 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
     [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

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=200202221137.g1MBbZk02551@kogs46.informatik.uni-hamburg.de \
    --to=utcke@kogs1.informatik.uni-hamburg.de \
    --cc=emacs-devel@gnu.org \
    --cc=pot@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.