Unicode checkbox

[sindresorhus]

Not sure if it would be feasible, but might consider using unicode symbols:

☐☑☒ though I fear these might be too small.

or just a checkmark on the chosen one and nothing on the others: ✔

or same as above, but an other symbol: ❯ ➤ ➔

Could also consider using unicode combinators:
http://unicodinator.com/#20E3 combined with ✔ makes ✔⃣ or ✖⃣

or this http://unicodinator.com/#20DD combined with ✔ makes ✔⃝ or ✖⃝

[SBoudrias]

We tough about using checkbox on #14

My only concerns is to support a large set of fonts and Windows - which was a given with the X. I know Mocha uses a check in their test who's working on PowerShell.

We'll need some support test for that - or make sure we can have a clean fallback.

[SBoudrias]

To keep up with what I found, I'll post here.

chcp in Windows returns currents language.

http://stackoverflow.com/questions/1259084/what-encoding-code-page-is-cmd-exe-using

[SBoudrias]

Added a check so unix system use the symbols, and windows will fallback to the X. May revisit later, but I really got some weird output on windows so for now I don't want to overthink this...

Planned to be release with 0.2 who'll add some new prompts - work is in wip branch.

[sindresorhus]

Awesome!

Sidenote: Add some screenshots of the prompts to the readme for better marketing ;)

[SBoudrias]

@sindresorhus Oh yeah, good idea! Will do!

[mikedevita]

Is there a way to force inquirer to use non unicode characters?

[SBoudrias]

@mikedevita no, that's not a feature at the moment. Are you running somewhere where unicode is not supported?

[mikedevita]

Were a shop which runs windows and uses putty to connect to RHEL servers and can't reliably set putty to use fonts which support unicode...

Rather than fixing all our machines to use a unicode font I'd rather just use plaintext and bypass the issue.