qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

Docbroke · 2017-09-21 03:16:19

Oh, didn't realize that, as I used PKGBUILD from qutebrowser-git to replace webkit with webengine, as dependancy.

Trilby · 2017-09-22 20:49:52

I got yaml colors thanks to TheCompilers suggestion above. I modified it a bit though to have a single unified yaml config, and to add *all* config options to my yaml config. There was one tricky bit with the tabs.padding, so that was just pulled out before everything else is converted from dicts object attributes. My config.py:

import os, yaml

path = os.path.dirname(os.path.abspath(__file__))
with open(path + '/config.yaml', 'r') as f:
    conf = yaml.load(f)

def _dict_attrs(obj, path=''):
    if isinstance(obj, dict):
        for k, v in obj.items():
            yield from _dict_attrs(v, '{}.{}'.format(path, k) if path else k)
    else:
        yield path, obj

config.load_autoconfig = False
c.bindings.default = {}
c.bindings.commands = conf['bindings']

c.tabs.padding = conf['general']['tabs']['padding']
del conf['general']['tabs']['padding']

conf['general']['colors'] = conf['colors']
for k, v in _dict_attrs(conf['general']):
    config.set(k, v)

del conf

And the config.yaml

Last edited by Trilby (2017-09-22 20:59:14)

The Compiler · 2017-09-28 19:04:07

Hey,

just a quick update to let you know that the last one of four big changes is now done:

[x] The new completion, based on sqlite
[x] The new config system
[x] Dropping legacy support
[x] Making QtWebEngine the default backend

If QtWebEngine can't be used on your system for some reason, you'll get a message about it. If it can, it'll automatically use that unless you set the "backend" setting to "webkit".

I still hope to get v1.0.0 with all this out in mid-November, before Firefox 57 is released - if possible, with some initial form of per-domain settings!

If you find any issues or need help, please let me know!

Florian

The Compiler · 2017-10-12 09:30:52

I'm delighted to announce that I just released qutebrowser v1.0.0!
This release comes with many big breaking changes such as the new config and QtWebEngine by default, so please take a look at the changelog.
As announced previously, per-domain settings unfortunately didn't make it into v1.0.0 - it's the next thing I plan on tackling. However, there's more than enough big things in v1.0.0!
Enjoy!

parchd · 2017-10-12 12:03:02

Congrats, and thanks for all the hard work!

WorMzy · 2017-10-12 12:13:39

Thanks for all the hard work!

Ambrevar · 2017-10-12 12:31:57

I'll package this as soon as possible!

The Compiler · 2017-10-12 18:28:35

Ambrevar wrote:

I'll package this as soon as possible!

Note that a v1.0.1 release will follow quite soon (i.e. probably today or tomorrow morning) because of a rather bad bug which makes qutebrowser not start when you configure the tab font.

Ambrevar · 2017-10-12 18:45:58

Roger that, will wait for tomorrow then.

holytrousers · 2017-10-12 21:37:22

I really enjoyed qutebrowser a lot but had to give up after a while because it was a bit heavy on my limited resources.

firecat53 · 2017-10-12 21:37:46

Sorry if I missed it here someplace, but when using

editor = urxvtc -title edit -e vim "{}"

, any existing text in the text area is not populated into the vim instance. Works fine with gvim. What am I missing?

Thanks!

jasonwryan · 2017-10-12 21:50:05

Can confirm.

My editor line is more involved:

c.editor.command = ["urxvt", "-title", "scratchpad", "-geometry", "86x24+40+60", "-e", "vim", "-f", '"{}"']

and I get an error in vim when I :wq:

""/tmp/qutebrowser-editor-jgjgjr_"" E212: Can't open file for writing

The Compiler · 2017-10-13 04:27:17

@firecat53 Where are you setting it like that? With v0.11.1 or v1.0.0?

@jasonwryan Don't double-quote {} - there's no shell involved.

jasonwryan · 2017-10-13 04:53:12

That works, thanks Florian.

firecat53 · 2017-10-13 05:26:40

Community repo v0.11.1, in ~/.config/qutebrowser/(config file... On mobile can't remember exactly name). I haven't tested the 1.0.x release yet.

The Compiler · 2017-10-13 08:33:27

Ambrevar wrote:

Roger that, will wait for tomorrow then.

v1.0.1 has now been released, with the following fixes:

Fixed starting after customizing `fonts.tabs` or `fonts.debug_console`.
Fixed starting with old PyQt versions compiled against newer Qt versions.
Fixed check for PyQt version to correctly enforce 5.7 (not 5.2).

firecat53 wrote:

Sorry if I missed it here someplace, but when using
editor = urxvtc -title edit -e vim "{}"
, any existing text in the text area is not populated into the vim instance. Works fine with gvim. What am I missing?

I'd expect the text to show up in vim anyways (but not be applied to the website correctly) in this case. The problem is that urxvtc exits immediately before you exit vim, so qutebrowser doesn't know when you're finished with editing. Might want to try spawning urxvt instead.

firecat53 · 2017-10-13 19:58:41

Works correctly with urxvt, thanks!

Ambrevar · 2017-10-13 20:04:29

Qutebrowser 1.0.1 is in community!

Let me know if you spot anything wrong with the packaging as there are quite a few changes.

jasonwryan · 2017-10-13 20:42:17

Thanks Ambrevar!

captaincurrie · 2017-10-14 06:09:57

Hello,

I would like to write a TOR toggler. Right now i have in my config.py

  config.bind('<Ctrl-t>', 'set network proxy socks://localhost:9050/', mode='normal')

But it would be better if it would work as a toggle. That is, be able to check if qutebrowser is already connected to TOR and then turn
it off. Something like

  config.bind('<Ctrl-t>, torToggle(), mode='normal')

How would I write that torToggle function?

The Compiler · 2017-10-14 20:50:13

Ambrevar wrote:

Qutebrowser 1.0.1 is in community!
Let me know if you spot anything wrong with the packaging as there are quite a few changes.

Thank you! Two small things I noticed:

- Please remove the "and QtWebKit" from pkgdesc
- I'm not sure what of the desktop-file-utils/hicolor-icon-theme/libxkbcommon-x11/xdg-utils dependencies are still needed. I think at least some of those were from back when there weren't pacman hooks yet, and those were needed for the old qutebrowser.install?

edit: Oh, note that I might release v1.0.2 already tomorrow or so (sorry!), as v1.0 broke the workaround making qutebrowser work on nvidia graphiccards

captaincurrie wrote:

I would like to write a TOR toggler. Right now i have in my config.py
  config.bind('<Ctrl-t>', 'set network proxy socks://localhost:9050/', mode='normal')
But it would be better if it would work as a toggle. That is, be able to check if qutebrowser is already connected to TOR and then turn
it off. Something like
  config.bind('<Ctrl-t>, torToggle(), mode='normal')
How would I write that torToggle function?

Bind it to something like config-cycle -p content.proxy socks://localhost:9050/ system instead.

Last edited by The Compiler (2017-10-14 21:07:50)

Docbroke · 2017-10-15 06:28:23

I was waiting for this update for a long time, thanks.

I am missing "open in new window" on right click menu? There is only follow link. I have to use copy link and use that link to open new instance of qutebrowser. Am I missing something?

The Compiler · 2017-10-15 08:35:11

Docbroke wrote:

I was waiting for this update for a long time, thanks.
I am missing "open in new window" on right click menu? There is only follow link. I have to use copy link and use that link to open new instance of qutebrowser. Am I missing something?

qutebrowser doesn't customize the context menu, so that's just the different engine running now.

You can use hints via wf to open things in a new window though.

The Compiler · 2017-10-17 06:02:22

The Compiler wrote:

Ambrevar wrote:
Qutebrowser 1.0.1 is in community!
Let me know if you spot anything wrong with the packaging as there are quite a few changes.
Thank you! Two small things I noticed:
- Please remove the "and QtWebKit" from pkgdesc
- I'm not sure what of the desktop-file-utils/hicolor-icon-theme/libxkbcommon-x11/xdg-utils dependencies are still needed. I think at least some of those were from back when there weren't pacman hooks yet, and those were needed for the old qutebrowser.install?
edit: Oh, note that I might release v1.0.2 already tomorrow or so (sorry!), as v1.0 broke the workaround making qutebrowser work on nvidia graphiccards

I released v1.0.2 now, with a handful of fixes:

- Fix workaround for black screens or crashes with Nvidia cards
- Handle a filesystem going read-only gracefully
- Fix crash when setting fonts.monospace
- Fix list options not being modifyable via .append() in config.py
- Mark the content.notifications setting as QtWebKit only correctly
- Fix wrong rendering of keys like <back> in the completion
- Nicer error messages and other minor improvements

Ambrevar · 2017-10-17 22:02:51

1.0.2 online with change in dependencies:

- desktop-file-utils/hicolor-icon-theme: Qutebrowser has hicolor icons and should normally depend on xdg-icon-resource.
The KDE page on the wiki (https://wiki.archlinux.org/index.php/KD … tall_files) seems out of date... Anyone?

- libxkbcommon-x11: this one is a dependency of PyQt5 so it's safe to remove it.

- xdg-utils: no clue about that one.

@The Compiler: You did add those dependencies when you first created the PKGBUILD, didn't you?

If anything fails for anybody here, please let me know.

Arch Linux

#551 2017-09-21 03:16:19

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#552 2017-09-22 20:49:52

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#553 2017-09-28 19:04:07

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#554 2017-10-12 09:30:52

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#555 2017-10-12 12:03:02

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#556 2017-10-12 12:13:39

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#557 2017-10-12 12:31:57

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#558 2017-10-12 18:28:35

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#559 2017-10-12 18:45:58

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#560 2017-10-12 21:37:22

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#561 2017-10-12 21:37:46

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#562 2017-10-12 21:50:05

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#563 2017-10-13 04:27:17

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#564 2017-10-13 04:53:12

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#565 2017-10-13 05:26:40

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#566 2017-10-13 08:33:27

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#567 2017-10-13 19:58:41

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#568 2017-10-13 20:04:29

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#569 2017-10-13 20:42:17

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#570 2017-10-14 06:09:57

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#571 2017-10-14 20:50:13

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#572 2017-10-15 06:28:23

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#573 2017-10-15 08:35:11

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#574 2017-10-17 06:02:22

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

#575 2017-10-17 22:02:51

Re: qutebrowser - A keyboard-driven, vim-like browser based on PyQt5

Board footer