Hi,
Thank you for you the answers.
> 2. Yes, "implicit cd" is gone. I found it to be too easy to accidentally
> invoke.
That's pity. Can this feature be switchable?
I'm sorry for being bothering. It would be painful to learn it back again
(:
> 4. I think fish is doing the right thing with "false ; and sdlkfjsdklf".
> That semicolon means that the 'and' is the beginning of a new statement,
> and fish agrees with other shells (including fish trunk) that this is an
> error. Remove the semicolon ("false and sdlkfjdsklf") and it does not
> error.
This statement confronts all my fish experience. I use fish as default
shell for the long time.
What about "echo 123 and echo 234" and "echo 123; and echo 234"?
I like very much the fact that fish switched from bashisms || and && to the
'and' and 'or' commands. It makes the syntax clean. Shell now do not need
to parse the whole line "false && echo 123". Instead it have just to parse
two commands divided by semicolon "false; and echo 123".
So in case you have 'and' and 'or' as logical units, you need that
semicolon
to split the commands. "false and sdlkfjdsklf" doesn't issue an error,
because
'false' command accepts 'and' and 'sdlkfjdsklf' as arguments and simply
ignores them.
This doesn't make any sense.
And the actual usage:
which existingcommand; and existingcommand arg1 arg2 # should be executed
which notexistingcommand; and notexistingcommand arg1 arg2 # should not be
executed and should not emit any warnings
which notexistingcommand and notexistingcommand arg1 arg2 # will try to
find commands
notexistingcommand, and, notexistingcommand, arg1, arg2
I still do not understand the existing behavior.
> 5. What you're seeing is the "internalized scripts" behavior, where at
> build time, fish compiles all the default functions into itself (as C
> strings). This reduces the number of files touched at launch. I did this
> under the belief that these functions generally depended on each other,
> and ought not to be modified. However, since this is causing problems,
> we should restrict the functions internalized in this way, or eliminate
> the optimization altogether. I filed
> https://github.com/ridiculousfish/fishfish/issues/15
>
> Can you share which functions from /usr/local/share/fish/ you override?
fish_prompt is what I see from the beginning.
As an example I've tried to override 'll'.
> (The fish_prompt case is particularly bad - I didn't realize the effect
> that would have. I put my prompt in config.fish)
I would prefer to have a possibility to override any function, even
internalized.
Sometimes it's very useful, especially for debugging.
And from the usage point of view, it is more clean when there are no
implicit limitations.
> 6. There is a color "fish_color_autosuggestion" which defaults to #555
> (gray), but if your term doesn't support term256, you won't see it.
> Maybe we could pick a color for classic 16 color terms. What term are
> you using?
I've missed it, because my default color is gray (:
I will check them.
Maxim
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
