Patrik Svensson 58eff30787 LineTreeGuide should not fall back to ASCII ...

If the user's environment didn't support unicode, we used
to fall back to using the AsciiTreeGuide if LineTreeGuide
was being used (which it is by default). This commit removes
that fallback since the characters used in LineTreeGuide is
covered by extended ASCII, which SHOULD be fine in almost all
scenarios.

Closes #324

2021-07-10 18:01:17 -04:00

..

Program.cs

LineTreeGuide should not fall back to ASCII

2021-07-10 18:01:17 -04:00

Trees.csproj

Add example infrastructure

2021-04-11 22:03:13 -04:00