#1041702 git-email: crashes when returning from "edit"

Package:
git-email
Source:
git-email
Submitter:
David Bremner
Date:
2023-09-15 13:45:06 UTC
Severity:
normal
#1041702#5
Date:
2023-07-22 12:42:08 UTC
From:
To:

I can send patches OK, and if I pass --annotate, I can also edit them
before sending. If I fail to pass --annotate, but rather type 'e' for
edit, then on returning from the text editor (emacsclient, if it
matters), I get

Can't locate object method "IN" via package "FakeTerm" at /usr/lib/git-core/git-send-email line 962.

and the script exits.

- -- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages git-email depends on:
ii  git  1:2.40.1-1

Versions of packages git-email recommends:
ii  libauthen-sasl-perl    2.1600-3
ii  libemail-valid-perl    1.203-1
ii  libio-socket-ssl-perl  2.083-1
ii  libmailtools-perl      2.21-2
ii  libnet-smtp-ssl-perl   1.04-2
ii  perl                   5.36.0-7

Versions of packages git-email suggests:
pn  git-doc  <none>

- -- no debconf information
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS7zp8ACgkQA0U5G1Wq
FSFq7RAAoyPd6fekwpEZ9ifyy+c64uhNMVEDBqAmvA/qCniFZmquXQEvMfpp9pUA
8H3qZukmpzUxsXpbjDb1pnn/bDJSdRsHSSjS8f/P7SgD4bQgP8NOmx9lCjDLvo4f
IctgVDyPslo1IDhrwXgBfhAida23dea5y6fy86E5Z4d/WXMYvJ3Xp3t1DCP09KAT
6LK7vKlXYH4pdCSwTR7v2YC1LmJOkeBcHoHQwBef24WmLxpK5iwGzWPYI5xZJVHF
RV8fboVlvjBAvYMSurr0rHuBMealoQoL4gEa6ARWcTzFEls4c1gRuxRltPxXCJWu
07Z+bLT/z5goB8I4hNJ945jl17FRy96xj32j6/8mfsK72JzwpJD1hTg1HzUWiEoq
v35DO3v3znpQOOSLopS5QyrEuqB6hiLuvdhWJnlRNvYKRYnD2PzDEC+n7tzPJNRJ
bgrebnGyCLFl63PhOXxWJ5/ap4gYA30ZqqRaTNJMSznU1J2fNQlLLguaUTY4OFoO
Nrz8oaMXzJcIMq0j7logbg61hUTHBWSHT1Ea3arcvlM9UXIMOVauw6SR0h3u0whE
8xB0s02tefKbMPJP72sDBWKrhXQd54MrRv0nbvVLmidmWJLf4VX1Cmbpmncmkpqd
OA1I3+XeSsnB5ymlQU8pwWS1XJmjzF4glHluvvjlGAaeOfY/8EI=
=XQ9n
-----END PGP SIGNATURE-----
#1041702#10
Date:
2023-07-27 19:17:39 UTC
From:
To:
For me this seems to happen whenever I do not give an email address via
the "--to" option.  In this case, "git send-email" prompts

"To whom should the emails be sent (if anyone)?"

but no matter what I type, I get the exact same error as you.

This is basic stuff which must be used by thousands of people every day.
What is so special about our setups that it mysteriously fails?  Beside
this bug report, I have not found anything on the web.

Puzzled,
Sven
#1041702#15
Date:
2023-09-15 11:42:57 UTC
From:
To:
Sven Joachim <svenjoac@gmx.de> writes:

Hmm. I am seeing it when prompted for an 8bit encoding. I guess the
common theme is prompting.
#1041702#20
Date:
2023-09-15 12:55:35 UTC
From:
To:
David Bremner <david@tethera.net> writes:

prompted by Kibi on IRC, I observed that installing
libterm-readline-perl-perl and removing libterm-readline-gnu-perl
leads to

      Cannot create second readline interface, falling back to dumb.
      Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll):

this "dumb" seems to succeed.
#1041702#25
Date:
2023-09-15 13:44:34 UTC
From:
To:
David Bremner <david@tethera.net> writes:

And removing libterm-readline-perl-perl causes the warning messages to
go away. So maybe most people don't have these problems because they
don't have libterm-readline-*-perl installed.