Skip to content

Conversation

@mqudsi
Copy link
Contributor

@mqudsi mqudsi commented Dec 15, 2018

This prevents fish from loading the user configuration file at startup.
It is not intended to affect interactive uses of fish, which will end up
sourcing the file automatically, but it does prevent sourcing the user
config.fish file when fish is called non-interactively.

i.e. users with bad config.fish entries that should not be executed in non-interactive mode (but aren't guarded with if not status --interactive) will not be run at startup. But running fish interactively with --no-config will end up loading (or creating) the needed files to automatically source functions, etc.


Either this or #5417 should be merged, depending on how far we want to take this.

This prevents fish from loading the user configuration file at startup.
It is not intended to affect interactive uses of fish, which will end up
sourcing the file automatically, but it does prevent sourcing the user
`config.fish` file when fish is called non-interactively.
@faho
Copy link
Member

faho commented Mar 13, 2019

So, this one just removes the source ~/.config/fish/config.fish step.

It still

  • keeps ~/.config/fish in $fish_function_path and $fish_complete_path
  • reads ~/.config/fish/conf.d (since that's done in /usr/share/fish/config.fish)
  • uses uvars

Which seems like a bit too little. So I'm closing this one. Sorry for taking sooo long to get to it!

@faho faho closed this Mar 13, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants