Skip to content
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

Command line length issue #249

ggets opened this issue May 3, 2016 · 0 comments

Command line length issue #249

ggets opened this issue May 3, 2016 · 0 comments


Copy link

@ggets ggets commented May 3, 2016

I have been using this regedit shell snippet to open a cygterm prompt in a drive/directory:

Windows Registry Editor Version 5.00
@="Open &in Cygterm"
"MUIVerb"="Open &in Cygterm"

just for a bit of sanity, the command actually translates to:

"E:\Tools\Network & Internet\putty.exe" -load "Cygterm" /bin/xhere /bin/bash.exe "%L"

with the following session (the important part only, no clutter):

Windows Registry Editor Version 5.00
"CygtermCommand"="                                                                                                                                                            "

So the CygtermCommand has to be filled with spaces so the whole shell command is executed, otherwise, for example, if you truncate CygtermCommand as follows "CygtermCommand"=" " you will get the following output:

/bin/xh: No such file or directory"

which is exactly this part of the shell command:

"E:\Tools\Network & Internet\putty.exe" -load "Cygterm" /bin/xhere /bin/bash.exe "%L"

Bottom line is as many characters you input in the command box that many you'll get parsed from the shell command.
BTW I am using version p0.66-t027

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.