1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Command History Failure?

Discussion in 'Support' started by NetMage, Apr 6, 2011.

  1. NetMage

    Joined:
    Nov 18, 2009
    Messages:
    17
    Likes Received:
    0
    I am puzzled as to why commands are not going into my command history in a TCC tab in Take Command x64 on Windows 7.

    I do a command like
    ffind /[da2011-1-1] /[s1M] /M \\servername\*\exchange\*.pst

    and it shows up in command history. I up arrow and modify it:

    ffind /[da2011-1-1] /[s1M] /M \\servername\*\exchange\*.pst|for %file in (@CON:) echo %file

    and now no ffind commands are in my command history at all?

    What happened?
     
  2. NetMage

    Joined:
    Nov 18, 2009
    Messages:
    17
    Likes Received:
    0
    Never mind, I believe I found the issue - I still had a TCC/LE Window open and I had share command history setup.

    For some reason using the pipe caused command history to fail, when it worked without it???

    Ooops!!! Spoke too soon - without a TCC window open, the Take Command tab still fails at command history.
     
  3. NetMage

    Joined:
    Nov 18, 2009
    Messages:
    17
    Likes Received:
    0
    Still having the same thing using TCC 13.00.22 x64 Win 7 6.1.7601.

    Typed in a command
    grep "^[a-zA-Z]=" all-logons.ini|tr [:upper:] [:lower:]|sort >sort-all-logons.ini

    and hitting up arrow or typing grep than up arrow shows no command in history.

    Why does command history forget complicated commands?
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,804
    Likes Received:
    82
    Not reproducible here.

    Did you put GREP in a HistoryExclude variable?
     

Share This Page