From me at the-compiler.org Mon Jun 1 17:44:00 2020 From: me at the-compiler.org (Florian Bruhin) Date: Mon, 1 Jun 2020 17:44:00 +0200 Subject: [qutebrowser] qutebrowser v1.12.0 released Message-ID: <20200601154400.ggadjfyusffjflou@hooch.localdomain> Hey, I'm happy to announce that I just released qutebrowser v1.12.0! This issue adds another workaround for sessions on Qt 5.15, where sessions.lazy_restore caused sessions to be lost, as (like mentioned previously) Qt 5.15 only loads the most recently opened page for every tab. Now, lazy_restore is ignored on Qt 5.15. Despite that, I decided to bundle Qt 5.15 for Windows/macOS and enable Qt 5.15 for mkvenv.py by default, to get security updates in the underlying Chromium out. If you're using a virtualenv install and prefer staying on an older Qt, run mkvenv.py with --pyqt-version 5.14 to keep the older Qt version. More information can be found in the following issue: https://github.com/qutebrowser/qutebrowser/issues/5359 I'll now take a break from qutebrowser and open-source stuff for the remainder of this week (i.e. essentially mostly-at-home holidays) and then figure out how to solve this issue (and, if possible time-wise, also integrate some PRs related to sessions at the same time) next week. This release also comes with various new features and changes, such as settings for Chromium's dark mode or per-domain support for the content.cookies.accept setting. See the full changelog for more details: ## Removed - `tox -e mkvenv` which was deprecated in qutebrowser v1.10.0 is now removed. Use the `mkvenv.py` script instead. - Support for using `config.bind(key, None)` in `config.py` to unbind a key was deprecated in v1.8.2 and is now removed. Use `config.unbind(key)` instead. - `:yank markdown` was deprecated in v1.7.0 and is now removed. Use `:yank inline [{title}]({url})` instead. ## Added - New `:debug-keytester` command, which shows a "key tester" widget. Previously, that was only available as a separate application via `python3 -m scripts.keytester`. - New `:config-diff` command which opens the `qute://configdiff` page. - New `--debug-flag log-cookies` to log cokies to the debug log for debugging. - New `colors.contextmenu.disabled.{fg,bg}` settings to customize colors for disabled items in the context menu. - New line selection mode (`:toggle-selection --line`), bound to `Shift-V` in caret mode. - New `colors.webpage.darkmode.*` settings to control Chromium's dark mode. Note that those settings only work with QtWebEngine on Qt >= 5.14 and require a restart of qutebrowser. ## Changed - Windows and macOS releases now ship Qt 5.15, which is based on Chromium 80.0.3987.163 with security fixes up to 81.0.4044.138. - The `content.cookies.accept` setting now accepts URL patterns. - Tests are now included in release tarballs. Note that only running them with the exact dependencies listed in `misc/requirements/requirements-tests.txt{,-raw}` is supported. - The `:tab-focus` command now has completion for tabs in the current window. - The `bindings.key_mappings` setting now maps `` to the tab key by default. - `:tab-give --private` now detaches a tab into a new private window. ## Fixed - Using `:open -s` now only rewrites `http://` in URLs to `https://`, not other schemes like `qute://`. - When an unhandled exception happens in certain parts of the code (outside of the main thread), qutebrowser did crash or freeze when trying to show its exception handler. This is now fixed. - `:inspector` now works correctly when cookies are disabled globally. - Added workaround for a (Gentoo?) PyQt/packaging issue related to the `QWebEngineFindTextResult` handling added in v1.11.0. - When entering caret selection mode (`v, v`) very early before a page is loaded, an error is now shown instead of a crash happening. - The workaround for session loading with Qt 5.15 now handles `sessions.lazy_restore` so that the saved page is loaded instead of the "stub" page with no possibility to get to the web page. - A site specific quirk to allow typing accented characters on Google Docs was active for docs.google.com, but not drive.google.com. It is now applied for both subdomains. - With older graphics hardware (OpenGL < 4.3) with Qt 5.14 on Wayland, WebGL causes segfaults. Now qutebrowser detects that combination and suggests to disable WebGL or use XWayland. Enjoy! Florian -- me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From konubinix at gmail.com Fri Jun 5 12:09:41 2020 From: konubinix at gmail.com (Samuel Loury) Date: Fri, 05 Jun 2020 10:09:41 -0000 Subject: [qutebrowser] Automatically enabling passthrough mode on certain websites In-Reply-To: <20200501152727.ihfs7n5kbc3a4c2o@valoup> References: <20200501152727.ihfs7n5kbc3a4c2o@valoup> Message-ID: <87h7wuzg0b.fsf@gmail.com> Valentin Iovene writes: > +1 for this. it could be very useful also for things like Jupyter > notebooks. right now, when i have to deal with Jupyter notebooks i have > to switch to another browser. I have been using qutebrowser for 1 year and I just realized the passthrough mode. That's a very nice feature. +1 for the jupyter notebook use case :-). By the way, qutebrowser is awesome?! -- Konubinix GPG Key : 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: From andy.ashley at sky.com Thu Jun 11 02:00:55 2020 From: andy.ashley at sky.com (Andy Ashley) Date: Thu, 11 Jun 2020 01:00:55 +0100 Subject: [qutebrowser] Feature request and bug References: <0e9f3412-fe10-23b4-ff00-3597e3dcd390.ref@sky.com> Message-ID: <0e9f3412-fe10-23b4-ff00-3597e3dcd390@sky.com> I have a feature request: to be able to delete storage when closing qutebrowser. The directories: .cache/qutebrowser/webengine/Cache/ .local/share/qutebrowser/webengine/Service Worker in particular grow very large. It's difficult to know what I can safely delete. Memory use has also increased (and keeps increasing the longer qutebrowser is running). I've only noticed it since Qt5.15, but I run out of memory after 2 days of qutebrowser open, would go a week without noticing before. Using Arch Linux, Xfce desktop, qutebrowser with webengine backend. From me at the-compiler.org Thu Jun 11 22:41:55 2020 From: me at the-compiler.org (Florian Bruhin) Date: Thu, 11 Jun 2020 22:41:55 +0200 Subject: [qutebrowser] Feature request and bug In-Reply-To: <0e9f3412-fe10-23b4-ff00-3597e3dcd390@sky.com> References: <0e9f3412-fe10-23b4-ff00-3597e3dcd390.ref@sky.com> <0e9f3412-fe10-23b4-ff00-3597e3dcd390@sky.com> Message-ID: <20200611204155.jp5dnmv5mf4jh3uy@hooch.localdomain> Hey, Note you're not subscribed to the mailinglist, so your mail was held back - I whitelisted you now, but you'll not get any answers unless people explicitly add you to Cc. On Thu, Jun 11, 2020 at 01:00:55AM +0100, Andy Ashley via qutebrowser wrote: > I have a feature request: to be able to delete storage when closing > qutebrowser. > The directories: > .cache/qutebrowser/webengine/Cache/ > .local/share/qutebrowser/webengine/Service Worker > in particular grow very large. It's difficult to know what I can safely > delete. qutebrowser doesn't know more about those directories than you do - they're managed by the underlying Chromium. You can delete some stuff via :inspector, though. The one in ~/.cache is definitely safe to delete entirely. The "Service Worker" one *should* be fine, but there might be semi-persistent data in there too, I'm not sure. Also see https://github.com/qutebrowser/qutebrowser/issues/58 > Memory use has also increased (and keeps increasing the longer qutebrowser > is running). I've only noticed it since Qt5.15, but I run out of memory > after 2 days of qutebrowser open, would go a week without noticing before. > > Using Arch Linux, Xfce desktop, qutebrowser with webengine backend. See https://github.com/qutebrowser/qutebrowser/issues/1476 Florian -- me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From pauloalibano at hotmail.com Mon Jun 22 18:24:15 2020 From: pauloalibano at hotmail.com (=?iso-8859-1?Q?Paulo_Silva_de_Al=EDbano?=) Date: Mon, 22 Jun 2020 16:24:15 +0000 Subject: [qutebrowser] How to unfocus a text input field? Message-ID: Dear Qutebrowser, How can we unfocus a text input field so we can continue scrolling a page with j and k? I could not find the answer. For example: Open qute://settings/ and enter a text field (make as if you wanted to change auto_save.interval to another value). After checking you can insert text in that field, try to leave it with Esc. * Expected behavior: Insert mode was terminated and you can use j and k keys to scroll down and up. * Actual behavior: Insert mode was terminated but the text input cursor is still blinking in the field and you cannot use j and k keys to scroll. Am I missing something obvious there? I am able to get the expected behavior if I click an empty area with the mouse, but in a Qutebrowser context it goes without saying that I prefer not to use the mouse. Yours faithfully, Paulo -------------- next part -------------- An HTML attachment was scrubbed... URL: From javier at lufte.net Mon Jun 22 18:45:20 2020 From: javier at lufte.net (Javier Ayres) Date: Mon, 22 Jun 2020 13:45:20 -0300 Subject: [qutebrowser] How to unfocus a text input field? In-Reply-To: References: Message-ID: <70d238e7-c084-4b16-8de1-1f136f8347aa@www.fastmail.com> You can press tab to focus the next element, as long as it's not an input you will be able to scroll with j and k. On Mon, Jun 22, 2020, at 13:24, Paulo Silva de Al?bano wrote: > Dear Qutebrowser, > > How can we unfocus a text input field so we can continue scrolling a > page with j and k? I could not find the answer. > > For example: Open qute://settings/ and enter a text field (make as if > you wanted to change auto_save.interval to another value). After > checking you can insert text in that field, try to leave it with Esc. > * Expected behavior: Insert mode was terminated and you can use j and > k keys to scroll down and up. > * Actual behavior: Insert mode was terminated but the text input > cursor is still blinking in the field and you cannot use j and k keys > to scroll. > Am I missing something obvious there? I am able to get the expected > behavior if I click an empty area with the mouse, but in a Qutebrowser > context it goes without saying that I prefer not to use the mouse. > > Yours faithfully, > Paulo > > From me at the-compiler.org Fri Jun 26 10:58:08 2020 From: me at the-compiler.org (Florian Bruhin) Date: Fri, 26 Jun 2020 10:58:08 +0200 Subject: [qutebrowser] qutebrowser v1.13.0 released Message-ID: <20200626085808.esrhlswvfzsqaxcp@hooch.localdomain> Hey, I'm happy to announce that I released qutebrowser v1.13.0 today! Unfortunately I still haven't had the time to look at the sessions restoring code with Qt 5.15 - there were some other things I've started looking at a while back, which I wanted to finish first. Thus, that'll have to wait until v1.14.0 - but there are a lot of other new features and improvements even though v1.12.0 is only 25 days old, so I thought it was time for another release! The main new shiny thing in this release is probably the much improved developer tools, which can now be docked to the main window. They now use a new :devtools command rather than :inspector (which is now deprecated). Here's a GIF I posted a few days ago (still using the old command): https://www.reddit.com/r/qutebrowser/comments/hc9smt/soon/ Another quite visible change is that qutebrowser now shows overlay scrollbars by default: https://www.reddit.com/r/qutebrowser/comments/hc9rro/overlay_scrollbars/ Thanks to everyone who contributed something to this release! :) Talking about contributions, we're now at 45 merged pull requests since opening the project board some 10 weeks ago (and over 1500 closed PRs total!): https://github.com/qutebrowser/qutebrowser/projects/4 In this release, there's also a lot of smaller changes, improvements, and many bugfixes - here's the full changelog: ## Deprecated - The `:inspector` command is deprecated and has been replaced by a new `:devtools` command (see below). ## Removed - The `:debug-log-level` command was removed as it's replaced by the new `logging.level.console` setting. - The `qute://plainlog` special page got replaced by `qute://log?plain` - the names of those pages is considered an implementation detail, and `:messages --plain` should be used instead. ## Changed - Changes to commands: * `:config-write-py` now adds a note about `config.py` files being targeted at advanced users. * `:report` now takes two optional arguments for bug/contact information, so that it can be used without the report window popping up. * `:message` now takes a `--logfilter` / `-f` argument, which is a list of logging categories to show. * `:debug-log-filter` now understands the full logfilter syntax. - Changes to settings: * `fonts.tabs` has been split into `fonts.tabs.{selected,unselected}` (see below). * `statusbar.hide` has been renamed to `statusbar.show` with the possible values being `always` (`hide = False`), `never` (`hide = True`) or `in-mode` (new, only show statusbar outside of normal mode. * The `QtFont` config type formerly used for `fonts.tabs` and `fonts.debug_console` is now removed and entirely replaced by `Font`. The former distinction was mainly an implementation detail, and the accepted values shouldn't have changed. * `input.rocker_gestures` has been renamed to `input.mouse.rocker_gestures`. * `content.dns_prefetch` is now enabled by default again, since the crashes it caused are now fixed (Qt 5.15) or worked around. * `scrolling.bar` supports a new `overlay` value to show an overlay scrollbar, which is now the default. On unsupported configurations (on Qt < 5.11, with QtWebKit or on macOS), the value falls back to `when-searching` or `never` (QtWebKit). * `url.auto_search` supports a new `schemeless` value which always opens a search unless the given URL includes an explicit scheme. - New handling of bindings in hint mode which fixes various bugs and allows for single-letter keybindings in hint mode. - The statusbar now shows partial keychains in all modes (e.g. while hinting). - New `t[Cc][Hh]` default bindings which work similarly to the `t[Ss][Hh]` bindings for JavaScript but toggle cookie permissions. - The `tor_identity` userscript now takes the password via a `-p` flag and has a new `-c` flag to customize the Tor control port. - Small performance improvements. ## Added - New settings: * `logging.level.ram` and `logging.level.console` to configure the default logging levels via the config. * `fonts.tabs.selected` and `fonts.tabs.unselected` to set the font of the selected tab independently from unselected tabs (e.g. to make it bold). * `input.mouse.back_forward_buttons` which can be set to `false` to disable back/forward mouse buttons. - New `:devtools` command (replacing `:inspector`) with various improved functionality: * The devtools can now be docked to the main window, by running `:devtools left` (`wIh`), `bottom` (`wIj`), `top` (`wIk`) or `right` (`wIl`). To show them in a new window, use `:devtools window` (`wIw`). Using `:devtools` (`wi`) will open them at the last used position. * The devtool window now has a "qutebrowser developer tools" window title. * When a resource is opened from the devtools, it now opens in a proper qutebrowser tab. * On Fedora, when the `qt5-webengine-devtools` package is missing, an error is now shown instead of a blank inspector window. * If opened as a window, the devtools are now closed properly when the associated tab is closed. * When the devtools are clicked, insert mode is entered automatically. ## Fixed - Crash when `tabs.focus_stack_size` is set to -1. - Crash when a `pdf.js` file for PDF.js exists, but `viewer.html` does not. - Crash when `:completion-item-yank --sel` is used on a platform without primary selection support (e.g. Windows/macOS). - Crash when there's a feature permission request from Qt with an invalid URL (which happens due to a Qt bug with Qt 5.15 in private browsing mode). - Crash in rare cases where QtWebKit/QtWebEngine imports fail in unexpected ways. - Crash when something removed qutebrowser's IPC socket file and it's been running for 6 hours. - `:config-write-py` now works with paths starting with `~/...` again. - New site-specific quirk for a missing `globalThis` in Qt <= 5.12 on Reddit and Spotify. - When `;` is added to `hints.chars`, using hint labels containing `;;` now works properly. - Hint letters outside of ASCII should now work. - When `bindings.key_mappings` is used with hints, it now works properly with letters outside of ASCII as well. - With Qt 5.15, the audible/muted indicators are not updated properly due to a Qt bug. This release adds a workaround so that at least the muted indicator is shown properly. - As a workaround for crashes with QtWebEngine versions between 5.12 and 5.14 (inclusive), changing the user agent (`content.headers.user_agent`) exposed to JS now requires a restart. The corresponding HTTP header is not affected. Enjoy! Florian -- me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From elfio at hiperones.es Tue Jun 30 11:27:11 2020 From: elfio at hiperones.es (J Pablo Navarro) Date: Tue, 30 Jun 2020 11:27:11 +0200 Subject: [qutebrowser] Sharing sessions between machines Message-ID: <7702344.h1X2DWkBCQ@ulises> Hi there! Is there a way to share sessions between different machines? Other option I'd like would be to peak into other session and copy/move tabs from machine A to machine B. My usecase involves a laptop for being in the move and a desktop while I'm at home, so sometimes I'd like to rescue a few tabs I left opened in my laptop. The sync-side wouldn't be an issue if I can export a list through a shared Nextcloud account, maybe syncthing or even ssh. So in the end, maybe what I'm asking for is a way to export a session to a file or if there is such a file already in my disk. Cheers and thank you for this wonderful piece of software, Pablo. From felix.vanderjeugt+qutebrowser at posteo.net Tue Jun 30 11:37:29 2020 From: felix.vanderjeugt+qutebrowser at posteo.net (Felix Van der Jeugt) Date: Tue, 30 Jun 2020 11:37:29 +0200 Subject: [qutebrowser] Sharing sessions between machines In-Reply-To: <7702344.h1X2DWkBCQ@ulises> References: <7702344.h1X2DWkBCQ@ulises> Message-ID: <159350984999.25345.7171522694268858331@abysm> Hi, There's a sessions directory in your data directory (~/.local/share/qutebrowser by default, check :version if it's not). I'm not sure all sessions there could be shared, though. AFAIK there's no machine-specific information (in my current sessions) but there might be. Sincerely, Felix