Comment by 🕹️ skyjake

Re: "clagrange doesn't open https urls in browser"

In: s/Lagrange

Looking at Lagrange's `openInDefaultBrowser` function, it unfortunately does not have an implementation for the terminal.

To fix this, you'd probably want to configure some shell command that opens the appropriate (TUI?) browser. I'll make a note of adding such a configuration option in a future release.

🕹️ skyjake [mod, sysop]

Jan 26 · 4 months ago

3 Later Comments ↓

👾 fab [OP] · Jan 26 at 17:22:

@skyjake That would be awesome! Thanks for your great work!

🚀 ibannieto · Jan 26 at 18:33:

May be you can use xdg-open?

👾 fab [OP] · Jan 26 at 19:11:

@ibannieto It seems that this functionality is not built into clagrange. Hopefully @skyjake will add an option to set a specific browser for opening web links soon.

Original Post

🌒 s/Lagrange

clagrange doesn't open https urls in browser — I don't have much experience with lagrange (I used to use amfora) so please be patient. When I open a https link in Lagrange it opens in qutebrowser as it should. But when I follow a https link in clagrange nothing happens - the page isn't opened. So how do I configure clagrange to open https links in my favorite browser? I really like TUI interfaces and maybe I'll switch to clagrange because it supports gemini, gopher and finger (and some others I...

💬 fab · 5 comments · Jan 26 · 4 months ago