slash appended to tab so its two // at end

i in 5.2.15 bash aarch64 termux did $ cp -ap db2.*/ and got db2.i5// db2.i7// // should be / i think greets , xmb

Re: [PATCH] Add missing docs for 'set +o', 'set -o'

On Tue, Jul 18, 2023, at 9:29 AM, Beer, Mathis wrote: > Add documentation for 'set -o', 'set +o' syntax to 'help set', 'info'. > 'set -o'/'set +o' matches the POSIX behavior, but Bash's own documentation > should also mention it. > Phrasing is copied from the manpage, which already mentions it.

Re: [PATCH] normalization tweaks for macOS

On Tue, Jul 18, 2023 at 9:55 AM Chet Ramey wrote: > Unicode normalization on macOS has always been a pain in the ass. I can see that! > This is the basic assumption that drives all the decisions: character input > you get from the terminal is in NFC, and files from the file system (names > and

Re: [PATCH] normalization tweaks for macOS

On 7/17/23 6:12 PM, Grisha Levit wrote: On Mon, Jul 17, 2023 at 3:29 PM Chet Ramey wrote: On 7/7/23 5:05 PM, Grisha Levit wrote: A few small tweaks for the macOS-specific normalization handling to handle the issues below: The issue is that the behavior has to be different between cases

[PATCH] Add missing docs for 'set +o', 'set -o'

Add documentation for 'set -o', 'set +o' syntax to 'help set', 'info'. 'set -o'/'set +o' matches the POSIX behavior, but Bash's own documentation should also mention it. Phrasing is copied from the manpage, which already mentions it. --- builtins/set.def | 4 doc/bashref.texi | 5 + 2

Re: [PATCH] normalization tweaks for macOS

i no much here the topic .. just for short .. i found uconv of icu-devtools has more opts has also some transliteration opt just that u may not know it i no pro i still cant achieve what i had to do On Tue, Jul 18, 2023, 12:13 AM Grisha Levit wrote: > On Mon, Jul 17, 2023 at 3:29 PM Chet Ramey

Re: [PATCH 1/2] <<# indent-stripping heredoc

On Sat, 15 Jul 2023, 10:18 Dennis Williamson, wrote: > Would a declared spaces-per-level indent amount be useful? Something like > <<4# that would be the script writer's responsibility to conform to since > they set it. This might be in addition to the already proposed <<#. > I briefly pondered

[PATCH] fix bind -X quoting

The output of `bind -X' is not reusable if the bound command has quotes, backslashes, etc. $ bind -x '"\eX": echo "x"' $ bind -X "\eX": "echo \"x\"" $ bind -x "$(bind -X)" $ bind -X "\eX": "echo \\\"x\\\"" This patch changes rl_macro_dumper to not untranslate the macro body when passed a