On 04/07/2015 03:38 AM, Gareth Skinner wrote:
In bash, you can hit Ctrl-x-e to open your current command line in
$EDITOR, make your modifications, and the shell runs your command
when you exit.
Thanks for pointing that out; I had no idea, even though I used bash for many
years before
On Tue, Apr 7, 2015 at 9:38 AM, Gareth Skinner g...@sknr.org wrote:
Hi fish-users,
In bash, you can hit Ctrl-x-e to open your current command line in
$EDITOR, make your modifications, and the shell runs your command when you
exit. It also exists in zsh:
Greg, unfortunately, you cannot rewrite it like that. You have to put
quotes around (cat $tmp), or each token will end up on its own line in the
command buffer. (And in fish, you cannot do command substitution inside
quotes.)
Something like
[...]
commandline -r
cat $tmp | while read -l cmd;
Yes, I missed that feature too. Hopefully developers of fish will consider
adding that.
That seems more adhere to the linux philiosophy---better leave it to the
editor instead of the shell to do the editing.
On Tue, Apr 7, 2015 at 12:38 AM, Gareth Skinner g...@sknr.org wrote:
Hi fish-users,
It is possible to implement this with a fish function.
function edit_commandline
set -l tmp (mktemp /tmp/fish-fc.XX)
commandline $tmp
eval $EDITOR $tmp
cat $tmp | read -l cmd
commandline -r $cmd
rm $tmp
end
Of course, if you do this properly, you'd have to check whether mktemp
On 04/15/2015 11:45 AM, Sanne Wouda wrote:
Greg, unfortunately, you cannot rewrite it like that. You have to
put quotes around (cat $tmp), or each token will end up on its own
line in the command buffer.
I understand what you mean now, but this problem does not happen for me. Maybe
the
On 04/15/2015 11:45 AM, Sanne Wouda wrote:
Greg, unfortunately, you cannot rewrite it like that. You have to
put quotes around (cat $tmp), or each token will end up on its own
line in the command buffer. (And in fish, you cannot do command
substitution inside quotes.)
I don't understand.
This is my first time trying to contribute to fish, so please forgive any
mistakes I make. The patch is included as an attachment and Sanne Wouda
sanne.wo...@gmail.com wrote this function which I changed a little.
From 64af63b71f2bbf168a6e833390e72b5e04d27b66 Mon Sep 17 00:00:00 2001
From: Greg
I think it'll be best if you send the patch via github, where others
can review and give comments easily.
I'm not a reviewer, but the last time I sent commits (more than a yr
ago), it was via github. Easy to track changes there (maybe you can
open a feature request for it there).
On Wed, Apr
Yeah, I'm on the nightlies :)
On Wed, 15 Apr 2015 19:06 Greg Reagle greg.rea...@umbc.edu wrote:
On 04/15/2015 11:45 AM, Sanne Wouda wrote:
Greg, unfortunately, you cannot rewrite it like that. You have to
put quotes around (cat $tmp), or each token will end up on its own
line in the
10 matches
Mail list logo
