Re: [Nmh-workers] Feature Request: Comments in $HOME/.mh_profile

2012-04-25 Thread Christer Boräng
In message 20120424214609.68b674c...@db.pthbb.org, Jerrad Pierce writes: Maybe we should simply reserve # as a profile component and document #: as the .mh_profile comment character(s) rather than leave it as a puzzle. Makes sense to me. If documenting, point out that you cannot have blank lines,

Re: [Nmh-workers] Feature Request: Comments in $HOME/.mh_profile

2012-04-24 Thread Ken Hornstein
I and at least one other user -- and probably many others, have .mh_profile entries that we added years ago, for reasons now obscure and not remembered. There ought to be an easy way to incorporate comments in that file. As I read the man page, there is none provided. Yeah let me speak on

Re: [Nmh-workers] Feature Request: Comments in $HOME/.mh_profile

2012-04-24 Thread Jerrad Pierce
My long standing work around for this, is to use the profile entry # As in #:# #: System wide variables Aliasfile: aliases Draft-Folder: drafts editor: emacs #:# #: Program defaults ... Works like a charm ___ Nmh-workers mailing list

Re: [Nmh-workers] Feature Request: Comments in $HOME/.mh_profile

2012-04-24 Thread Bill Wohler
Me too: #: Variable Settings ... Maybe we should simply reserve # as a profile component and document #: as the .mh_profile comment character(s) rather than leave it as a puzzle. Earl Hood e...@earlhood.com writes: On Tue, Apr 24, 2012 at 11:23 AM, norm wrote: I and at least one other

Re: [Nmh-workers] Feature Request: Comments in $HOME/.mh_profile

2012-04-24 Thread Jerrad Pierce
Maybe we should simply reserve # as a profile component and document #: as the .mh_profile comment character(s) rather than leave it as a puzzle. Makes sense to me. If documenting, point out that you cannot have blank lines, hence my use of #:# To separate blocks, although if someone were so