Configurable file hyperlinks

[jennybc]

This PR makes it possible for Positron (or any execution context) to inform cli how file hyperlinks need to be constructed in order to work in Positron's terminals. What I mean by "work" is that file hyperlinks open in this product and don't delegate to the operating system. This is beneficial for Positron's R package development tasks, most especially devtools::test(), which will emit links like path/to/test-foo:10:3 when tests fail. Companion to the already-merged #739. Here's a video of running devtools::test() and taking advantage of clickable filepaths and runnable code (for reviewing or accepting snapshots):

Screen.Recording.2024-12-16.at.4.10.39.PM.mov

Note the screen recording is made with a local branch of Positron, which also needs another PR.

---

Still a draft, because I need to add tests and docs, but I'll start adding some comments to get a discussion going.

[jennybc]

I'm going to need to detect this version in Positron. We only want to enable hyperlinks in the relevant terminals if we know they're going work exactly as we want.

[jennybc]

This became narrower, i.e. just about parsing.

[jennybc]

This turns the parsed filepath into the data style_hyperlink() needs.

[jennybc]

As it stands, only an explicitly configured hyperlink format has any effect.

But you could imagine detecting that we're in, e.g. a Positron or VS Code terminal, and setting this configuration from the cli side. Food for thought. But definitely something that could be added later.

[jennybc]

I took inspiration from other tools, such as ripgrep. Here's how ripgrep can be configured to construct hyperlinks for various environments:

https://github.com/BurntSushi/ripgrep/blob/bf63fe8f258afc09bae6caa48f0ae35eaf115005/crates/printer/src/hyperlink_aliases.rs#L4-L22

/// Aliases to well-known hyperlink schemes.
///
/// These need to be sorted by name.
const HYPERLINK_PATTERN_ALIASES: &[(&str, &str)] = &[
    #[cfg(not(windows))]
    ("default", "file://{host}{path}"),
    #[cfg(windows)]
    ("default", "file://{path}"),
    ("file", "file://{host}{path}"),
    // https://github.com/misaki-web/grepp
    ("grep+", "grep+://{path}:{line}"),
    ("kitty", "file://{host}{path}#{line}"),
    // https://macvim.org/docs/gui_mac.txt.html#mvim%3A%2F%2F
    ("macvim", "mvim://open?url=file://{path}&line={line}&column={column}"),
    ("none", ""),
    // https://macromates.com/blog/2007/the-textmate-url-scheme/
    ("textmate", "txmt://open?url=file://{path}&line={line}&column={column}"),
    // https://code.visualstudio.com/docs/editor/command-line#_opening-vs-code-with-urls
    ("vscode", "vscode://file{path}:{line}:{column}"),
    ("vscode-insiders", "vscode-insiders://file{path}:{line}:{column}"),
    ("vscodium", "vscodium://file{path}:{line}:{column}"),
];

Documentation of the vscode:// URL scheme and, therefore, the positron:// URL scheme:

https://code.visualstudio.com/docs/editor/command-line#_opening-vs-code-with-urls

delta is another tool that has a similar configuration point:

https://dandavison.github.io/delta/tips-and-tricks/using-delta-with-vscode.html

https://dandavison.github.io/delta/hyperlinks.html

[jennybc]

In actual use this is looking pretty good now. For my own convenience, I want to record how to test drive this even without the necessary changes in Positron.

In a terminal inside VS Code, set up some environment variables and then start R:

export R_CLI_HYPERLINKS=true
export R_CLI_HYPERLINK_FILE_URL_FORMAT=vscode://file{path}:{line}:{column}
R

In that R session, you should be able to create cli file hyperlinks and Ctrl/Cmd+click on them to open in VS Code, e.g.:

cli::cli_text("{.file ~/.gitconfig}")

Likewise, you could do some in a terminal inside a released version of Positron but changing the file hyperlink format:

export R_CLI_HYPERLINKS=true
export R_CLI_HYPERLINK_FILE_URL_FORMAT=positron://file{path}:{line}:{column}
R

I'll be back to soon finalize this and remove the draft status.