From: Anand Tamariya <atamariya@gmail.com>
To: Pankaj Jangid <p4j@j4d.net>
Cc: emacs-devel@gnu.org
Subject: Re: GNU Emacs as a lightweight Java IDE (Debugging)
Date: Fri, 13 Dec 2019 10:19:48 +0530 [thread overview]
Message-ID: <CADm7Y4m5w-xM5vqyNtbPdMC126+snEU+sxC2dJGcQH+UTPrQ6g@mail.gmail.com> (raw)
In-Reply-To: <0100016efd62b4a3-15d5b9f3-37d5-4f4c-9ee4-7a768e98ea35-000000@email.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
> What difference the LSPs make? There are so many options in that area -
> Eclipse, IntelliJ servers. Do they have some advantage or is it just a
> fad?
>
IMHO LSP is to VSCode what CEDET Semantic is to Emacs. Only CEDET is a
tad better and it predates LSP by almost two decades.
LSP offloads all language related editing to a language specific external
service. This overlooks the fact that programming languages are more
similar in their structure than there are differences. CEDET seems to have
beautifully captured this idea. For a demo, I've been able to use the
refactoring logic to extract method that I'd written for Java to refactor
Elisp code!!
For further discussion on the subject, you might want to go through this
thread
https://sourceforge.net/p/cedet/mailman/cedet-semantic/?viewmonth=201911
[-- Attachment #2: Type: text/html, Size: 1130 bytes --]
next prev parent reply other threads:[~2019-12-13 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 8:48 GNU Emacs as a lightweight Java IDE (Debugging) Anand Tamariya
2019-12-11 8:56 ` Anand Tamariya
2019-12-12 3:27 ` Richard Stallman
2019-12-12 5:20 ` Anand Tamariya
2019-12-12 13:38 ` Pankaj Jangid
2019-12-13 0:24 ` Anand Tamariya
2019-12-13 3:52 ` Pankaj Jangid
2019-12-13 4:49 ` Anand Tamariya [this message]
2019-12-13 10:11 ` Pankaj Jangid
2019-12-26 14:09 ` Alex Ott
2019-12-13 4:26 ` Richard Stallman
2019-12-13 4:38 ` Anand Tamariya
2019-12-14 4:20 ` Richard Stallman
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=CADm7Y4m5w-xM5vqyNtbPdMC126+snEU+sxC2dJGcQH+UTPrQ6g@mail.gmail.com \
--to=atamariya@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p4j@j4d.net \
/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).