You are not logged in.

#26 2014-12-19 08:45:29

Marie-Lou
Member
Registered: 2012-03-29
Posts: 6

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

Thank you very much The Compiler for your work. Sounds promising!

I wonder if you plan to integrate some of dwb extensions (formfiller, unique_tabs, refcontrol… you have already answered about request policy).

Another question: dwb sets the variables DWB_URI, DWB_TITLE (etc., etc.) with userscripts. Any equivalent with qutebrowser?

Thanks again smile

Offline

#27 2014-12-19 09:00:18

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

Marie-Lou wrote:

I wonder if you plan to integrate some of dwb extensions (formfiller, unique_tabs, refcontrol… you have already answered about request policy).

After there's some kind of (python-) plugin support, I'll sure port some of them - also to see if the plugin API has everything it needs.

Of course javascript plugin support, maybe even compatible to dwb, would be nice. But there are some problems with that, because I can't run javascript when javascript is turned off for the page, and the page has access to all plugin javascript objects, which... isn't exactly ideal.

Portix himself wanted to look into using QJSEngine to create a javascript plugin API, but I haven't heard back from him.

Marie-Lou wrote:

Another question: dwb sets the variables DWB_URI, DWB_TITLE (etc., etc.) with userscripts. Any equivalent with qutebrowser?

There's QUTE_URL and QUTE_FIFO. I just opened issue #379 to set some more useful variables.

Florian


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#28 2014-12-19 11:14:37

r6
Member
From: Melbourne
Registered: 2008-07-02
Posts: 156

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

Hi Florian,

The Compiler wrote:

Huh? So it scrolls up when you scroll down and vice-versa? That's odd.

Does that also happen in other widgets than the web view, e.g. if you do :report and open the text field under "Show log" there? Does it also happen when you start minimal_webkit_testbrowser.py with some URL as argument?

Can you share some more details, like the hardware you're on, and the output of xinput list --long?

The touchpad is configured for natural scrolling, using xinput set-button-map. It works in other apps but for some reason not qutebrowser (nor the minimal test browser or the text in the :report dialog). I don't think it's Qt because I just installed another Qt app and that scrolled correctly. The touchpad is a Logitech T650. The output of xinput list --long:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
	Reporting 9 classes:
		Class originated from: 9. Type: XIButtonClass
		Buttons supported: 24
		Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown"
		Button state:
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 0:
		  Label: Rel X
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 1:
		  Label: Rel Y
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 2:
		  Label: Rel Horiz Wheel
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 3:
		  Label: Rel Dial
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 4:
		  Label: Rel Vert Wheel
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 2
		  type: 2 (horizontal)
		  increment: 1.000000
		  flags: 0x0
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 3
		  type: 2 (horizontal)
		  increment: 1.000000
		  flags: 0x0
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 4
		  type: 1 (vertical)
		  increment: -1.000000
		  flags: 0x2 ( preferred )

⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
	Reporting 3 classes:
		Class originated from: 4. Type: XIButtonClass
		Buttons supported: 10
		Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
		Button state:
		Class originated from: 4. Type: XIValuatorClass
		Detail for Valuator 0:
		  Label: Rel X
		  Range: -1.000000 - -1.000000
		  Resolution: 0 units/m
		  Mode: relative
		Class originated from: 4. Type: XIValuatorClass
		Detail for Valuator 1:
		  Label: Rel Y
		  Range: -1.000000 - -1.000000
		  Resolution: 0 units/m
		  Mode: relative

⎜   ↳ Logitech Unifying Device. Wireless PID:4101	id=9	[slave  pointer  (2)]
	Reporting 10 classes:
		Class originated from: 9. Type: XIButtonClass
		Buttons supported: 24
		Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown"
		Button state:
		Class originated from: 9. Type: XIKeyClass
		Keycodes supported: 248
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 0:
		  Label: Rel X
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 1:
		  Label: Rel Y
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 2:
		  Label: Rel Horiz Wheel
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 3:
		  Label: Rel Dial
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIValuatorClass
		Detail for Valuator 4:
		  Label: Rel Vert Wheel
		  Range: -1.000000 - -1.000000
		  Resolution: 1 units/m
		  Mode: relative
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 2
		  type: 2 (horizontal)
		  increment: 1.000000
		  flags: 0x0
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 3
		  type: 2 (horizontal)
		  increment: 1.000000
		  flags: 0x0
		Class originated from: 9. Type: XIScrollClass
		Scroll info for Valuator 4
		  type: 1 (vertical)
		  increment: -1.000000
		  flags: 0x2 ( preferred )

⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
	Reporting 1 classes:
		Class originated from: 8. Type: XIKeyClass
		Keycodes supported: 248

    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
	Reporting 1 classes:
		Class originated from: 5. Type: XIKeyClass
		Keycodes supported: 248

    ↳ Power Button                            	id=6	[slave  keyboard (3)]
	Reporting 1 classes:
		Class originated from: 6. Type: XIKeyClass
		Keycodes supported: 248

    ↳ Power Button                            	id=7	[slave  keyboard (3)]
	Reporting 1 classes:
		Class originated from: 7. Type: XIKeyClass
		Keycodes supported: 248

    ↳ Eee PC WMI hotkeys                      	id=10	[slave  keyboard (3)]
	Reporting 1 classes:
		Class originated from: 10. Type: XIKeyClass
		Keycodes supported: 248

    ↳ Topre Corporation HHKB Professional     	id=8	[slave  keyboard (3)]
	Reporting 1 classes:
		Class originated from: 8. Type: XIKeyClass
		Keycodes supported: 248
TheCompiler wrote:
r6 wrote:

Is it possible to follow links by typing the link text?

Yes - :set hints mode number.

Great! Is it possible to see which link is selected?

Offline

#29 2014-12-19 18:16:51

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

r6 wrote:

The touchpad is configured for natural scrolling, using xinput set-button-map. It works in other apps but for some reason not qutebrowser (nor the minimal test browser or the text in the :report dialog). I don't think it's Qt because I just installed another Qt app and that scrolled correctly. The touchpad is a Logitech T650.

Is the other Qt application you tested Qt4 or Qt5? My guess would be it's a Qt4 -> Qt5 regression and you tested a Qt4 application, as the test browser is really simple.

I opened issue #387 so I don't forget with the flood of bugreports and suggestions I get lately big_smile

r6 wrote:
TheCompiler wrote:
r6 wrote:

Is it possible to follow links by typing the link text?

Yes - :set hints mode number.

Great! Is it possible to see which link is selected?

What do you mean exactly? The link which would be selected when you only type a part and then would press enter? Then issue #69 would be the one for that. big_smile


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#30 2014-12-19 21:24:08

r6
Member
From: Melbourne
Registered: 2008-07-02
Posts: 156

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

The Compiler wrote:

Is the other Qt application you tested Qt4 or Qt5? My guess would be it's a Qt4 -> Qt5 regression and you tested a Qt4 application, as the test browser is really simple.

You're right, it was znotes which is Qt4.

TheCompiler wrote:
r6 wrote:

Great! Is it possible to see which link is selected?

What do you mean exactly? The link which would be selected when you only type a part and then would press enter? Then issue #69 would be the one for that. big_smile

Yes, that's what I meant. Thanks smile

Offline

#31 2014-12-22 04:02:27

wretch
Member
From: pdx
Registered: 2012-11-24
Posts: 22

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

The Compiler wrote:
wretch wrote:

I currently set my window/frame borders in hlwm, and my colors in bar, based off my terminal color hex codes for urxvt in Xresources.  Are there any hooks (current or planned) that would allow me to do this during qutebrowser startup? A post-configuration callback (python or otherwise)? Or should I just do some sed'ing in xinit?

There's issue #35 for "generic" hooks calling scripts. And issue #30 for Python plugin support. Though both probably will take a while until they're implemented (unless someone contributes code on that!), so for now probably the sed'ing tongue

Any kind of generic hook would suffice. I played around with the run-userscript command and can get qutebrowser looking exactly how I want it. I wasn't aware it could do what I needed it to do. Awesome that this is already possible in v0.1 smile Just would like a run-userscript call post configuration....

JS and Python scripts would still be awesome, of course

The Compiler wrote:
wretch wrote:

Any way to change status and tab bar heights via the conf file?

They should adjust to the text size in them, which you can customize via the fonts -> statusbar and fonts -> tabbar settings.

Does this suffice for you? Maybe a "padding" setting would make sense? Or what's the motivation behind changing this exactly?

Yeah, "padding" is what I guess I'm talking about. In some browsers (Luakit), the status bar is the same size as the tab bar, and I prefer it that way. More space for content and all.

The Compiler wrote:
wretch wrote:

How about disabling the scroll-on-tabbar-to-switch-tabs feature?

Oh! I got bitten by that as well but didn't think about turning it off big_smile

I'll probably add a config option though, as there might be people who want that behaviour.

I opened issue #374 for that.
[...]
Florian

Yeah, I work on a windows box, so muscle memory from click-to-focus makes me think that "If I'm scrolling, I expect a page to scroll" no matter what my mouse is hovering over smile.

Offline

#32 2015-01-16 23:31:30

hollandheese
Member
Registered: 2014-08-11
Posts: 2

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

The Compiler wrote:
hollandheese wrote:

Super fast. Just wish it wasn't using QT5 since font rendering is terrible in that toolkit. Not your fault of course.

Could you explain (and maybe add a screenshot) of what you're seeing exactly? I'm having some issues on Windows with ClearType (their subpixel-rendering feature, AFAIK) turned off (so my ProggyTiny bitmap font looks right). But on Linux, everything looks great for me.

Florian

In Linux for me and many others (it may have to do with Infinality), QT5 fonts are extremely light and fuzzy compared to everything else.

Here's a screenshot from the most recent build of qutebrowser (right) and dwb_collect (left).

Last edited by hollandheese (2015-01-16 23:35:52)

Offline

#33 2015-01-18 02:22:25

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

hollandheese wrote:
The Compiler wrote:
hollandheese wrote:

Super fast. Just wish it wasn't using QT5 since font rendering is terrible in that toolkit. Not your fault of course.

Could you explain (and maybe add a screenshot) of what you're seeing exactly? I'm having some issues on Windows with ClearType (their subpixel-rendering feature, AFAIK) turned off (so my ProggyTiny bitmap font looks right). But on Linux, everything looks great for me.

Florian

In Linux for me and many others (it may have to do with Infinality), QT5 fonts are extremely light and fuzzy compared to everything else.

Here's a screenshot from the most recent build of qutebrowser (right) and dwb_collect (left).

Meh.

There's an issue about it here: https://github.com/The-Compiler/qutebrowser/issues/423

There's been a font-width related change in Qt recently - I want to check if that maybe helps, and if not, I might report it upstream.

The reporter also mentioned a workaround, to switch to a different font:

It helps a bit to set the fonts to a font that is naturally more "weighty", like this:
web-family-serif: Roboto Medium
web-family-sans-serif: Roboto Medium


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#34 2015-01-28 12:26:09

Roshless
Member
Registered: 2013-02-28
Posts: 7
Website

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

Is there an option to restore tabs from last session? Can't find it in settings.

@edit: thanks for responding, keep up the good work.

Last edited by Roshless (2015-01-28 16:57:36)

Offline

#35 2015-01-28 12:28:12

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

Roshless wrote:

Is there an option to restore tabs from last session? Can't find it in settings.

Not yet, but I'll work on that very soon - hopefully in the next 2 weeks or so!


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#36 2015-01-30 19:49:51

Gadileth
Member
Registered: 2013-08-02
Posts: 32

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

Some things i discovered:

Scrolling in /r/talesfromtechsupport on reddit is lagging hard. But that seems to be a problem with that specific subreddit. So not that important.

A bigger problem is that going back and forward (H and L) does not work on reddit.com. It just reloads the page.

Offline

#37 2015-01-30 22:11:38

rikn00
Member
Registered: 2014-06-26
Posts: 21

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

Gadileth wrote:

Some things i discovered:

Scrolling in /r/talesfromtechsupport on reddit is lagging hard. But that seems to be a problem with that specific subreddit. So not that important.

A bigger problem is that going back and forward (H and L) does not work on reddit.com. It just reloads the page.

That /r/talesfromtechsupport lag happens for me too. Something similar but less freezing seems to happen on long GitHub code pages. /r/talesfromtechsupport lag happened also with Qupzilla so that is maybe qt related.

Offline

#38 2015-01-30 23:01:21

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

Gadileth wrote:

A bigger problem is that going back and forward (H and L) does not work on reddit.com. It just reloads the page.

I pinpointed down this issue but I don't know how to fix it yet. See the bug report you opened, #493

rikn00 wrote:

That /r/talesfromtechsupport lag happens for me too. Something similar but less freezing seems to happen on long GitHub code pages. /r/talesfromtechsupport lag happened also with Qupzilla so that is maybe qt related.

The GitHub issue was reported upstream by me a while ago (QTBUG-40559) and a patch which should improve this was posted later. It'll land in Qt 5.5 (not 5.4.1 unfortunately), which should be released on 28th of April.

I ran Valgrind/Callgrind to figure out if the /r/talesfromtechsupport lagging is the same, and I think it is.

Flo

Last edited by The Compiler (2015-01-30 23:02:01)


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#39 2015-02-08 23:20:55

mkolenda
Member
Registered: 2014-11-08
Posts: 1

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

I've just started using qutebrowser. It's great.
I would like to see way to run command for last active browser window from console.
It just came to my mind when i tried to make pidgin and qutebrowser play together. It's opening new window for all `qutebrowser http://google.com` for now.

Offline

#40 2015-02-08 23:27:36

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

The Compiler wrote:
Roshless wrote:

Is there an option to restore tabs from last session? Can't find it in settings.

Not yet, but I'll work on that very soon - hopefully in the next 2 weeks or so!

Small update: I started working on this in the sessions branch - it should be ready in the next few days smile

mkolenda wrote:

I would like to see way to run command for last active browser window from console.
It just came to my mind when i tried to make pidgin and qutebrowser play together. It's opening new window for all `qutebrowser http://google.com` for now.

You can change that behaviour with :set general new-instance-open-target tab.

However you can also send a command by starting qutebrowser with :command args as a (single) argument, e.g. qutebrowser ":tab-close".

Flo


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#41 2015-02-13 17:32:26

ArturShaik
Member
Registered: 2015-02-13
Posts: 5

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

Nice work man. Have question, what about caret mode?

Offline

#42 2015-02-13 17:51:39

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

ArturShaik wrote:

Nice work man. Have question, what about caret mode?

Thanks!

There's spatial navigation provided by QtWebKit, you can turn that on by using :set input spatial-navigation true. Though I've never tested it, and I'm not sure if it's entirely the same thing you're referring to. Let me know how it works out!


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#43 2015-02-16 03:04:04

ArturShaik
Member
Registered: 2015-02-13
Posts: 5

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

The Compiler wrote:

There's spatial navigation provided by QtWebKit, you can turn that on by using :set input spatial-navigation true. Though I've never tested it, and I'm not sure if it's entirely the same thing you're referring to. Let me know how it works out!

Unfortunately it allows only jump through links by arrow keys. My general request is to have ability visually select and yank text.

Offline

#44 2015-03-10 13:45:20

nadley
Member
Registered: 2014-09-01
Posts: 7

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

I have been using qutebrowser for a while now and have to say that it truly is an excellent browser! I have a couple of feature requests though:

  • I would like a hint-rapid command instead of using hint with the rapid target. I often want to download several files on a page (I use hint together with spawn to execute a command that append the selected urls to a file and then run wget), and it would really be convenient not having to invoke hint multiple times, but instead just type all desired hints in one go. I have tried to use :repeat, but it doesn't seem to work with hint.

  • When typing :open, the quickmarks are shown. I would like qutebrowser to be able to invoke a command instead to produce this list. Then it would be possible to integrate it neatly with an external bookmark handler, for example something like bm (https://github.com/cym13/bookmark).

  • It would also be nice if it was possible to run a command each time an url is opened (with the url as argument). That would for example make it possible to keep track of the browsing history in a database.

Offline

#45 2015-03-10 20:06:10

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

ArturShaik wrote:
The Compiler wrote:

There's spatial navigation provided by QtWebKit, you can turn that on by using :set input spatial-navigation true. Though I've never tested it, and I'm not sure if it's entirely the same thing you're referring to. Let me know how it works out!

Unfortunately it allows only jump through links by arrow keys. My general request is to have ability visually select and yank text.

I don't have a better solution for that currently I'm afraid. It also would probably be quite some effort, so I don't think it's something I'll do... Patches welcome though!

edit: ArturShaik implemented caret browsing in the meantime! smile

nadley wrote:

I have been using qutebrowser for a while now and have to say that it truly is an excellent browser! I have a couple of feature requests though:

  • I would like a hint-rapid command instead of using hint with the rapid target. I often want to download several files on a page (I use hint together with spawn to execute a command that append the selected urls to a file and then run wget), and it would really be convenient not having to invoke hint multiple times, but instead just type all desired hints in one go. I have tried to use :repeat, but it doesn't seem to work with hint.

Great idea! I just added a --rapid parameter to :hint and deprecated the rapid and rapid-win targets. The new option can be used with the tab-bg/window/run/hover/userscript/spawn targets, so you should be good to go! I tested with :hint --rapid links spawn notify-send {hint-url}.

nadley wrote:
  • When typing :open, the quickmarks are shown. I would like qutebrowser to be able to invoke a command instead to produce this list. Then it would be possible to integrate it neatly with an external bookmark handler, for example something like bm (https://github.com/cym13/bookmark).

I don't think this is something which should be added as a simple option right now, but I added that as a possible use case for issue #30 (plugin support). Then of course plugins can also update the completion if needed, etc.

nadley wrote:
  • It would also be nice if it was possible to run a command each time an url is opened (with the url as argument). That would for example make it possible to keep track of the browsing history in a database.

See issue #35 for that.

Both will probably take a while though, as I'm busy with a lot of other stuff for v0.2 and v0.3 currently wink

Florian

Last edited by The Compiler (2015-06-11 05:44:00)


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

#46 2015-03-11 09:56:05

nadley
Member
Registered: 2014-09-01
Posts: 7

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

Thanks a lot for the amazingly fast update! I just tried the new --rapid parameter and it works very well.

Offline

#47 2015-03-24 15:43:58

NoSuck
Member
Registered: 2015-03-04
Posts: 157
Website

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

Well, you got me.  I never new a web browser could be so fun.  Thank you.

I am making a concerted effort to use qutebrowser for my daily driver, which is crazy, when you think about it... In one corner, you have a handful of international organizations, each with hundreds of millions of dollars, entire teams of programmers, and squadrons of researchers--and in the other corner, a rogue programmer from Switzerland.  Granted, you have Python, Qt, and forefathers like dwb and uzbl on your side--but Mozilla and company have those, too.

... but they don't have me.   Starting today, my allegiance lies with qutebrowser.  That might not mean much to Mozilla, Google, you, or anyone else, but it means a lot to me.

Offline

#48 2015-03-24 18:57:17

chickenPie4tea
Member
Registered: 2012-08-21
Posts: 309

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

Just trying this out, I was impressed at how quickly it loaded a page full of images after a google search for "cats" compared to firefox.
Trouble is I always use firefox mostly because of the "Last-Pass" plugin. None of the smaller browsers have anything as easy to use and convenient.
Using keepass is such a drag.  Good job though.


You can like linux without becoming a fanatic!

Offline

#49 2015-03-25 07:45:46

NoSuck
Member
Registered: 2015-03-04
Posts: 157
Website

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

Anyone migrating from Firefox might find it convenient to export browsing history from places.sqlite to plain text using sqlitebrowser.  I sorted by the last_visit_date field.

As for bookmark management, I'm still looking.  Bookmarks.public looks good, but SRESI has a collapsible hierarchy.  I also think multiple tags should be selectable when filtering, but neither seems to offer such functionality.

Offline

#50 2015-03-25 09:26:41

The Compiler
Member
From: Winterthur, Switzerland
Registered: 2011-05-01
Posts: 211
Website

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

NoSuck wrote:

Well, you got me.  I never new a web browser could be so fun.  Thank you.

I am making a concerted effort to use qutebrowser for my daily driver, which is crazy, when you think about it... In one corner, you have a handful of international organizations, each with hundreds of millions of dollars, entire teams of programmers, and squadrons of researchers--and in the other corner, a rogue programmer from Switzerland.  Granted, you have Python, Qt, and forefathers like dwb and uzbl on your side--but Mozilla and company have those, too.

... but they don't have me.   Starting today, my allegiance lies with qutebrowser.  That might not mean much to Mozilla, Google, you, or anyone else, but it means a lot to me.

Thank you for the kind words! And it does mean much to me - I'm always happy when I see people using and appreciating qutebrowser. Honestly, I never thought it'd be such a success smile

chickenPie4tea wrote:

Just trying this out, I was impressed at how quickly it loaded a page full of images after a google search for "cats" compared to firefox.
Trouble is I always use firefox mostly because of the "Last-Pass" plugin. None of the smaller browsers have anything as easy to use and convenient.
Using keepass is such a drag.  Good job though.

There will be plugin support at some point. Then, doing a LastPass plugin with something like lastpass-python shouldn't be too hard! smile


>>> from __future__ import braces
  File "<stdin>", line 1
SyntaxError: not a chance

Offline

Board footer

Powered by FluxBB