Anyone who's still using tcsh after all these years might recognize that export is a Bourne shell thing - but it's absolutely vital that it's documented in case new people come along.

Wouldn't it be better to wrap the paragraph in <note></note> or <important></important>?

For reference, with (t)csh you use: setenv VARIABLE "value"

in case new people come along

Yep, that's the case here - my co-op student ended up modifying the host's own /etc/fstab
I'll take a look at <note> examples.

We would have to sweep the handbook for more such examples to either add more such notes or change the instructions to be written for /bin/sh.

We should indeed do a comprehensive review of the examples in the handbook but I'd hope that we can at least address this case which has tripped someone up. (A cursory look turned up references to sh or csh for other examples.)

@bcr please can you take a look at this changes? (For me everything it's correct)

If everything it's correct I can make the commit myself

(I can commit with approval from a doc committer)

Ping?

Oooooops, I completely forgot about this. I'm going to make the commit right now!