> "CR" == Chet Ramey writes:
>> $ history needs a --no-numbers-please option (-u maybe?), as I can't
>> recall when I didn't run the output through sed to get rid of them.
CR> Why not just use fc -ln?
Because "help history" didn't tip me off that I could try that. However
$ history|wc -l
999
> $ history needs a --no-numbers-please option (-u maybe?), as I can't
> recall when I didn't run the output through sed to get rid of them.
Why not just use fc -ln?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRUc...@case.eduhttp://tiswww.tis.case.e
$ history needs a --no-numbers-please option (-u maybe?), as I can't
recall when I didn't run the output through sed to get rid of them.
Ivan Zahariev a écrit :
> Same here, as Marc said.
>
> I think that usually we are reading the script from a file and this is
> the use-case we must focus on. Currently, we have the problem I
> described when executing a script from a file and I think this must be
> fixed/changed.
Hey, wait.
On Aug 5, 2:05 pm, Marc Herbert wrote:
> I am not sure I get this... first of all, the script itself is usually
> not read from stdin (but from fd 255 in bash).
>
> Now considering the seldom cases where the script is actually read from
> stdin, are you saying that: it is a wanted feature that s
