mh-profile.man

早期freebsd实现

MH-PROFILE(5)        BSD Programmer's Manual        MH-PROFILE(5)


       Similarly, if you define the envariable MMHHCCOONNTTEEXXTT, you can
       specify  a  context other than the normal context file (as
       specified in the _M_H profile).  As always, unless the value
       of  MMHHCCOONNTTEEXXTT  is  absolute,  it will be presumed to start
       from your _M_H directory.

       _M_H programs also support other envariables:

       MMAAIILLDDRROOPP : tells _i_n_c the default maildrop
            This supercedes the "MailDrop:" profile entry.

       SSIIGGNNAATTUURREE : tells _s_e_n_d and _p_o_s_t your mail signature
            This supercedes the "Signature:" profile entry.

       HHOOMMEE : tells all _M_H programs your home directory

       SSHHEELLLL : tells _b_b_l the default shell to run

       TTEERRMM : tells _M_H your terminal type
            The TTEERRMMCCAAPP envariable is also consulted.  In partic-
            ular,  these tell _s_c_a_n and _m_h_l how to clear your ter-
            minal, and how many columns wide  your  terminal  is.
            They  also tell _m_h_l how many lines long your terminal
            screen is.

       eeddiittaalltt : the alternate message
            This is set by _d_i_s_t and _r_e_p_l during edit sessions  so
            you  can  peruse  the  message  being  distributed or
            replied to.  The message is also available through  a
            link called "@" in the current directory if your cur-
            rent working directory and  the  folder  the  message
            lives in are on the same UNIX filesystem.

       mmhhddrraafftt : the path to the working draft
            This is set by _c_o_m_p, _d_i_s_t, _f_o_r_w, and _r_e_p_l to tell the
            _w_h_a_t_n_o_w_p_r_o_c which file to ask "What  now?"  questions
            about.    In  addition,  _d_i_s_t,  _f_o_r_w,  and  _r_e_p_l  set
            mmhhffoollddeerr if appropriate.  Further, _d_i_s_t and _r_e_p_l  set
            mmhhaallttmmssgg  to  tell the _w_h_a_t_n_o_w_p_r_o_c about an alternate
            message associated with the draft (the message  being
            distributed  or  replied to), and _d_i_s_t sets mmhhddiisstt to
            tell the _w_h_a_t_n_o_w_p_r_o_c that message re-distribution  is
            occurring.   Also,  mmhheeddiittoorr is set to tell the _w_h_a_t_-
            _n_o_w_p_r_o_c the user's choice of editor (unless  overrid-
            den  by  `-noedit').   Similarly, mmhhuussee may be set by
            _c_o_m_p.  Finally, mmhhmmeessssaaggeess is set by _d_i_s_t, _f_o_r_w,  and
            _r_e_p_l  if annotations are to occur (along with mmhhaannnnoo--
            ttaattee, and mmhhiinnppllaaccee).  It's amazing all the  informa-
            tion  that  has to get passed via envariables to make
            the "What now?" interface look squeaky clean  to  the
            _M_H  user,  isn't it?  The reason for all this is that



[mh.6]                        MH.6.8                            5








MH-PROFILE(5)        BSD Programmer's Manual        MH-PROFILE(5)


            the _M_H user can select _a_n_y program  as  the  _w_h_a_t_n_o_w_-
            _p_r_o_c,  including  one  of  the standard shells.  As a
            result, it's not possible to pass information via  an
            argument list.
            If the WHATNOW option was set during _M_H configuration
            (type `-help' to an _M_H command to find out),  and  if
            this envariable is set, if the commands _r_e_f_i_l_e, _s_e_n_d,
            _s_h_o_w, or _w_h_o_m are not  given  any  `msgs'  arguments,
            then they will default to using the file indicated by
            mmhhddrraafftt.  This is  useful  for  getting  the  default
            behavior supplied by the default _w_h_a_t_n_o_w_p_r_o_c.

       mmhhffoollddeerr : the folder containing the alternate message
            This  is set by _d_i_s_t and _r_e_p_l during edit sessions so
            you can peruse other messages in the  current  folder
            besides the one being distributed or replied to.  The
            mmhhffoollddeerr envariable is also set by  _s_h_o_w,  _p_r_e_v,  and
            _n_e_x_t for use by _m_h_l.

       MMHHBBBBRRCC :
            If  you define the envariable MMHHBBBBRRCC, you can specify
            a BBoards information file other  than  _._b_b_r_c  to  be
            read by _b_b_c.  If the value of MMHHBBBBRRCC is not absolute,
            (i.e., does not begin with a // ), it will be presumed
            to start from the current working directory.

       MMHHFFDD :
            If  the  OVERHEAD option was set during _M_H configura-
            tion (type `-help' to an _M_H  command  to  find  out),
            then if this envariable is set, _M_H considers it to be
            the number of a  file  descriptor  which  is  opened,
            read-only  to  the  _M_H  profile.   Similarly,  if the
            envariable MMHHCCOONNTTEEXXTTFFDD is set, this is the number  of
            a file descriptor which is opened read-only to the _M_H
            context.  This feature of _M_H is experimental, and  is
            used  to  examine  possible speed improvements for _M_H
            startup.  Note that these envariables must be set and
            non-empty  to enable this feature.  However, if OVER-
            HEAD is enabled during _M_H configuration, then when _M_H
            programs call other _M_H programs, this scheme is used.
            These file descriptors are not closed throughout  the
            execution  of  the  _M_H  program, so children may take
            advantage of this.  This approach is  thought  to  be
            completely  safe  and does result in some performance
            enhancements.


FFIILLEESS
       $HOME/.mh_profile                         The user profile
       or $MH                                    Rather than the standard profile
       <mh-dir>/context                          The user context



[mh.6]                        MH.6.8                            6








MH-PROFILE(5)        BSD Programmer's Manual        MH-PROFILE(5)


       or $CONTEXT                               Rather than the standard context
       <folder>/.mh_sequences                    Public sequences for <folder>

PPRROOFFIILLEE CCOOMMPPOONNEENNTTSS
       All

SSEEEE AALLSSOO
       mh(1), environ(5), mh-sequence(5)

DDEEFFAAUULLTTSS
       None

CCOONNTTEEXXTT
       All

HHIISSTTOORRYY
       In previous versions of _M_H, the current-message value of a
       writable  folder  was  kept  in a file called "cur" in the
       folder itself.  In _m_h_._3,  the  _._m_h___p_r_o_f_i_l_e  contained  the
       current-message  values  for  all  folders,  regardless of
       their writability.

       In all versions of _M_H since _m_h_._4, the _._m_h___p_r_o_f_i_l_e contains
       only  static  information,  which  _M_H  programs  will  NNOOTT
       update.  Changes in context are made to the  _c_o_n_t_e_x_t  file
       kept in the users MH _d_i_r_e_c_t_o_r_y.  This includes, but is not
       limited to: the "Current-Folder"  entry  and  all  private
       sequence information.  Public sequence information is kept
       in a file called _._m_h___s_e_q_u_e_n_c_e_s in each folder.

       To convert from the format used in releases of _M_H prior to
       the  format used in the _m_h_._4 release, _i_n_s_t_a_l_l_-_m_h should be
       invoked with the `-compat' switch.  This generally happens
       automatically  on  _M_H  systems generated with the "COMPAT"
       option during _M_H configuration.

       The _._m_h___p_r_o_f_i_l_e may override the path of the _c_o_n_t_e_x_t file,
       by  specifying  a  "context" entry (this must be in lower-
       case).  If the entry is not absolute (does not start  with
       a  // ),  then  it is interpreted relative to the user's _M_H
       directory.  As a result, you can actually have  more  than
       one  set  of  private sequences by using different context
       files.

BBUUGGSS
       The shell quoting conventions are  not  available  in  the
       .mh_profile.  Each token is separated by whitespace.

       There is some question as to what kind of arguments should
       be placed in the profile as options.  In order to  provide
       a  clear  answer,  recall command line semantics of all _M_H



[mh.6]                        MH.6.8                            7








MH-PROFILE(5)        BSD Programmer's Manual        MH-PROFILE(5)


       programs:  conflicting  switches   (e.g.,   `-header   and
       `-noheader')  may  occur more than one time on the command
       line, with the last switch  taking  effect.   Other  argu-
       ments,  such  as message sequences, filenames and folders,
       are always remembered on the invocation line and  are  not
       superseded  by  following  arguments  of  the  same  type.
       Hence, it is safe to place only switches (and their  argu-
       ments) in the profile.

       If one finds that an _M_H program is being invoked again and
       again with the same arguments, and those arguments  aren't
       switches,  then there are a few possible solutions to this
       problem.  The first is to create a  (soft)  link  in  your
       _$_H_O_M_E_/_b_i_n  directory to the _M_H program of your choice.  By
       giving this link a different name, you can  create  a  new
       entry in your profile and use an alternate set of defaults
       for the _M_H command.  Similarly, you could create  a  small
       shell  script  which  called the _M_H program of your choice
       with an alternate set of invocation line  switches  (using
       links and an alternate profile entry is preferable to this
       solution).

       Finally, the _c_s_h user could create an alias for  the  com-
       mand of the form:

            alias cmd 'cmd arg1 arg2 ...'

       In  this  way,  the  user can avoid lengthy type-in to the
       shell, and still give _M_H commands  safely.   (Recall  that
       some _M_H commands invoke others, and that in all cases, the
       profile is read,  meaning  that  aliases  are  disregarded
       beyond an initial command invocation)






















[mh.6]                        MH.6.8                            8