From: Akib Azmain Turja <akib@disroot.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: EBrowse obsolete?
Date: Thu, 21 Jul 2022 12:44:46 +0600 [thread overview]
Message-ID: <87y1wn0xsx.fsf@disroot.org> (raw)
In-Reply-To: <72125fc3-358c-2f89-1cb6-16c4ff18185e@gmail.com> ("Gerd Möllmann"'s message of "Thu, 21 Jul 2022 08:16:40 +0200")
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> I see that ebrowse is still in Emacs, which is something I wrote ~30 years
> ago.
>
> I wonder if that is still useful to anyone?
>
> Actually, in the time of language servers, ebrowse looks almost
> embarrasingly antiquated to me.
Do we have a similar functionality in Eglot? Though I use it, I'm not
sure, since I use it only for xref and completion. If we have such
feature in Eglot, then I would suggest to first add Eglot to core Emacs
and then obsolete ebrowse.
And what about CEDET?
--
Akib Azmain Turja
Find me on Mastodon at @akib@hostux.social.
This message is signed by me with my GnuPG key. It's fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-07-21 6:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 6:16 EBrowse obsolete? Gerd Möllmann
2022-07-21 6:44 ` Akib Azmain Turja [this message]
2022-07-21 12:46 ` CEDET obsolete? (was: Re: EBrowse obsolete?) Stefan Kangas
2022-07-21 13:00 ` CEDET obsolete? Po Lu
2022-07-22 10:26 ` Jose E. Marchesi
2022-07-22 13:26 ` Stefan Kangas
2022-07-23 11:44 ` CEDET obsolete? (was: Re: EBrowse obsolete?) Lynn Winebarger
2022-07-21 6:49 ` EBrowse obsolete? Po Lu
2022-07-21 7:26 ` Eli Zaretskii
2022-07-21 7:56 ` Bozhidar Batsov
2022-07-21 12:16 ` Zhiwei Chen
2022-07-21 8:16 ` Po Lu
2022-07-21 11:12 ` Gerd Möllmann
2022-07-21 11:44 ` Po Lu
2022-07-21 12:21 ` Dmitry Gutov
2022-07-21 12:28 ` Gerd Möllmann
2022-07-21 12:33 ` Akib Azmain Turja
2022-07-21 17:02 ` Yuri Khan
2022-07-21 12:15 ` Eli Zaretskii
2022-07-21 12:19 ` Dmitry Gutov
2022-07-21 12:28 ` Eli Zaretskii
2022-07-21 15:21 ` Stefan Monnier
2022-07-21 16:16 ` Visuwesh
2022-07-21 16:51 ` Stefan Monnier
2022-07-21 17:07 ` Visuwesh
2022-07-21 17:16 ` Jim Porter
2022-07-21 17:39 ` Stefan Monnier
2022-07-21 21:26 ` Jim Porter
2022-07-22 2:01 ` Tim Cross
2022-07-23 10:18 ` Michael Albinus
2022-07-24 23:25 ` Tim Cross
2022-07-22 14:29 ` Brian Cully via Emacs development discussions.
2022-07-22 17:22 ` Jim Porter
2022-07-23 10:35 ` Michael Albinus
2022-07-23 10:28 ` Michael Albinus
2022-07-23 10:13 ` Michael Albinus
2022-07-23 9:57 ` Michael Albinus
2022-07-23 14:36 ` Stefan Monnier
2022-07-23 15:04 ` Michael Albinus
2022-07-23 9:51 ` Michael Albinus
2022-07-22 1:06 ` Po Lu
2022-07-22 4:55 ` Gerd Möllmann
2022-07-22 5:15 ` tomas
2022-07-22 6:52 ` Eli Zaretskii
2022-07-22 1:35 ` Tim Cross
2022-07-21 12:58 ` Gerd Möllmann
2022-07-21 13:04 ` Eli Zaretskii
2022-07-21 13:16 ` Po Lu
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=87y1wn0xsx.fsf@disroot.org \
--to=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).