Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: edit-command-line with spaces in EDITOR
- X-seq: zsh-workers 26148
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: edit-command-line with spaces in EDITOR
- Date: Tue, 16 Dec 2008 20:04:07 -0800
- In-reply-to: <20081216214517.GA14544@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20081216153846.GA10426@xxxxxxxx> <237967ef0812160907s6481321dnf796fcdcbb93fb1f@xxxxxxxxxxxxxx> <20081216214517.GA14544@xxxxxxxx>
On Dec 16, 9:45pm, Clint Adams wrote:
}
} Are you aware of any applications which _do not_ split EDITOR on spaces
} or is this all theoretical?
I suspect that most applications do the equivalent of
eval "$EDITOR $1"
which accomplishes the splitting of $EDITOR at some security risk if the
environment is tainted.
Then the spaces-in-the-path problem is solvable by embedding quotes or
backslashes in the value of $EDITOR.
Zsh could meet the two extremes halfway by using ${(Q)${(z)EDITOR}}.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author