Add documentation for unicode prompt #841
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geekosaur
approved these changes
Nov 7, 2023
|
Actually, can you shorten the commit title and move the rest into the description? Git prefers a title length less than 50 characters. Also, there should be a blank line between the title and the description. |
jpolchlo
changed the title
jpolchlo
changed the title
Having this file is required for the prompt to work, and how to obtain it may not be immediately obvious.
slotThe
force-pushed
the
docs/unicode-prompt
branch
from
832d151 to
da566d6
Compare
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds some additional context regarding the required UnicodeData.txt file needed for the
XMonad.Prompt.Unicodemodule.Closes #840
Checklist
I've read CONTRIBUTING.md
I've considered how to best test these changes (property, unit,
manually, ...) and concluded: there are only documentation changes; no testing required
I updated the
CHANGES.mdfile