From: David Kastrup <dak@gnu.org>
Subject: Re: etags: M-. jump to the tag(called func), but then how can i jump BACK(the calling line)?
Date: Sat, 17 Sep 2005 08:39:02 +0200 [thread overview]
Message-ID: <85r7bonqpl.fsf@lola.goethe.zz> (raw)
In-Reply-To: dgfpnv$1m1b$1@agate.berkeley.edu
Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
> [A complimentary Cc of this posting was sent to
> David Kastrup
> <dak@gnu.org>], who wrote in article <85acih4cmy.fsf@lola.goethe.zz>:
>> >> > This is a gaping hole in the Emacs UI. I wrote a package,
>> >> > imenu-go.el, which behaves "as expected".
>
>> >> Hardly.
>
>> This means the "gaping hole".
>
> Sorry that I was not clear enough: I understood this.
>
>> > a) Can't parse your last paragraph;
>>
>> It was just the online help.
>
> Kevin Rodgers provided a very nice roundup; can it replace this
> cryptic paragraph?
>
>> So you want to claim a deficiency in Emacs because you don't want to
>> try out the function and keybinding which it provides for that
>> purpose?
>
> Again, sorry that I was not clear enough. On the contrary, I'm very
> glad that finally, after more than a decade of bitching (while having
> the working code available!) this feature is finally available in the
> standard distribution. A lot of thanks for including it!
You could have cut your decade of bitching short. The function was
provided in 1998, more than 7 years ago.
> All that I said is that
>
> a) I have no incentive to check whether the Emacs 21.4
> implementation is sane; and
Well, then you should also have no incentive to bitch about it.
> b) that my prior experience does not allow for a lot of hope in
> "a" (I remember there was *some* tricky stuff to code in imenu-go;
> but the only thing which immeditely jumps to mind is not related
> to return-back functionality; so, contrary to what I wrote, it is
> quite possible that there is no pitfall to avoid...).
So you reserve the right for bitching without checking whether it is
warranted?
> Hope this helps,
I don't see how this helps with anything except giving a good idea how
serious to take any of your bitching in future.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-09-17 6:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 11:01 etags: M-. jump to the tag(called func), but then how can i jump BACK(the calling line)? zhengfish
2005-09-11 13:43 ` Ian Zimmerman
2005-09-11 14:57 ` Peter Lee
2005-09-11 20:39 ` Ilya Zakharevich
2005-09-11 20:42 ` David Kastrup
2005-09-13 7:14 ` Ilya Zakharevich
2005-09-13 8:04 ` David Kastrup
2005-09-17 0:58 ` Ilya Zakharevich
2005-09-17 6:39 ` David Kastrup [this message]
2005-09-18 1:05 ` Ilya Zakharevich
2005-09-18 7:00 ` Redo/Undo (was: etags: M-. jump to the tag(called func), ...) B. Smith
2005-09-19 14:07 ` etags: M-. jump to the tag(called func), but then how can i jump BACK(the calling line)? Stefan Monnier
[not found] ` <mailman.7386.1127026972.20277.help-gnu-emacs@gnu.org>
2005-09-19 21:52 ` Redo/Undo (was: etags: M-. jump to the tag(called func), ...) Ilya Zakharevich
2005-09-20 8:11 ` David Kastrup
2005-09-20 22:50 ` Ilya Zakharevich
2005-09-21 2:47 ` Redo/Undo Stefan Monnier
2005-09-13 17:26 ` etags: M-. jump to the tag(called func), but then how can i jump BACK(the calling line)? Kevin Rodgers
[not found] ` <mailman.6922.1126632664.20277.help-gnu-emacs@gnu.org>
2005-09-16 23:12 ` Ilya Zakharevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85r7bonqpl.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).