Re: [PATCH] [[:blank:]] only matches on SPC and TAB

[Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>]

On 14 May 2018 at 04:27, Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx> wrote:
> I'm currently coding a new plugin and literally have chosen [[:blank:]] because it's not unicode spaces.


I thought that I'll prove this – follows main code from my ini-file parser:

while read -r -t 1 __line; do
if [[ "$__line" = (#b)[[:blank:]]#\[([^\]]##)\][[:blank:]]# ]]; then
__cur_section="${match[1]}"
elif [[ "$__line" =
(#b)[[:blank:]]#([^[:blank:]=]##)[[:blank:]]#[=][[:blank:]]#(*) ]];
then
match[2]="${match[2]%"${match[2]##*[! $'\t']}"}"
__access_string="${__out_hash}[${__key_prefix}<$__cur_section>_${match[1]}]"
: "${(P)__access_string::=${match[2]}}"
fi
done < "$__ini_file"

[[:blank:]] is like a platform. I've really gone into paranoid state
that my platform will change, so I'm even proving this. If I would
want users to use unicode spaces in ini-file, I would use [[:space:]].
Let's not discard this degree of freedom.

Whole code:
https://github.com/zdharma/the-z-invoker/blob/master/-zflai_read_ini_file
-- 
Best regards,
Sebastian Gniazdowski