[566] in Release_7.7_team
Re: New options for add
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Jun 2 22:18:29 1996
To: Craig Fields <cfields@MIT.EDU>
Cc: release-team@MIT.EDU
In-Reply-To: Your message of "Sun, 02 Jun 1996 22:08:14 EDT."
<199606030208.WAA15618@mad-scientist.MIT.EDU.MIT.EDU>
Date: Sun, 02 Jun 1996 22:18:20 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> add -m locker
> behaves normally if locker wasn't in your path already. If locker
> was anywhere in your path though, it moves it to the end. Similarly,
> add -m -f locker
> will move locker to the front of your path.
I claim that -m is needless complication. "add -f" should move the
locker to the front of your path if it's already there, and if the
user really wants to move a locker to the end of their path, they can
"add -r" and "add".
Rationale: "add -f" is fairly useless right now except in your
dotfiles, since it doesn't have any reliable behavior unless you know
what path you started with. So people would always use "add -f -m"
when recommending commands to users. But it's pretty rare for someone
to want a locker *last* in their path.
