From: Yuan Fu <casouri@gmail.com>
To: 62029@debbugs.gnu.org
Subject: bug#62029: 29.0.60; Allow users to customize eldoc buffer separator
Date: Mon, 6 Mar 2023 23:56:08 -0800 [thread overview]
Message-ID: <E7BDE4D5-CE96-43C6-9A79-6C6ECC0FEF13@gmail.com> (raw)
Eldoc can combine documentation from multiple sources and display them
together, however, if I’m not mistaken, it separates them with newline. It would be nice
if users can customize the separator to be some other things, like a
horizontal bar, eg,
(setq eldoc-source-separator
(propertize "----------"
'display '(space :width text)
'face '(:stike-through t)))
Maybe even allow it to be a function so we can draw an appropriate
number of "-" in terminals.
Prompted by this report: https://github.com/casouri/eldoc-box/issues/61
I can do it, if everyone agrees that this is a good idea, and can come
up with a good name for the variable ;-)
next reply other threads:[~2023-03-07 7:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 7:56 Yuan Fu [this message]
2023-03-08 0:25 ` bug#62030: 29.0.60; Allow users to customize eldoc buffer separator Yuan Fu
2023-03-08 17:14 ` bug#62029: " João Távora
2023-03-08 21:28 ` Yuan Fu
2023-03-23 21:33 ` João Távora
2023-03-24 0:12 ` Yuan Fu
2023-03-24 17:44 ` João Távora
2023-03-25 3:04 ` Yuan Fu
2023-03-25 8:10 ` João Távora
2023-03-30 5:22 ` Yuan Fu
2023-03-30 8:13 ` João Távora
2023-03-30 8:25 ` Yuan Fu
2023-04-11 0:04 ` Dmitry Gutov
2023-04-11 11:25 ` João Távora
2023-04-12 1:38 ` Dmitry Gutov
2023-04-12 11:06 ` João Távora
2023-04-13 0:20 ` Dmitry Gutov
2023-04-13 4:20 ` Yuan Fu
2023-04-13 9:50 ` João Távora
2023-04-13 10:11 ` João Távora
2023-04-13 10:48 ` João Távora
2023-04-13 21:53 ` Dmitry Gutov
2023-04-13 22:13 ` Dmitry Gutov
2023-04-13 23:01 ` João Távora
2023-04-13 23:26 ` Dmitry Gutov
2023-04-14 0:04 ` João Távora
2023-04-14 23:50 ` Dmitry Gutov
2023-04-15 9:41 ` João Távora
2023-10-23 1:39 ` Dmitry Gutov
2023-04-18 0:47 ` Dmitry Gutov
2023-04-18 11:17 ` João Távora
2023-04-18 23:05 ` 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=E7BDE4D5-CE96-43C6-9A79-6C6ECC0FEF13@gmail.com \
--to=casouri@gmail.com \
--cc=62029@debbugs.gnu.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).