Sorry for the long message. I've been using TakeCommand for many years now, but lately I'm seeing some weird behavior with history, recall (up arrow) and tpipe.
On the Command Line options tab, I have checked [Move to End] and selected the [Save Last] radio button under Command History.
I have also specified a location for history2.log.
I started with a clean history file and ran the following commands (note: NB. is followed by a comment).
> tcc: NB. Alias for my local TCC config folder.
> type somefile.txt
> history NB. The above two commands are displayed as expected.
> tcc:
> type somefile.txt
> history NB. Everything displays normally and no duplicates commands are displayed.
Now the weirdness starts.
> type somefile.txt | tpipe /dup=0,0,1,100,0,0 NB. Remove duplicate lines from somefile.txt and it works as expected.
But now the history is all screwed up. In particular, duplicates have reappeared. Also, the tpipe line does not show up when I try the up arrow.
To make matters worse, a copy of TakeCommand seems to persists in memory after I exit. At least, that's what the Task Manager says. I can tell that something funny is going on because my laptop (a brand new Dell Precision Workstation) starts to heat up.
After I make sure that TakeCommand is no longer running and restart the shell, I check the history and confirm that duplicates have reappeared. Now if I repeat a command and check the history, once again duplicates are correctly removed. In fact, as long as I avoid the command that includes tpipe above, everything works as expected. And exiting TakeCommand causes no problems.
I see the same problems if I replace problematic command above with
> tpipe /input=somefile.txt /dup=0,0,1,100,0,0
Is there a problem with tpipe?
rick
On the Command Line options tab, I have checked [Move to End] and selected the [Save Last] radio button under Command History.
I have also specified a location for history2.log.
I started with a clean history file and ran the following commands (note: NB. is followed by a comment).
> tcc: NB. Alias for my local TCC config folder.
> type somefile.txt
> history NB. The above two commands are displayed as expected.
> tcc:
> type somefile.txt
> history NB. Everything displays normally and no duplicates commands are displayed.
Now the weirdness starts.
> type somefile.txt | tpipe /dup=0,0,1,100,0,0 NB. Remove duplicate lines from somefile.txt and it works as expected.
But now the history is all screwed up. In particular, duplicates have reappeared. Also, the tpipe line does not show up when I try the up arrow.
To make matters worse, a copy of TakeCommand seems to persists in memory after I exit. At least, that's what the Task Manager says. I can tell that something funny is going on because my laptop (a brand new Dell Precision Workstation) starts to heat up.
After I make sure that TakeCommand is no longer running and restart the shell, I check the history and confirm that duplicates have reappeared. Now if I repeat a command and check the history, once again duplicates are correctly removed. In fact, as long as I avoid the command that includes tpipe above, everything works as expected. And exiting TakeCommand causes no problems.
I see the same problems if I replace problematic command above with
> tpipe /input=somefile.txt /dup=0,0,1,100,0,0
Is there a problem with tpipe?
rick
