all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Hong Xu <hong@topbug.net>, 23436@debbugs.gnu.org
Subject: bug#23436: [PATCH] Attemp to use the true name of a file to determine responsible vc if the genuine name does not work.
Date: Tue, 25 Oct 2016 02:41:31 +0300	[thread overview]
Message-ID: <1ad97145-d21e-5d64-8b6c-4b4b2bc2ab49@yandex.ru> (raw)
In-Reply-To: <a434df63-c4e8-fdbc-782e-6a97493fd5a5@topbug.net>

On 21.10.2016 02:04, Hong Xu wrote:

> Sorry for the confusion. Either keeping what it was or adding a new
> command [which essentially calls (vc-responsible-backend (vc-follow-link
> file)) ] would be the best option regarding performance.

Shouldn't the command call find-alternate-file instead? Then you can 
continue working with buffer-file-name and default-directory inside the 
symlink target directory. And if you visit any nearby files there, you 
won't have to call the vc-follow-link for each of them again?

What are the downsides to this approach?

> e need to
> clarify that symlinks are not followed in vc-responsible-backend, and If
> the first option is adopted, mention that vc-follow-link should be used
> if link following is desired.

OK, mention where?





  reply	other threads:[~2016-10-24 23:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 21:32 bug#23436: [PATCH] Use the true name of a file to determine responsible vc Hong Xu
2016-10-19 19:19 ` Hong Xu
2016-10-19 19:33   ` bug#23436: [PATCH] Attemp to use the true name of a file to determine responsible vc if the genuine name does not work Hong Xu
2016-10-19 23:37     ` Dmitry Gutov
2016-10-19 23:49       ` Hong Xu
2016-10-19 23:58         ` Dmitry Gutov
2016-10-20  0:16           ` Hong Xu
2016-10-20  6:58             ` Eli Zaretskii
2016-10-20  7:21               ` Hong Xu
2016-10-20  8:23                 ` Eli Zaretskii
2016-10-20  8:50                   ` Dmitry Gutov
2016-10-20  9:46                   ` Andreas Schwab
2016-10-20 10:02                     ` Eli Zaretskii
2016-10-20 10:58                       ` Eli Zaretskii
2016-10-20  9:47             ` Dmitry Gutov
2016-10-20 16:39               ` Hong Xu
2016-10-20 22:34                 ` Dmitry Gutov
2016-10-20 23:04                   ` Hong Xu
2016-10-24 23:41                     ` Dmitry Gutov [this message]
2016-10-25 19:05                       ` Hong Xu
2016-10-25 23:12                         ` Dmitry Gutov
2016-10-30  0:42                           ` Hong Xu
2016-10-30 16:21                             ` Eli Zaretskii
2016-10-30 22:50                               ` Hong Xu
2016-10-31 15:43                                 ` Eli Zaretskii
2016-10-31 19:38                                   ` Hong Xu
2016-11-01 18:47                                     ` Eli Zaretskii
2016-11-04  7:46                                       ` Hong Xu
2016-11-04 10:08                                         ` Eli Zaretskii
2016-10-31 11:34                             ` Dmitry Gutov
2016-10-31 19:24                               ` Hong Xu

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=1ad97145-d21e-5d64-8b6c-4b4b2bc2ab49@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=23436@debbugs.gnu.org \
    --cc=hong@topbug.net \
    /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.