unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matheus Fillipe <matheusfillipeag@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: "emacs-erc@gnu.org" <emacs-erc@gnu.org>,
	"54536@debbugs.gnu.org" <54536@debbugs.gnu.org>
Subject: bug#54536: 29.0.50; Improve ERC's handling of multiline prompt input
Date: Sun, 3 Apr 2022 17:15:21 -0300	[thread overview]
Message-ID: <BA2B47B7-2D86-4BE8-991C-034778071AF8@getmailspring.com> (raw)
In-Reply-To: <87y20m7xzs.fsf@neverwas.me>

[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]

So far the patches seem to have fixed the issue I long had sending empty lines randomly.

Here are my replies to your questions.
1) erc-send-whitespace-lines was set to nil
2) Hmm no I don't have nothing quite unusual on erc that i can think of now. I have erc-nl-nicks.
3) Yes exactly nothing unusual about that.
4) I will since it seems to have "fixed" the issue so far. I will keep that in mind in case it happens again.

That one case was the only until now. Didn't happen again and I've tried to reproduce but would never happen, so I'm not sure if it really matters. I will keep testing.
On Apr 3 2022, at 4:44 pm, J.P. <jp@neverwas.me> wrote:
> Matheus Fillipe <matheusfillipeag@gmail.com> writes:
>
> > I've been testing this and as an evil-mode user I had a problem that
> > whenever I paste something or sometimes just out of the blue I would
> > send one empty line after my message. After a few hours using erc this
> > it only happened once but Im not able to reproduce it so... I think
> > this is a great addition and it solves my problem!
>
> Appreciate the feedback! (Although, we ought not settle for "it
> only happened once," if we can help it.) A few silly questions:
>
> 1. In your testing, what was the value of `erc-send-whitespace-lines'?
> 2. Do you have any unusual bindings or minor modes going (other than
> Evil)? Just asking to try and gauge whether it's worth doing
> something like an emacs -Q.
>
> 3. How do you send input normally? For example: switch to insert state,
> type stuff after the prompt, hit RET. Just asking in case I try
> recreating your setup.
>
> 4. Are you willing to keep testing it? If so and it happens again, can
> you try a `view-lossage' and maybe also a `report-emacs-bug', and
> just copy-paste all the generated facts into a reply?
>
> BTW, I guess the "reply" button on the MHonArc-generated bug-gnu-emacs
> pages doesn't do a "reply all" (or else there's some trick I don't know
> about to get it to include Cc participants).
>


[-- Attachment #2: Type: text/html, Size: 2355 bytes --]

       reply	other threads:[~2022-04-03 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y20m7xzs.fsf@neverwas.me>
2022-04-03 20:15 ` Matheus Fillipe [this message]
     [not found] <ADC23CE3-E6A4-4FF8-B033-174F60B2D59E@getmailspring.com>
2022-04-03 19:44 ` bug#54536: 29.0.50; Improve ERC's handling of multiline prompt input J.P.
2022-03-23 13:26 J.P.
2022-03-23 13:50 ` bug#54536: " Lars Ingebrigtsen
     [not found] ` <87czic93sa.fsf@gnus.org>
2022-03-24 19:50   ` J.P.
2022-03-24 20:16     ` Michael Albinus
     [not found]     ` <8735j7jecz.fsf@gmx.de>
2022-03-24 23:38       ` J.P.
     [not found]       ` <87tubm53ar.fsf@neverwas.me>
2022-03-25 15:29         ` Lars Ingebrigtsen
     [not found]         ` <874k3mf3th.fsf@gnus.org>
2022-03-25 19:23           ` J.P.
2022-03-26 16:44             ` Lars Ingebrigtsen
     [not found]   ` <87ee2rb04e.fsf@neverwas.me>
2022-03-25 15:31     ` Lars Ingebrigtsen
     [not found]     ` <87zgledp6a.fsf@gnus.org>
2022-03-25 19:20       ` J.P.
2022-04-23  3:17 ` J.P.
2022-04-29 13:05 ` J.P.
2022-05-17 13:10 ` J.P.
     [not found] ` <874k1os3te.fsf@neverwas.me>
2022-05-17 22:48   ` Will Mengarini via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <YoQmVCugPRXY58eO@eskimo.com>
2022-05-18  1:34     ` 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=BA2B47B7-2D86-4BE8-991C-034778071AF8@getmailspring.com \
    --to=matheusfillipeag@gmail.com \
    --cc=54536@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).