• Options
• Login
• Register
• Desktop Style
• Accelerated Mobile Pages Theme

/D switch missing when running cmd in Windows Terminal?

• Index

  • QAP Support Forum
  • Quick Access Popup Forum
  • QAP Support
  • /D switch missing when running cmd in Windows Terminal?
• /D switch missing when running cmd in Windows Terminal?

• /D switch missing when running cmd in Windows Terminal?

  joeNOR > 2020-10-24 15:39

  As the subject says.
  
  Is the /D switch missing when changing folders and CMD runs in in Windows Terminal (WT), or is it just me...again?
  
  When running CMD "standalone" the /D switch is in the command line.
  
  In case it matters, here is my cmd config in the WT settings.json file:
  
  

  Code:

  // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "startingDirectory": "C:/MyTools",
                "tabTitle" : "Command",
                "colorScheme" : "Vintage",
                "cursorColor" : "#FFFFFD",
                "hidden": false

  
  Regards,
  joeNOR

• RE: /D switch missing when running cmd in Windows Terminal?

  Jean Lalonde > 2020-10-24 15:57

  If I remember well, the /D switch was only required to change folder in CMD.EXE, not for PowerShell. And when I added Conemu and Windows Terminal support, it worked in my tests without it.

• RE: /D switch missing when running cmd in Windows Terminal?

  joeNOR > 2020-10-24 16:01

  That's correct, it works in PowerShell, but I run CMD.EXE (see the settings.json config) in a tab in WT.
  
  Without /D the drive don't change, I have to enter the drive manually.
  
  -joeNOR

• RE: /D switch missing when running cmd in Windows Terminal?

  Jean Lalonde > 2020-10-24 16:21

  QAP is detecting the app running by looking at the process name. If it is "cmd.exe", it add the /D. In my case (without having looked at or changed the settings.json file), the process name for WT is "WindowsTerminal.exe". Could you change "commandline": "WindowsTerminal.exe" or just leave it to its default value?

• RE: /D switch missing when running cmd in Windows Terminal?

  joeNOR > 2020-10-24 16:51

  That is not how Windows Terminal works.
  WT is a "wrapper" process that can run different shells/terminals defined in the settings.json file, they are called profiles.
  The config in my previous post is the default setting for CMD in settings.json.
  
  You can start different shells from the dropdown menu or with parameters when starting WT.
  F.ex
  wt -p "SSH1" ; split-pane -p "SSH2"
  opens two profiles, SSH1 and SSH2 in a split pane in WT.
  (in my case they connects to two different SSH host)
  
  wt -p "CMD ; -p "Powershell"
  opens the two profiles in two tabs.
  
  I have attached two screen shots, where WT runs a CMD config (the default), three different PowerShell configs, and an Azure Cloud Shell.
  (EDIT: It is the original guid created when installing WT, but I added some options)
  
  Regards,
  joeNOR

• RE: /D switch missing when running cmd in Windows Terminal?

  Jean Lalonde > 2020-10-24 17:26

  I'm not that familiar with this tool. Instead of relying on the process name to add or not the /D, maybe QAP could check the window's class name.
  
  Using the "Get window info" tool available in QAP (Options, Popup menu), what data is returned?
  
  In my case, for Windows Terminal:
  
  Windows PowerShell
  CASCADIA_HOSTING_WINDOW_CLASS
  WindowsTerminal.exe
  
  For PowerShell:
  Windows PowerShell
  ConsoleWindowClass
  powershell.exe
  
  For CMD:
  Invite de commandes
  ConsoleWindowClass
  cmd.exe

• RE: /D switch missing when running cmd in Windows Terminal?

  joeNOR > 2020-10-24 17:50

  I am on that very thin ice again (not a developer)
  
  But I don't think it will work:
  
  Window Title:
  Command
  Class:
  CASCADIA_HOSTING_WINDOW_CLASS
  Process name:
  WindowsTerminal.exe
  
  Window Title:
  Azure Cloud Shell
  Class:
  CASCADIA_HOSTING_WINDOW_CLASS
  WindowsTerminal.exe
  
  Window Title:
  PowerShell 7 (Core)
  Class:
  CASCADIA_HOSTING_WINDOW_CLASS
  Process name:
  WindowsTerminal.exe
  
  Window Title is useless because it can be anything, defined by the "tabTitle" setting in the json.
  
  -joeNOR
  

  ---

  I also checked with the GUIPropView tool by NirSoft, but it basically tells me the same as your tool.
  

  ---

  .... or just skip the whole ting. It is very, very minor after all.
  
  -j

• RE: /D switch missing when running cmd in Windows Terminal?

  Jean Lalonde > 2020-10-24 21:22

  Hum... The issue is that QAP cannot detect what is running inside the WT window. Honestly, I don't see what I could do with this but, as you say, we can let this aside for now.

• RE: /D switch missing when running cmd in Windows Terminal?

  joeNOR > 2020-10-25 01:27

  Yeah, unless you can implement something like this:
  
  

  Code:

  (dir 2>&1 *`|echo CMD);&<# rem #>echo ($PSVersionTable).PSEdition

  
  at runtime (given that the process returned is WindowsTerminal.exe).
  
  It returns "CMD" in cmd.exe, "Desktop" in powershell.exe and "Core" in pwsh.exe.
  
  I have no idea if that is possible to do or not in QAP...... you coder dudes have to answer that!
  
  -joeNOR

• RE: /D switch missing when running cmd in Windows Terminal?

  Jean Lalonde > 2020-10-25 08:34

  Noted. Thanks.
• Next Oldest Next Newest