Re: customization

[Bill W. <wo...@ne...>]

d.henman <dh...@gm...> wrote:

> This sounds like a nice way, though newies think of setq as setq, and we're
> telling them to learn all about "customize-set-variable"

On the contrary. MH-E newbies will never have to even edit .emacs.

> Newbies, are just as likely to be more taken aback from the
> customization ui than anything else....

I would disagree since the documentation is right there along with
possible settings (as in the case of mh-variant), cross-references to
related variables and manual sections, and grouped with related
variables to make it easier to explore. I'd think newbies would be more
taken aback with an empty .emacs file and expected to fill it with
something.

>                                         And those customizations have
> to be stored somewhere... another file somewhere????

By default they go in .emacs, although the location can be customized
too.

> timotheus <tim...@ts...> wrote:
> > (setq my-mh (if (file-exists-p "/usr/bin/mu-mh/inc")
> >                 'gnu
> >               'nmh))
> 
> I have never seen any reference to a "my-mh" variable.

That's because it is a local variable used below.

> > (when (eq my-mh 'gnu)
> >   (setq mh-variant "GNU Mailutils 1.1")
> >   (setq mh-path '("/usr/bin/mu-mh"))
> >   )
> > (when (eq my-mh 'nmh)
> >   (setq mh-variant "nmh 1.1")
> >   (setq mh-path '("/usr/bin" ))
> >   )

Note that folks precede their own variables with "my" or their initials
to avoid naming conflicts in the global namespace.

-- 
Bill Wohler <wo...@ne...>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD