Any Bash features you'd like to see?
Ken O. Burtch
kburtch-Zd07PnzKK1IAvxtiuMwx3w at public.gmane.org
Thu May 12 16:36:17 UTC 2005
On Thu, 2005-05-12 at 11:20, Lennart Sorensen wrote:
> On Thu, May 12, 2005 at 05:56:54PM +0300, Peter wrote:
> > The purpose of having a log is to be able to backtrack. That implies
> > order is important. One could have a record format similar to the log
> > file entries a la '${time}(${pid}): line \n' but the writes must be done
> > line-locked or they will be interspersed with output from other shells.
>
> I never considered the bash history to be a log, just a great source of
> previous command lines.
>
> If it was a log, I would expect it to not keep loosing information when
> multiple shells are running, hence it is not a log. A log feature could
> be useful though.
>
> Lennart Sorensen
For what it's worth, my business shell (Bush) has history log.
If you want a powerful scripting language / shell / template engine, use
Bush or a similar project. It's time to give Bash a well-deserved rest.
Ken B.
> --
> The Toronto Linux Users Group. Meetings: http://tlug.ss.org
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
--
The Toronto Linux Users Group. Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
More information about the Legacy
mailing list