On Thu, Aug 14, 2008 at 07:23:12AM -0400, Thomas Dickey wrote:
"Anything" that would prompt from a string will do that either directly
from the keyboard, or by calling a function that takes the next token
from a buffer containing possibly more than one token. For consistency,
that token's quotes are removed, and the commands which read (via
kbd_reply, etc), do not expect quotes.
In your example, the quotes are removed to deliver the parameters to the
low-level commands (which do not expect quotes). vile stores data in
[History] with quotes (as needed...), and reconstructs/dequotes values
that it retrieves from [History] as part of a prompt. The
expression-evaluation can read quoted strings, but also assumes that its
output will be acceptable to the commands, which do not expect quotes.
With all of that, there're occasional inconsistencies (bugs). I don't
_see_ any obvious ones in your example.
Thanks for the explanation. To be honest, I'm not quite sure if
you're saying that you're aware of the limitation and there's just
nothing surprising in my observations, or that you think it isn't a
problem worth solving or not a problem at all. Obviously it matters