On Sat, Jun 27, 2015 at 11:55:32AM -0500, Ryan Gonzalez wrote:
> I think so...
>
> So, in order to get my cd command, I enter '-' at the rc prompt? Is there
> some way for that to happen automatically?
>
> On June 27, 2015 8:34:24 AM CDT, Neven Sajko wrote:
> >From the manual:
> >
> >
I think so...
So, in order to get my cd command, I enter '-' at the rc prompt? Is there some
way for that to happen automatically?
On June 27, 2015 8:34:24 AM CDT, Neven Sajko wrote:
>From the manual:
>
> -l If -l is given or the first character of argument
>
>From the manual:
-l If -l is given or the first character of argument
zero is -, rc reads commands from
$home/lib/profile, if it exists, before reading
its normal input.
Does this help you?
Finally booted up Plan 9 again. Indeed, the function works when placed in
the shell, but *not in lib/profile*.
I'm putting in $HOME/lib/profile. That's the correct location, right?
On Sat, Jun 13, 2015 at 1:46 PM, Ingo Krabbe wrote:
> try
>
> whatis cd
>
> to test if the function as active at
try
whatis cd
to test if the function as active at all
btw: I just saw your signature. Great :D
>>> --
>>> Ryan
>>> [ERROR]: Your autotools build scripts are 200 lines longer than your
>>> program. Something’s wrong.
>>> http://kirbyfan64.github.io/
>
> --
> Sent from my Android device with
I added it to the end of lib/profile.
On June 13, 2015 3:02:56 AM CDT, Ingo Krabbe wrote:
>I tried it in a fresh window, where it works for me.
>
>> Thanks for replying! Unfortunately, that doesn't change anything.
>Still
>> stuck at the 'term% ' prompt.
>>
>>
>> On Sun, Jun 7, 2015 at 6:43 PM,
I tried it in a fresh window, where it works for me.
> Thanks for replying! Unfortunately, that doesn't change anything. Still
> stuck at the 'term% ' prompt.
>
>
> On Sun, Jun 7, 2015 at 6:43 PM, Ingo Krabbe wrote:
>
>> try it with
>>
>> fn cd{
>> builtin cd $1
>> prom
It works:
: root; fn cd {builtin cd $* ; prompt=(': '`{pwd}^'; ' '')}
: root; cd
: /usr/a; cd /tmp
: /tmp;
If you’re still having trouble, paste a transcript like that, so we can see
what’s going on.
Note also that spaces in file names will screw up the
On Fri, 12 Jun 2015 16:05:21 CDT Ryan Gonzalez wrote:
>
> Thanks for replying! Unfortunately, that doesn't change anything. Still
> stuck at the 'term% ' prompt.
Invoke rc with -l flag (in acme middleclick on win rc -l).
Thanks for replying! Unfortunately, that doesn't change anything. Still
stuck at the 'term% ' prompt.
On Sun, Jun 7, 2015 at 6:43 PM, Ingo Krabbe wrote:
> try it with
>
> fn cd{
> builtin cd $1
> prompt=(`{pwd}^'% ' '')
> }
>
> the difference is `{pwd} not '{pwd}.
>
try it with
fn cd{
builtin cd $1
prompt=(`{pwd}^'% ' '')
}
the difference is `{pwd} not '{pwd}.
> Coming from a bash world, I really like knowing what directory I'm in at
> the prompt. I tried putting this at the end of 'lib/profile':
>
>
>
> fn cd{
> built
Coming from a bash world, I really like knowing what directory I'm in at
the prompt. I tried putting this at the end of 'lib/profile':
fn cd{
builtin cd $1
prompt=('{pwd}^'% ' '')
}
cd $HOME
However, it doesn't work! The 'cd' command seems to do what it normally
does. The prompt
12 matches
Mail list logo