Thread View: comp.sys.next.misc
4 messages
4 total messages
Started by Scott Anguish
Mon, 27 Jul 1992 19:08
Using MANPATH on Next
Author: Scott Anguish
Date: Mon, 27 Jul 1992 19:08
Date: Mon, 27 Jul 1992 19:08
19 lines
652 bytes
652 bytes
We are wanting to set up the MANPATH enviroment variable for our users so that it searches /usr/man /usr/local/man ~/Unix/man Unfortunately, we haven't had any success as yet. Any suggestions? Thanks Scott -- - Scott Anguish - sanguish@digifix.com (NextMail)
Re: Using MANPATH on Next
Author: Carl Edman
Date: Mon, 27 Jul 1992 20:15
Date: Mon, 27 Jul 1992 20:15
23 lines
968 bytes
968 bytes
Scott Anguish writes > We are wanting to set up the MANPATH enviroment variable for our users so > that it searches > > /usr/man > /usr/local/man > ~/Unix/man > > Unfortunately, we haven't had any success as yet. > > Any suggestions? Why, just put export MANPATH=/usr/man:/usr/local/man:$HOME/Unix/man into your global sh/ksh/zsh startup file and setenv MANPATH /usr/man:/usr/local/man:$HOME/Unix/man into your global csh/tcsh startup file. Carl Edman
Re: Using MANPATH on Next
Author: Graham Stoney
Date: Mon, 03 Aug 1992 01:47
Date: Mon, 03 Aug 1992 01:47
30 lines
1785 bytes
1785 bytes
cedman@714-725-3165.nts.uci.edu (Carl Edman) writes: >Scott Anguish writes >> We are wanting to set up the MANPATH enviroment variable for our users so >> that it searches ... I've had this problem too, and found no good solution. NeXT really should provide a way to set environment variables like this - reading a setting from the defaults database seems reasonable. >Why, just put >export MANPATH=/usr/man:/usr/local/man:$HOME/Unix/man But this doesn't help for programs launched from the workspace. For example, I'd like Cmd-M in NeXT edit to search our local manual directory, but the only way I can get it to work is by putting a 'man' shell script in /usr/local/bin (which, by pure luck, is ahead of /usr/ucb/man in the default PATH) and getting it to add my local directory to MANPATH before running the real 'man'. Ugly. Another alternative is to play some tricks to run a script instead of Workspace when you log in, and get the script to set whatever environment variables you need, then run Workspace. Also ugly. Graham -- Graham Stoney | "a Perl script is correct if it's halfway Flip Dibner fan club, "Hi Flip!" | readable and gets the job done before your Ph: +61 2 805-2909 Fax: -2929 | boss fires you." L. Wall & R. Schwartz
Re: Using MANPATH on Next
Author: Steve Anderson
Date: Mon, 03 Aug 1992 20:33
Date: Mon, 03 Aug 1992 20:33
12 lines
1236 bytes
1236 bytes
This continuing thread about getting man to know about MANPATH reminds
me I've had the same problem. Using zsh, I have MANPATH set in my
.zshenv file (and exported). Individual shells know what the value is,
but somehow man can't find anything that's on $MANPATH but not in
/usr/man. I finally gave up and aliased "man" to a function
{/usr/ucb/man -M $MANPATH $*}
and that works fine! Wierd (note that the function explicitly refers
to the shell variable - I didn't cade the MANPATH into it). I haven't
had any problem with zsh exporting other variables, so it looks like a
fact about /usr/ucb/man to me.
--Steve Anderson
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads