-
Notifications
You must be signed in to change notification settings - Fork 43
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
doskey is not working #428
Comments
This comment was marked as outdated.
This comment was marked as outdated.
While you are right it might be a security flaw many developer environments set them. It is unfortunate that I cannot use vtm in developer shells. As long not everyone is using Windows Terminal there is not much we could use for cmd shell scripting. |
We can make this configurable and off by default. |
That would be a great addition! |
I have now realized that this is vital functionality, and it must be implemented unconditionally. |
I implemented the DOSKEY functionality. You can test the branch from the pull request. I'll publish a release a little later. |
Thanks. The test build looks good. Doskey macros are showing up now. Thanks! |
My environment has VS2019, VS2022, VS2022 Preview, and VS2017 Build tools. Looks like cmake did create a solution which did target VS2019. It was targetting Build Tools 14.3, but these were not installed. |
I have noticed that the new vtm when started from a Windows Terminal Session with a cmd shell
is showing up. The old VTM did not have this warning. |
When having a file with doskey macros
keys.txt
doskey /macrofile=keys.txt
and then list the defined ones the list comes back empty when running vtm inside Windows Terminal:
With vtm
![image](https://private-user-images.githubusercontent.com/101576413/258315556-47d83c95-8fce-4647-98fd-368b593b2cc9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyMzA2NzcsIm5iZiI6MTcyMjIzMDM3NywicGF0aCI6Ii8xMDE1NzY0MTMvMjU4MzE1NTU2LTQ3ZDgzYzk1LThmY2UtNDY0Ny05OGZkLTM2OGI1OTNiMmNjOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcyOVQwNTE5MzdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wZWMyMTRmY2U4YzI3MWE4NWIyMzkyNmU0NGYzZTliMTAxYjcyNWViZWY5MDRmZjJhYzYwZDM5ODFmMjk4NzEzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.nfGHqF22OQAd4gnVNDOGO83TTMlK9oYcWeqK0KveF5k)
when doing this in a Windows Terminal cmd prompt then it works
With cmd.exe
![image](https://private-user-images.githubusercontent.com/101576413/258315644-c997198f-0a97-4db4-a40b-899125e4bffe.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyMzA2NzcsIm5iZiI6MTcyMjIzMDM3NywicGF0aCI6Ii8xMDE1NzY0MTMvMjU4MzE1NjQ0LWM5OTcxOThmLTBhOTctNGRiNC1hNDBiLTg5OTEyNWU0YmZmZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcyOVQwNTE5MzdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05OTRkYWFiMTZmZjg4Zjc1NTZmM2U0ZTZkMTBjYWMzMmMxYWMxMDdmZDhhOWVjYWEzNThlYzM4ODg1MTI5NTI1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.ka1I4Y21UZkvH-aMhtf6QEAEJ8NB3tdWDYs0yFs2X7s)
No errors. That is really strange.
The text was updated successfully, but these errors were encountered: