Excerpts from Florian Bruhin's message of January 6, 2019 4:18 pm:
> I'm not sure actually. Is there other use-cases you can think of apart
> from setting the file type?
I personally can't. But then, it's not something I've devoted a lot of
thought to. It does seem to me there is more
On Sun, Jan 06, 2019 at 01:36:21PM +0930, David Nebauer wrote:
> Excerpts from Jay Kamat's message of January 6, 2019 8:20 am:
> >
> > I already said this in the issue you posted, but I think the cleanest
> > solution for this is to add url pattern support to editor.command directly.
>
> I
Excerpts from Jay Kamat's message of January 6, 2019 8:20 am:
>
> I already said this in the issue you posted, but I think the cleanest
> solution for this is to add url pattern support to editor.command directly.
I wholeheartedly agree. As I posted in the issue, I have been able to
come up
David Nebauer writes:
> When I attempted to set a per-domain editor.command in config.py and
> source it, I received an error that editor.command does not support URL
> patterns.
I already said this in the issue you posted, but I think the cleanest
solution for this is to add url pattern
I use gvim as external editor and want to be able to set a particular
filetype when it is launched from a specific domain. One way to
"communicate" this from qutebrowser to gvim is that when launching from
the specific domain, editor.command would include a "set filetype"
command.
In case it
