issues
search
command-line-interface-pages
/
syntax
Syntax definition and highlighting for different editors
4
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Fix/47: use correct syntax version in badge
#48
EmilyGraceSeville7cf
closed
1 year ago
0
Fix version badge
#47
EmilyGraceSeville7cf
closed
1 year ago
0
Introduce concept of OS-specific options and subcommands
#46
EmilyGraceSeville7cf
opened
1 year ago
0
Automatic placeholder quoting can break shell syntax
#45
EmilyGraceSeville7cf
opened
1 year ago
2
Refresh syntax definition: remove "Why not*" chapters
#44
EmilyGraceSeville7cf
closed
1 year ago
0
Remove all "Why not*" chapters
#43
EmilyGraceSeville7cf
closed
1 year ago
0
Permit mnemonics for not just options and subcommands
#42
EmilyGraceSeville7cf
opened
1 year ago
0
Allow use spaces in file names for subcommands
#41
EmilyGraceSeville7cf
opened
1 year ago
0
Allow mnemonics to be spread among several words
#40
EmilyGraceSeville7cf
opened
1 year ago
0
Introduce concept of page tag inheritance
#39
EmilyGraceSeville7cf
closed
1 year ago
0
Use annotations to present placeholder examples to make code shorter and permit more expressive placeholder annotations
#38
EmilyGraceSeville7cf
opened
1 year ago
0
New YAML-based syntax
#37
EmilyGraceSeville7cf
closed
1 year ago
4
Complete migration to YAML
#36
EmilyGraceSeville7cf
opened
1 year ago
0
Solve issue with {option ...} placeholder
#35
EmilyGraceSeville7cf
closed
1 year ago
0
Feature/33: split syntax definition and explain directory page syntax
#34
EmilyGraceSeville7cf
closed
1 year ago
0
Split syntax into several pages to describe how to write directory pages too
#33
EmilyGraceSeville7cf
closed
1 year ago
0
Permit splitting example in several lines
#32
EmilyGraceSeville7cf
closed
1 year ago
1
Introduce concept of placeholder annotations
#31
EmilyGraceSeville7cf
closed
1 year ago
1
Introduce new syntax for so named "comprehensive placeholders"
#30
EmilyGraceSeville7cf
closed
1 year ago
1
Introduce new syntax for so named "comprehensive placeholders"
#29
EmilyGraceSeville7cf
closed
1 year ago
0
Introduce better expansion syntax for ranges
#28
EmilyGraceSeville7cf
opened
1 year ago
1
Introduce expansion for file extensions
#27
EmilyGraceSeville7cf
opened
1 year ago
1
Clarify syntax
#26
EmilyGraceSeville7cf
closed
1 year ago
0
Allow mnemonics in command description: recognize and highlight them
#25
EmilyGraceSeville7cf
closed
1 year ago
0
Extend Help/Version tags to accept multiple arguments
#24
EmilyGraceSeville7cf
closed
1 year ago
0
Syntax version 2.6.0
#23
EmilyGraceSeville7cf
closed
1 year ago
0
`Syntax compatible` tag to mention tools syntactically compatible with the current one
#22
EmilyGraceSeville7cf
closed
1 year ago
0
Allow switch between several placeholder examples along with alternatives in descriptions
#21
EmilyGraceSeville7cf
closed
1 year ago
3
Standardize the way compatibility is described
#20
EmilyGraceSeville7cf
closed
1 year ago
0
Fix typos and simplify explanations
#19
EmilyGraceSeville7cf
closed
1 year ago
0
Allow escaping pipe character
#18
EmilyGraceSeville7cf
closed
1 year ago
0
Standardize quoting rules
#17
EmilyGraceSeville7cf
closed
1 year ago
0
Syntax version 2: more tags, stricter mnemonic and description requirenments and more reliance on render
#16
EmilyGraceSeville7cf
closed
1 year ago
0
Add emojis for quotes
#15
EmilyGraceSeville7cf
closed
1 year ago
0
Add Why not Better TlDr chapter
#14
EmilyGraceSeville7cf
closed
1 year ago
0
Refresh "Why not TlDr" chapters
#13
EmilyGraceSeville7cf
closed
1 year ago
1
Increase standardization
#12
EmilyGraceSeville7cf
closed
1 year ago
0
Introduce syntax for mentioning commands without any output (to any of output streams or files)
#11
EmilyGraceSeville7cf
closed
1 year ago
0
Introduce placeholders for remote path and arbitraty objects
#10
EmilyGraceSeville7cf
closed
1 year ago
0
Require explicitly state how much items are handled via "all" term in code description
#9
EmilyGraceSeville7cf
closed
1 year ago
0
Require "source" and "destination" terms for placeholder descriptions for commands copiying or moving data from one place to another
#8
EmilyGraceSeville7cf
closed
1 year ago
0
Require dot before extensions to be present in code descriptions
#7
EmilyGraceSeville7cf
closed
1 year ago
0
Rewrite TlDr drawbacks in a more positive way
#6
EmilyGraceSeville7cf
closed
1 year ago
0
Add Micro syntax highlighting
#5
EmilyGraceSeville7cf
opened
1 year ago
0
Add Emacs syntax highlighting
#4
EmilyGraceSeville7cf
closed
1 year ago
0
Add VS Code syntax highlighting
#3
EmilyGraceSeville7cf
opened
1 year ago
0
Add Micro syntax highlighting
#2
EmilyGraceSeville7cf
opened
1 year ago
0
Add Vim syntax highlighting
#1
EmilyGraceSeville7cf
opened
1 year ago
1