Re: hurd does NOT need /hurd
email@example.com (Thomas Bushnell, BSG) writes:
> Richard Kettlewell <firstname.lastname@example.org> writes:
>> I still don't see why settrans can't search some kind of path list (or
>> add a fixed prefix to relative names for that matter, it'd be "/hurd/"
>> on current systems presumably) before the 'squirrelling' step.
> Of course it could; the question is: is this valuable or not?
Yes, I think it is. Requiring the user to type /hurd when the
computer could work it out automatically is an example of requiring a
human to do a repetitive task that a computer could do easily enough
(and probably better - the computer is unlikely to typo it as /hrd).
I'm philosophically opposed to that, and think anyone else designing a
human-computer interface ought to be to.
More practically and less philosophically, extra typing increases the
risk of RSI; wastes time; makes lines more likely to wrap; etc.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org