Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode checkbox #31

Closed
sindresorhus opened this issue Jun 13, 2013 · 8 comments
Closed

Unicode checkbox #31

sindresorhus opened this issue Jun 13, 2013 · 8 comments

Comments

@sindresorhus
Copy link
Contributor

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
Copy link
Owner

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
Copy link
Owner

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 commit that referenced this issue Jun 20, 2013
@SBoudrias
Copy link
Owner

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
Copy link
Contributor Author

Awesome!

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

@SBoudrias
Copy link
Owner

@sindresorhus Oh yeah, good idea! Will do!

SBoudrias added a commit that referenced this issue Jun 27, 2013
@mikedevita
Copy link

mikedevita commented Nov 8, 2016

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

@SBoudrias
Copy link
Owner

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

@mikedevita
Copy link

mikedevita commented Nov 8, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants