From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path. Date: Thu, 11 Nov 2021 03:56:29 +0100 Message-ID: <87zgqbe6xu.fsf@gnus.org> References: <877dfkxyt4.fsf@elite.giraud> <87cznef8ah.fsf@gnus.org> <86ilx5iaze.fsf@gmail.com> <87pmrdb0zv.fsf@gnus.org> <86mtmgx6gg.fsf@gmail.com> <87fe707b-f2b4-febd-d2ae-acc697b4cee1@yandex.ru> <87zgqgjeaz.fsf@gnus.org> <87cznbt2r1.fsf@elite.giraud> <87h7cn803w.fsf@gnus.org> <878rxzszl8.fsf@elite.giraud> <877ddiuhv7.fsf@gnus.org> <87y25x3e6g.fsf@elite.giraud> <87a6icoqkm.fsf@gnus.org> <8856c512-a603-fa3e-bf21-c191a8a45afa@yandex.ru> <87bl2slv3j.fsf@gnus.org> <87y25wkfnb.fsf@gnus.org> <838rxw41dt.fsf@gnu.org> <87h7ckf9oz.fsf@gnus.org> <83sfw42ipa.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19344"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 50572@debbugs.gnu.org, andrewjmoreton@gmail.com, manuel@ledu-giraud.fr, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 11 03:57:09 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ml0Gz-0004q7-Bq for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 Nov 2021 03:57:09 +0100 Original-Received: from localhost ([::1]:43424 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ml0Gy-0002xr-0g for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 10 Nov 2021 21:57:08 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42668) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ml0Gs-0002uf-5V for bug-gnu-emacs@gnu.org; Wed, 10 Nov 2021 21:57:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56312) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ml0Gr-0004uB-Pq for bug-gnu-emacs@gnu.org; Wed, 10 Nov 2021 21:57:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ml0Gr-0005EQ-Ly for bug-gnu-emacs@gnu.org; Wed, 10 Nov 2021 21:57:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 Nov 2021 02:57:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50572 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 50572-submit@debbugs.gnu.org id=B50572.163659940620086 (code B ref 50572); Thu, 11 Nov 2021 02:57:01 +0000 Original-Received: (at 50572) by debbugs.gnu.org; 11 Nov 2021 02:56:46 +0000 Original-Received: from localhost ([127.0.0.1]:39625 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ml0Gc-0005Dt-HM for submit@debbugs.gnu.org; Wed, 10 Nov 2021 21:56:46 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:48566) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ml0Gb-0005Dg-2P for 50572@debbugs.gnu.org; Wed, 10 Nov 2021 21:56:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=mT21B24Jaf8ellZR0cEsmE1tTYy68AsiLWkZ6Iz3tpM=; b=Wiq9Q+SQKziF1J8f/XkXtfGNzS Of/SuFqlHnCZaMJu9+jH36PzQ1cE7mex5n4VHpiBWIO7+yriOS5fkTm/jhxGgokq5SskiNaBZz1AB fPOhDx9noO62U+GAdbkx3pJLU6FWOfipTlEfR+4C330TaSkhQI2SAbZVD92ijuHCTJdM=; Original-Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ml0GQ-0001Zt-Ve; Thu, 11 Nov 2021 03:56:37 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAD1BMVEVKLCVPLCORZE60 ln7///8IGfnBAAAAAWJLR0QEj2jZUQAAAAd0SU1FB+ULCwIsAv43SG0AAAF7SURBVDjLnZPbecMg DIUFXQBpAkss0MD+u+UIgQ1t+lISXz5+ju4m8sXMheJtPsfKGiBtYDxaA+CUBbu3EueMzBWcK+5S SEoA6larmTWr+GM1NQ1Qe++ttZe11jvAq9sAr3FcrSXDfayhsG9iQVwFLljhazmvl6cB8NWrtQ1g pUGG7iMIYfkDMH0AttVsAYEDMfsB2PeUkQCuEkenwsG8gkwgSC5ylgOQ+AaKCHMs1wHuJSgURdO8 JSYakKetUGQPKVudTnbnEEgNSZiaecC5aDRCd4DzHi5a2ZzeILHXW7zDw1q5o0KdFNNVretSBMiY J0qXR9Rsz8PfvegiHu71APhIiCp5cWWWdzo33KIksyEBxEEMo6luCo9FvYO1rX6EjyLjuAfBuyni 0Tux7atJtI0JIJ+K2IcGfnifRFpjpc/E7abQimfinn1vCK5TwZnHRyMo12nKR45H1Kct7wnT+g5O gn2Jz2CBmRDj5xlS+qUow9YqxgbudP+53hVgPjdMzr2BAAAAJXRFWHRkYXRlOmNyZWF0ZQAyMDIx LTExLTExVDAyOjQ0OjAyKzAwOjAwzg6UZAAAACV0RVh0ZGF0ZTptb2RpZnkAMjAyMS0xMS0xMVQw Mjo0NDowMiswMDowML9TLNgAAAAASUVORK5CYII= X-Now-Playing: Fairport Convention's _Come All Ye (5)_: "Dawn (Alternate Take)" In-Reply-To: <83sfw42ipa.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Nov 2021 16:23:13 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:219575 Archived-At: Eli Zaretskii writes: > We can always use "/\\" as SEPARATORS on MS-Windows, can't we? I was wondering about that -- are both of those characters disallowed in file name components on Windows? If so, then yes. What would be the test to identify the systems where this is the case? > Alternatively, we could loop with file-name-directory, I guess. That's what the current implementation does, and it's slow (since it consults the file name handlers). > But if we want a function that returns the "depth" of a file in a > filesystem, then it will need to call expand-file-name internally > anyway, for the same reason I point out above, right? Yes. This function can be used as a component in that calculation, but if that's the purpose of the call, then the caller has to make the file name non-relative first. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no