New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't see start message #3973
Comments
What do you mean by "always"? Under what circumstances can you or can't you see it? This should be printed
Is it just totally random? |
You'll only see that message for interactive shells and only if you have not defined a |
Thanks.
I found |
No. That's the equivalent of Are you using any third-party plugins or frameworks like oh-my-fish or fisherman? Any prompts or functions or themes you've downloaded from somewhere else? |
If you simply want to see the default greeting just run |
I see.
Yes. I using fisherman and these plugins.
|
Neither of those plugins is likely to be the cause. It is more likely that sometime in the past you ran |
I did it. But I can't see it. Hmm...
|
I didn't it. Because I install the fish to a clean installed MacBook Pro a while ago. |
Thanks for working with us, @m-nagae, by answering our questions. I now see the problem. The __fish_config_interactive.fish has a subtle bug introduced 2016-09-10, seven months ago, by commit 90e535f. The problem is that a No one has noticed this before now because most of us explicitly disable the greeting. Thanks for bringing this to our attention. I'll fix it for the 2.6.0 release. |
Also, the reason you end up with a |
Yes, open a new issue since it is unrelated to this issue. Note, however, that I cannot tell what the problem is from the information in your last comment. What exactly do you expect to happen if you type |
fish, version 2.5.0
iTerm2 Build 3.0.15
macOS Sierra 10.12.4
Darwin 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
xterm-256color
I always can't see this message when start fish.
The text was updated successfully, but these errors were encountered: