-
Notifications
You must be signed in to change notification settings - Fork 253
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
[Feature] Consider undeprecating should_launch_new_instance #1297
Comments
Here's the expected behavior (using the build in the synctex_update branch): screencapture-020225-185907.mp4Each document gets opened in a different window and instance, gets swallowed properly and quitting one doesn't quit the other. |
There is a way to launch new instances by specifying the name in the development branch as of this commit: 4c99080. You should pass the |
Yes, and that's great if you want to manage different named instances, however this complicates matters when sioyek is not called directly from the command line but rather through multiple layers of software. In the examples above I am using the lf file manager and to achieve different instances per window, rather than just changing the value in sioyek's config, I would have to hard-code the lf config to use sioyek with the |
I mean I will probably add an option to automatically create new instances, but if you window manager can not handle apps with multiple windows ... you need a better window manager! |
Re-added the |
Currently there is no intuitive way to open multiple documents with sioyek on both different windows and different instances. This leads to some issues with interfaces that expect different instances for every document opened.
Notice in this example how my terminal/WM swallows the first window I open but doesn't swallow the other (new) windows, and they all close when I press Q to quit since they are all within the same instance (I assume this is intended behavior, but I find it really unintiutive). Having all of them in a different instance would fix these issues.
out.mp4
The text was updated successfully, but these errors were encountered: