Re: [BASH] shell functions don't work the same when opening sub-shells
From: Lars Kellogg-Stedman (8273grkci8q8kgt_at_jetable.net)
Date: 11/28/05
- Next message: Lars Kellogg-Stedman: "Re: Env variable whit asterisk"
- Previous message: danr: "Re: Problem with using extended filename globbing in Ksh"
- In reply to: Andrew Falanga: "[BASH] shell functions don't work the same when opening sub-shells"
- Next in thread: Chris F.A. Johnson: "Re: [BASH] shell functions don't work the same when opening sub-shells"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 28 Nov 2005 09:55:31 -0600
> When starting a new shell all works as it should, but after exiting a
> sub-shell and using this function again, the function completely ignores
> the -p option and simply uses the default. Can anyone shed some light
> as to why for me?
Can you post the code so that we can take a look at it?
Have you tried running the script in debug (-x) mode? You can get trace
output for just the function in question by adding 'set -x' at the
beginning of the function (and 'set +x' before the function exits to
turn off tracing).
-- Lars
-- Lars Kellogg-Stedman <8273grkci8q8kgt@jetable.net> This email address will expire on 2005-11-23.
- Next message: Lars Kellogg-Stedman: "Re: Env variable whit asterisk"
- Previous message: danr: "Re: Problem with using extended filename globbing in Ksh"
- In reply to: Andrew Falanga: "[BASH] shell functions don't work the same when opening sub-shells"
- Next in thread: Chris F.A. Johnson: "Re: [BASH] shell functions don't work the same when opening sub-shells"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
