Show HN: Curl https://ec2.shop • Hacker News Board

Re: Show HN: Curl https://ec2.shop

#81

Post by ryanmccullagh » Wed, Jul 01, 2020, 2:01 AM UTC

Nice list. Recently, I loaded all the prices into an Excel document to make things easier for projecting costs and determining prices. I always use the following formula for estimating monthly costs on Amezmo.

$Hourly * 750

750 being the number of hours in 1 month.

Re: Show HN: Curl https://ec2.shop

#82

Post by skissane » Wed, Jul 01, 2020, 8:48 AM UTC

geofft wrote: post #69

gruez wrote: post #55

Earlier quoted context omitted.

but why "ansi"? ANSI is only an encoding. You can have html that's in ansi, and you can have something like OP's that's not in ansi (eg. if you add emojis).

This is "ANSI" as in ANSI X3.64 escape sequences, not "ANSI" as in a character encoding. You can output color to curl on an ANSI-compatible terminal but not to something expecting actual plain text like a browser.

I think text/ecma48 would be a better name. There are lots of ANSI standards. (I guess text/ansi-x3.64 might also work, but text/ecma48 seems simpler.)

Re: Show HN: Curl https://ec2.shop

#83

Post by hnlmorg » Wed, Jul 01, 2020, 10:28 AM UTC

elemenophy wrote: post #28

baliex wrote: post #13

Could you update the `...&filter...` example to wrap the URL in quotes so that the `&` isn't interpretted by the shell as sending the process to the background?

this is an issue of ZSH.

That is a POSIX standard and not something specific to zsh

Re: Show HN: Curl https://ec2.shop

#84

Post by jasonjayr » Wed, Jul 01, 2020, 12:37 PM UTC

skissane wrote: post #82

geofft wrote: post #69

Earlier quoted context omitted.

This is "ANSI" as in ANSI X3.64 escape sequences, not "ANSI" as in a character encoding. You can output color to curl on an ANSI-compatible terminal but not to something expecting actual plain text like a browser.

I think text/ecma48 would be a better name. There are lots of ANSI standards. (I guess text/ansi-x3.64 might also work, but text/ecma48 seems simpler.)

Yes, I should have been more specific. text/x-term-${TERM} probably would be better, since it could be any number of terminal types...