You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
cortsf
changed the title
Allow users to use any quickmarks filepath
Allow users to provide any quickmarks filepath
Nov 4, 2024
cortsf
changed the title
Allow users to provide any quickmarks filepath
Allow users to provide a list of toml files
Nov 13, 2024
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
Allow users to provide a--quickmarks_file
optional argument (defaulting to the standard QB file) when callingquterofi/set_quickmarks
,quterofi/manage_quickmarks
andquterofi/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.The text was updated successfully, but these errors were encountered: