You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PATH
Directories not containing a : (I think this is separated by :.
POSIX' definition of it can be found here: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
In particular, it's possible to have a zero-length prefix by either leading/trailing : or multiple adjacent :.
As said, these are just some ideas that might make sense - I don't have any strong need for this, so if you don't like the idea, just close it.
Thanks,
Chris.
The text was updated successfully, but these errors were encountered:
They are good ones to support, though the concept that GNU is a "standard" is not acceptable. There are many places in bash-completion where the generated completions can be improved, so the priority of the support for this Issue among such is not so high (unless you submit a PR for it), but we can keep this issue open.
Describe the feature/solution
Hey.
Just a few ideas, what could be added for completion as part of
_comp_variable_assignments()
:LANGUAGE
as used by GNU gettext (which makes it IMO fairly "standardised")AFAIU, this is not just a locale string as in
LC_ALL
or so but something likenb:no
. See https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-variable.html#The-LANGUAGE-variable and according to https://superuser.com/a/392466 even more than two fields can be used like infr:de:en
.PATH
Directories not containing a
:
(I think this is separated by:
.POSIX' definition of it can be found here: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html
In particular, it's possible to have a zero-length prefix by either leading/trailing
:
or multiple adjacent:
.As said, these are just some ideas that might make sense - I don't have any strong need for this, so if you don't like the idea, just close it.
Thanks,
Chris.
The text was updated successfully, but these errors were encountered: