Jon wrote:
> Ralph Corderoy writes:
> > When implementing this, was there a reason whatnow doesn't implement
> > `cd' with chdir, as normal Unix commands that offer cd do, and instead
> > "fake" it for `pwd', `ls', and `attach', but not `mime', etc?
>
> Well, the most honest answer that I can
Hi Jon,
> I do think that your example above is sort of bogus; whatnow does not
> provide full shell functionality so you can't do things like that
> anyway.
It's not bogus as it happened to me in normal use, that's how I found
the problem. whatnow isn't a full shell, but that doesn't matter.
Ralph Corderoy writes:
> Hi Jon,
>
> > David wrote:
> > > > It's very unintuitive, well, wrong, that a `cd' command at a
> > > > command's prompt doesn't change the current working directory as
> > > > far as all other commands are concerned. That's not how other
> > > > Unix commands that
Hi David,
> > $ comp -ed false
> > whatnow: problems with edit--draft left in /home/ralph/mail/drafts/,42
>
> I see your point but don't feel strongly about it. It looks like it
> was intentional, and has been that way for nearly 27 years (though the
> error message changed along the
Hi Jon,
> David wrote:
> > > It's very unintuitive, well, wrong, that a `cd' command at a
> > > command's prompt doesn't change the current working directory as
> > > far as all other commands are concerned. That's not how other
> > > Unix commands that provide cd work. If it can't be fixed
