Are you excited for the upcoming BASH release? I'm literally steaming with anticipation.
>This release fixes several outstanding bugs in bash-5.2 and introduces
>a number of new features. There are significant new features of note:
>* There is a new form of command substitution that executes the command in
> the current shell execution context. Two forms are implemented: one that
> reads the command substitution's output and another that expects to find
> the result in the REPLY shell variable when the command substitution
> completes.
>* The GLOBSORT shell variable determines how the shell will sort the results
> of pathname completion.
>* The compgen builtin has an option to put the generated completions into a
> designated shell variable instead of writing them to the standard output.
>* The read builtin has a new `-E' option that uses readline with the default
> bash completion, including programmable completion.
>* The source builtin has a new `-p PATH' option, which makes it use the PATH
> argument instead of $PATH to search for the file.
>The source code has been updated for C23 conformance. This means that bash
>will no longer compile with K&R-style C compilers.
>Readline has a new option that allows case-insensitive searching, a new
>command that executes a named readline command, and a new command that
>exports possible word completions in a specified format for consumption
>by another process.
https://ftp.gnu.org/pub/gnu/bash/

>There are several notable bug fixes. The shell no longer marks jobs as
>notified in several cases where it did before without actually notifying
>the user. There are changes for POSIX conformance in areas where POSIX is
>evolving. There is a set of fixes that improve behavior when command status
>is being inverted while `set -e' is enabled. The intl library has been
>updated to the one from gettext-0.21.1. Bash does a much better job of
>handling integer overflow in places like the printf builtin. A complete
>list of changes is appended.
>There are a few incompatible changes between bash-5.2 and bash-5.3. The
>test builtin uses slightly different parsing behavior when parenthesized
>subexpressions are present and test has been supplied more than four
>arguments, for compatibility with coreutils. When the shell is running
>interactively, it no longer notifies about completed jobs while sourcing
>a script, deferring notification until the script completes.

>steaming with anticipation over the new bash

Does this mean wiki wooledge is outdated?

it isnt JUST new=bad (though that is usually the case) its new=broken=bad or new=slow=bad. you wont find real opposition to incremental improvment. go get your fix somehwere else.

>>105798379 (OP)
Hi, yes, thank you for posting this.
1/3rd of my work time is bash.
When do you think we can start seeing 5.3 jn mainstream distributions?

>>105799620
Just use something like arch or opensuse it should come soon enough.

> C - CR23 (ISO/IEC 9899:2024)
Shameless bastard, bash hasn't been K&R for decades. I wouldn't be surprised if they hidden GCC compiler dependencies aswell

>>105798379 (OP)
No, BASH kinda sucks, I hope it dies in a pile of fire.

>>105798379 (OP)
>Are you excited for the upcoming BASH release?
i wasn't but i guess i am, new bash always good
>>105799620
your sylveon is missing pants

I use zsh

>>105800053
My condolences.

>>105798379 (OP)
> Are you excited for the upcoming BASH release?

No, bash is a pile of steaming shit and I'll be excited when they'll let this horrid crap rest in piss for good
There are plenty of better scripting shell than bash or even other scripting language like python and perl (which was its original goal)
Rc is 30 years old and still is better than today bash https://en.wikipedia.org/wiki/Rc_(Unix_shell)

Learn lisp. Nothing else is worth

>>105800175
Yeah, it's sad that even lisp is a better alternative for bash

But if you like scripting with kebab-case and higher order function you can use the es shell
https://wryun.github.io/es-shell/
https://wryun.github.io/es-shell/paper.html

>>105798379 (OP)
BASH is what happens when you let the so called "UNIX PHILOSOPHY" going so far

>>105798379 (OP)
>The source code has been updated for C23 conformance. This means that bash
>will no longer compile with K&R-style C compilers.
huh, bash had always been my example for software that still uses K&R function decl.

>>105798408
nah
the author of that website still participates in bash development

>>105799672
bash 5.2 can be compiled with vbcc and runs fine on amiga os

I've been using this shillware to write CLI utils for a while. Bash is good for simple loops but i never really liked the insane quotation and escaping rules
https://docs.astral.sh/uv/

>>105798379 (OP)
I'm throwing a huge BASH bash. It's going to be a terminal smash.

>>105800175
This
https://book.babashka.org/

>>105800608
WOOOO WOOOOOOOo WOOOOOOO BRNTTTTTTTTTTTTTTTT DOOODOOOODOOODOOOOOO!
RETARD ALERT! RETARD ALERT!

>>105800608
It was the world's fault, GNU wanted to move on to something like Guile but nobody wanted to listen. Bash was the only way to prevent a worse outcome.

But bash was deprecated altogether

>>105801380
>2 complete rewrites in 20 years
>about 5 users around the globe
kek

>>105801380
If we'd have to deprecate bash, Tbh I'd prefer ksh over fish.

>>105799628
It's about compatibility.

Newest feature of bash that you actively use?

>>105801639
this is neat
> ‘search-ignore-case’
> If set to ‘on’, Readline performs incremental and
> non-incremental history list searches in a case-insensitive
> fashion. The default value is ‘off’.