Long SSH commands are hard to see

[strictlyskyler]

Referencing strictlyskyler/harbormaster#1

[strictlyskyler]

@luzlab What would be an appropriate change, in your opinion? Swapping the <input> for a <textarea>?

[luzlab]

I like that it's only a single line, that should stay the same. Can you make it reactively sized?

[strictlyskyler]

What would be a sensible cap for resizing? Or did you mean resizing the text to be smaller for longer commands? And if we're talking about size, another valid way to handle long commands might be with line breaks, e.g.:

curl \
  -f \
  -H "token: [the token for this user with this lane]" \
  -H "user_id: [the user id]" \
  -X POST [url]/lanes/[lane name]/ship[?key=value]

Perhaps it would make sense to provide two toggles about the command: wide and tall.

A wide command might expand the input horizontally, whereas a tall one would provide more vertical height.

Or, perhaps we just change it to a textarea and provide a toggle for enabling/disabling resizing.

Really, in my haste, you've seen some of my "sensible defaults" creep in. I think configuration probably makes sense for this, and would love to hear your ideas (and PRs) for sensible defaults.

[luzlab]

I'll give it a shot tonight...