[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with
From: |
Eli Zaretskii |
Subject: |
bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path. |
Date: |
Tue, 14 Sep 2021 15:57:24 +0300 |
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: 50572@debbugs.gnu.org
> Date: Tue, 14 Sep 2021 14:08:36 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > Isn't that already available with "C-u C-x v v"?
> >>
> >> It does not work for me. It still tries to register in my homedir
> >> subversion.
> >
> > It didn't work for me, either. Which is a pity, since the manual says
> > it should. I guess we lost this at some point; patches to fix that
> > are welcome.
>
> Ok. I could try to work on this issue then but maybe I should file
> another bug report, no?
Yes, please.
> > I'm worried that we are arbitrarily changing the defaults, for the
> > sole reason that the new default plays better with someone's
> > workflows.
>
> I think you are right and as you said the "choose the correct backend"
> behaviour is already documented in the manual (in "Advanced Control in
> ‘C-x v v’").
>
> > AFAIR, it used to be the case that the order of VCS names in
> > vc-handled-backends determined the way the default is sought out and
> > set. This change (and I think the other one Dmitry mentioned in his
> > response?) change that in a way that doesn't leave any "fire escape"
> > to users who might be setting things up to have a meaningful (for
> > them) order in that list.
>
> Yes, in "Customizing VC", the manual insists on the order importance of
> the vc-handled-backends list. So maybe, just fixing "C-u C-x v v" and
> remember this customization is enough here.
Let's wait for Dmitry to chime in, as I expect he will have different
opinions.
Thanks
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Manuel Giraud, 2021/09/13
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Eli Zaretskii, 2021/09/13
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Dmitry Gutov, 2021/09/13
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Manuel Giraud, 2021/09/14
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Manuel Giraud, 2021/09/14
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Eli Zaretskii, 2021/09/14
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Manuel Giraud, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Dmitry Gutov, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Eli Zaretskii, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Dmitry Gutov, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Dmitry Gutov, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Eli Zaretskii, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Dmitry Gutov, 2021/09/15
- bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path., Eli Zaretskii, 2021/09/15