Re: bash aesthetics question: special characters in reg exp in [[ ... =~~ ... ]]

On 23.07.2024 00:47, Kaz Kylheku wrote:

On 2024-07-22, Kenny McCormack <gazelle@shell.xmission.com> wrote:

The problem is that if the above is in a function, when you list out the
function with "type funName", the \n has already been digested and
converted to a hard newline.  This makes the listing look strange.  I'd
rather see "\n".

 
I see what you mean:
 
$ test() {  [[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar" ; }
$ set | grep -A 4 '^test'
test ()
{
    [[ "$f" =~ foo[^'
']*bar ]] && echo "foo bar"
}
 

Is there any way to get this?

Of course (and out of curiosity) I tried that display detail as well
in Kornshell to see how it behaves, and using a different command to
display it...


With my (old?) bash:

$ f() {  [[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar" ; }
$ typeset -f f
f ()
{
    [[ "$f" =~ foo[^'
']*bar ]] && echo "foo bar"
}


The same with ksh:

$ f() {  [[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar" ; }
$ typeset -f f
f() {  [[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar" ; }


And for good measure also in zsh:

% f() {  [[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar" ; }
% typeset -f f
f () {
[[ "$f" =~ foo[^$'\n']*bar ]] && echo "foo bar"
}


Both seem to show "better aesthetics". Too bad it doesn't help for
your bash context.

Janis

[...]