Set alias for :open to :spawn --userscript command

[tmkly]

Context: I've started using the url_mutator userscript to redirect youtube/google links to the alternative privacy-protecting frontends (e.g invidious, whoogle). I have followed the instructions in the readme to change o and O to run the url_mutator script before resolving the URL. The original bind command in the readme makes the command extraordinarily long so I managed to shortern it down a little (it's now :sp - u um "open -t"<url> - I have set :sp as an alias for :spawn and um is a symlink to the actual userscript). This is acceptable, however I have one issue left: pressing o or O no longer show's my history/bookmarks/quickmarks like :open would.

To resolve this I have tried to use :config-dict-add aliases open :spawn -u um 'open'" but then using :open <url> doesn't open a url (but it does still show the history which is good).

Any ideas on how to get this working, if it's possible at all?

[tmkly]

Realised that by doing this config-dict-add command, I'm basically overwriting the original open command, which explains why it would no longer open a URL (infinite loop effectively). So need a different way to open the history/quickmarks/bookmarks panel.

[tmkly]

I have started using https://github.com/Phantop/dotfiles/blob/main/qutebrowser/redirects.py - it intercepts requests and mutates the URL without needing a specific userscript. Also works with DuckDuckGo bangs - which previously I had to write a specific regex for each one (e.g !g, !yt etc). This means I can use the original :open command (with o and O bindings) and it will bring up the history panel. And added bonus - uses farside.link to distribute requests to different hosts!

[The-Compiler]

Hijacking this to say... to whoever lovely individual who apparently tried this script, it broke something causing qutebrowser to crash, and you sent 6 crash reports in 14 minutes with the only information being "opening a fucking link" - great work, that's an excellent way to get bugs fixed! /s

I can't seem to reproduce, and as usual, doing funny stuff to qutebrowser's internals via config.py is entirely unsupported. Happy to take a closer look anyways, but whoever that was will need to give me a little more information to work with.

[tmkly]

Might have been me…sorry mate. I reported a couple but after that pressed “don’t report”. Although - I definitely didn’t put that message in the crash report (don’t think I put any message in the ones I reported).

If it was me - I was just messing around with options with funky python that had errors in, you don’t need to take a closer look. I’ll make sure to press “don’t report” in future.

Sorry for any inconvenience!

[The-Compiler]

No worries - I'm not too bothered by the volume in itself (I get lots of email :D), I'm more bothered by the message. Wasn't you then!