Note that autocomplete will not suggest commands that were not found.
So in this case, because the "def" command failed, fish will not
suggest it via autocomplete. However search (i.e. up arrow) is not
similarly restricted.
If you do
$ whoami
mjs
$ echo whoami
whoami
and then type "w", fish will
I am also using 2.1.1 (-1025-g5d1ddc9 on Ubuntu).
After:
~> def
def : commande introuvable
~> abc def
abc : commande introuvable
If I type "de" then use up arrow to navigate through history, I get "abc
def" as first choice. Thus for me it is the last command containing "de",
not the last start
2015-05-07 19:28 GMT+02:00 Robert Carpenter :
> `env NAME=value command` is a perfectly acceptable system. It is
> *different*. But it is different for good reasons. ...
Generally yes, but in this case it surfaced a nasty problem: `man` knows
about fish commands because it's a function (`type ma
> On May 8, 2015, at 5:43 PM, Greg Reagle wrote:
>
>>> I think it's worth noting here that in fish, if you just type 'c' on an
>>> empty command line, it will automatically show you the last command that
>>> started with 'c'.
>
>> More precisely, it brings back the last command that *contains*
> > I think it's worth noting here that in fish, if you just type 'c' on an
> > empty command line, it will automatically show you the last command that
> > started with 'c'.
> More precisely, it brings back the last command that *contains* a 'c'. Huge
> difference.
Not for me. For me, it does a
>>
>>> -Original Message-
>>> From: Sanne Wouda
>>> Date: Fri, 08 May 2015 10:26:01
>>> To: Gour; fish-users Mailing List<
>>> fish-users@lists.sourceforge.net>
>>> Subject: Re: [Fish-users] 5 minutes fish from 1
984
>> Email: jack...@pythian.com
>>
>> -Original Message-
>> From: Sanne Wouda
>> Date: Fri, 08 May 2015 10:26:01
>> To: Gour; fish-users Mailing List<
>> fish-users@lists.sourceforge.net>
>> Subject: Re: [Fish-users] 5 minutes
Thanks for this pointer! I’d been thinking of figuring out how to do it, and
there it was.
The only problem I had was that I had to edit and save bind_bang and
bind_dollar separately, it didn’t work when I tried to edit them together with
fish_user_key_bindings. But once I figured that out, it
> It took me a while to get over the lack of history expansions. But it's
> actually easier to hit Up arrow (!!) or Alt-Up (!$)
Yes, except when you want to combine a previous command with the new one. For
example, something I do very often (maybe it’s just me), in bash:
$ which footer
/usr/lo
Wouda
> Date: Fri, 08 May 2015 10:26:01
> To: Gour; fish-users Mailing List<
> fish-users@lists.sourceforge.net>
> Subject: Re: [Fish-users] 5 minutes fish from 15 years bash impression
>
>
> --
Wouda
Date: Fri, 08 May 2015 10:26:01
To: Gour; fish-users Mailing
List
Subject: Re: [Fish-users] 5 minutes fish from 15 years bash impression
--
One dashboard for servers and applications across Physical-Virtual-
Take a look at https://github.com/fish-shell/fish-shell/wiki/Bash-Refugees
for a fish implementation of !! and !$ .
On Fri, 8 May 2015 08:08 Gour wrote:
>
> Diego Zamboni writes:
>
> > Aleksey: fish is indeed not bash, but in a good way. There are many
> things
> > that could be improved, for s
Diego Zamboni writes:
> Aleksey: fish is indeed not bash, but in a good way. There are many things
> that could be improved, for sure, but it’s great even now.
I was never really bash user, but was trying zsh and the the main seeling
point for fish is that is *usable* out-of-the-box, while othe
I also miss ! and friends, let me know if you end up implementing these!
On Thu, May 7, 2015 at 4:06 PM, Diego Zamboni wrote:
> Robert,
>
> I couldn’t agree more. There are a few things I found frustrating in fish
> at first (some I still do, like the inability to recall previous
> commands/argu
Robert,
I couldn’t agree more. There are a few things I found frustrating in fish at
first (some I still do, like the inability to recall previous
commands/arguments with !! and !$ - I have to look more into coding those with
functions), but over time I’ve found the interactive shell experience
> Not really good: the default PAGER is 'less' which doesn't fully
> comply with 'quick and easy'.
In every shell I know, the environment variable PAGER is responsible for
the pager. There's nothing special with fish. And it's just one line to change
it:set -x PAGER xcowsay
--
Aleksey,
I honestly can't decide if you're trying to troll the mailing list or if you
have legitimate questions. I'm going to take a risk of feeding the troll here
in hopes that you're actually, honestly trying to understand fish-shell.
To save yourself some time, I'll put the summation at the
On Tue, May 5, 2015 at 3:01 PM, Siteshwar wrote:
> Hello Aleksey,
>
> Thanks for trying fish.
>
> On Tue, May 5, 2015 at 4:31 PM, Aleksey Midenkov
> wrote:
>>
>> > help for
>>
>> It opened browser window... I don't need browser, I need quick and
>> easy way to access basic syntax what does inline
On 05/06/2015 01:40 PM, Luciano ES wrote:
> "Choosing 'less' as default pager is among the worst of our sins."
>
> There, I made a slogan for fish. And it took me less than five minutes.
"If choosing 'less' as the default pager is wrong, then I don't want to be
right."
:>
"Choosing 'less' as default pager is among the worst of our sins."
There, I made a slogan for fish. And it took me less than five minutes.
--
Luciano ES
>>
**
On Tue, 5 May 2015 14:01:53 +0300, Aleksey Midenkov wrote:
> > help for
>
> It opened browser window... I don't
Hello Aleksey,
Thanks for trying fish.
On Tue, May 5, 2015 at 4:31 PM, Aleksey Midenkov
wrote:
> > help for
>
> It opened browser window... I don't need browser, I need quick and
> easy way to access basic syntax what does inline help in bash. It's
> console app after all!
>
> > man for
>
> Not
21 matches
Mail list logo
