all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: emacs-27 e1e0a7a 2/2: xref--collect-matches: Speed up on remote
Date: Sat, 28 Dec 2019 11:54:13 -0500	[thread overview]
Message-ID: <jwv8smwqtmm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <3df43b9a-9b87-1ae5-727f-22ef3c8bf33f@yandex.ru> (Dmitry Gutov's message of "Sat, 28 Dec 2019 18:22:38 +0300")

>> so in that case `expand-file-name` should presumably "always" return
>> without contacting the remote host, right?
> Personally, I don't see why file-local-name should ever call
> expand-file-name.  The caller can do that itself, when necessary.

I think I agree, but I don't see how that relates to the discussion, so
maybe I'm missing something (I can't remember any reference to `file-local-name`).


        Stefan




  reply	other threads:[~2019-12-28 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191227141917.13328.16721@vcs0.savannah.gnu.org>
     [not found] ` <20191227141919.03F1321537@vcs0.savannah.gnu.org>
2019-12-27 15:58   ` emacs-27 e1e0a7a 2/2: xref--collect-matches: Speed up on remote Stefan Monnier
2019-12-27 16:18     ` Dmitry Gutov
2019-12-27 19:30       ` Stefan Monnier
2019-12-27 20:19         ` Michael Albinus
2019-12-27 22:06           ` Stefan Monnier
2019-12-28 10:09             ` Michael Albinus
2019-12-28 16:53               ` Stefan Monnier
2019-12-28 15:22             ` Dmitry Gutov
2019-12-28 16:54               ` Stefan Monnier [this message]
2019-12-28 16:58                 ` Dmitry Gutov
2019-12-28 18:58               ` Michael Albinus

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=jwv8smwqtmm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.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 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.