Re: BashPitfall 65, read reading past the delimiter on records ending in truncated characters

My two cents: I know `read` to be one of the worst way for reading data, in term of performances. I know *shell* not to be able to manage binary and mostly null bytes, The most reliable way I use for parsing strings that contain null bytes is mapfile (readarray): $ printf %b\\0 winter spring 's

[bug #67045] bash parsing error, when using readline, backslashes, and

URL: Summary: bash parsing error, when using readline, backslashes, and Group: The GNU Bourne-Again SHell Submitter: None Submitted: Tue 22 Apr 2025 08:41:19 PM UTC Category:

Re: Bash documentation is missing ID anchor

On 4/19/25 12:02 AM, Antti Savolainen wrote: https://www.gnu.org/software/bash/manual/html_node/Directory-Stack-Builtins.html pushd on this page is missing an anchor and I'm unable to link directly to it due to that. Looks like the scripts that generate the HTML require that @item come before @