You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the terminal supports Unicode, the console CLI will use a number of emojis and other symbols as icons etc. This is good, because it's easier to visually scan the UI this way, and in many cases, it uses fewer characters, allowing more screen real estate for things like paths that are potentially long. However, in some cases, the precise meaning of a particular emoji may not be quite as obvious as text. We might want to add some kind of glossary explaining the meanings of some of the emoji/symbols we use.
This could be in the documentation, or somewhere in the UI itself (a floating help window you toggle by pressing a key?)
The text was updated successfully, but these errors were encountered:
Looking at the code and thinking a spending some more time thinking about the implementation:
Different views would have different help information to display (including the glossary of emojis if they are being used), which pertains specifically to the view. If every view had a way to display help information (probably in the bottom row in one or two lines) then we could hook the event handler to display the right help information based on the current view state.
When the terminal supports Unicode, the console CLI will use a number of emojis and other symbols as icons etc. This is good, because it's easier to visually scan the UI this way, and in many cases, it uses fewer characters, allowing more screen real estate for things like paths that are potentially long. However, in some cases, the precise meaning of a particular emoji may not be quite as obvious as text. We might want to add some kind of glossary explaining the meanings of some of the emoji/symbols we use.
This could be in the documentation, or somewhere in the UI itself (a floating help window you toggle by pressing a key?)
The text was updated successfully, but these errors were encountered: