From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Generalizing find-definition Date: Thu, 06 Nov 2014 17:22:19 +0200 Message-ID: <86fvdwgxqs.fsf@yandex.ru> References: <20141102151524.0d9c665c@forcix> <20141102172944.0f7944e3@forcix> <20141103084433.12117c03@forcix> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415287381 21323 80.91.229.3 (6 Nov 2014 15:23:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Nov 2014 15:23:01 +0000 (UTC) Cc: emacs-devel@gnu.org, Jorgen Schaefer To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 06 16:22:55 2014 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 1XmOtf-0003Q0-Kb for ged-emacs-devel@m.gmane.org; Thu, 06 Nov 2014 16:22:51 +0100 Original-Received: from localhost ([::1]:54341 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmOtf-0004jx-6P for ged-emacs-devel@m.gmane.org; Thu, 06 Nov 2014 10:22:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmOtK-0004fH-W0 for emacs-devel@gnu.org; Thu, 06 Nov 2014 10:22:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XmOtD-0001LV-WD for emacs-devel@gnu.org; Thu, 06 Nov 2014 10:22:30 -0500 Original-Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:61720) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmOtD-0001Kv-Pc for emacs-devel@gnu.org; Thu, 06 Nov 2014 10:22:23 -0500 Original-Received: by mail-wg0-f46.google.com with SMTP id x13so1462334wgg.33 for ; Thu, 06 Nov 2014 07:22:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=HC5Cd3AjHcPx43+oZYS8iX9wM+imuuWugII9R1u0H7Q=; b=l8ETei40obYKmASmCdbk6G7YiMEiyho3cONHKWYmgInVC8T1vUxmshxXA+ESzPdI6l 9KC7gOAz+8fCUvUkKSxj+TSZCKmwBs/vrpT/V31JYxJ+VdScP0Z8fNCndydrHxJl0iFN 9k/w6tQ5ARFGFwR4DHkUZQOQyPz11kJnQrtvTjO+s1JSi/s4bYl2KLMMqDDUnyuNRR0+ bjLFb/TsvQIHoEMjuJ/NVaVf4hXqJsIwe9bToD1h9MnVcZ1Jwfw9la4KEkQes5PGWv6p 0FuLQZR9XtSd9wTVC5f43+hyrCaUSopxRMkx8hqpGYdLQXfOdA8pXCgLv3sCx2hXE0RV sf9w== X-Received: by 10.180.210.195 with SMTP id mw3mr4339252wic.62.1415287342586; Thu, 06 Nov 2014 07:22:22 -0800 (PST) Original-Received: from axl (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id wx3sm8198794wjc.19.2014.11.06.07.22.21 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 06 Nov 2014 07:22:21 -0800 (PST) In-Reply-To: (Stefan Monnier's message of "Mon, 03 Nov 2014 09:30:56 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.51 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22e 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:176446 Archived-At: Stefan Monnier writes: >> The only benefit would be that M-, is now "go back after M-.", which is >> what a lot of the packages that redefine M-. do to the key. Hence the >> suggestion to swap the two keys, to unify that apparently rather >> widespread use of M-,. If Emacs would prefer to keep M-, as is, that is >> fine with me, too. > > I see, so it's compatibility with other packages vs. compatibility with > etags.el. Luckily, I think there is no hurry to make this choice. > So we could poll the users. I believe ergonomics and frequency of use have also been mentioned. And if find-tag will provide the "multiple occurences" interface on its own, there won't be a need for the "next tag" command. So, +1 from me. You might also take into account that elisp-slime-nav is a relatively popular package: http://melpa.org/#/elisp-slime-nav