Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove home folder paths from README.md
See original GitHub issueTwo distinct issues here:
Before #248, there were ~ on some of the paths in quick start commands, but not on at least one other. #248 updated the file to be consistent, with ~.
The problem is that this is wrong. We don’t want to prescribe doing this in anyone’s home folder. The ~ path specifiers should be removed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Rmdir - removed long file & folder paths in command prompt
Rmdir - removed long file & folder paths in command prompt - README.md. ... Specifies the location and name of the directory that...
Read more >Github README.md and readme.md - how to delete one?
The way to remove a file is to remove it locally, usually with a terminal window and the command line with git rm...
Read more >Remove files which not named "today.md" [duplicate]
Closed 4 years ago. I have the a series of markdown files in the working directory: $ ls *.md csv_reader.md ...
Read more >Build home section — build_home_index • pkgdown
build_home() function generates pages at the top-level of the site including: The home page HTML files from any .md files in ./ or...
Read more >DeleteFiles@1 - Delete files v1 task - Microsoft Learn
The file/folder paths to delete. Supports multiple lines of minimatch patterns; each one is processed before moving onto the next line.
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 Free
Top 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
Submitted https://github.com/pytorch/serve/pull/292 to address this.
I would change every
~to a.- that changes it from “do it in your home directory” to “do it in your current directory” - the difference being that if a user doesn’t want to do it in~(I know mine is pretty cluttered), they then have to go and change every~-containing command line that we provide them - the convenient, cut-and-paste runthrough is no longer an option. Changing to.works everywhere, including the home directory.