Re: What is the status of bash-5.3?

[Todd Zullinger]

Bruce Dubbs wrote:
> At the linuxfromscratch project, we document for users how to build a
> relatively complete Linux system from source code.  When we do this we
> consider bash to be one of the most important packages in the system.
> 
>   https://www.linuxfromscratch.org/lfs/view/stable/
> 
> Our policy is to use the most recent "stable" versions of applications (that
> is, no release candidates or git clones) when at all possible.  Right now we
> are using bash-5.2.37.  Recently gcc-15.1 was released and we would like to
> update our system to that, but bash-5.2.37 does not build with that version
> of gcc.

While this isn't an answer to your main question, building
bash-5.2.37 should only require adding '-std=gnu17'
to CFLAGS.  That's what the Fedora builds did when the
recent release added gcc-15:

https://src.fedoraproject.org/rpms/bash/blob/ddaa95f/f/bash.spec#_141-143

It's likely that other projects will take some time to catch
up and make releases which don't trip over the same issue,
so it may well be helpful to set -std=gnu17 for those which
aren't quite ready to support the defaults from the gcc-15.

-- 
Todd


signature.asc
Description: PGP signature

Re: Bash does not complete the filename once the situation becomes singular

[Chet Ramey]

On 5/12/25 8:04 PM, Adam Purkrt wrote:

GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
OS: Gentoo Linux


Originally met this while the download of iso file in firefox was
nearing completion, and I was preparing myself to move the
downloaded foobar.iso file elsewhere. I opened terminal with bash,
typed "mv foobar." in the Downloads dir and pressed . Two options
appeared: foobar.iso and and foobar.[somecode].iso.part. I kept pressing
, but after the download finished, with repeated presses bash kept 
displaying "foobar.iso" as a single option of completion and did not

complete to the already singular name.


This is (but see below) standard readline behavior. If the key
sequence for `complete' is entered two or more times in succession,
without changes to the line buffer in the meantime, readline executes
the equivalent of the `possible-completions' command.



Expected behaviour:

Bash should complete to "foobar.a" as soon as it is an unique option,
i.e. as soon as foobar.b is removed after 10 seconds. Offering a
singular option for completion does not make sense anyway.


I have changed readline in the past (readline-8.1) to insert a single
completion if the number of possible completions changes from 0 to 1,
when the previous complete command failed to produce any matches.

I may change it in the future to insert a single completion if the
number of possible completions changes from > 1 to 1. That will not
happen before bash-5.3, though.



Also, when, in the erroneous situation after the 10 seconds elapsed, the
"." at the end of filename is deleted and written again (visually the same 
situation) and then  is pressed, the completion succeeds.


Yes, you changed the line before attempting completion again.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/


OpenPGP_signature.asc
Description: OpenPGP digital signature