From: Corwin Brust <corwin@bru.st>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 43847@debbugs.gnu.org, Amin Bandali <bandali@gnu.org>
Subject: bug#43847: ERC - prevent yanking multiple lines into IRC (feature request) *patch*
Date: Sat, 10 Oct 2020 00:00:31 -0500 [thread overview]
Message-ID: <CAJf-WoTmrnjC=b_Rxhpn4NuqhE-Gt1V=rtbG5qFq+-JvR-f8Fg@mail.gmail.com> (raw)
In-Reply-To: <CAJf-WoQqPZaWGtzUhLKWG0p=Hz1VfO8jRUwh+87G-tcFe3zRKg@mail.gmail.com>
If you are using this patch please ROLLBACK. 😊
On Thu, Oct 8, 2020 at 9:01 PM Corwin Brust <corwin@bru.st> wrote:
>
> Many thanks, Noam.
>
> On Wed, Oct 7, 2020 at 11:05 AM Noam Postavsky <npostavs@gmail.com> wrote:
> >
> > I hope an ERC user will follow up (I think Bandali was going over ERC
> > patches at some point?), but just some general comments:
>
> I'm hoping Bandali and other ERC users will look, also. [...]
This has unpleasant results when the point is not immediately after
the ERC prompt, and likely in other cases I haven't found.
For a next pass I plan to:
* use `erc-display-line' instead of `insert'
* remove the new binding while we discuss ideal approaches
* create from master and see if I can I get tabs/spaces correct
* CC emacs-erc in hopes of soliciting more inputs
Thanks to Amin and others for discussions on IRC this evening.
Regards
Corwin
next prev parent reply other threads:[~2020-10-10 5: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 [this message]
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
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='CAJf-WoTmrnjC=b_Rxhpn4NuqhE-Gt1V=rtbG5qFq+-JvR-f8Fg@mail.gmail.com' \
--to=corwin@bru.st \
--cc=43847@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=npostavs@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).