From: <rsbecker@nexbridge.com>
To: "'D. Ben Knoble'" <ben.knoble@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] Strange git notes completion behaviour
Date: Tue, 21 Oct 2025 17:52:38 -0400 [thread overview]
Message-ID: <013201dc42d5$07a71550$16f53ff0$@nexbridge.com> (raw)
In-Reply-To: <CALnO6CD8JU2qMCnC=qQmNOV6Wy1ZnveT3tRxUz1E0LVMj5oU9w@mail.gmail.com>
On October 21, 2025 5:33 PM, D. Ben Knoble wrote:
>On Tue, Oct 21, 2025 at 5:07 PM <rsbecker@nexbridge.com> wrote:
>>
>> Hi All,
>>
>> I tried the following in git 2.51.0 on NonStop (big endian x86):
>>
>> git notes add -m "Test Note" HEAD
>> git notes show HEAD
>>
>> The git notes show reports a completion code of 037777777764 (-12).
>> This gets hidden by bash, which truncates negative results so it shows
>> as 0, not -12.
>> This
>> only seems to happen in git notes show, not any other commands or
>> sub-commands. I checked in gdb and this is in fact happening. Anywhere
>> I can look to try to find where this is failing?
>>
>> --Randall
>
>Exit code or shell (tab) completion? I'm a bit confused, so maybe someone else is,
>too.
It is the exit code. When in gdb, the return from notes is -12 as above. By the time
It gets back to bash, the lower bytes are dropped so I end up with a 0xFF, which
bash thinks is a 0, so the exit code is hidden from view. I tried the !!fn construct
in a standard alone test program with no wisdom gained.
next prev parent reply other threads:[~2025-10-21 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 21:06 [BUG] Strange git notes completion behaviour rsbecker
2025-10-21 21:32 ` D. Ben Knoble
2025-10-21 21:52 ` rsbecker [this message]
2025-10-22 9:27 ` Jeff King
2025-10-22 14:27 ` rsbecker
2025-10-23 12:48 ` Jeff King
2025-10-24 17:33 ` rsbecker
2025-10-24 17:46 ` Jeff King
2025-10-24 18:38 ` rsbecker
2025-10-24 18:52 ` Jeff King
2025-10-24 19:02 ` rsbecker
2025-10-24 20:16 ` Jeff King
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='013201dc42d5$07a71550$16f53ff0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.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.
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).