Plans on the future of NOCLOSE.EXE ?

[CatalinC]

I have always used my own custom NOCLOSE.EXE (which in previous versions I was renaming to NOCLOSE.PIF in the \Windows folder and Windows was smart enough to know what to do) but I am now wondering if things can become more organized now with the new version?

Is there any plan to incorporate the NOCLOSE plugin? Since that one looks to have some extra options than the version which is currently part of TOTALCMD!

I would also suggest one extra option (which is the one that I use EXTENSIVELY - and for v8 I had to rebuild my old NOCLOSE.EXE with Unicode in order to use it) - my ideal usage scenario is that after I use SHIFT+ENTER I do not need to give any other commands, and as such I need to type EXIT in order to close the window - so instead of that my own version of NOCLOSE.EXE is just waiting for the first key (after displaying the return code from the command passed, but that is just some gimmick) and the closing the window - a lot quicker !

[Flint]

CatalinC
Take a look at my NoClose Replacer which allows to implement what you need. By default it does the same TC's original noclose does, but you can customize it to launch applications via a batch file with following contents:

Code: Select all

@echo off
cmd /c %*
pause

and after you start an application via Shift+Enter, it will just require to press any key, and then close the console window. Actually, that's the sceme I'm using myself.

The source code is opened, you can take it and modify for your needs, or port some features into your own replacement tool.

[CatalinC]

Take a look at my NoClose Replacer which allows to implement what you need.
...

Thank you - when above I mentioned a NOCLOSE plugin I actually wanted to mention your program!

However please note that the 'problem' (not in any way a bug, but definitely a missing feature) still is present in the current NoClose Replacer - after running a command from the keyboard with SHIFT+ENTER I still need to either type EXIT [+Enter] at the command prompt OR take my hands of the keyboard and move to the mouse, locate the close button and click it - either way pretty inconvenient

I am going around that by having my own NOCLOSE program as a CONSOLE application - that way CMD.EXE inherits the console auomatically, and at the end (after CMD.EXE closes and becomes signaled) the console returns back to my own NOCLOSE program - then I write the return code from the command (I only needed that once or twice but I found it a nice gimmick), and then I have something along the lines of

_tprintf(_T("\nPress any key to continue..."));
MessageBeep(MB_OK);

while(_kbhit()==0)
{
Sleep(200);
}

and then I exit my own NOCLOSE.EXE - which is also closing the console

(the MessageBeep is also very handy on longer commands, since I can hear those in the background).

[Flint]

However please note that the 'problem' (not in any way a bug, but definitely a missing feature) still is present in the current NoClose Replacer - after running a command from the keyboard with SHIFT+ENTER I still need to either type EXIT [+Enter] at the command prompt OR take my hands of the keyboard and move to the mouse, locate the close button and click it - either way pretty inconvenient

I don't want to sound rude, but did you read my reply? I was talking exactly about what to do to improve this behaviour and make the console just wait for any keypress instead of typing EXIT…

[CatalinC]

I don't want to sound rude, but did you read my reply? I was talking exactly about what to do to improve this behaviour and make the console just wait for any keypress instead of typing EXIT…

OOPS, sorry - I did my tests with NoClose Replacer some time ago and I did not experiment too much - but I guess having noclose.ini with a command pointing to noclose.cmd which would contain your suggestion should also work - there might only be some small differences since I believe it might run 2 instances of CMD.EXE and the keyboard handling for commands like "dir | more" might be a little different but I guess that should be fine!