From: Lars Ingebrigtsen <larsi@gnus.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Mathieu Marques <mathieumarques78@gmail.com>,
47109@debbugs.gnu.org
Subject: bug#47109: eldoc.el: Allow custom separator between documentations in the echo area
Date: Tue, 18 May 2021 15:39:56 +0200 [thread overview]
Message-ID: <87r1i4f9eb.fsf@gnus.org> (raw)
In-Reply-To: <CALDnm50RBsMOVWEswujO8=wjn6n70+rQjeW8UbwPBuo6sFPTMw@mail.gmail.com> ("João Távora"'s message of "Mon, 17 May 2021 16:44:57 +0100")
João Távora <joaotavora@gmail.com> writes:
> Thanks for the ping, Lars. I will read that bug, too. I hope to
> propose my own patch to solve this problem in the not so distant
> future.
>
> To be clear, I'm just slightly wary of introducing this patch, a limited
> way to solve this, if that means we would have to provide backward
> compatibility for it in case we want to move to a more robust system
> later on. Thing is, as far as I understand it, between two Emacs
> releases (i.e. in trunk) we're generally not obliged to provide this
> backward compatibility. But Eldoc is also distributed independently
> in ELPA releases, directly from trunk, and that may change things
> a bit. So erring on the side of caution here. Feel free to comment
> on the policy followed here.
Yeah, I understand the worries here -- especially since eldoc is such a
central feature in Emacs.
So waiting while you develop a more thorough solution here is fine by me.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-05-18 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 19:10 bug#47109: eldoc.el: Allow custom separator between documentations in the echo area Mathieu Marques
2021-03-12 21:13 ` Basil L. Contovounesios
2021-03-13 12:26 ` Mathieu Marques
2021-03-13 14:02 ` Basil L. Contovounesios
2021-03-13 14:35 ` João Távora
2021-03-18 18:30 ` Mathieu Marques
2021-05-17 15:37 ` Lars Ingebrigtsen
2021-05-17 15:44 ` João Távora
2021-05-18 13:39 ` Lars Ingebrigtsen [this message]
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=87r1i4f9eb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47109@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=joaotavora@gmail.com \
--cc=mathieumarques78@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 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).