From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Cc: Danny Freeman <danny@dfreeman.email>
Subject: Re: Parsing JDT:// scheme in Eglot
Date: Mon, 14 Nov 2022 14:54:30 -0500 [thread overview]
Message-ID: <jwvh6z1s49j.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87mt8u39g4.fsf@alshehhi.io
Husain Alshehhi [2022-11-13 20:07:10] wrote:
> After investigating the issue, this appears to be because JDT returns paths
> on the format `jdt://' which eglot is not able to interpret. Eglot takes
> them as normal files, opens them, which end up to be an empty file (since it
> does not correspond to a file in the filesystem.)
Sounds like something similar to what Jarchive
(http://elpa.gnu.org/packages/jarchive.html) does for other URLs.
Maybe Jarchive`could try and handle that as well?
(I don't think it does right now)
Stefan
next prev parent reply other threads:[~2022-11-14 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 20:07 Parsing JDT:// scheme in Eglot Husain Alshehhi
2022-11-14 19:54 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-14 23:11 Danny Freeman
2022-11-16 6:18 ` Husain Alshehhi
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=jwvh6z1s49j.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=danny@dfreeman.email \
--cc=monnier@iro.umontreal.ca \
/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.
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).