unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Francesco Potorti` <pot@gnu.org>
Cc: alinsoar@voila.fr, "Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: find-tag and partial completion mode -- Francisco, urgent!
Date: Fri, 04 May 2007 10:10:14 -0400	[thread overview]
Message-ID: <jwvirb8isv6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1HjxcO-0005NL-Jq@tucano.isti.cnr.it> (Francesco Potorti`'s message of "Fri\, 04 May 2007 15\:14\:40 +0200")

> So: either we implement the change to etags.el that I suggest above, or
> else I can add a couple of lines in the manual such as:

>  Notice that, in the usual case of using relative file names, you should
>  not use a symbolic link to a tags file in a different directory.

That seems like the better option.  After all, it's very unusual to make
such symlinks to TAGS files, and it's not clear exactly what is the
motivation for such a thing: depending on the motivation the current
behavior can be wrong or right, and if we change it as you suggest, it will
still be sometimes right and sometimes wrong.  Better keep things dumber, so
it's easier for the user to predict.


        Stefan

  reply	other threads:[~2007-05-04 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 20:26 find-tag and partial completion mode -- Francisco, urgent! A Soare
2007-05-03  1:46 ` Stefan Monnier
2007-05-04 13:14 ` Francesco Potorti`
2007-05-04 14:10   ` Stefan Monnier [this message]
2007-05-04 21:17   ` Richard Stallman
2007-05-05  0:37     ` Francesco Potorti`
  -- strict thread matches above, loose matches on Subject: below --
2007-05-03  9:41 A Soare
2007-05-02 20:27 A Soare
2007-05-02 20:26 A Soare
2007-05-02 11:02 find-tag and partial completion mode A Soare
2007-05-02 17:44 ` find-tag and partial completion mode -- Francisco, urgent! Richard Stallman
2007-05-02 20:13   ` Glenn Morris
2007-05-02 20:02     ` Tom Tromey

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=jwvirb8isv6.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=alinsoar@voila.fr \
    --cc=emacs-devel@gnu.org \
    --cc=pot@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).