one small addition , <<'foo' ( with quotes is used ) .. .. should tell bash expliciply preserve data ..
On Mon, Apr 7, 2025, 23:51 microsuxx <fxmb...@gmail.com> wrote: > i dunno what lithist is , but remaining data one to one is a big bug thats > gotta be fixed > its like u write foo "$1" "$2" and it sends foo $1 $2 > .. if data , in case heredoc content , which is highly underrated and > underused , is not remained .. its nothing else than a big broken cmd > plz fixx > greets++ ur microsucker .. > > On Mon, Apr 7, 2025, 22:34 Chet Ramey <chet.ra...@case.edu> wrote: > >> On 4/4/25 4:18 PM, Jens Schmidt wrote: >> >> > [bashbug output manually adapted to real version ...] >> > Bash Version: 5.3 >> > Commit: a6767763de5e7859107711b166a64a9e4a77a8ae >> > Release Status: compiled from recent devel branch >> > >> > >> > Description: >> > Bash skips empty lines when reading history file in multiline mode. >> >> This is a problem even if lithist isn't set -- it's not uncommon to have >> blank lines in here-documents. >> >> But do you really think people want blank history entries even with >> lithist >> set? How about history processing blank lines as part of the command after >> it reads the first non-blank line? >> >> -- >> ``The lyf so short, the craft so long to lerne.'' - Chaucer >> ``Ars longa, vita brevis'' - Hippocrates >> Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/ >> >
