Use consistent format for paths in documentation.
See original GitHub issueCurrently there are several file paths in command line promts in the documentation used in in different formats.It would be helpful if this is unified.
Found variants:
~/hono$
~hono/deploy$
$ /hono/cli/target$
~/hono/services/device-registry $
- No file path given, even if the command depends on it
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Make a consistent drive letter or path to a removable drive
Migrating drive letters is a problem when programs remember fixed drive letters in paths to documents. All Office programs do that in their...
Read more >Formatting your documentation content - Apple Developer
To ensure consistent structure and styling, use DocC's documentation ... In the example above, both symbol paths are identical, regardless of text case....
Read more >Connecting to Volumes With Consistent Device Paths
Oracle Cloud Infrastructure supports consistent device paths for block volumes that are attached to compatible Linux-based instances.
Read more >Formatting text in instructions - Microsoft Style Guide
Element Convention Example
Command‑line commands Bold. All lowercase. copy
Database names Bold. The capitalization of database names varies. WingtipToys...
Device and port names All uppercase. USB...
Read more >File naming and structure - Research Data Management at ...
Files should be named consistently · File names should be short but descriptive (<25 characters) (Briney, 2015) · Avoid special characters or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe that wasn’t a good example either 😃 But still, the base directory is be completely implicit with this and the reader needs to figure out the context before pasting the command into the shell. Do you mind adding (initial) path information where necessary in a comment? Like e.g.:
This is short, doesn’t disturb copy & paste and IMHO ticks the “Don’t make me think” box.
@b-abel can we (you) close this?