From: Yuan Fu <casouri@gmail.com>
To: Felician Nemeth <felician.nemeth@gmail.com>
Cc: 61072@debbugs.gnu.org, "Wei-Ting Lin" <linwaytin@gmail.com>,
"João Távora" <joaotavora@gmail.com>
Subject: bug#61072: How to change the length of the separation lines in eldoc, used by eglot?
Date: Wed, 29 Mar 2023 16:59:58 -0700 [thread overview]
Message-ID: <B706D121-921C-450F-A287-846B78829547@gmail.com> (raw)
In-Reply-To: <87fs9n5tz9.fsf@betli.tmit.bme.hu>
> On Mar 29, 2023, at 10:48 AM, Felician Nemeth <felician.nemeth@gmail.com> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
>>> 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?
>>
>> Yes, there is, with just the same code we use in eldoc now to separate
>> documentation from different backends.
>>
>> (concat "\n" (propertize "\n" 'face '(:inherit separator-line :extend
>> t)) "\n")
>
> Surprisingly, this does not work in the *scratch* buffer. It does work
> in a non elisp-mode buffer. I wonder why.
If font-lock-mode is on, it overwrites the ‘face property. I always apply both ‘face and ‘font-lock-face to be safe.
>
> make-separator-line is a bit more complicated than the code above.
> Would it make sense to use that when it's available? (I.e., Emacs 29 and
> above.)
>
>> I've mailed Jason Blevins, markdown.el maintainer but he hasn't
>> responded. Maybe make a bug report in the Github repo.
>
> Yuan Fu (CC'd) has already made one:
> https://github.com/jrblevin/markdown-mode/issues/753
The contributor thinks their fix for another problem also solves the issue I raised, but I don’t have the energy to argue with them.
Yuan
next prev parent reply other threads:[~2023-03-29 23:59 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
2023-03-28 22:27 ` João Távora
2023-03-29 17:48 ` Felician Nemeth
2023-03-29 23:59 ` Yuan Fu [this message]
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=B706D121-921C-450F-A287-846B78829547@gmail.com \
--to=casouri@gmail.com \
--cc=61072@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--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.