-
Notifications
You must be signed in to change notification settings - Fork 430
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
CopyQ autostart with Windows? #1925
Comments
On Windows, this is only supported in the installer. You can run the installer again, it should not override any data/configuration. I think the manual way is still to drop the application link to an autostart folder in Start menu. |
This is good, but in the portable version, you need to manually create a shortcut before moving, which is a bit troublesome, can you add a self-launch option to the program? |
Unfortunately, On Windows, autostart can be only enabled in installer. |
Just to clarify: I don't plan to add the feature myself since I don't use Windows and I'm not even sure how I would implement the feature for the system. |
But as you said, you can put the application link into the autostart folder in the Start menu. I've seen other programs do this |
Yes. I'm accepting pull requests if anyone wants to give implement the feature. Specifically you would need to implement the following methods: CopyQ/src/platform/win/winplatform.h Lines 19 to 24 in 340aaaa
|
I am trying to get CopyQ enabled on an Remote Desktop Server. I enabled the start of the program during login by group policy, but that does not seem to work. How can I automatically start CopyQ at windows login on an RDS? I also added a task schedule to start qopyq.exe at login, I can see it runs, but the program does not start. |
CopyQ is great, but I can’t find a way to set it to Auto-Start with Windows? There may have been an option when it was first installing which I rejected at the time, but I can’t find this option within the Application menus now. Apologies if I'm missing something obvious.
The text was updated successfully, but these errors were encountered: