unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "J.P." <jp@neverwas.me>
To: 67032-done@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#67032: 30.0.50; ERC 5.6-git: Treat erc-send-message more responsibly
Date: Mon, 13 Nov 2023 12:11:10 -0800	[thread overview]
Message-ID: <87fs19za5d.fsf__17746.6191047401$1699906407$gmane$org@neverwas.me> (raw)
In-Reply-To: <87h6lt850d.fsf@neverwas.me> (J. P.'s message of "Fri, 10 Nov 2023 17:15:14 -0800")

"J.P." <jp@neverwas.me> writes:

> v2. Revive `erc-command-indicator' functionality as new module.
>
> [...]
>
> but the damage had long since been done. My point in drudging this up is

dredging*

> merely to highlight where the behavior concerned diverged and that we'll
> likely never know why. I really have no interest in relitigating ancient
> motivations and methods. (It's quite possible that discussions did take
> place elsewhere, like on Freenode or the old sourceforge list.)
>
> Anyway, since both the interface (options, fonts) and infrastructure are
> still in place, I think it behooves us to revive this functionality, not
> least as a signal to others that ERC picks up after itself (eventually).
> I've thus added some changes to this effect (see last patch).

This has been installed as

  1d2aa130cae * Revive erc-command-indicator as new module

And changes similar to those initially proposed can be found in and
around

  174b3dd9bd7 * Make nested input handling more robust in ERC

Thanks and closing.





  parent reply	other threads:[~2023-11-13 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v8aa9wd0.fsf@neverwas.me>
2023-11-11  1:15 ` bug#67032: 30.0.50; ERC 5.6-git: Treat erc-send-message more responsibly J.P.
     [not found] ` <87h6lt850d.fsf@neverwas.me>
2023-11-13 20:11   ` J.P. [this message]
     [not found]   ` <87fs19za5d.fsf@neverwas.me>
2024-03-14  2:11     ` J.P.
     [not found]     ` <878r2l5zql.fsf@neverwas.me>
2024-03-28 17:34       ` J.P.
2023-11-10  2:26 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='87fs19za5d.fsf__17746.6191047401$1699906407$gmane$org@neverwas.me' \
    --to=jp@neverwas.me \
    --cc=67032-done@debbugs.gnu.org \
    --cc=emacs-erc@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).