%% Chet Ramey <[EMAIL PROTECTED]> writes:
cr> Paul D. Smith wrote:
>> This isn't a bug, actually. I'm wondering if there's any way to
>> access the string provided with the -c option to the shell, from
>> within the shell init files.
cr> The $BASH_EXECUTION_STRING variable exists in ba
$BAw?.!&G[?.;v6H$7$J$$J}$O(B[EMAIL PROTECTED]
$B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B
$B!Z%-%c%C%7%s%0![B>$b$*NO$K$J$j$^$9(B
$B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B
$B(Bhttp://www.f-power.com/mein/
(B
$B(,(,(
Paul D. Smith wrote:
> This isn't a bug, actually. I'm wondering if there's any way to access
> the string provided with the -c option to the shell, from within the
> shell init files.
>
>
> For example, if I run this;
>
> bash --login -c 'echo hi'
>
> How can I find the string 'echo hi' f
This isn't a bug, actually. I'm wondering if there's any way to access
the string provided with the -c option to the shell, from within the
shell init files.
For example, if I run this;
bash --login -c 'echo hi'
How can I find the string 'echo hi' from within my ~/.bash_profile? I
tried t