Code: Select all
!ls;pause
Code: Select all
!ls;pause
Well it works for me, but the more I think about this the more I wonder about what's correct.admin wrote:I will re-add /k and /c for cmd.exe. That should do, right?
Code: Select all
[x] Custom Interpreter
Exe: [cmd.exe]
Args: [-custom -args <command>]
Code: Select all
Interpreter:
!: ["cmd.exe" -custom -args <command>]
!!: ["cmd.exe" -custom -args <command>]
Code: Select all
!: ["%comspec%" /k <command>]
!!: ["%comspec%" /c <command>]
Code: Select all
*.0300
Short names do not work, so they are out here.
Default command line
! -> opens command prompt - Good
!! -> opens and closes command prompt - Good
!dir -> open command prompt with directory listing - Good
!!dir -> open command prompt with directory listing and closes - Good
%winsysnative%\WindowsPowerShell\v1.0\powershell.exe
! -> opens powershell - Good
!! -> opens powershell - OK
!dir -> opens powershell with listing and closes - Should have stayed open - Bad
!!dir -> opens powershell with listing and closes - Should have stayed open - Good
Code: Select all
Default command line is in line with *.0300 -> Good
Short name (powershell)
! -> Doesn't seem to do anything, but maybe it opens and closes - Should have remained open - Bad
!! -> Doesn't seem to do anything, but maybe it opens and closes - Good
!dir -> Opens powershell with listing and closes - Should have stayed open - Bad
!!dir -> Opens powershell with listing and closes - Good
Full path (%winsysnative%\WindowsPowerShell\v1.0\powershell.exe)
! -> Opens powershell - Good
!! -> Open powershell - OK
!dir -> Opens powershell - Bad (Should have done a directory listing as well)
!!dir -> Opens powershell - Bad (Should have done a directory listing and closed)
Hm, why the documents folder? And why is this a problem? I think the current behavior is totally OK. No need for extra smartness.nerdweed wrote:And besides this, there is a small issue in general. The command prompt doesn't open up with a ! when in this computer (or other location that command prompt cannot show). I believe it should open up at the documents folder instead.
'!' - Does nothing.<xyini> wrote:CustomCLI=powershell
CustomCLIArgs=
'!' - CreateProcess with cmdLine containing module only - correctly opens powershell.<xyini> wrote:CustomCLI=%winsysnative%\WindowsPowerShell\v1.0\powershell.exe
CustomCLIArgs=
Case 3: User specifies full path for CCLI and custom arguments:NOTE: ANSI specifications require that argv[0] should be equal to the application name, but CreateProcess gives the calling application the flexibility to override this rule for 32-bit processes.
'!' - CreateProcess with cmdLine containing module only - correctly opens powershell.<xyini> wrote:CustomCLI=%winsysnative%\WindowsPowerShell\v1.0\powershell.exe
CustomCLIArgs=-NoExit -Command "<command>"
'!' - CreateProcess with cmdLine containing module only - correctly opens powershell.<xyini> wrote:CustomCLI=%winsysnative%\WindowsPowerShell\v1.0\powershell.exe
CustomCLIArgs=powershell.exe -NoExit -Command "<command>"
TheQwerty wrote:Well it works for me, but the more I think about this the more I wonder about what's correct.admin wrote:I will re-add /k and /c for cmd.exe. That should do, right?
I'm currently thinking the best might be:
1) Remove the /k|/c smartness from XY.
2) Migrate the existing settings from (this is from memory so forgive my errs):to:Code: Select all
[x] Custom Interpreter Exe: [cmd.exe] Args: [-custom -args <command>]
The defaults would actually be:Code: Select all
Interpreter: !: ["cmd.exe" -custom -args <command>] !!: ["cmd.exe" -custom -args <command>]
Code: Select all
!: ["%comspec%" /k <command>] !!: ["%comspec%" /c <command>]