From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] rc: whatis broken
Date: Sat, 01 Jul 2017 18:27:13 +0100 [thread overview]
Message-ID: <1498930033.221781.1027514904.072DC15F@webmail.messagingengine.com> (raw)
In-Reply-To: <1398CEEA-6DBA-4955-8798-7E59E9F0F5C4@stanleylieber.com>
On Sat, Jul 1, 2017, at 03:58 PM, Stanley Lieber wrote:
> On my system a function still overrides the existence of a file of the same name in /bin. What gives?
now it works properly on mine, even in the same window and shell which was earlier failing. i see what it is now. i ran into the problem after using a script which defined a function without first calling `rfork e`. the function thus got into the shell's environment but not its cache. it affected other scripts such as B, but whatis in the shell itself failed to find it. it's arguably not a bug in rc, but i hate it. :)
--
Linux? I used ext4 for a few years. In proportion to the time spent using it, I lost as much data to it as I lost to the very worst released version of reiserfs.
prev parent reply other threads:[~2017-07-01 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 14:38 cinap_lenrek
2017-07-01 14:58 ` Stanley Lieber
2017-07-01 17:27 ` Ethan Grammatikidis [this message]
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=1498930033.221781.1027514904.072DC15F@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/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).