Re: 3.17.0 (bug?): ".mode" command ignoring ".separator" when -init used
On Tue, 14 Feb 2017 07:57:17 -0500
Richard Hipp <[hidden email]> wrote:
> It does not ignore it, it overwrites it. The ".mode" command now
> always also sets the ".separator" (to the default separator value) for
> those modes where the separator is used. This was added to work
> around the unexpected behavior described by
Ok, but in the stackoverflow example, the user didn't set
".separator", so I understand it was a bug.
In my case, I'm explicitly setting the .separator to ",", so it
shouldn't be overwritten. Otherwise, every time I use .mode, I'll have
to set the .separator afterward?
A better solution would be to overwrite the separator *just* if
the user didn't set the separator, otherwise there's no reason anymore
to set the separator in the -init file, since we'll have to set the
separator every single time we use .mode.