mksh
Here are 12 public repositories matching this topic...
I'm packaging modernish for FreeBSD now. Usually, we put examples under share/examples/name, documentation under share/doc/name and any other data, that do not belong to any of the aforementioned directories, into share/name.
I wonder if you'd like to follow the same convention in this repository.
The reason is that I am not sure if I should move modernish examples to a standard pla
-
Updated
Jan 17, 2020 - Shell
Add glyph check API
The use of Unicode code points (or other glyphs) in plugins can only work properly if the plugin is able to detect if the terminal will be able to display the glyph. We should let the user tell angel-PS1 what font is used to render the terminal and add an API that plugins could use to check if a given glyph is available in the font.
Design idea:
- add a
--fontcommand-line option to let the use
-
Updated
Feb 8, 2020 - Shell
-
Updated
Feb 9, 2020 - C
Improve this page
Add a description, image, and links to the mksh topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mksh topic, visit your repo's landing page and select "manage topics."


For example,
ParamExphas aNamefield of type*Lit, but it can never be nil. The reason it's a pointer is for consistency with all the other literal fields.