From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Wesley <wesleys@opperschaap.net>, git@vger.kernel.org
Subject: Re: [[PATCH v2]] Fix bug when more than one readline instance is used
Date: Fri, 11 Aug 2023 09:05:48 -0700 [thread overview]
Message-ID: <xmqqjzu1o97n.fsf@gitster.g> (raw)
In-Reply-To: <20230811145121.GB2303200@coredump.intra.peff.net> (Jeff King's message of "Fri, 11 Aug 2023 10:51:21 -0400")
Jeff King <peff@peff.net> writes:
>> diff --git a/git-svn.perl b/git-svn.perl
>> index e919c3f172..6033b97a0c 100755
>> --- a/git-svn.perl
>> +++ b/git-svn.perl
>> @@ -427,7 +427,7 @@ sub ask {
>> my $default = $arg{default};
>> my $resp;
>> my $i = 0;
>> - term_init() unless $term;
>> + my $term = term_init();
>>
>> if ( !( defined($term->IN)
>> && defined( fileno($term->IN) )
>
> Hmm. Isn't that an indication that git-svn is OK as-is?
Yes. As long as we know they share the same kind of code structure
to use the same library function that wants its callers to stick to
a singleton instance, there is a value in using the same structure
on the side of our callers, but yes, we can rely on the global $term
for it being a singleton.
> It could still benefit from cleaning up FakeTerm, since we lazily init
> the object since 30d45f798d (git-svn: delay term initialization,
> 2014-09-14). But I don't think there's a visible bug here with the new
> version of Term::ReadLine::Gnu.
True. Let me drop the patch from the 'next down to master
fast-track' candidate status.
Thanks.
next prev parent reply other threads:[~2023-08-11 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:39 [PATCH] Fix bug when more than one readline instance is used Wesley Schwengle
2023-08-10 0:49 ` Jeff King
2023-08-10 1:18 ` [[PATCH v2]] " Wesley Schwengle
2023-08-10 14:31 ` Junio C Hamano
2023-08-10 15:14 ` Wesley
2023-08-11 1:01 ` Junio C Hamano
2023-08-11 1:09 ` Wesley
2023-08-11 5:30 ` Junio C Hamano
2023-08-11 14:51 ` Jeff King
2023-08-11 16:05 ` Junio C Hamano [this message]
2023-08-30 22:32 ` [PATCH] git-svn: drop FakeTerm hack Junio C Hamano
2023-08-31 0:13 ` Jeff King
2023-08-31 0:28 ` Junio C Hamano
2023-08-10 1:05 ` [PATCH] Fix bug when more than one readline instance is used Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqjzu1o97n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=wesleys@opperschaap.net \
/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.
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 NNTP newsgroup(s).