On 2023-06-27 00:35, Dennis Nezic wrote:
On 26 Jun 19:53, Kim Woelders wrote:
On 2023-06-25 19:22, Dennis Nezic wrote:
Currently comments in bindings.cfg are parsed dumbly (but efficiently)
as the first occurrence of '#', even if it occurs in a pair of quotes.
Attached is a more intelligent
On 26 Jun 19:53, Kim Woelders wrote:
> On 2023-06-25 19:22, Dennis Nezic wrote:
> > Currently comments in bindings.cfg are parsed dumbly (but efficiently)
> > as the first occurrence of '#', even if it occurs in a pair of quotes.
> > Attached is a more intelligent way that handles such quotes.
> >
On 2023-06-25 19:22, Dennis Nezic wrote:
Currently comments in bindings.cfg are parsed dumbly (but efficiently)
as the first occurrence of '#', even if it occurs in a pair of quotes.
Attached is a more intelligent way that handles such quotes.
"eesh exec" in a terminal, and the exec commands in
Here's a slightly more robust inside of that for-loop, in case there are
escaped quotes outside a quoted pair (eg. quotes in filenames?), not
sure it's necessary to worry about these :p.
if (*s3 == '\'' && (s3 == s || *(s3 - 1) != '\\')) {
while
Currently comments in bindings.cfg are parsed dumbly (but efficiently)
as the first occurrence of '#', even if it occurs in a pair of quotes.
Attached is a more intelligent way that handles such quotes.
"eesh exec" in a terminal, and the exec commands in the .menu files are
both able to handle
