Chet,
I'll do that right now.
Thanks for the QUICK response.
George...
On Tue, Mar 29, 2011 at 11:19 AM, Chet Ramey wrote:
> On 3/29/11 2:09 PM, George Goffe wrote:
> > Howdy,
> >
> > I am experiencing a problem with sourcing a file. It's really my bashrc
> but
> > I want to keep the corporat
On 3/29/11 2:09 PM, George Goffe wrote:
> Howdy,
>
> I am experiencing a problem with sourcing a file. It's really my bashrc but
> I want to keep the corporate version separate.
>
> What I'm seeing:
>
> 1) make a change to .grgrc
> 2) enter . .grgrc
> 3) usually use the changed "code".
>
> This
Howdy,
I am experiencing a problem with sourcing a file. It's really my bashrc but
I want to keep the corporate version separate.
What I'm seeing:
1) make a change to .grgrc
2) enter . .grgrc
3) usually use the changed "code".
This change is not appearing. My .grgrc is almost 3000 lines of code
Chet Ramey wrote:
>
> You might have better luck moving the trap command inside the { ... },
> before the while loop.
>
Yes. I realized that after a bit of testing :). Thanks
--
View this message in context:
http://old.nabble.com/bizarre-trap-behavior-while-reading-a-file-tp31242064p31267546
On Tue, Mar 29, 2011 at 08:02:17AM -0400, Steven W. Orr wrote:
> Is there a difference between
>
> while read line < file
> do
> stuff
> done
>
> vs
>
> while read line
> do
> stuff
> done < file
Yes. It's a huge difference. In the first one, the file is re-opened
by read every time t
On 3/29/2011 2:33 AM, Mart Frauenlob wrote:
On 28.03.2011 18:03, tytus64 wrote:
[...]
trap "" HUP; cat $log_file | {
while read line
[...]
useless use of cat!
while read ... < file
no need for a subshell actually (introducted by the pipe).
I'm a big opponent of useless cats, but I ha
