[EMAIL PROTECTED] wrote:
> The problem is that if I did this out of the box
> like the following, it 'flattens' the list:
>
> Example:
> for j in `cat $i`; do
> echo $j
> done
>
>
Andreas,
This doesn't work unfortunately, and yields the same errors seen with
the backticks.
-Garrett
-Original Message-
From: Andreas Schwab [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 2:06 AM
To: Cooper, Garrett W
Cc: bug-bash@gnu.org; [EMAIL PROTECTED]
Subject: R
Thilo Six wrote the following on 10.05.2007 18:56:
> OK then thank you and i would like to open a wishlist bug for it. ;)
...and in the interim we probably should add a notice to the manpage, that
erasedups currently deons´t work session persistent.
> bye Thilo
--
i am on Ubuntu 2.6 KDE
- so
Chet Ramey wrote the following on 10.05.2007 05:46:
> If you want to force the history file to be completely rewritten, you
> can use `history -w' at shell exit to rewrite it.
$ top
$ htop
$ top
$ htop
$ history
1 top
2 htop
3 history
$ history -w
in new shell:
$ history
1
> Bash Version: 3.0
> Patch Level: 0
> Release Status: release
>
> Description:
>
> Summary:
> Characters aren't being properly escaped/evaluated in a Bash
>
> Full Description:
>
> I'm trying to take a series of lines in a file like so (ignore
> 1.-3. c
> Chet Ramey wrote:
> > If you want to force the history file to be completely rewritten, you
> > can use `history -w' at shell exit to rewrite it. There is, unfortunately,
> > currently no easy way to force the `rewrite-at-exit' behavior.
>
> Could a shell trap be used to do this?
>
> trap 'h
[EMAIL PROTECTED] writes:
> Fix:
> The problem lies in the parser somewhere,
The problem is that you are not correctly quoting. Better use $(...)
instead of `...`, that is easier for beginners to get right.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products Gmb
