Hello.
I have noticed that declare -f does not output valid code when a
pattern is `esac'.
To use esac as a pattern you need to use the (esac) syntax, but
declare -f does not use it, and ends up generating invalid code.
a () {
case $1 in
hi) echo hi ;;
(esac) echo esac ;;
On 2/24/24 5:40 AM, Koichi Murase wrote:
Meanwhile, the behavior that `exec 50>2.txt' does not have an effect
does not seem to be the intentional design. It seems to be just a
side effect of the manipulation of the saved fds. In this sense, the
strange behavior I observe is the one that Chet d
On 2/24/24 12:11 AM, Koichi Murase wrote:
I have a question. Maybe it's not technically a bug as fd > 9 is
involved, but the resulting behavior appears to be strange. I
received some reports from users in my project and tried to find out
what is happening. This is a reduced case:
#!/usr/bi
On 2/25/24 5:37 AM, Martin D Kealey wrote:
Unicode has categories for "modifiers" (especially "modifier letters") and
for "combining characters". Note that each symbol can be in multiple
categories.
Modifiers change how another character is displayed. They may or may not be
considered to have t
