The audit file should not eliminate duplicates or lines starting with spaces. However, the history file is generated and read by the user, and the user knows which commands are run multiple times in a row.
On Fri, Jan 3, 2014 at 5:47 PM, Mark McCullough <[email protected]>wrote: > Just to throw a different perspective on it. Knowing that a command was > run multiple times in a row, can be very useful to me when reading a > history file. Especially if HISTFILE (or the similar ksh_audit) is pointed > to /dev/udp/central_log_host/514 > > > On 2014 Jan 3, at 17:35 , David Korn <[email protected]> wrote: > > > Since all HISTCONTROL does is eliminate immediate duplicates or no keep > commands that start with a space, I don't know why this can't be the > default behavior. > > > > Ignoring failed commands seems like a bad idea. Failed command often > occur because of a typo and in this case I want to edit the failed command. > > > > > > On Thu, Jan 2, 2014 at 8:47 PM, Ed Horch <[email protected]> wrote: > > What bash does is a good start. I've always wanted a more powerful way > to exclude certain things from the command history, especially erroneous > and failed commands. I haven't been able to think of a good way to specify > that. For example: > > > > $ cat ~/.kshcr > > cat: /home/ebh/.kshcr: No such file or directory > > > > That shouldn't go into the history. But what about: > > > > $ cat ~/.kshrc > > cat: /home/ebh/.kshrc: No such file or directory > > $ echo 'alias l=ls\ -xF' >~/.kshrc > > $ # Would like to do M-PM-P here > > > > Maybe some "keep-previous-command-anyway" editing function or some such. > > > > -Ed Horch > > > > ---- > "The speed of communications is wondrous to behold. It is also true that > speed can multiply the distribution of information that we know to be > untrue." Edward R Murrow (1964) > > Mark McCullough > [email protected] > > > > >
_______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
