From: Neven Sajko <nsajko@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Trying to override 'cd' command
Date: Sat, 27 Jun 2015 15:34:24 +0200 [thread overview]
Message-ID: <CAL+bK4MtU=m7iAsYoHspdm+K+nS2tF5gZojAgDiaR6yh-r5dXA@mail.gmail.com> (raw)
In-Reply-To: <CAO41-mP3q0NCnZ4f848dM=QwCbBCLfvn9EuhUPfWi6rE9NjpKA@mail.gmail.com>
>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?
next prev parent reply other threads:[~2015-06-27 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 23:29 Ryan Gonzalez
2015-06-07 23:43 ` Ingo Krabbe
2015-06-12 21:05 ` Ryan Gonzalez
2015-06-12 21:35 ` Bakul Shah
2015-06-12 21:50 ` Anthony Sorace
2015-06-13 8:02 ` Ingo Krabbe
2015-06-13 17:22 ` Ryan Gonzalez
2015-06-13 18:46 ` Ingo Krabbe
2015-06-27 0:24 ` Ryan Gonzalez
2015-06-27 13:34 ` Neven Sajko [this message]
2015-06-27 16:55 ` Ryan Gonzalez
2015-06-27 20:23 ` Teodoro Santoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL+bK4MtU=m7iAsYoHspdm+K+nS2tF5gZojAgDiaR6yh-r5dXA@mail.gmail.com' \
--to=nsajko@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).