From: Eric Hanchrow <eric.hanchrow@gmail.com>
To: Deniz Dogan <deniz@dogan.se>
Cc: 11592@debbugs.gnu.org
Subject: bug#11592: [PATCH] prevent accidental pastes in ERC
Date: Thu, 31 May 2012 17:07:26 -0700 [thread overview]
Message-ID: <CAHZoxq8XQdN_WvMKTvej-UQm_x=kz0Lv3Lzu70iS8+ZUuu_OgQ@mail.gmail.com> (raw)
In-Reply-To: <4FC7CFC1.3020505@dogan.se>
If I accidentally paste into a shell buffer, I (generally) harm nobody
but myself. But if I accidentally paste into an IRC buffer, I can
annoy everybody on that channel. I've done it many times, and it
happens to other people often too.
On Thu, May 31, 2012 at 1:08 PM, Deniz Dogan <deniz@dogan.se> wrote:
> Glenn Morris skrev 2012-05-31 21:24:
>
>>
>> Perhaps you could give the motivation/explanation for this change.
>> Why are accidental pastes into an erc buffer more of an issue than for
>> say, a shell buffer?
>>
>
> Accidentally pasting (and thereafter sending) large amounts of data on an
> IRC server will in many cases cause you to either be disconnected due to
> "excess flood" and in other cases, where some anti-flood client setting
> prevents that, just cause lots of disruption in the IRC channel.
>
> Having said that: I don't really know how suitable this patch is.
next prev parent reply other threads:[~2012-06-01 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHZoxq-3j2ksOMRsL9UEitu3oEjk0ro1CKoOfUhcUGeZtsQv9w@mail.gmail.com>
2012-05-31 0:32 ` bug#11592: [PATCH] prevent accidental pastes in ERC Eric Hanchrow
2012-05-31 19:24 ` Glenn Morris
2012-05-31 20:08 ` Deniz Dogan
2012-06-01 0:07 ` Eric Hanchrow [this message]
2012-06-02 7:39 ` Chong Yidong
[not found] ` <CAHZoxq8yfAYwp_LH0nMnsw-QAg9pX9AVEnLCXos7N0yTgAVeDQ@mail.gmail.com>
2012-06-10 22:04 ` bug#11592: Fwd: " Eric Hanchrow
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='CAHZoxq8XQdN_WvMKTvej-UQm_x=kz0Lv3Lzu70iS8+ZUuu_OgQ@mail.gmail.com' \
--to=eric.hanchrow@gmail.com \
--cc=11592@debbugs.gnu.org \
--cc=deniz@dogan.se \
/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).