On Wed, Jun 24, 2020 at 09:43:51PM -0500, Alexander Perlis wrote:
Although it seems that variable values themselves can be longer than
1022 bytes, if one places a dollar-variable-expansion inside another
variable, then only the first 1022 bytes will be expanded. The internal
buffer has size 102
> On Jun 25, 2020, at 8:39 AM, Kevin J. McCarthy wrote:
>
> I wonder why they treated \ and " differently though: it appears purposely
> done.
I'd guess just this: for an incoming \ or " you still store the incoming
character merely preceding it with a \, whereas for the other incoming
char
On Wed, Jun 17, 2020 at 07:20:40PM -0700, Kevin J. McCarthy wrote:
On Thu, Jun 18, 2020 at 03:17:09AM +0200, Vincent Lefevre wrote:
There's Tamo's patch that does that for ~[Tab] to get help on the
patterns.
Thanks Vincent! I will take a look this weekend. It's amazing all
the things people
On Thu, Jun 25, 2020 at 06:39:27AM -0700, Kevin J. McCarthy wrote:
On Wed, Jun 24, 2020 at 09:43:51PM -0500, Alexander Perlis wrote:
As for increasing the variable expansion limit: if I follow the
parsing code correctly, it mostly uses the BUFFER type, but
parse_set() calls mutt_extract_token()
While working on converting configuration variable expansion to use
buffers, I noticed $my_ variables were directly expanded, while
configuration variables have escaping done (via escape_string() in
init.c).
This leads to strange behavior:
set spam_separator = 'foo"bar'
set my_ss = $spam_sepa
