From: Lars Ingebrigtsen <larsi@gnus.org>
To: "J.P." <jp@neverwas.me>
Cc: 54826@debbugs.gnu.org, emacs-erc@gnu.org
Subject: bug#54826: 29.0.50; Prevent duplicate prompts when reconnecting in ERC
Date: Sun, 10 Apr 2022 14:36:31 +0200 [thread overview]
Message-ID: <8735ilqfn4.fsf__34687.7293007978$1649594243$gmane$org@gnus.org> (raw)
In-Reply-To: <87pmlqgfvg.fsf@neverwas.me> (J. P.'s message of "Sat, 09 Apr 2022 13:29:23 -0700")
"J.P." <jp@neverwas.me> writes:
> The proposed patch leverages a long abandoned option called
> `erc-hide-prompt' to help address both these concerns.
Makes sense to me.
> 1. Currently, channels and queries are lumped together as 'target'. What
> about changing the shape of the option to a set of {'server',
> 'channel', 'query'} in a union with t for "all of the above" (to
> preserve compatibility)?
Sure.
> Is overloading the "prompt hidden" indicator with multiple meanings
> too distracting? (Currently, it means both "disconnected" and
> "physically connected but possibly not resumable".) Should we instead
> just reveal the prompt for all queries upon reconnecting, even though
> it may not be possible to continue certain conversations? Would it be
> worth accommodating both behaviors via yet another knob (or perhaps
> different 'query' variants, when going with 1, above)?
I think a new knob would be probably be preferable.
> 2. Right now, the prompt looks like this when hidden:
>
> n-1 | *** ERC finished *** [04:30]
> n | >_
>
> Where _ is the cursor at point max. Should we leave a space after the
> ">"?
I think having a space there would be good.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next parent reply other threads:[~2022-04-10 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pmlqgfvg.fsf@neverwas.me>
2022-04-10 12:36 ` Lars Ingebrigtsen [this message]
[not found] ` <8735ilqfn4.fsf@gnus.org>
2022-04-29 13:08 ` bug#54826: 29.0.50; Prevent duplicate prompts when reconnecting in ERC J.P.
2022-04-09 20:29 J.P.
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='8735ilqfn4.fsf__34687.7293007978$1649594243$gmane$org@gnus.org' \
--to=larsi@gnus.org \
--cc=54826@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
/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).