Skip to content
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

update_manpage_completions.py is run on every new shell #1343

Closed
nagisa opened this issue Mar 13, 2014 · 6 comments
Closed

update_manpage_completions.py is run on every new shell #1343

nagisa opened this issue Mar 13, 2014 · 6 comments
Labels
bug Something that's not working as intended
Milestone

Comments

@nagisa
Copy link
Contributor

nagisa commented Mar 13, 2014

Every invocation of fish command built from today’s git (44e94b8) will fire off update_manpage_completions.py script which consumes substantial amount of resources.

Might be related to #997. If nobody can reproduce it I'll bisect.

Possibly also related, but might also be not – I ran fish_update_completions manually just after freshly installing git version of fish. Can’t tell whether that is what caused the behaviour as I built and ran git fish for the first time in a long time.

@nagisa
Copy link
Contributor Author

nagisa commented Mar 13, 2014

Removing the code introduced by commit linked in #997 fixes the issue.

The issue seems to stem from the fact that update_manpage_completions.py puts completions into /home/nagisa/.config/fish/generated_completions/, but my $XDG_CONFIG_HOME is actually /home/nagisa/config (note the missing leading dot).

@zanchey
Copy link
Member

zanchey commented Mar 14, 2014

Fish detects a non-standard XDG_CONFIG_HOME correctly in __fish_config_interactive.fish, but not in update_manpage_completions.py or in fish_update_completions.fish.

@zanchey
Copy link
Member

zanchey commented Mar 14, 2014

Additionally, we should probably be storing this stuff in XDG_DATA_HOME rather than XDG_CONFIG_HOME.

@zanchey zanchey added the bug label Mar 14, 2014
@zanchey zanchey added this to the next-minor milestone Mar 14, 2014
@mrak
Copy link
Contributor

mrak commented Mar 14, 2014

I'll add a vote for these generated files (that are currently under XDG_CONFIG_HOME to go under XDG_DATA_HOME:

generated_completions/
fish_read_history
fish_history
fishd.<hostname>

@zanchey
Copy link
Member

zanchey commented Mar 14, 2014

See #744 and #1257 regarding those files.

@siteshwar
Copy link
Contributor

@zanchey #1350 looks ok ?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something that's not working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants