unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	"Eli Zaretskii" <eliz@gnu.org>,
	emacs-erc@gnu.org, bandali@gnu.org, 54458@debbugs.gnu.org
Subject: bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow
Date: Sat, 07 May 2022 22:16:40 -0300	[thread overview]
Message-ID: <87sfpk4ydj.fsf__35509.3679785327$1651972671$gmane$org@gmail.com> (raw)
In-Reply-To: <874k22zu7s.fsf@neverwas.me> (J. P.'s message of "Fri, 06 May 2022 06:06:15 -0700")

Hello J.P.,

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

> And without more insight into what's going on precisely with your
> inputs, I don't think there's a whole lot we can do beyond speculate.
> So, in the end, I guess I'm just asking you to suffer the status quo on
> this one.

No problem! Your patches solved the main problem I was facing, so the
small inconvenience of an unresponsive Emacs for very short periods of
time doesn't affect my experience that much.

> If you're able to try these, great. If not, no worries.

Although with these new suggested changes, which I applied, I was able
to perform several large file transfers (about twenty in total, divided
in five blocks of four simultaneous transfers) without experiencing any
loss of control from Emacs!

In all transfers I used the `-t' and `-s' flags (although I think the
sender doesn't support the SSEND detection).

> I'll leave them for a bit anyhow to focus on our main
> initiatives. Thanks for bearing with me all these weeks (and with ERC
> all these years)!

I wish all the luck for these main initiatives of yours and I would like
to take this opportunity to thank you for your patience and your
commitment to solve the problem, including the inconveniences that arose
with the first solution proposed.

I hope the ERC team implements your suggested changes.

Thanks!

-- 
Regards,
Fernando de Morais.





  parent reply	other threads:[~2022-05-08  1:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 22:59 bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow Fernando de Morais
2022-03-21 14:09 ` J.P.
2022-03-22 13:50   ` Fernando de Morais
2022-03-22 14:36     ` Eli Zaretskii
     [not found]       ` <87tubj1eq4.fsf@gmail.com>
2022-03-27 17:56         ` Eli Zaretskii
2022-03-27 22:09           ` Fernando de Morais
2022-03-27 20:54 ` Mattias Engdegård
2022-03-28  9:23   ` Mattias Engdegård
2022-03-28 11:14     ` Eli Zaretskii
2022-03-28 12:08       ` J.P.
2022-03-29 15:49         ` Mattias Engdegård
2022-03-29 16:45           ` Eli Zaretskii
2022-03-29 17:47             ` Mattias Engdegård
2022-03-29 19:44               ` J.P.
2022-03-30  4:02                 ` J.P.
     [not found]                 ` <87mth8rst7.fsf@neverwas.me>
2022-03-30 15:28                   ` Mattias Engdegård
2022-03-31 19:18                     ` J.P.
     [not found]                     ` <87sfqygccz.fsf@neverwas.me>
2022-04-03 17:20                       ` Fernando de Morais
2022-04-03 19:46                         ` J.P.
     [not found]                         ` <87wng67xxd.fsf@neverwas.me>
2022-04-10 21:31                           ` J.P.
     [not found]                           ` <875yng39sa.fsf@neverwas.me>
2022-04-11  3:17                             ` J.P.
     [not found]                             ` <87sfqkz4ts.fsf@neverwas.me>
2022-04-25  0:59                               ` Fernando de Morais
     [not found]                               ` <87ilqyrn9s.fsf@gmail.com>
2022-04-25 12:08                                 ` J.P.
     [not found]                                 ` <878rrtz7or.fsf@neverwas.me>
2022-04-29 14:51                                   ` Fernando de Morais
     [not found]                                   ` <87r15guen2.fsf@gmail.com>
2022-04-30 13:39                                     ` J.P.
     [not found]                                     ` <87ilqqy9km.fsf@neverwas.me>
2022-05-04 13:03                                       ` Fernando de Morais
     [not found]                                       ` <87pmkth2lr.fsf@gmail.com>
2022-05-06 13:06                                         ` J.P.
     [not found]                                         ` <874k22zu7s.fsf@neverwas.me>
2022-05-08  1:16                                           ` Fernando de Morais [this message]
     [not found]                                           ` <87sfpk4ydj.fsf@gmail.com>
2022-05-11 14:29                                             ` J.P.
     [not found]                                             ` <87ee10xhw3.fsf@neverwas.me>
2022-05-23  1:22                                               ` J.P.
2022-04-01  6:32                   ` 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='87sfpk4ydj.fsf__35509.3679785327$1651972671$gmane$org@gmail.com' \
    --to=fernandodemorais.jf@gmail.com \
    --cc=54458@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    --cc=mattiase@acm.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).