From: Stefan Kangas <stefankangas@gmail.com>
To: emacs-devel@linabee.uk
Cc: emacs-devel@gnu.org
Subject: Re: Eglot rename, create, delete support
Date: Thu, 26 Sep 2024 06:20:47 -0700 [thread overview]
Message-ID: <CADwFkmkx3qagE8MjALrk4bsi+fvKpfhWnT4uGQCkU6oJ=dgHtA@mail.gmail.com> (raw)
In-Reply-To: <D3DF43A3-F46D-48FE-A266-EFD82B3B3211@linabee.uk>
emacs-devel@linabee.uk writes:
> On 22 September 2024 12:46:37 BST, Stefan Kangas <stefankangas@gmail.com> wrote:
>>I didn't see anyone followup to your email from March, so I'm sending
>>this form to you now. Sorry for the delay.
>
> Hi Stefan, unfortunately me and FSF legal ran into a roadblock with
> regard to my university's IP policy. I've attempted to retrofit the
> functionality into Eglot using a bunch of advices, but didn't get
> anywhere before it turned out I didn't need to write Java anymore and
> so I lost interest. I'm probably going to end up writing more Java in
> the near future so I will probably get back to that when the need
> arises, but in the meantime if any hooks could be written into Eglot
> to make this easier I'm happy to elaborate on what I wish I could do
> with Eglot without advices.
We are usually forthcoming when it comes to adding hooks that are
motivated by concrete use cases, indeed. I'd recommend sending this
feature request to the bug tracker, detailing which hooks you need, and
let's take it from there.
next prev parent reply other threads:[~2024-09-26 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:00 Eglot rename, create, delete support me
2024-09-22 11:46 ` Stefan Kangas
[not found] ` <CADwFkmnjtKog0Pr7Bzs6V80NBJp4Q2i2-uMWGy0v8B76DfH=Tw@mail.gmail.com>
2024-09-26 10:14 ` emacs-devel
2024-09-26 13:20 ` Stefan Kangas [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 19:18 Lina Bhaile
2024-03-04 20:14 ` Eli Zaretskii
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='CADwFkmkx3qagE8MjALrk4bsi+fvKpfhWnT4uGQCkU6oJ=dgHtA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-devel@linabee.uk \
/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).