New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wslpath has no "usage" or "help" information #2715
Comments
Man page is tricky (we don't want to dump a bunch of our own files in /usr or /usr/local), but I agree that we should at least have usage information. |
I can wait but yes man page is definitely needed. Took me forever to remember what the command was. Google searching "convert wsl path to windows" doesn't get me to the release notes. Speaking of which it shouldn't just be officially listed in the release note. Put it everywhere it's useful!! |
@jstarks In my eyes, wslpath is a great tool. I understand that a man page is too much, but --help and --version options would be great! There are many discussions concerning such a tool, but nobody seems to know that there is an official solution to the problem. A blog post would be great to raise awareness. Also, the follwing features would make it enough powerful to deserve a paragraph in the wsl/interop documentation. A simple google search would then reveal the commands and the documentation. Handle arguments as paths not only as strings
I'm sorry that this is partly a feature request. But it only concerncs the wslpath functionality and doesn't seem to complex, so I decided to post it here. |
I discovered a program called It's also interesting that both wslpath and winpath both exists in all WSL Linuces. How many WSL-programs are there? i.e. that are added by WSL to all distributions. |
@mobluse I have no binary called |
@pd93 I have Microsoft Windows [Version 10.0.17134.1] 17134.1.amd64fre.rs4_release.180410-1804. Both wslpath and winpath exists in most updated Ubuntu 16.04 and openSUSE Leap 42.2. |
@mobluse Can you run |
In WSL Ubuntu:
|
Both my Windows machine are on 17134.5 and neither of them have I get the same results as you when running
|
Sorry about So if you see
|
Usage info comes from microsoft/WSL#2715 Signed-off-by: Christopher Larson <kergoth@gmail.com>
For the forgetful amongst us here is a temporary hack -- put in your PATH with chmod 755. I called it wslpath (in which case it needs to be in PATH before /bin) but you can call it whatever you want. Thanks to rodrymbo for the usage content.
|
The new wslpath is a wonderful addition. Thank you.
Some sticklers might point out that it lacks the usual --help and --version options. It also responds
when it should respond
as found in the release notes.
Yeah, I know, no sooner do you add something that lots of people want (and for which we are very grateful) but we start complaining about it. But still, how hard is it to print usage when the program name is entered without parameters? So, yes, I'll be an ungrateful git and say this is a bug that needs to be fixed before it is released.
Yeah, I'm one of those who can't remember parameters exactly from one minute to the next and constantly refer to usage reminders. I'm sure I'll be wasting lots of time hunting for the usage in release-notes every time I need it, or here since I made this entry.
It also needs a man page.
Version 10.0.17046.1000
lrwxrwxrwx 1 root root 5 Nov 28 13:33 /bin/wslpath -> /init
Ah, so it is really /init. Well, /init (as opposed to /sbin/init) needs a man page too. 📦
The text was updated successfully, but these errors were encountered: