Skip to content

feat: allow configuring bacon command path #63

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

Merged
merged 1 commit into from
May 19, 2025

Conversation

Milly
Copy link
Contributor

@Milly Milly commented May 16, 2025

A new configuration option, runBaconInBackgroundCommand, which allows users to specify the path to the command used to run bacon in the background. Previously, the path was hardcoded. This change enhances flexibility and allows users to specify alternative bacon installations or custom commands.

I've been using this feature to debug bacon-ls and install bacon without polluting my $PATH.

A new configuration option, `runBaconInBackgroundCommand`, which allows users to specify the path to the command used to run `bacon` in the background.
Previously, the path was hardcoded.  This change enhances flexibility and allows users to specify alternative `bacon` installations or custom commands.
@Milly
Copy link
Contributor Author

Milly commented May 16, 2025

This might become unnecessary if we migrate to a cargo backend. 😢

@crisidev crisidev merged commit ce1af15 into crisidev:main May 19, 2025
4 of 5 checks passed
@crisidev
Copy link
Owner

Thanks a lot. I will sooner or later make the cargo native backend default, but I don't think we are planning to remove the bacon backend.

@Milly Milly deleted the bacon-command-path branch May 20, 2025 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants