{"action":"created","issue":{"url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/1415","repository_url":"https://api.github.com/repos/The-Compiler/qutebrowser","labels_url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/1415/labels{/name}","comments_url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/1415/comments","events_url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/1415/events","html_url":"https://github.com/The-Compiler/qutebrowser/issues/1415","id":147271286,"number":1415,"title":"Restore a session in a separate instance","user":{"login":"lahwaacz","id":1289205,"avatar_url":"https://avatars.githubusercontent.com/u/1289205?v=3","gravatar_id":"","url":"https://api.github.com/users/lahwaacz","html_url":"https://github.com/lahwaacz","followers_url":"https://api.github.com/users/lahwaacz/followers","following_url":"https://api.github.com/users/lahwaacz/following{/other_user}","gists_url":"https://api.github.com/users/lahwaacz/gists{/gist_id}","starred_url":"https://api.github.com/users/lahwaacz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lahwaacz/subscriptions","organizations_url":"https://api.github.com/users/lahwaacz/orgs","repos_url":"https://api.github.com/users/lahwaacz/repos","events_url":"https://api.github.com/users/lahwaacz/events{/privacy}","received_events_url":"https://api.github.com/users/lahwaacz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-10T21:45:41Z","updated_at":"2016-04-11T04:59:04Z","closed_at":null,"body":"Continuing https://github.com/The-Compiler/qutebrowser/issues/499#issuecomment-207596718, how can I restore a session in a separate instance? The behaviour of `--restore` in qutebrowser is fundamentally different from that of [dwb](http://portix.bitbucket.org/dwb/resources/manpage.html), which always starts a new instance. The `--basedir` flag is not useful here because the sessions storage (`~/.local/share/qutebrowser/sessions/` by default) is affected by `--basedir`.\r\n\r\nTo take it more generally, I don't think that mixing sessions in a single instance is a good idea. One thing is performance (the more separate processes the better), second is that `:q` affects the whole session and there is no `:session-close`. When `:session-load`, you have two sessions mixed together, each possibly involving multiple windows, without any way to separate them at this point. And the original session might have been accidentally unsaved."},"comment":{"url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/comments/208163164","html_url":"https://github.com/The-Compiler/qutebrowser/issues/1415#issuecomment-208163164","issue_url":"https://api.github.com/repos/The-Compiler/qutebrowser/issues/1415","id":208163164,"user":{"login":"The-Compiler","id":625793,"avatar_url":"https://avatars.githubusercontent.com/u/625793?v=3","gravatar_id":"","url":"https://api.github.com/users/The-Compiler","html_url":"https://github.com/The-Compiler","followers_url":"https://api.github.com/users/The-Compiler/followers","following_url":"https://api.github.com/users/The-Compiler/following{/other_user}","gists_url":"https://api.github.com/users/The-Compiler/gists{/gist_id}","starred_url":"https://api.github.com/users/The-Compiler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/The-Compiler/subscriptions","organizations_url":"https://api.github.com/users/The-Compiler/orgs","repos_url":"https://api.github.com/users/The-Compiler/repos","events_url":"https://api.github.com/users/The-Compiler/events{/privacy}","received_events_url":"https://api.github.com/users/The-Compiler/received_events","type":"User","site_admin":false},"created_at":"2016-04-11T04:59:03Z","updated_at":"2016-04-11T04:59:03Z","body":"The behaviour of dwb is different even without sessions involved, as it simply starts one instance per window (e.g. even `:winopen` actually opens a new instance).\r\n\r\nThis seems to work because WebKitGTK seems to provide the means to do so - unfortunately QtWebKit (and quite possibly also QtWebEngine) doesn't, so qutebrowser has to use one instance for multiple windows, and can only have another instance with a completely separate cache/local storage/cookie/... store. It might be possible to share the config across instances (especially after the config revolution™), but probably not any other data.\r\n\r\n---\r\n\r\n> One thing is performance (the more separate processes the better)\r\n\r\nQtWebEngine will have a renderer process for each tab, FWIW.\r\n\r\n> second is that `:q` affects the whole session and there is no `:session-close`.\r\n\r\nI think it's a good idea to add `:session-close`, and maybe even (optionally) indicating what session a window belongs to in the title. There is some previous discussion about this in #572, so I think this can be closed as a duplicate if you agree?"}}