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
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
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
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
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
