Dear Juergen,
I think there is a significant difference in philosophy here. I think a history mechanism should keep a history of what _I_ type, but _not_ what is output by the system. If I were to type in a new function, it should be added to history. But if I list an existing function, it is displaying _output_ and _not_ what I am typing. Having the system add its own output to history makes the history nearly unusable for me because I have to scroll through meaningless history in order to get to the last think I typed - in order to try that again. This is a significant issue IMO.
The rule should be "all user input goes into history" and "no system output goes into history".
In the example I gave, I input the line to request the system to list the function. The display of the function was system output and nothing I typed.
Thanks.
Blake