GNU bug report logs - #48078
Verbatim environments with key-value arguments

Previous Next

Full log

Message #22 received at 48078 <at> debbugs.gnu.org (full text, mbox):

From: Arash Esbati <arash <at> gnu.org>
To: Tassilo Horn <tsdh <at> gnu.org>
Cc: Dario Gjorgjevski <dario.gjorgjevski <at> gmail.com>, 48078 <at> debbugs.gnu.org
Subject: Re: bug#48078: Verbatim environments with key-value arguments
Date: Thu, 29 Apr 2021 23:39:49 +0200

Hi Tassilo,

Tassilo Horn <tsdh <at> gnu.org> writes:

> Arash Esbati <arash <at> gnu.org> writes:
>
>> Thank you for the quick fix.  I also removed some unnecessary escaping
>> of characters in the regexp for the optional arguments.
>
> I had to check the docs to understand that. :-)

I have to check the docs every time I deal with regexp's :-)

>> While we're at, I think we should replace
>>
>>     "\\(?:\\[[^][]*\\(?:\\[[^][]*\\][^][]*\\)*\\]\\)?"
>>
>> with
>>
>>     "\\(?:\\[[^][]*\\(?:{[^}{]*}[^}{]*\\)*\\]\\)?"
>>
>> at some point.
>
> But your advertised new regex doesn't even match the normal nested
> bracket case, e.g., [foo=[1,2], bar={~}].

It has to match [foo={[1,2]}, bar={~}].  In your example above, LaTeX
scanner stops matching for the optional argument after ] and everything
after that would be part of the environment.

>> Rationale: One can have a single ] in an optional argument which is
>> hidden inside {}.
>
> Not everything that can be written should be written. ;-)

A slight delay might be acceptable, sometimes :-)

Best, Arash

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.