https://github.com/awaescher/commandline
A tiny tool to show the command line arguments passed to it
https://github.com/awaescher/commandline
arguments command-line command-line-tool
Last synced: 4 months ago
JSON representation
A tiny tool to show the command line arguments passed to it
- Host: GitHub
- URL: https://github.com/awaescher/commandline
- Owner: awaescher
- Created: 2018-10-12T20:29:13.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-10-12T20:56:15.000Z (over 7 years ago)
- Last Synced: 2025-09-16T10:37:21.235Z (10 months ago)
- Topics: arguments, command-line, command-line-tool
- Language: C#
- Homepage:
- Size: 36.1 KB
- Stars: 5
- Watchers: 2
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ![windows][windows] CommandLine
This project is probably one of the smallest ones I've ever done and likely even simpler than "Hello World!".
Anyway, I needed this way too often and I had to code it again and again because I never kept it.
This tool simply shows the command line arguments passed to it. That's it, for real.

Despite its simplicity, it (or the versions I coded and threw away) was quite useful in the past. For example, when I wrote the Setup Wizard for [RepoZ](https://github.com/awaescher/RepoZ) and wanted to start [PathEd](https://github.com/awaescher/PathEd) with some arguments.
As I was testing the setup, I had issues with adding RepoZ to the Windows PATH variables. By replacing PathEd.exe in the Setup with CommandLine.exe (named PathEd.exe), I found out that I was not escaping the path string correctly in the NSIS script which then skipped the quotes in the directory argument. Windows then split directories with spaces as multiple arguments (of course 😐).
So this tool helped me again to spot the error quickly by showing the first part of the following image. I knew I wanted the second one, of course.

[windows]: https://raw.githubusercontent.com/MarcBruins/awesome-xamarin/master/images/windows.png