From: Felician Nemeth <felician.nemeth@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: sebastian.poeplau@mailbox.org, adonovan@google.com,
62116@debbugs.gnu.org
Subject: bug#62116: RFE: eglot: support window.showDocument LSP RPC
Date: Tue, 09 May 2023 19:03:07 +0200 [thread overview]
Message-ID: <87h6sla14k.fsf@betli.tmit.bme.hu> (raw)
In-Reply-To: <CALDnm52V_B7p_Eg-VgzOcTpy206fEb1Z96xs4+5=aT3R3UBsmg@mail.gmail.com> ("João Távora"'s message of "Mon, 8 May 2023 17:36:43 +0100")
João Távora <joaotavora@gmail.com> writes:
>> Since it advances the status quo, can this be merged? If not, how
>> should we proceed?
>
> Haven't looked at it, but I'd say yes. However, Alan Donovan
> has replied recently, with a recipe showcasing his particular
> use case. I dont' have time to try it right now, but if you
> could try his recipe/use case with your solution, it would be
> great.
It requires to patch and recompile gopls, which would be too much effort
for me, unfortunately.
> One note that I didn't yet reply to is that IMO (likely in Alan's
> opinion too), it does make sense to raise the frame. The
> showDocument may indeed come from somewhere else which is not
> Emacs at all. I used to work with Common Lisp IDEs like that
> allowed the application being developed to issue requests to
> the editor and pop it up to the user. It was extremely convenient.
I've looked into this. The docstring of x-focus-frame says "If there is
no window system support, this function does nothing." However, this
command
emacs -Q -nw --eval "(x-focus-frame nil)"
errors out instead of doing nothing. But supporting the frame raising
feature is approximately as simple as
(let ((frame (window-frame (get-buffer-window buf t))))
(raise-frame frame)
(x-focus-frame frame))
However, I don't work with multiple frames, so I don't know whether the
all-frames parameter of the get-buffer-window should really be t. I
hope the latest patch can be merged as is, and someone with more
experience with multiple frames can later step in and provide an
additional patch for this extra feature.
Thanks.
next prev parent reply other threads:[~2023-05-09 17:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 15:34 bug#62115: RFE: eglot: support window.showDocument LSP RPC Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 15:40 ` bug#62116: " Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 12:56 ` João Távora
2023-03-11 13:17 ` Eli Zaretskii
2023-03-11 20:20 ` João Távora
2023-03-12 6:26 ` Eli Zaretskii
2023-04-22 9:08 ` Felician Nemeth
2023-05-05 6:03 ` Eli Zaretskii
2023-05-05 7:35 ` João Távora
2023-05-05 16:51 ` João Távora
2023-05-05 17:06 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 17:19 ` João Távora
2023-05-05 17:35 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 17:36 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-11 23:12 ` João Távora
2023-05-06 12:46 ` Felician Nemeth
2023-05-08 13:23 ` Felician Nemeth
2023-05-08 16:36 ` João Távora
2023-05-09 17:03 ` Felician Nemeth [this message]
2023-05-09 17:13 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-11 22:41 ` João Távora
2023-05-12 0:54 ` João Távora
2023-05-12 20:46 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-15 8:48 ` João Távora
2023-05-13 10:21 ` Felician Nemeth
2023-05-13 11:57 ` João Távora
2023-05-14 19:02 ` Felician Nemeth
2023-05-14 19:19 ` João Távora
2023-05-15 10:45 ` João Távora
2023-05-16 18:34 ` João Távora
2023-05-24 22:13 ` Alan Donovan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 1:03 ` Dmitry Gutov
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=87h6sla14k.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=62116@debbugs.gnu.org \
--cc=adonovan@google.com \
--cc=joaotavora@gmail.com \
--cc=sebastian.poeplau@mailbox.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).