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

Allow quterofi to read toml files from any user provided location #35

Open
cortsf opened this issue Nov 4, 2024 · 0 comments
Open

Allow quterofi to read toml files from any user provided location #35

cortsf opened this issue Nov 4, 2024 · 0 comments

Comments

@cortsf
Copy link
Owner

cortsf commented Nov 4, 2024

Allow users to provide a --quickmarks_file optional argument (defaulting to the standard QB file) when calling quterofi/set_quickmarks, quterofi/manage_quickmarks and quterofi/open

Support for standard quickmarks file/s is being deprecated in favor of quteromarks. Allow users to provide a custom path to the toml file, or a list of paths such that the user can organize engines and quteromarks in multiple files. This approach have the disadvantage of having to force users to specify which file to operate on when using quterofi/quteromarks to manage quteromarks. And of course, the undesirable layer of noise in the code base.

@cortsf cortsf changed the title Allow users to use any quickmarks filepath Allow users to provide any quickmarks filepath Nov 4, 2024
@cortsf cortsf changed the title Allow users to provide any quickmarks filepath Allow users to provide a list of toml files Nov 13, 2024
@cortsf cortsf changed the title Allow users to provide a list of toml files Allow quterofi to read toml files from any user provided location Nov 13, 2024
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

No branches or pull requests

1 participant