From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: etags: M-. jump to the tag(called func), but then how can i jump BACK(the calling line)? Date: Tue, 13 Sep 2005 11:26:59 -0600 Message-ID: References: <1126436508.461480.28080@z14g2000cwz.googlegroups.com> <85d5nfe3oy.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1126632904 6368 80.91.229.2 (13 Sep 2005 17:35:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 13 Sep 2005 17:35:04 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Sep 13 19:35:01 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EFEeT-0004dU-Kh for geh-help-gnu-emacs@m.gmane.org; Tue, 13 Sep 2005 19:33:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EFEeT-0005SZ-0M for geh-help-gnu-emacs@m.gmane.org; Tue, 13 Sep 2005 13:33:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EFEcY-0004lO-E7 for help-gnu-emacs@gnu.org; Tue, 13 Sep 2005 13:31:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EFEcX-0004kX-2e for help-gnu-emacs@gnu.org; Tue, 13 Sep 2005 13:31:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EFEcW-0004k5-JC for help-gnu-emacs@gnu.org; Tue, 13 Sep 2005 13:31:00 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1EFEbj-0007a5-Lu for help-gnu-emacs@gnu.org; Tue, 13 Sep 2005 13:30:11 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EFEZi-00039Q-SO for help-gnu-emacs@gnu.org; Tue, 13 Sep 2005 19:28:06 +0200 Original-Received: from 207.167.42.60 ([207.167.42.60]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Sep 2005 19:28:06 +0200 Original-Received: from ihs_4664 by 207.167.42.60 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Sep 2005 19:28:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: help-gnu-emacs@gnu.org Original-Lines: 43 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 207.167.42.60 User-Agent: Mozilla Thunderbird 0.9 (X11/20041105) X-Accept-Language: en-us, en In-Reply-To: X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:29446 Archived-At: Ilya Zakharevich wrote: > ], who wrote in article <85d5nfe3oy.fsf@lola.goethe.zz>: >>M-* runs the command pop-tag-mark >> which is an interactive compiled Lisp function in `etags'. >>It is bound to M-*. >>(pop-tag-mark) >> >>Pop back to where M-. was last invoked. >> >>This is distinct from invoking M-. with a negative argument >>since that pops a stack of markers at which tags were found, not from >>where they were found. > > a) Can't parse your last paragraph; That last paragraph is part of pop-tag-mark's doc string. To me it means that if at buffer/point A you move to tag X, then at buffer/point B you move to tag Y, then at buffer/point C you move to tag Z, then at buffer/point D: M-- M-. will take you back to Z, Y, then X M-* will take you back to C, B, then A > b) I vaguely remember indeed somebody wanting to propagate the code > from imenu-go back into etags; it may be that pop-tag-mark has the > functionality of imenu-go (at least when imenu-go works with tags; > it can get info where-to-jump from other sources too). > > c) My experience with my code propagated back to Emacs is very > negative: a lot of times the resulting code has only subset of > the original functionality. So I have no incentive to check how > well pop-tag-mark behaves... According to etc/NEWS, pop-tag-mark was introduced in Emacs 20.4, but I can't find any reference to imenu-go in the etc/*NEWS files. Absent any evidence in the lisp/ChangeLog* files that pop-tag-mark was derived from your imenu-go, I think you have plenty of incentive to find out whether it meets your requirements (and thus obviates your complaint about a "gaping hole in the Emacs UI"). Thanks, -- Kevin Rodgers