-
Notifications
You must be signed in to change notification settings - Fork 4
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
New restart method #17
Comments
It's really a shame, I was using that (admittedly buggy) thing for more than just restarting Firefox. I had actually already changed the text in the restart notice to the
Calling So I don't think that is a good idea. It only marginally helps in the normal case, but can behave very wrong in other cases. Another option would be to kill Firefox (the PID is easy to get) and start it again. But this would require the exact original command line (which is not that stable to get across OSes) and would still mess with the process tree. (And would also require the So that is unstable as well. I did not know about the But I think, with considerable effort and OS-specific implementations) this could be automated: send Buuut that's a lot of work to get right. So for now the text is changed and that's it. Reference: https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options |
FWIW, I just found a cool page on 64.0b2 called |
- make restart notifications optional (#18) - make style updates slightly more efficient - handle subframes differently
Thanks for the update! reStyle now suggests to use |
It seems like the Shift+F2 bar will go away soon, it is gone already for me in 62 beta and 63 nightly.
Easiest way to restart now would be going to
about:profiles
and clickingRestart normally...
I was also thinking, maybe reStyle can automate some of it, with the help of NativeExt?
Opening the page automatically/with a button would be a good start.
Alternatively, as suggested in the link, user could press
Ctrl
+Shift
+J
and thenCtrl
+Alt
+R
, but that is a lot of buttons to press and leaves a potentially confusing log-spamming window open.The text was updated successfully, but these errors were encountered: