From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: xref backends for elisp-related modes Was: Re: Bad moves with xref-find-definitions Date: Wed, 29 Apr 2015 15:01:42 +0200 Message-ID: References: <87h9s6c27z.fsf@gmail.com> <87zj5wnlyt.fsf@gmail.com> <553C285B.4070400@yandex.ru> <838udfx7rt.fsf@gnu.org> <87383kcy0u.fsf@gmail.com> <87twvz85w7.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430312543 6116 80.91.229.3 (29 Apr 2015 13:02:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 13:02:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: Vitalie Spinu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 29 15:02:18 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YnRd1-0002L1-K2 for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 15:02:15 +0200 Original-Received: from localhost ([::1]:38754 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnRcv-0004pV-Sb for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 09:02:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56577) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnRcc-0004dg-Bu for emacs-devel@gnu.org; Wed, 29 Apr 2015 09:01:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnRcY-0006Ym-Ca for emacs-devel@gnu.org; Wed, 29 Apr 2015 09:01:50 -0400 Original-Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:36230) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnRcY-0006YT-6d for emacs-devel@gnu.org; Wed, 29 Apr 2015 09:01:46 -0400 Original-Received: by wgen6 with SMTP id n6so27327971wge.3 for ; Wed, 29 Apr 2015 06:01:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=Ni/poL5VgBGlx37fFPg62gFuBWjDTElmFm6LkiPdqbg=; b=dp4Cczm8zI5kLKhDGh+I1XKUEjSJloGWy7/BXUWHvmWVRg9mSgXb11YZODK4SXEH1y t2Nlpl98mDxAhlIfb68SNO1mjH9m3ZUIwry0hpXmw8FXzSNpSCSUTujc2CNXjnChkW9Y SfXLnjd4x6kHrnGqfdOeSzjHZ2q32sAxqfmAE5JbbtCCVlYjXSE4OygrCO9AAaMfc3LR dGf23b2H4PX4u716hOcCIBXRwZZWQPurJbDJ+bG1Q5IxiZM4RGJL95tB1DRDCDXUzZsp kHmPvcr3G5Tpmc9vMWBkpxVubXPY94U3j0rSod56Kg7vmBHJirkpWwgbMlW4sPmisd4p 95Mg== X-Received: by 10.194.248.132 with SMTP id ym4mr6033415wjc.74.1430312504888; Wed, 29 Apr 2015 06:01:44 -0700 (PDT) Original-Received: from ix (dial-185099.pool.broadband44.net. [212.46.185.99]) by mx.google.com with ESMTPSA id e2sm21127627wix.15.2015.04.29.06.01.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Apr 2015 06:01:44 -0700 (PDT) Original-Received: from helmut by ix with local (Exim 4.84) (envelope-from ) id 1YnRcU-00072l-MJ; Wed, 29 Apr 2015 15:01:42 +0200 In-Reply-To: <87twvz85w7.fsf@gmail.com> (Vitalie Spinu's message of "Wed, 29 Apr 2015 14:40:08 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::230 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:186009 Archived-At: On Wed, Apr 29 2015, Vitalie Spinu wrote: > > For me those are convincing arguments too delegate duplicate removal to > > backends. > > I probably miss something essential but this doesn't make sense to > me. We are talking about merged backends. So, the task of frontend is to > remove duplicates which result from merging multiple candidate lists > coming from backends. How an individual backend can deal with that? You have 2 backends. Create a third backend that calls the other two and does the merging. The front-end is doesn't need to know how to merge. Helmut