unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: pbreton@cs.umb.edu, tramp-devel@gnu.org,
	raman@users.sourceforge.net, emacs-devel@gnu.org
Subject: Re: Reverting *Locate* buffers.
Date: Wed, 28 Jun 2006 22:13:58 -0500 (CDT)	[thread overview]
Message-ID: <200606290313.k5T3DwTj002620@jane.dms.auburn.edu> (raw)
In-Reply-To: <17569.64920.191861.355581@localhost.localdomain> (raman@users.sourceforge.net)

T. V. Raman wrote:

   While on the error message regarding tramp, I've found that tramp
   being around causes *a lot* of recursive expand file calls ---
   try running edebug on anything that calls expand-file-name to see
   what I mean.

   Basically, tramp should only fire on the  "head" of the path
   being expanded -- at present it appears to fire for *each* path
   component. 

Just as a general question to everybody interested (not just to the
person in the "To" field):

Where do we stand now in this thread?  Obviously, I can not implement
David's suggestion as long as there is this error message (assuming it
would not give other problems, even without that message, which I can
not test).

Do I just commit my previously sent patch, or do we have the feeling
that there are bugs in Tramp which should be reported?  Note that
Tramp is independently maintained by tramp-devel, which I have CC-ed,
rather than by emacs-devel.  I believe that the people maintaining
Tramp also read emacs-devel, but I am not sure that they have followed
this thread.

Sincerely,

Luc.

  reply	other threads:[~2006-06-29  3:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26  3:27 Reverting *Locate* buffers Luc Teirlinck
2006-06-26  7:43 ` David Kastrup
2006-06-28  1:58   ` Luc Teirlinck
2006-06-28  3:55     ` T. V. Raman
2006-06-29  3:13       ` Luc Teirlinck [this message]
2006-06-29  6:27         ` David Kastrup
2006-06-29 21:52         ` Michael Albinus
2006-06-30  1:55           ` Luc Teirlinck
2006-07-02 20:39             ` Michael Albinus
2006-07-02 20:52         ` Michael Albinus
2006-07-03  2:51           ` Luc Teirlinck
2006-07-03 13:43             ` Michael Albinus
2006-07-03 23:21               ` Richard Stallman
2006-07-04  0:14               ` Luc Teirlinck
2006-07-03 15:05           ` Richard Stallman
2006-07-03 15:37             ` Michael Albinus
2006-07-03 15:41               ` David Kastrup
2006-07-04 15:42           ` Stefan Monnier
2006-06-29 21:58       ` Michael Albinus
2006-06-26 13:15 ` Peter Breton
2006-06-27  1:55   ` Luc Teirlinck

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=200606290313.k5T3DwTj002620@jane.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=pbreton@cs.umb.edu \
    --cc=raman@users.sourceforge.net \
    --cc=tramp-devel@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).