summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorClement Tsang <34804052+ClementTsang@users.noreply.github.com>2023-03-29 00:40:26 -0400
committerGitHub <noreply@github.com>2023-03-29 00:40:26 -0400
commit4d61ca4d418a4e78497c209f5926a94c19e8a83e (patch)
tree9235088a50f64a5002fd50a77632b4fc476c3f24
parentbde2dac56ec5a5ff7d35034d37a9ec2de026ccfe (diff)
docs: add mention for braille font issues on Linux (#1080)
-rw-r--r--docs/content/troubleshooting.md13
1 files changed, 11 insertions, 2 deletions
diff --git a/docs/content/troubleshooting.md b/docs/content/troubleshooting.md
index c9fd5852..97d7bf9b 100644
--- a/docs/content/troubleshooting.md
+++ b/docs/content/troubleshooting.md
@@ -19,10 +19,19 @@ which generally seems better supported out of the box, at the expense of looking
<figcaption><sub>Example using <code>btm --dot_marker</code></sub></figcaption>
</figure>
-Another (better) alternative is to install a font that supports braille fonts, and configure your terminal to use it. For example, installing
-something like [UBraille](https://yudit.org/download/fonts/UBraille/) or [Iosevka](https://github.com/be5invis/Iosevka)
+Another (better) alternative is to install a font that supports braille fonts, and configure your terminal emulator to use it.
+For example, installing something like [UBraille](https://yudit.org/download/fonts/UBraille/) or [Iosevka](https://github.com/be5invis/Iosevka)
and ensuring your terminal uses it should work.
+### Braille font issues on Linux
+
+See [here](https://github.com/cjbassi/gotop/issues/18) for possible fixes if you're having font issues. Generally, the
+problem comes down to you either not having a font that supports the braille markers, or your terminal emulator is not
+using the correct font for the braille markers.
+
+If you're still having issues, feel free to open a [discussion](https://github.com/ClementTsang/bottom/discussions/new/)
+question about it.
+
### Installing fonts for Windows Command Prompt/PowerShell
**Note: I would advise backing up your registry beforehand if you aren't sure what you are doing!**