From: Felician Nemeth <felician.nemeth@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 61072@debbugs.gnu.org, Wei-Ting Lin <linwaytin@gmail.com>
Subject: bug#61072: How to change the length of the separation lines in eldoc, used by eglot?
Date: Tue, 28 Mar 2023 17:16:00 +0200 [thread overview]
Message-ID: <87o7oc6h5b.fsf@betli.tmit.bme.hu> (raw)
In-Reply-To: <87wn37ceo6.fsf@gmail.com> ("João Távora"'s message of "Thu, 23 Mar 2023 21:59:21 +0000")
João Távora <joaotavora@gmail.com> writes:
> See docstring of eldoc-documentation-functions.
The docstring is quite easy to follow. Nice work.
> I stopped short of adding :content-type there. There's not much point
> in moving rendering from Eglot to ElDoc if the rendering is going to
> suck just as bad. So I think this has to be analyzed carefully. Here
> are some ideas:
>
> 1. Use eww to render HTML, as you suggest. But how to get that HTML?
> Call an external process?
My idea was to leave the door open for a potential ElDoc backend that
produces raw HTML documentation. But it is a half-backed idea. I don't
know how images should be specified. Just as an IMG tag: <img
src="example.jpg">. Or inline like in an email.
If I understood correctly, one of your original ideas was to let ElDoc
backends (Eglot) to specify a flag whether the documentation was in
markdown format. Using terminology of the
eldoc-documentation-functions, I simply suggested a :content-type key to
generalize the markdown flag hoping Emacs had helper functions to help
handling a content-type specification.
Unfortunately, I now see a small problem with the :content-type
approach. How should Eglot know whether ElDoc can render a markdown
formatted documentation? If Eglot can request the documentation in
multiple formats, how it should know which one to choose.
> 2. You seem to suggest that eww can render markdown directly. Sure?
This is a misunderstanding. I didn't intend to suggest that.
> 3. Lobby for markdown.el to become more render-friendly, (remove hard
> newlines from paragraphs, remove invisible text, etc.)
Sure, but can a better markdown.el solve the original issue? Is there a
way to render a separation line independently of the current
window-width?
> 4. Make a new Markdown mode based on a tree-sitter grammar
I think a simple mode just to view a markdown document would be useful.
However, tree-sitter only helps parse a document. Turning an abstract
syntax tree into a viewable Emacs buffer is still a substantial work, I
suppose.
Felicián
next prev parent reply other threads:[~2023-03-28 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 1:42 bug#61072: How to change the length of the separation lines in eldoc, used by eglot? Wei-Ting Lin
2023-01-26 11:12 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-27 1:08 ` Wei-Ting Lin
2023-02-09 17:05 ` Felician Nemeth
2023-02-18 15:08 ` Wei-Ting Lin
2023-02-21 17:11 ` Felician Nemeth
2023-02-21 17:19 ` João Távora
2023-03-15 12:07 ` Felician Nemeth
2023-03-23 21:59 ` João Távora
2023-03-28 15:16 ` Felician Nemeth [this message]
2023-03-28 22:27 ` João Távora
2023-03-29 17:48 ` Felician Nemeth
2023-03-29 23:59 ` Yuan Fu
2023-04-08 8:52 ` Felician Nemeth
2023-04-08 9:10 ` João Távora
2023-03-23 21:53 ` João Távora
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7oc6h5b.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=61072@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=linwaytin@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.