🚀 go-pugleaf

In comp.unix.shell you write:
>! >! Also, the history list should save a command only if it is different 
>! >! from the last one.
>! 
>! >No way.  You will be able to reach the next *different* command in the
>! 
>! DISAGREE!
>! if you are developing something, and you get into a debug mode, the
>! usual sequence of commands goes something like:
>!     edit
>!     compile
>!     run ( or debug )
>!     edit
>!     compile
>!     ... ( ad infinitum )
>! 
>! if after doing this 30 times, the last 100 entries in your history are
>! the same three commands over and over, what if you then want to do

>Have you ever seen a windowing environment?

yes, I use one every day, how does this relate to the question?
Are you suggesting that I should open a new window for every different
thing I want to do? lets see, I'll have a couple of windows for
editing source, a window for make, a window for gbd, another window
for viewing output, oh and I'ld like a window to create datafiles, and
another window for setting the environment variables that the program
uses, now if I could just have a window for making coffee, and then if
I could find that source window again, I'ld be right! ( one window
manager wouldn't be enough, I would need a corporation of window
manager, then I would need a window manager manager, and of course all
the manager want their own secretaries ) what the hell has this got to
do with shell histories anyway?

I think my brain copes with three windows better!

>! Also, I would really love a 'merge_histories' feature, this is relevant
>! only if you have many tcsh's running at the same time, because when I
>! quit my XWindows session, by dumb luck or whatever, the last tcsh to
>          ^^^^^^^^^^^^^^^^somehow answers the question above, I guess.....

it does?

>! save the history seems to be the one I used the least, with all the
>! most boring, and least used commands in the history, any solutions?
>! anyone come up with some sort of .logout hack?

>No suggestions.  What exactly do you mean with "merge histories"?  I imagine
>the last 100 or so commands from 5-10 shells, intermixed, but will it ever
>constitute interesting stuff?  Oh sure, you might want to use it for
>documentational purposes........:)

Not exactly. Documentation is something that needs improving wrt unix,
however not in this field. The way I see the merge-history feature
working would be to take the timestamps ( which tcsh so kindly puts in
your .history ) and sort the last $savehist unique commands that
appear in the history, taking the input from the dying tcsh and the
existing .history. This way they remain in some sort of useful order
( if order is important to you ), and you get the last $savehist
things that you did saved. It was just a whim. perhaps one day when I
have a computer of my own and I don't have anything better to do on a
rainy night I will sit down and hack something together. Its summer
and I don't have my own computer. Of course there would have to be
some sort of file locking done, so that race conditions are solved,
but this is another problem.

! ( ~~harald E. )

S.Riehm: constantly being distracted by the possibilities of life.
		- Alice in Wonderland
smr@pki-nbg.philips.de