From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: philipk@posteo.net (Philip K.) Newsgroups: gmane.emacs.devel Subject: Re: Xref Fallback Date: Tue, 11 Aug 2020 20:19:17 +0200 Message-ID: <87a6z159lm.fsf@posteo.net> References: <6288a8d5-1891-7382-0404-422821f6a37f@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14610"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 11 20:20:07 2020 Return-path: Envelope-to: ged-emacs-devel@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 1k5YsY-0003ip-JA for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Aug 2020 20:20:06 +0200 Original-Received: from localhost ([::1]:47614 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k5YsX-0007oq-M5 for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Aug 2020 14:20:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37292) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5Yru-0007OS-QQ for emacs-devel@gnu.org; Tue, 11 Aug 2020 14:19:26 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:60465) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5Yrs-0005XN-PU for emacs-devel@gnu.org; Tue, 11 Aug 2020 14:19:26 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 6358E2400FB for ; Tue, 11 Aug 2020 20:19:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1597169961; bh=Eyzo63GyZDNqZIwm4pD9cMtqwtSuUnitPZ7NLkqKiF4=; h=From:To:Cc:Subject:Date:From; b=OXEJV9pSTbn+VYm1lgEbpYmQUScBJY164N82iBWc42ZD6TnIvOVMwn/HWhzDcBjVi bcT0I6Z6uMndE10T/GZCSQKANikRPCsTp7RY6CVfU2cfF5JmYLtJ2R+R5YKtwIJyXt JHpECP/wck6FR89XQ96zgz4BDASiY4jp+kbCD/HqBU6/DXrv58Fhloh3QhLNVLjGRt 3RbtfrfqCwqQDLWbm18y74xwITT82BilK8exTJK0geBVFS3ei9lN9TKPSYToZqWwj+ 1tz0ZGfAw1RF6qty0Z0Gqn4nVFXyMtz+iRv7exBfEGUJtkkgYJpfSATGNOoLBm/7X6 IPP6IxIjHRyBw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4BR1Lw5cNwz9rxg; Tue, 11 Aug 2020 20:19:20 +0200 (CEST) In-Reply-To: <6288a8d5-1891-7382-0404-422821f6a37f@yandex.ru> (message from Dmitry Gutov on Mon, 10 Aug 2020 22:01:34 +0300) Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/11 14:19:21 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:253641 Archived-At: Dmitry Gutov writes: >> What I would want to know, is if there have been discussion on this >> issue, what the status is, and if not what would have to be done. I can >> imagine, that falling back onto the next backend isn't always desirable >> (especially if etags is next, and it demands a TAGS file that doesn't >> exist). > > How would you feel about creating an xref backend that would implement > the fallback logic? It would basically only do the combining, without > having any navigation logic of its own. > > This way users could include it in the xref-backend-functions to enable > fallback mechanics. The said combinator backend could also hardcode some > particular backends to skip. This sounds interesting, I'll try to get something like this working. Would this be merged into Xref, or should it be a separate package?