taskbook
taskbook copied to clipboard
Characters dont display in wsl
Describe the bug The checkbox(on/off) do not display properly in windows subsystem for linux(ubuntu). You just see the symol that is used when a character cannot be displayed.
To Reproduce Install in wsl(window subsystem for linux) Add task run tb
Expected behavior I should see checkbox
Screenshots
Technical Info (please complete the following information)
- OS: windows 10, wsl(ubuntu)
- Node.js Version: 10.4.1
- Taskbook Version: 0.1.1
Additional context Add any other context about the problem here.
FWIW, it works in Powershell.
It does work in powershell. And git bash as well. Although it defaults back to basic characters so you don't get the nice looking checkbox, ect.
Even in powershell
, seems that the star character (U+2605) won't display properly.
Seems that a solution will still need to know whether a terminal supports unicode. This npm package might help.
If the terminal doesn't support unicode, a replacement ASCII character could be used. I vote using *
in place of ★
@kalexmills Could you make a PR for this?
How do go about testing it locally? I cloned the fork/branch. But how do i run the taskbook commands?
For me, working on powershell, running npm install
from the project root directory will install taskbook. I can then access the command using tb
as usual.
That doesn't seem to work. I think it's using the global taskbook.
You could try a global install, but you'll need to replace it with the original version afterwards.
You can test by editing the version in package.json, installing, and then
running tb --version
and see if the version output by taskbook changes.
K. Alex Mills
I'm having the same issue. I change the font for my Linux subsystem shell to Lucida Console, and that SORT of helped in that instead of getting the question mark in a box now I just get these ☐. Overall I don't mind that since they are still color coded appropriately, but it is causing other issues. For instance tb -clear doesn't work and my guess is b/c it doesn't think it has found the correct character to trigger correctly
use cascadia code pl font that would do the job! ( in settings.json of windows terminal if you are using that)