From: Brett Gilio <brettg@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: 43847@debbugs.gnu.org, "Lars Ingebrigtsen" <larsi@gnus.org>,
"Amin Bandali" <bandali@gnu.org>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: bug#43847: ERC - prevent yanking multiple lines into IRC (feature request) *patch*
Date: Fri, 09 Oct 2020 11:00:18 -0500 [thread overview]
Message-ID: <87blhbo0dp.fsf@debian> (raw)
In-Reply-To: <CAJf-WoQ94iYRZS6-gMZOprZd02_3FCCOwUeSXyzUyLbMQNO8bA@mail.gmail.com> (Corwin Brust's message of "Fri, 9 Oct 2020 10:41:26 -0500")
Corwin Brust <corwin@bru.st> writes:
> This hasn't come up for me outside IRC/ERC, that I can recall, but it
> definitely does makes sense to me that people would want an easy way
> to strip new-lines when yanking in contexts out-side IRC. Any thoughts
> as to the approach for this?
>
After giving it more thought, perhaps a prefix arg is the correct way to
go here. It would be enough that people would not experience a breaking
change. Or, it could be such that ERC alerts in the echo buffer that you
are about to send a multiline paste and ask if it should be sanitized?
Brett Gilio
next prev parent reply other threads:[~2020-10-09 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 14:11 bug#43847: ERC - prevent yanking multiple lines into IRC (feature request) *patch* Corwin Brust
2020-10-07 15:27 ` Noam Postavsky
2020-10-07 15:30 ` Corwin Brust
2020-10-07 16:05 ` Noam Postavsky
2020-10-09 2:01 ` Corwin Brust
2020-10-10 5:00 ` Corwin Brust
2020-10-07 16:56 ` Brett Gilio
2020-10-09 1:32 ` Corwin Brust
2020-10-09 1:59 ` Corwin Brust
2020-10-09 14:32 ` Brett Gilio
2020-10-09 4:54 ` Lars Ingebrigtsen
2020-10-09 7:52 ` Kévin Le Gouguec
2020-10-09 15:41 ` Corwin Brust
2020-10-09 16:00 ` Brett Gilio [this message]
2020-10-10 20:11 ` Lars Ingebrigtsen
2020-10-10 20:22 ` Brett Gilio
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=87blhbo0dp.fsf@debian \
--to=brettg@gnu.org \
--cc=43847@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=corwin@bru.st \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.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).