file:// URIs (in PR #7526 )VtEngine::_SetHyperlink uses fmt::format to render the hyperlinks, and it should really use _WriteFormattedStringProposed order of attack:
Hey so hover tooltip might be hard - we can't embed a webview, so doing something like

Might be _especially_ hard. But we could start with a TeachingTip sytle one for now

Unless we could somehow pre-render a web page to an image and display that in the tooltip. Or use something like the "social" image from github (though I haven't the damndest clue how that works.)
Maybe we should just start with
Open [web page | file]:
{url}
in the tooltip
Yeah i definitely think _tooltip_ and “the link preview from the video” are different workitems that we should tackle separately :)
If you have to have a "link preview", I'd recommend something really basic based on the page meta data (like the meta title and description, and maybe a favicon and/or og:image). But as cool as this might seem, I don't think it's practical for a hover effect given the delay needed to download and render these things (unless you're pre-rendering the previews, which sounds like a really bad idea).
Which brings me to the main problem. Even if you're only connecting to the site on hover, that still seems inadvisable. When I'm using a terminal I really wouldn't expect it to be making internet connections without my consent. So this feature would definitely have to be optional, and arguably I think should be off by default.
I'm possibly a little biased here, because my internet connection is metered to a certain extent. But even if that weren't the case, would most people be comfortable with their terminal downloading unknown webpages in the background?
Yeah, I definitely don't think that "fetch any link I hover over" is something we should ship in core or opt-in by default. It makes for a really compelling video because it shows how modern and flashy we are, but it's too much of a disclosure and safety risk to put right into our project.
- Allow
mailto:URIs
Would this be RFC conforming 😒 mailto: URL, or 😍 mailto: URL that allows multiple email addresses?
Generally, "whatever type of thing is supported by the registered protocol handler" ;P
I don't know whether this has been considered already, but when doing a rich-text copy of the terminal buffer the hyperlinks should probably be preserved on paste
Thanks @jantari! Just added that to the main scenario body.
I just built the latest commit, but it can't parse an url, you have to use the escape sequences. Is this use case planned:
bash
echo 'Hello from Windows Terminal: https://github.com/microsoft/terminal/'
And then click on the link and it opens?
@giggio er..



I don't just say these things for fun 😉 (edit: this was intended to be read as "funny", not "wow Dustin's a jerk" (but I get it!))
I had seen that comment, I was just not sure that this is what it meant, thanks for the clarification, Dustin!
And good thing you explained, so I could see it as funny. ;)
So, if I understand correctly, we don't have yet an issue tracking this item (auto-detection) specifically?
@giggio There's a lot of discussion about how to do autodetection in the comments on https://github.com/microsoft/terminal/issues/574 :smile: so we're somewhat treating that issue as canonical.
Question about url detection in 1.5.3142.
Works great in the terminal, but not inside vi. Is the app doing something special to disable this, or a different mode that url detection does not work with? I was really hoping to be able to Ctrl-Click all those documentation links in code comments.


So, Vim (if that's your vi implementation of choice) enables "mouse mode" -- it lets you select text and navigate the document with your mouse. You can either turn off mouse mode (:set mouse=) or temporarily suppress it by holding down Shift.
(This is also the reason that you cannot select text _using the terminal_ when Vim is running.)
Thanks for the information, "mouse mode" was not turned on by default for me in:
and links worked OOTB, but I could enable it on either with :set mouse=a and not only did it exhibit the behavior you described but I also learned about mouse-mode today, thanks!
Most helpful comment
Proposed order of attack: