Ken Hornstein writes:
>
>>By the way, it would be nice if man mhparam listed the parameters it took.
>
>I think it does? It sure looks like it does when I run "man mhparam". Or do
>you mean something else?
I apologize.
I should have read the man page much more carefully before
Ralph Corderoy wrote:
|I wrote:
|> EXIT STATUS
|> mhparam returns the number of components that were not found.
|...
|> $ mhparam `yes | sed 256q`; echo $?
|> 0
|
|I've just pushed to git.
|
|
Hi,
I wrote:
> EXIT STATUS
> mhparam returns the number of components that were not found.
...
> $ mhparam `yes | sed 256q`; echo $?
> 0
I've just pushed to git.
http://git.savannah.nongnu.org/cgit/nmh.git/commit/?id=e8eb3afba50cbec8d1aeabcf85a06084977d54cd
Limit
Paul F wrote:
> oh: it looks like "mhparam -all -debug" might give everything.
This is kinda interesting. -debug is currently ignored with -all.
It wasn't before commit 234c9cc4, which replaced a badly formatted
conditional statement with an else branch. Instead, it could be
changed to be two
Date:Fri, 17 Feb 2017 15:49:41 -0500
From:Ken Hornstein
Message-ID: <20170217204942.1eddb6a...@pb-smtp2.pobox.com>
| And mhparam(1) has a SEE ALSO that points to mh-profile(5).
Unless it has been changed in a version more recent than I am running,
>But what could be done is to find all the places where the nmh code looks for
>a profile entry (perhaps ignoring any that are pure debug, or expert use only),
>and make sure all of those are documented.
AFAIK, we've documented them all in mh-profile(5) (I'll double-check
to make sure we've got
Date:Fri, 17 Feb 2017 12:01:00 -0500
From:Ken Hornstein
Message-ID: <20170217170102.97c0f66...@pb-smtp1.pobox.com>
| That's the same one I have. But ... essentially, the possible profile
| entries are unlimited, because you could create a
>>I think it does? It sure looks like it does when I run "man mhparam".
>
>I doesn't seem to when I run it. I must be somehow muddled. I am
>attaching a copy /usr/local/nmh-1.6/share/man/man1/mhparam.1 .
That's the same one I have. But ... essentially, the possible profile
entries are
Ken Hornstein writes:
>>What is the best way to determine my drafts folder, from within
>>norms-cool-editor? Is the only way to read $MH (or ~/.mh_profile), looking
>>for the first line starting with "Draft-Folder:" ?
>>
>>Will mhparam do it? If so, with what argument?
>
>Yup!
Hi Ken,
> % mhparam draft-folder
> Does exactly that.
And exits 1 if that isn't set.
> > By the way, it would be nice if man mhparam listed the parameters it
> > took.
>
> I think it does? It sure looks like it does when I run "man mhparam".
> Or do you mean something else?
Perhaps Norm means
ken wrote:
> >What is the best way to determine my drafts folder, from within
> >norms-cool-editor? Is the only way to read $MH (or ~/.mh_profile), looking
> >for
> >the first line starting with "Draft-Folder:" ?
> >
> >Will mhparam do it? If so, with what argument?
>
> Yup! Looks like:
>What is the best way to determine my drafts folder, from within
>norms-cool-editor? Is the only way to read $MH (or ~/.mh_profile), looking for
>the first line starting with "Draft-Folder:" ?
>
>Will mhparam do it? If so, with what argument?
Yup! Looks like:
% mhparam draft-folder
Does
What is the best way to determine my drafts folder, from within
norms-cool-editor? Is the only way to read $MH (or ~/.mh_profile), looking for
the first line starting with "Draft-Folder:" ?
Will mhparam do it? If so, with what argument?
By the way, it would be nice if man mhparam listed the
13 matches
Mail list logo