Abusing url handling in iTerm2 and Hyper for code execution

1. iterm2

   1 38 - -

   [0] https://gitlab.com/gnachman/iterm2/-/issues/10994 the discussion in there makes it seem like it's okay because many schemes that aren't http[s] cause the browser to open a dialog box

   Features of iTerm2 I use:

     - fullscreen without using MacOS's spaces implementation of fullscreen

2. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

3. skopeo

   2 23 9,428 9.2 Go

   Work with remote images registries - retrieving information, images, signing content

   

   I believe skopeo should allow you to: https://github.com/containers/skopeo

4. coreutils

   3 124 4,643 9.7 C

   upstream mirror (by coreutils)

   

   AFAIK, the remote applications simply do an isatty() check on the stdout and that's it; a proper terminal is then apparently expected to correctly skip and quietly ignore any OSC sequence it does not understand. See the source of ls [0], for example.

   [0] https://github.com/coreutils/coreutils/blob/2a72cf1e9959f40b...

Suggest a related project