Comment

Comment by zhengt

Warp engineer here! The shell has arbitrary access to the environment, and there's a long tail of shell config to play nice with. For example, here's a fun technical read about how we supported PS1 and how the 9c byte caused some issues (https://www.warp.dev/blog/whats-so-special-about-ps1). We've prioritized issues based on the impact for the product. If you're up for it, I'd love if you could file some issues about the problems you're experiencing.

There are a lot of great shell configs. One advantage of Warp is that the terminal & shell have these features out-of-the-box.

> A shell script will run in it's interpreter regardless of what shell you happen to use, shared commands will inherently be in the flavour of shell-script that the sharer is used to, and so i have to know how to use their shell as well as mine to translate between them, which again isn't a problem when running a script.

Workflows in Warp specify the shell in the metadata.

The idea for workflows is to allow people to search commands based on what they accomplish, rather than requiring everybody to remember the command and type. For example, if I wanted to delete all empty files in a line, instead of remembering the exact incantation of sed to accomplish this, I could search "delete empty files".

parent zhengt 4 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton