all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: zappo@gnu.org, 51102@debbugs.gnu.org
Subject: bug#51102: [PATCH] Make speedbar XEmacs compatibility mode obsolete (etags)
Date: Sat, 09 Oct 2021 10:52:21 +0300	[thread overview]
Message-ID: <835yu6y6ru.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmCJWKapTH7AP9KuQG=hAo68H5DrHv_cAA=orX-P4hpbA@mail.gmail.com> (message from Stefan Kangas on Sat, 9 Oct 2021 00:08:06 -0700)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 9 Oct 2021 00:08:06 -0700
> Cc: 51102@debbugs.gnu.org, zappo@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I also don't understand the "Etags support is not as robust as imenu
> > support" part of the doc string.
> 
> The author seems to have held the opinion that etags is not relevant on
> Emacs:
> 
> ;;; Tag Management -- etags  (old XEmacs compatibility part)
> 
> That comment dates to 1998, when speedbar.el was first imported.

Yes, I've seen that.  I'd like the author to elaborate on that: what
exactly is not robust in the etags support by Speedbar?





  reply	other threads:[~2021-10-09  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 21:36 bug#51102: [PATCH] Make speedbar XEmacs compatibility mode obsolete (etags) Stefan Kangas
2021-10-09  6:29 ` Eli Zaretskii
2021-10-09  7:08   ` Stefan Kangas
2021-10-09  7:52     ` Eli Zaretskii [this message]
2021-10-10 16:31       ` Eric Ludlam
2021-10-10 17:51         ` Eli Zaretskii
2021-10-10 17:57           ` Eric Ludlam
2021-10-10 18:37             ` Eli Zaretskii
2021-10-10 20:16               ` Eric Ludlam
2021-10-11 14:18               ` Stefan Kangas
2021-10-11 15:57                 ` Eli Zaretskii
2022-09-12 11:11                 ` bug#51102: Document speedbar etags compatibility mode better Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835yu6y6ru.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51102@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    --cc=zappo@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.