On Fri, Nov 21, 2008 at 10:58 AM, Ryan Stewart wrote:
> On Fri, Nov 21, 2008 at 9:52 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
^^
There's a policy on this list of not including email addresses in the
body of messages, so as to minimize spam exposure. So please don't
include address
On Fri, Nov 21, 2008 at 9:52 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> To be fair, you have to do a lot of reading to learn the necessary
> concepts; there's not really a simple statement you can search for.
> Start with the section "COMMAND EXECUTION ENVIRONMENT", which is at
> line 1665 on my
On Fri, Nov 21, 2008 at 10:24 AM, Ryan Stewart wrote:
> A nearly 4900 line man page is not exactly "direct". That was the
> first place I looked. It was also the last place I looked, but even
> knowing more or less what I was looking for, I couldn't find it. Can
> you point me to a line number in t
On Fri, Nov 21, 2008 at 09:10:32AM -0600, Ryan Stewart wrote:
>On Fri, Nov 21, 2008 at 8:46 AM, Morche Matthias
><[EMAIL PROTECTED]> wrote:
>> I bet Your line with the call of .bashrc from .bash_profile looks like
>> .bashrc
>> change it to
>> . .bashrc
>> and it will do what You intend and then RT
On 2008-11-21 15:24Z, Ryan Stewart wrote:
> On Fri, Nov 21, 2008 at 9:13 AM, Christopher Faylor
> <[EMAIL PROTECTED]> wrote:
^^
http://www.cygwin.com/acronyms/#PCYMTNQREAIYR
>> google is not the final authority. "info bash" or "man bash" would give
>> you
Ryan Stewart wrote:
" A nearly 4900 line man page is not exactly "direct". That was the
" first place I looked. It was also the last place I looked, but even
" knowing more or less what I was looking for, I couldn't find it. Can
" you point me to a line number in the man page?
The '.' command is a
On Fri, Nov 21, 2008 at 9:13 AM, Christopher Faylor
<[EMAIL PROTECTED]> wrote:
> google is not the final authority. "info bash" or "man bash" would give
> you this info much more directly.
>
A nearly 4900 line man page is not exactly "direct". That was the
first place I looked. It was also the las
On Fri, Nov 21, 2008 at 09:10:32AM -0600, Ryan Stewart wrote:
>On Fri, Nov 21, 2008 at 8:46 AM, Morche Matthias
><[EMAIL PROTECTED]> wrote:
>> I bet Your line with the call of .bashrc from .bash_profile looks like
>> .bashrc
>> change it to
>> . .bashrc
>> and it will do what You intend and then RT
On Fri, Nov 21, 2008 at 8:46 AM, Morche Matthias
<[EMAIL PROTECTED]> wrote:
> I bet Your line with the call of .bashrc from .bash_profile looks like
> .bashrc
> change it to
> . .bashrc
> and it will do what You intend and then RTFM for an explanation :-)
>
Thanks. I'm a linux nub. It took a good b
Hi Ryan,
> -Original Message-
> From: [EMAIL PROTECTED]
...
> When bash is started with the "-l" (that's an 'L') flag, aliases that
> I've defined in .bashrc don't take effect. My .bash_profile includes a
> call to .bashrc, and I know that .bashrc is being executed because
...
I bet Your
When bash is started with the "-l" (that's an 'L') flag, aliases that
I've defined in .bashrc don't take effect. My .bash_profile includes a
call to .bashrc, and I know that .bashrc is being executed because
I've put an echo at the beginning and end of it, and both messages are
printed out. Even if
11 matches
Mail list logo
