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

Add a list of HLS executable file paths in settings #302

Closed
berberman opened this issue Oct 5, 2020 · 4 comments
Closed

Add a list of HLS executable file paths in settings #302

berberman opened this issue Oct 5, 2020 · 4 comments
Labels
type: enhancement An enhancement to an already existing feature

Comments

@berberman
Copy link
Collaborator

Although it is convenient for most of us, sometimes it can be noisy. I need switch hls between few versions (dynamic linked / static linked), and hls may not appear in PATH. Opening a project, I will find that the plugin has already started downloading it, before I set the path to hls executable manually, so I have to deleted the downloaded binaries to keep it clean, even if those binaries will not make any difference in runtime.

@jneira
Copy link
Member

jneira commented Oct 5, 2020

@berberman thanks for the suggestion, it makes totally sense. Fortunately the download is configurable in master, only left publish the extension.
(the pr closed #294, duplicate of this one)

@berberman
Copy link
Collaborator Author

Perhaps maintaining a list of hls executables' paths for switching in the settings will be nice. 😉

@jneira
Copy link
Member

jneira commented Oct 5, 2020

That would be nice too, please change the title of the issue then (or open a new one, as you wish)

@berberman berberman changed the title Option to disable downloading hls binaries automatically Add a list of HLS executable file paths in settings Oct 5, 2020
@jneira jneira added the type: enhancement An enhancement to an already existing feature label Oct 18, 2020
@fendor
Copy link
Collaborator

fendor commented Dec 5, 2022

Not relevant any more, if still a problem, please open a new issue with a new description.

@fendor fendor closed this as completed Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement An enhancement to an already existing feature
Projects
None yet
Development

No branches or pull requests

3 participants