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

WorMzy · 2017-10-30 21:04:48

Use tab to select completions/bookmarks/quickmarks/history items, up and down arrow keys scroll through your command history. You can switch back to the previous behaviour with

:bind -f -m command <Up> completion-item-focus prev
:bind -f -m command <Down> completion-item-focus next

See qute://help/configuring.html

ghus · 2017-10-31 08:52:21

Thanks a lot!

Paul-S · 2017-11-01 19:46:49

When I try the bind command I get Bind: unrecognized arguments: -f error.

Cheers
Paul-S

Trilby · 2017-11-01 21:07:48

Please post the full command you are trying.

Paul-S · 2017-11-01 21:32:04

Trilby wrote:

Please post the full command you are trying.

:bind -f -m command <Up> completion-item-focus prev

Cheers
Paul-S

Trilby · 2017-11-02 11:27:21

Thanks - that looks fine and doesn't result in an error here.

WorMzy · 2017-11-02 13:41:37

It seems that the -f flag has been removed from :bind (it's no longer needed to overwrite existing key binds)[1][2], and configuring.html wasn't updated before 1.0.2 was tagged (but has now [3]).

Trilby, I'm guessing you're using the -git package and have a build that predates this change?

[1] https://github.com/qutebrowser/qutebrow … fce9cde636
[2] https://github.com/qutebrowser/qutebrowser/issues/3049
[3] https://github.com/qutebrowser/qutebrow … 284cbb810c

Trilby · 2017-11-02 13:54:45

WorMzy wrote:

Trilby, I'm guessing you're using the -git package and have a build that predates this change

Ah, yes - as I'm travelling I've not rebuilt my AUR packages in a bit.

captaincurrie · 2017-11-03 16:57:01

how do you turn off the console messaging? That is, i don't want to see error messages while i'm browsing

The Compiler · 2017-11-03 22:29:58

captaincurrie wrote:

how do you turn off the console messaging? That is, i don't want to see error messages while i'm browsing

--loglevel warning (or error or critical), or just don't launch from a console

Last edited by The Compiler (2017-11-03 22:43:16)

captaincurrie · 2017-11-04 08:45:42

The Compiler wrote:

captaincurrie wrote:
how do you turn off the console messaging? That is, i don't want to see error messages while i'm browsing

--loglevel warning (or error or critical), or just don't launch from a console

Oh sorry, i meant error messages that show up in the statusbar.

I have the statusbar set to hide but error messages still appear.

When i say error messages i'm refferring to the messages that you get when a spawn command fails or when
you try to go back in history and you cannot. Things like that.

The Compiler · 2017-11-04 14:35:36

captaincurrie wrote:

The Compiler wrote:
captaincurrie wrote:
how do you turn off the console messaging? That is, i don't want to see error messages while i'm browsing

--loglevel warning (or error or critical), or just don't launch from a console
Oh sorry, i meant error messages that show up in the statusbar.
I have the statusbar set to hide but error messages still appear.
When i say error messages i'm refferring to the messages that you get when a spawn command fails or when
you try to go back in history and you cannot. Things like that.

There's no way to turn those off, and it's not something I want to support in a general way. I guess I could add a setting to suppress the back/forward errors, as this isn't the first time this came up. Why don't you want to see the other errors?

Trilby · 2017-11-04 15:07:52

You could set the bg and fg of error messages to 'transparent' so they would never be visible. Presumably there'd be a narrow bar at the bottom of the page that would be "unclickable" as it would briefly have a transparent error messaage over it, but I doubt that would be a problem.

However, I also don't see why one would want to hide actual error messages.

captaincurrie · 2017-11-06 21:14:12

Trilby wrote:

You could set the bg and fg of error messages to 'transparent' so they would never be visible. Presumably there'd be a narrow bar at the bottom of the page that would be "unclickable" as it would briefly have a transparent error messaage over it, but I doubt that would be a problem.
However, I also don't see why one would want to hide actual error messages.

Thats a great idea. Thanks!

The reason i don't want to see error messages is because 9999 times out of 10000 they are redundent and i hate distractions.

monodromy · 2017-11-26 20:30:11

Thanks for your work on this browser! It's been my main browser for several months now.

I have an occasional issue, however. I have private browsing set to true. Every so often, qutebrowser creates an empty folder named "databases-incognito" in the directory I started it (ie usually my home directory). How can I suppress this behavior?

The Compiler · 2017-11-27 04:06:37

monodromy wrote:

Thanks for your work on this browser! It's been my main browser for several months now.
I have an occasional issue, however. I have private browsing set to true. Every so often, qutebrowser creates an empty folder named "databases-incognito" in the directory I started it (ie usually my home directory). How can I suppress this behavior?

You're welcome!

That's a QtWebEngine issue, see QTBUG-62957. I'm not aware of any workaround - I guess the best you can do is creating a qutebrowser wrapper script which does cd /tmp or so first.

monodromy · 2017-11-27 06:22:54

I see, thanks! I guess I'll just be patient then.

null · 2017-12-13 16:51:24

In case anyone else was waiting: There is now a FreeBSD port available: https://www.freshports.org/www/qutebrowser/

captaincurrie · 2017-12-14 20:33:34

Hello,

When opening a tab on a link which will start a download, it would be nice if that tab would close once the download has started.
Instead you have to manually close all the blank tabs.

jasonwryan · 2017-12-14 20:37:19

Why not just ;d?

The Compiler · 2017-12-15 08:59:18

captaincurrie wrote:

When opening a tab on a link which will start a download, it would be nice if that tab would close once the download has started.
Instead you have to manually close all the blank tabs.

Unfortunately, there's currently no way for qutebrowser to know which tab started a download. That might change with Qt 5.11.

captaincurrie · 2017-12-18 01:32:27

jasonwryan wrote:

Why not just ;d?

Because point+click is faster, not to mention more intuitive, with a mouse then with a keyboard. Especially for multiple links.

But thank you for the suggestion, i didn't know that one.

jasonwryan · 2017-12-26 21:31:00

Whenever I copy something from the clipboard into a text field, the next keypress (Enter, Backspace, or anything really) will repaste the snippet again.

So, if I want to paste a URL here: I copy it and then hit Shift-Insert, Enter: the result is:

https://bbs.archlinux.org/viewtopic.php?id=57855
https://bbs.archlinux.org/viewtopic.php?id=57855

So, I have to then backspace over the second URL and newline to continue typing. Is anyone else seeing this?

I have tested in Firefox and Chromium and cannot reproduce there, which makes me think it is a Qute/QT issue.

qutebrowser 1.0.4-1
qt5-base 5.10.0-1
qt5-webengine 5.10.0-1

Trilby · 2017-12-26 21:33:22

Jason:
https://github.com/qutebrowser/qutebrowser/issues/3420
https://github.com/qutebrowser/qutebrowser/issues/3419

jasonwryan · 2017-12-26 21:47:23

Ugh, I didn't think to look at the issue tracker. FML. Sorry for the noise.

Arch Linux

#601 2017-10-30 21:04:48

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

#602 2017-10-31 08:52:21

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

#603 2017-11-01 19:46:49

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

#604 2017-11-01 21:07:48

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

#605 2017-11-01 21:32:04

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

#606 2017-11-02 11:27:21

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

#607 2017-11-02 13:41:37

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

#608 2017-11-02 13:54:45

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

#609 2017-11-03 16:57:01

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

#610 2017-11-03 22:29:58

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

#611 2017-11-04 08:45:42

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

#612 2017-11-04 14:35:36

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

#613 2017-11-04 15:07:52

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

#614 2017-11-06 21:14:12

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

#615 2017-11-26 20:30:11

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

#616 2017-11-27 04:06:37

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

#617 2017-11-27 06:22:54

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

#618 2017-12-13 16:51:24

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

#619 2017-12-14 20:33:34

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

#620 2017-12-14 20:37:19

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

#621 2017-12-15 08:59:18

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

#622 2017-12-18 01:32:27

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

#623 2017-12-26 21:31:00

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

#624 2017-12-26 21:33:22

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

#625 2017-12-26 21:47:23

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

Board footer