From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vitalie Spinu 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 17:30:53 +0200 Message-ID: <87d22n7xzm.fsf@gmail.com> 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 1430321506 9079 80.91.229.3 (29 Apr 2015 15:31:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 15:31:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 29 17:31:45 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 1YnTxf-0003zR-4r for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 17:31:43 +0200 Original-Received: from localhost ([::1]:39685 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnTxe-0006u2-Ga for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 11:31:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39499) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnTww-0005vi-Pq for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:30:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnTwt-0007FG-Ua for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:30:58 -0400 Original-Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]:36802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnTws-0007E6-Qt for emacs-devel@gnu.org; Wed, 29 Apr 2015 11:30:55 -0400 Original-Received: by wizk4 with SMTP id k4so184935077wiz.1 for ; Wed, 29 Apr 2015 08:30:54 -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=IvQhbuWdw6vw9/huVoPtPWA8pe1ktBfe8tD4DuBbi7o=; b=nTh8f9nJL2nSw+alZjxDJ1QATCJGRlTQohOj6bqFYNyXFzsBECy8ojWcECKu3M9SWZ 5zVNW+psPJnquu0YD3xcMmSjOXMCx2NuvKOYJkP7cPEwqykFh8UqNedjeBx61VenvTkr JeiMeUibfi8BV+LWPSTPhyYFPhmYzvt/4xN/CngVYLzsjN5BFblH/AB9lPgC+8qyBIL3 EwvnclIKk5puitDBj0NmUKalJ7F8+2GZiTGsAt+bymmr7U9iVv0wRp4wMc4YBdpfqG4x zyu//HiWNoS1WfB4ejXbF2xmIIy70I+tiV9beYFgY7suvzoXAa6zYlBJ52aC8oUa9/yu vLPw== X-Received: by 10.180.85.42 with SMTP id e10mr9711832wiz.17.1430321454242; Wed, 29 Apr 2015 08:30:54 -0700 (PDT) Original-Received: from localhost (dhcp-077-251-128-242.chello.nl. [77.251.128.242]) by mx.google.com with ESMTPSA id hj10sm39521694wjc.48.2015.04.29.08.30.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Apr 2015 08:30:53 -0700 (PDT) In-Reply-To: (Helmut Eller's message of "Wed, 29 Apr 2015 15:01:42 +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:c05::22d 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:186018 Archived-At: >>> Helmut Eller on Wed, 29 Apr 2015 15:01:42 +0200 wrote: > 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. Then for any combination of backends that you want to merge you need to write yet another backend. Vitalie