Artyom Bologov <[email protected]> writes:
> I implore you, please, preserve file names across
> calls by escaping the special chars that might
> break the identity of the remembered pathname we
> all care about so much.
My personal conceptualization of what % is,
it's like dump simple string templating tools. So
I never faced such issues, as I always escaped the
name myself. For example, I would do:
!rm '%'
If ed did shell escaping by itself, I would
actually be surprised. I assume that would cause
my commands to fail, because I escaped them myself
on top of ed's own escaping. So if ed translated:
!rm %
to
!rm \*
then my method of running it:
!rm '%'
would translate to:
!rm '\*'
which would break the command.
When using ! command, to execute command in
a shell, I would expect the exact semantics of the
shell to apply to what I'm running. Automatically
escaping anything is meddling with said semantics;
it would be weird to me, and would likely break on
all kinds of edge-cases, I now will have to learn,
and be aware of, how ed does its name escaping, at
all times, when running shell commands.
Best Regards,
Lumin Etherlight
