You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a bug, a missing feature, or a design decision. If the latter, close away.
Escaped newlines (i.e. lines ending with ) don't seem to work in my config.fish file. I couldn't find another way to do multi-line strings. It's not an essential feature, but some of us like to have 80-character-max scripts, especially on machines that we ssh into with frequency.
Some commands in particular get long really quickly, especially if you're slicing-and-dicing output with a bunch of cut, sed, grep, and tr commands. Jamming these all into one line makes them hard to read. I'd love to at least be able to line break right before a pipe.
I'm not sure if this is a bug, a missing feature, or a design decision. If the latter, close away.
Escaped newlines (i.e. lines ending with ) don't seem to work in my config.fish file. I couldn't find another way to do multi-line strings. It's not an essential feature, but some of us like to have 80-character-max scripts, especially on machines that we ssh into with frequency.
Some commands in particular get long really quickly, especially if you're slicing-and-dicing output with a bunch of
cut,sed,grep, andtrcommands. Jamming these all into one line makes them hard to read. I'd love to at least be able to line break right before a pipe.