Skip to content
View EmilyGraceSeville7cf's full-sized avatar
  • Canada, Toronto
  • 03:13 (UTC -12:00)

Organizations

@command-line-interface-pages
Block or Report

Block or report EmilyGraceSeville7cf

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

About 💕

I am a native russian speaker, open source contributor and I am keen on administrating, scripting, creating sites and presentations. It’s my life. I like to automate routine tasks and not to do them manually. Currently I have the following skills (just the most interesting tools are mentioned):

  • 💻 languages: Nushell (interactive session and scripting), Go (scripting), Hugo (generated site content), YAML (configs), JSON (configs and JSON schemas)
  • 📝 ides and editors: Visual Studio Code (programming stuff), Inkscape (drawing logos)
  • 🕜 vcs-tools: Git, GitHub

gopher

I support several projects and organizations such as (just the most interesting ones are mentioned):

command-line-interface-pages better-emacs schemastore

But now I mainly focused on [C]ommand [L]ine [I]nterface [P]ages project:

image

which provides neat command help pages.

How do I review pull requests? 👓

For the first 2 pages less than or equal 50 lines I provide detailed mistake expanations for all issues with links to contributing guides how to fix them.

Other remaining pages are not scanned for problems.

Placeholder syntax in my CLI tools

Starting from 29 december 2023 I use the following placeholder syntax in all my tools (Go-inspired):

  • {{placeholder}}: some arbitrary text with no constraints implied which should be exactly one CLI argument. If there are any they should be explicitly stated in the documentation. There is no standardized way for describing them.
  • {{placeholder ...}}: almost the same thing as the previous one, but here one or more arguments are expected. If no arguments or some specific amount of them is required it should be explicitly stated in the documentation. With | ellipsis (...) can be used just ones, at the end, implying that all alternatives accept several arguments unless the opposite is stated. There is no standardized way for mentioning it.
  • | can be used inside double curly braces to provide more than one alternative for what can be placed instead of placeholder. If some alternatives can be used just under certain circumstances, it should be explicitly stated in the documentation. There is no standardized way for mentioning it.

, where instead of placeholder any text can be written which explains what should be put instead of CLI argument(s), but without spaces unless it's explicitly permitted.


extensions youtube channels reddit discord whatsapp

Pinned

  1. personal-data personal-data Public archive

    My personal pictures, videos, audio and etc.

    HTML

  2. favorite-pictures favorite-pictures Public

    My favorite pictures.

    Nushell 1