CIW History

[Jake]

Hello,

I'm trying to make the 'history' command smarter for me by adding the
capability to include search strings (i.e. a history of every time I
used the command 'load'). It works beautifully, except that I've
noticed that my numerical results are off by 1 or 2 compared to what
is given by the history command. For example, history gives me:

1 history()
2 load( "/blah/script.il" )
3 Blah()
4 history()

Whereas my script gives me:

1 ddUpdateLibList()
2 history()
3 load( "/blah/script.il" )
4 Blah()
5 history()

How is the history() command calculating its numbers? I was looking
at the log file and searching for \a and \i and counting them up.
History ignored the start-up command ddUpdateLibList. How does it
know to do this? Is it reading a different log file somewhere? If it
is, where is it?

Thanks,
Jake

 

[Andrew Beckett]

Jake wrote, on 08/20/10 16:01:

Hello,

I'm trying to make the 'history' command smarter for me by adding the
capability to include search strings (i.e. a history of every time I
used the command 'load'). It works beautifully, except that I've
noticed that my numerical results are off by 1 or 2 compared to what
is given by the history command. For example, history gives me:

1 history()
2 load( "/blah/script.il" )
3 Blah()
4 history()

Whereas my script gives me:

1 ddUpdateLibList()
2 history()
3 load( "/blah/script.il" )
4 Blah()
5 history()

How is the history() command calculating its numbers? I was looking
at the log file and searching for \a and \i and counting them up.
History ignored the start-up command ddUpdateLibList. How does it
know to do this? Is it reading a different log file somewhere? If it
is, where is it?

Thanks,
Jake

It doesn't read the log file. Each time a function is called, it is stored in a
data structure which is used by the history() function.

Regards,

Andrew.