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
To currently make it work one has to make the configuration lines start with a whitespace for the regular expression to match, since [^#] requires any character but #.
There are more similar regular expressions below.
The text was updated successfully, but these errors were encountered:
Boy that was a long time ago! I guess your request makes sense. However, After being more acquainted with writing ZSH completions ever since, looking back at what I wrote, I feel there's so much room for improvements in this one which I never would have thought of at the time due to my lack of experience back then.
As a start, I'll ditch the use of external tools such as sed and grep and use ZSH's very extensive Parameter Expansion features to achieve the same results. You can fix that for now if you wish but I'll start now on a larger refinement which may take me a few hours or the whole weekend if I won't find time..
Example line: https://github.com/pimutils/todoman/blob/master/contrib/completion/zsh/_todo#L46
containing:
s/^[^#]\s*path\s*=\s*\(.*\)$/\1/p
requires the string to start with any character but
#
followed by any amount of spaces, followed bypath
and so on.To currently make it work one has to make the configuration lines start with a whitespace for the regular expression to match, since
[^#]
requires any character but#
.There are more similar regular expressions below.
The text was updated successfully, but these errors were encountered: