I could have sworn I had Ctrl-K working like emacs in my much older 4NT, but now (TCC 27.00.18 x64 Windows 10 [Version 10.0.19043.1165]) I can't figure it out, so maybe I dreamed it. By "working" I mean "copy the text from cursor to end of line to the clipboard and delete it" so that a later...

Seems the problem might have resolved by erasing the INI file. I migrated from an ancient version of 4NT and maybe some change in what's expected in that file caused bad behavior. In any case, TCC no longer has a mysterious inability to store that particular directive (PopupWinHeight) in the INI...

> If that's the case, it may be by design ... TCC thinking "this is a special-purpose INI file; don't mess with it". Anything's possible, but that would be incompatible with the fact that I can use the OPTION command to make lots of other changes to the same INI file. > changed the foreground...

TCC 27.00.18 x64 Windows 10 [Version 10.0.19041.985] Can anybody else on version 27 confirm that command history window size will not be written to the INI file if you gave it a custom INI on the command-line when starting TCC?

Interesting that the OPTION command seems able to update my INI file with no problem, so maybe that means there is no permission issue. I do specify a non-default INI file on the command-line via the Windows shortcut I use to start TCC. Let's see what happens if I eliminate that... Started...

Running as Administrator did not alter the problem. However I note my INI file was last modified in 2020, so maybe permission problem is the correct clue to follow. I'll poke around on that.

I have two monitors, one in portrait mode, the other in landscape. When I open the command history window, it is about the size of my portrait monitor. Unfortunately, its displayed on my landscape monitor which means most of the window is clipped and of no use. If I manually resize the window...

And the unusable tiny select window can be produced as simply as: echo foo >foo.txt %@select[foo.txt, 1, 1, 20, 80, 'bugg'] & Removing the trailing space-ampersand produces the correct size selection window. Possibly it should refuse to run rather than go bonkers in this situation.

Thanks, one mystery solved. I assume you're referring to the one-line note in the help file entry for DETACH? The space required before the ampersand (for DETACH, but not for separating commands!) remains undocumented, unless its lurking somewhere else. I can't tell if the documentation saying...

Just typing endiff & followed by Enter produces a message like "The process ID is nnnn". Or, I guess you can substitute any command for the endiff and get the same result.

Through tedious binary search, it appears that tcc, unlike 4nt, does not like the space after the final endiff. If I change this: endiff &^ to this: endiff&^ then the select window is normal, no message about a process ID, etc. Wonder what's really going on there? Here's a simple alias that I...

Hmmm, well, docs say TCC switches behavior depending on whether width is >= 150; that seems to be true interactively at least. Do I misunderstand the help file?

TCC 26.02.42 x64 Windows 10 [Version 10.0.19041.630] I'm trying to see if I can upgrade my ancient 4NT to TCC. In 4NT, I had the following alias: @alias gd `set gd_sel=%@select[%[DATRLB]\4nt\gd.txt, 1, 1, 20, 80, 'gd: Goto Directory'] &^ iff "%[gd_sel]" != "" then &^ iff isdir...

[posted this via NNTP first, but then realized I have no idea where that comes out now!] Returning to the JPSoft after a long absence, it appeared (though not 100% clear) that 4NT is to be replaced by TC 9. Not wanting the GUI interface, but also not wanting to have no upgrade path, I...