LWN: Comments on "Bash 5.1 and Readline 8.1 released" https://lwn.net/Articles/839212/ This is a special feed containing comments posted to the individual LWN article titled "Bash 5.1 and Readline 8.1 released". en-us Sun, 19 Oct 2025 16:57:31 +0000 Sun, 19 Oct 2025 16:57:31 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net "accept" as a loadable https://lwn.net/Articles/840868/ https://lwn.net/Articles/840868/ midol <div class="FormattedComment"> where did you find the tarball?<br> </div> Mon, 21 Dec 2020 01:56:08 +0000 Bash 5.1 and Readline 8.1 released https://lwn.net/Articles/839421/ https://lwn.net/Articles/839421/ eru <p> From announcement: <i>"The most significant change is a return to the bash-4.4 behavior of not performing pathname expansion on a word that contains backslashes but does not contain any unquoted globbing special characters."</i> <p> I wonder what was the logic behind performing pathname expansion here in the previous version? The backslash is not a metacharacter that causes globbing. Or that is what I have always believed. Wed, 09 Dec 2020 09:04:58 +0000 "accept" as a loadable https://lwn.net/Articles/839242/ https://lwn.net/Articles/839242/ CChittleborough I was intrigued to see that there is a new loadable builtin command named accept. Could it be <a href="https://man7.org/linux/man-pages/man2/accept.2.html">this <code>accept</code></a>? Surely not ... But this <em>is</em> Bash, after all ... <p> So when I pulled the tarball down, I took a look ... and sure enough ... it <em>is</em> that <code>accept</code>. <p> To quote from its help text, accept “allows a bash script to act as a TCP/IP server”. <p> Wow. Wed, 09 Dec 2020 02:22:11 +0000