Xhistory (window) and CursorUP in console

[Alpengreis]

If, after a PC reboot, I quickly start a TCC console (Conhost) after logging in and execute a command via the XHistory window, it is often (probably always) not available via CursorUp afterward.

However, if I wait a certain amount of time before executing a command via the XHistory window after rebooting, it is available via CursorUp as expected.

I'm not sure if I've already noticed this behavior with v35 on another notebook...

In any case, there seems to be some kind of timing issue with XHistory (the window).

 

[rconn]

I don't know what you mean by "CursorUp".

 

[Alpengreis]

CursorUp (I move the cursor key up) to repeat commands in a TCC console ... repeat commands I type manually and also executed through Xhistory window.

 

[rconn]

The history list and the extended history list are separate; running a command from the extended history list does not add it to the (local or global) history list.

 

[Alpengreis]

But normally it DOES add it. Why is that then? Why I can repeat then normally with Cursor Up a command which I executed from the extended history list?

Maybe that's then the "normal" temporary history, outside TCC which is also working in CMD probably?!

PS: I don't load a normal TCC history file currently.

PPS: Tested now, an executed command from xhistory window is at least added to this:

and this: