Reopen of #39 - specifying --config does not appear to work from Windows cmdline

[larray]

MSGVAULT_HOME may have inherited a new bug? I was attempting to test the --config (wasn't sure it was resolved)
v0.6.0

Set without quotes (working previously)

Set with quotes (because the updated documentation seems to indicate at least with PowerShell quotes are preferred)

Here is my attempt at using --config:

My attempts to use --config MAY not have been valid before because I realize I probably wasn't passing an actual command like TUI or sync-full. However I am getting the same error with Error: load config: decode config: toml: line 3 (last key "data.data_dir"): invalid escape in string '\G' in either case now.

[wesm]

It looks like you need to escape the backslashes (\\G not \G)

[larray]

That's a negative Ghostrider... :)

It LOOKS like it... but I don't think it fixes it :)

I'm a tad fearful now because without being able to set the environment variable - I'm wondering what will happen in my other instance which has a local environment variable in a session tab that is still working... if I close it the ENV variable might not work again. I'll have to test that later. W
Worst case I can go back to putting it in the home directory.

[wesm]

I have Claude looking at it now, just bear with me

[wesm]

I am working on fixing the issue in #87, I will do some manual QA on my side with my windows rdp box

[larray]

Absolutely no pressure here - just pondering options :). Still much appreciated!

[wesm]

Making progress, I should be able to cut a 0.6.1 release with the fix within an hour or so

[wesm]

I've tested this quite a bit locally and going to cut 0.6.1 now, please let me know how it goes, and reopen this issue if you have more or different problems!

[wesm]

see also wesm/msgvault-docs#8

[larray]

Single Quote:
I FINALLY realized that the error is in the config.toml NOT with the command line It DID need modifications to the TOML to set to single quote instead of double quote:

SUCCESS!

Nice testing of the --limit flag there too :)

There may be something glitchy with the single quote version of the command line though still: