unofficial mirror of bug-gnu-emacs@gnu.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 09:29:28 +0300	[thread overview]
Message-ID: <83czoeyalz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk+ooQLiaGMdar+7GR7B-wfc_5do5AtnUhgt8LBjVEEFw@mail.gmail.com> (message from Stefan Kangas on Fri, 8 Oct 2021 17:36:04 -0400)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 8 Oct 2021 17:36:04 -0400
> Cc: "Eric M. Ludlam" <zappo@gnu.org>
> 
>     (defcustom speedbar-use-imenu-flag t
>       "Non-nil means use imenu for file parsing, nil to use etags.
>     XEmacs prior to 20.4 doesn't support imenu, therefore the default is to
>     use etags instead.  Etags support is not as robust as imenu support."
>     :tag "Use Imenu for tags"
>     :group 'speedbar
>     :type 'boolean)
> 
> Is there any reason to keep the etags support around, or should we
> install something like the attached patch?

I see no reason to remove etags support.  I also don't understand the
"Etags support is not as robust as imenu support" part of the doc
string.





  reply	other threads:[~2021-10-09  6:29 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 [this message]
2021-10-09  7:08   ` Stefan Kangas
2021-10-09  7:52     ` Eli Zaretskii
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

  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=83czoeyalz.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 public inbox

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

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).