Conversation

Notices

1. steve (steve02081504@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 10:50:56 JST steve

   • ぽな (C.Ponapalt)

   @ponapalt
   I used 【start /d "E:\ssp\" ssp.exe /g Taromati2】 in cmd to no avail!
   Must 【E:\ssp\ssp.exe /g Taromati2】 to work
   Why is this? Can you fix it? :meow_thinking:

   • steve (steve02081504@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 10:50:55 JST steve

     in reply to

     • ぽな (C.Ponapalt)

     @ponapalt
     Firstly I wrote a script called Materia to start ssp to avoid duplicating the ssp name with the Single-step profile bin.
     Secondly in the script I think I have to use start to start ssp otherwise my shell will hang until the end of ssp.
     But as of now I can't start ssp with start.
     It's not really affecting me so no rush!

   • 月波 清火 on :ukadon: (tukinami_seika@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 10:50:55 JST 月波 清火 on :ukadon:

     in reply to

     @steve02081504
     Excuse me.
     If you are using PowerShell, try adding `&` before calling cmd. (e.g. & Materia.cmd)
     In PowerShell, cmd with double quotes inside seems to work in a special behavior.

     See the following URL (Japanese only, sorry)
     https://www.delftstack.com/ja/howto/powershell/run-cmd-commands-in-powershell/

   • ぽな (C.Ponapalt) (ponapalt@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 10:50:55 JST ぽな (C.Ponapalt)

     in reply to

     • 月波 清火 on :ukadon:

     @tukinami_seika @steve02081504 I ran the command with cmd.exe and it worked fine, so the problem is most likely dependent on PowerShell or other execution environment.

   • steve (steve02081504@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 11:11:23 JST steve

     in reply to

     • ぽな (C.Ponapalt)
     • 月波 清火 on :ukadon:

     @ponapalt @tukinami_seika
     I'm sorry, it's indeed a problem with my environment configuration.
     The `/d` parameter to start only specifies the directory where the program is to be run, and in the absence of a path it will still look for the executable in the environment path, so there was a problem with the way my cmd script was written (it was just running the Single-step profile in a different place).

     I changed the script to
     @start /d %~dp0 %~dp0ssp.exe %*
     @exit /b %ERRORLEVEL%

     Now it works fine!
     (As to why the script would cause the shell to hang until ssp ended if without using start, I'm inclined to explain it as a metaphysical problem and won't pursue it any further.)
     I'm sorry for the trouble I've caused you guys. :blobpray:

   • ぽな (C.Ponapalt) (ponapalt@ukadon.shillest.net)'s status on Monday, 04-Dec-2023 11:15:54 JST ぽな (C.Ponapalt)

     in reply to

     • 月波 清火 on :ukadon:

     @steve02081504 @tukinami_seika If you've figured out the cause on your end, then there's no problem at all. Happy hacking!