date:20190715

[qutebrowser] (no subject)

2019-07-15 Thread Adam Ladell

Hey!

I've been trying to use nvim (or even nano) as my editor for qutebrowser,
however, neither of them update the input field upon saving and closing.

In the logs it seems that the readback from the editor is showing up as
blank.

I've attached the logs from a session where I opened qutebrowser and then
opened the editor after selecting the duck-duck-go search field.

Any help would be greatly appreciated!

Thanks!

18:46:22 DEBUGinit   app:__init__:821 Initializing application...
18:46:22 DEBUGipcipc:send_to_running_instance:433 Connecting to
/run/user/1000/qutebrowser/ipc-6729149549b212a12bdb50e1132840d3
18:46:22 DEBUGipcipc:send_to_running_instance:466 No existing
instance present (error 2)
18:46:22 DEBUGinit   ipc:send_or_listen:495 Starting IPC server...
18:46:22 DEBUGipcipc:__init__:191 Not calling setSocketOptions
18:46:22 DEBUGipcipc:listen:202 Listening as
/run/user/1000/qutebrowser/ipc-6729149549b212a12bdb50e1132840d3
18:46:22 DEBUGinit   app:init:164 Starting init...
18:46:22 DEBUGextensions loader:_load_component:153 Importing
qutebrowser.components.adblock
18:46:22 DEBUGextensions loader:_load_component:162 Running init hook
'init'
18:46:22 DEBUGextensions loader:_load_component:153 Importing
qutebrowser.components.caretcommands
18:46:22 DEBUGextensions loader:_load_component:153 Importing
qutebrowser.components.misccommands
18:46:22 DEBUGextensions loader:_load_component:153 Importing
qutebrowser.components.scrollcommands
18:46:22 DEBUGextensions loader:_load_component:153 Importing
qutebrowser.components.zoomcommands
18:46:22 DEBUGinit   app:_init_modules:427 Initializing save
manager...
18:46:22 DEBUGinit   app:_init_modules:432 Checking backend
requirements...
18:46:22 DEBUGinit   app:_init_modules:435 Initializing prompts...
18:46:22 DEBUGinit   app:_init_modules:438 Initializing network...
18:46:22 DEBUGinit   networkmanager:init:109 Default Qt ciphers:
TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256,
TLS_AES_128_GCM_SHA256, ECDHE-ECDSA-AES256-GCM-SHA384,
ECDHE-RSA-AES256-GCM-SHA384, DHE-RSA-AES256-GCM-SHA384,
ECDHE-ECDSA-CHACHA20-POLY1305, ECDHE-RSA-CHACHA20-POLY1305,
DHE-RSA-CHACHA20-POLY1305, ECDHE-ECDSA-AES128-GCM-SHA256,
ECDHE-RSA-AES128-GCM-SHA256, DHE-RSA-AES128-GCM-SHA256,
ECDHE-ECDSA-AES256-SHA384, ECDHE-RSA-AES256-SHA384, DHE-RSA-AES256-SHA256,
ECDHE-ECDSA-AES128-SHA256, ECDHE-RSA-AES128-SHA256, DHE-RSA-AES128-SHA256,
ECDHE-ECDSA-AES256-SHA, ECDHE-RSA-AES256-SHA, DHE-RSA-AES256-SHA,
ECDHE-ECDSA-AES128-SHA, ECDHE-RSA-AES128-SHA, DHE-RSA-AES128-SHA,
RSA-PSK-AES256-GCM-SHA384, DHE-PSK-AES256-GCM-SHA384,
RSA-PSK-CHACHA20-POLY1305, DHE-PSK-CHACHA20-POLY1305,
ECDHE-PSK-CHACHA20-POLY1305, AES256-GCM-SHA384, PSK-AES256-GCM-SHA384,
PSK-CHACHA20-POLY1305, RSA-PSK-AES128-GCM-SHA256,
DHE-PSK-AES128-GCM-SHA256, AES128-GCM-SHA256, PSK-AES128-GCM-SHA256,
AES256-SHA256, AES128-SHA256, ECDHE-PSK-AES256-CBC-SHA384,
ECDHE-PSK-AES256-CBC-SHA, SRP-RSA-AES-256-CBC-SHA, SRP-AES-256-CBC-SHA,
RSA-PSK-AES256-CBC-SHA384, DHE-PSK-AES256-CBC-SHA384,
RSA-PSK-AES256-CBC-SHA, DHE-PSK-AES256-CBC-SHA, AES256-SHA,
PSK-AES256-CBC-SHA384, PSK-AES256-CBC-SHA, ECDHE-PSK-AES128-CBC-SHA256,
ECDHE-PSK-AES128-CBC-SHA, SRP-RSA-AES-128-CBC-SHA, SRP-AES-128-CBC-SHA,
RSA-PSK-AES128-CBC-SHA256, DHE-PSK-AES128-CBC-SHA256,
RSA-PSK-AES128-CBC-SHA, DHE-PSK-AES128-CBC-SHA, AES128-SHA,
PSK-AES128-CBC-SHA256, PSK-AES128-CBC-SHA
18:46:22 DEBUGinit   networkmanager:init:120 Disabling bad ciphers:
18:46:22 DEBUGinit   app:_init_modules:441 Initializing proxy...
18:46:22 DEBUGinit   app:_init_modules:444 Initializing
readline-bridge...
18:46:22 DEBUGinit   app:_init_modules:449 Initializing sql...
18:46:22 DEBUGsqlsql:__init__:179 Preparing SQL query: "PRAGMA
journal_mode=WAL"
18:46:22 DEBUGsqlsql:run:212 Running SQL query: "PRAGMA
journal_mode=WAL"
18:46:22 DEBUGsqlsql:run:215 query bindings: {}
18:46:22 DEBUGsqlsql:__init__:179 Preparing SQL query: "PRAGMA
synchronous=NORMAL"
18:46:22 DEBUGsqlsql:run:212 Running SQL query: "PRAGMA
synchronous=NORMAL"
18:46:22 DEBUGsqlsql:run:215 query bindings: {}
18:46:22 DEBUGinit   app:_init_modules:452 Initializing web
history...
18:46:22 DEBUGsqlsql:__init__:179 Preparing SQL query: "CREATE
TABLE IF NOT EXISTS History (url NOT NULL, title NOT NULL, atime NOT NULL,
redirect NOT NULL)"
18:46:22 DEBUGsqlsql:run:212 Running SQL query: "CREATE TABLE
IF NOT EXISTS History (url NOT NULL, title NOT NULL, atime NOT NULL,
redirect NOT NULL)"
18:46:22 DEBUGsqlsql:run:215 query bindings: {}
18:46:22 DEBUGsqlsql:__init__:179 Preparing SQL query: "CREATE
TABLE IF NOT EXISTS CompletionHistory (url PRIMARY KEY, title NOT NULL,
last_atime NOT NULL)"
18:46:22 DEBUGsqlsql:run:212 Running SQL query:

Re: [qutebrowser] Any probability of moving away from Chromium?

2019-07-15 Thread Florian Bruhin

Hi,

On Mon, Jul 15, 2019 at 06:38:18PM +1000, Paul W. Rankin wrote:
> Having looked at the Qt situation I think I already know the answer to this
> one, but is there any possibility of ever moving away from using
> Chromium/QtWebEngine?

You already can (and always could) run qutebrowser with QtWebKit instead.

It's not maintained as well as QtWebEngine though (which is why I wouldn't
recommend it, especially from a security point of view), but it's recently
gaining some traction again.

> Chromium burns through energy like a bitcoin farm, it runs at turtle speed,
> and there's the whole tragicomedy of Google removing the webRequest API to
> block blockers. But it seems like the only option?

FWIW the webRequest thing likely won't affect qutebrowser at all.

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/

signature.asc
Description: PGP signature

Re: [qutebrowser] nvim/nano as editor (was: no subject)

2019-07-15 Thread Florian Bruhin

Hey Adam,

two meta-things first:

- You aren't subscribed to the list, so your post was held back - I approved it
  and whitelisted you now, but you might want to subscribe to ensure you get
  all replies.

- Please set a subject when writing mails, especially to a mailinglist. There
  are many people who get a lot of mails (as well as mailinglist archives), so
  having a subject is very important to find things.

On Sun, Jul 14, 2019 at 06:59:08PM +1000, Adam Ladell wrote:
> I've been trying to use nvim (or even nano) as my editor for qutebrowser,
> however, neither of them update the input field upon saving and closing.
> 
> In the logs it seems that the readback from the editor is showing up as
> blank.
> 
> I've attached the logs from a session where I opened qutebrowser and then
> opened the editor after selecting the duck-duck-go search field.

The problem is that your terminator exits immediately, before you quit your
editor. Thus, qutebrowser thinks that you exited your editor.

Try adding --no-dbus to terminator's arguments so it always starts a new
instance instead of opening your editor as a new window inside the existing
instance.

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Re: [qutebrowser] (no subject)

2019-07-15 Thread Florian Bruhin

On Mon, Jul 15, 2019 at 09:58:17AM -0700, Jay Kamat wrote:
> 
> Adam Ladell writes:
> 
> > Hey!
> > 
> > I've been trying to use nvim (or even nano) as my editor for qutebrowser,
> > however, neither of them update the input field upon saving and closing.
> 
> Does the default (gvim) work fine for you? FWIW, the following
> editor.command works for me, I'm not 100% sure this is what you've set it
> to:
> 
> set editor.command '["terminator", "-x", "vim", "{file}"]'

Only when no other instance of terminator is open, at least here.

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Re: [qutebrowser] (no subject)

2019-07-15 Thread Jay Kamat




Adam Ladell writes:


Hey!

I've been trying to use nvim (or even nano) as my editor for qutebrowser,
however, neither of them update the input field upon saving and closing.


Does the default (gvim) work fine for you? FWIW, the following editor.command 
works for me, I'm not 100% sure this is what you've set it to:


set editor.command '["terminator", "-x", "vim", "{file}"]'

Could you also pastebin your :version please?

-Jay

[qutebrowser] (no subject)

Re: [qutebrowser] Any probability of moving away from Chromium?

Re: [qutebrowser] nvim/nano as editor (was: no subject)

Re: [qutebrowser] (no subject)

Re: [qutebrowser] (no subject)

5 matches

Site Navigation

Mail list logo

Footer information