Re: [Nmh-workers] relative message numbers?

2012-10-16 Thread Ralph Corderoy
Hi Jerrad, Commands which take a folder name (inc, refile, scan, sortm, ...) will accept the folder name in two formats: '+folder' and '@folder'. '+folder' specifies a folder underneath the Path defined in your nmh profile e.g; with the default '''Path: Mail''',

Re: [Nmh-workers] [PATCH] nmh.man: reorganize the command listing

2012-10-16 Thread Paul Fox
lyndon wrote: On 2012-10-15, at 7:10 PM, Paul Fox wrote: the alphabetical listing wasn't very user friendly. this grouping may make it easier to find related commands. (mh-chart also contains an alphabetical list.) mh-chart should stay as is. It's a concise list of

[Nmh-workers] Documenting @folder WAS Re: relative message numbers?

2012-10-16 Thread Jerrad Pierce
Is `scan +/tmp/foo' documented anywhere, i.e. the ability to treat any directory as a folder, not just one under Path? And `@..' after that.. Doh. Was planned but slipped my mind. Here are revised versions. 1) Insert into nmh.1 near: Commands which take a message number as an argument (

Re: [Nmh-workers] [PATCH] nmh.man: reorganize the command listing

2012-10-16 Thread Jerrad Pierce
For what it's worth, it make sense to me. The only draw back is that you cannot get an overview of it all in one screen. I might also suggest adding sub-headings for each action group. ___ Nmh-workers mailing list Nmh-workers@nongnu.org

Re: [Nmh-workers] [PATCH] nmh.man: reorganize the command listing

2012-10-16 Thread Lyndon Nerenberg
On 2012-10-16, at 10:59 AM, Paul Fox wrote: heh. i should be careful what i say. i was offering to do the bulk of the editing to nmh.1, if you could show me a few lines of how it should be done. i wasn't really offering to revamp all the nmh manpages. No, no, I meant changes to just

[Nmh-workers] man page change review

2012-10-16 Thread Lyndon Nerenberg
I just pushed a new nmh.7 man page. Along with Paul's content changes, it includes the troff source changes I am planning to make across the board. Specifically, I'm getting rid of the .RS/.RE/.fc/.ta hackery and replacing it with .TP tagged paragraphs. These changes also let me replace some

Re: [Nmh-workers] man page change review

2012-10-16 Thread Ken Hornstein
I just pushed a new nmh.7 man page. Along with Paul's content changes, it includes the troff source changes I am planning to make across the board. Specifically, I'm getting rid of the .RS/.RE/.fc/.ta hackery and replacing it with .TP tagged paragraphs. These changes also let me replace some of

Re: [Nmh-workers] man page change review

2012-10-16 Thread Anthony J. Bentley
Ken Hornstein writes: I just pushed a new nmh.7 man page. Along with Paul's content changes, it includes the troff source changes I am planning to make across the board. Specifically, I'm getting rid of the .RS/.RE/.fc/.ta hackery and replacing it with .TP tagged paragraphs. These changes

Re: [Nmh-workers] man page change review

2012-10-16 Thread Lyndon Nerenberg
On 2012-10-16, at 8:22 PM, Anthony J. Bentley wrote: Example: I understand that .B and \fB do the same thing, but why is the former preferred? I don't know if they do *exactly* the same thing. \fB says switch to the physical font named 'B' (as far as troff is concerned). .B says I want to

Re: [Nmh-workers] man page change review

2012-10-16 Thread Ken Hornstein
There is software out there (xman, for starters) that tries to interpret raw manpage source for its own purposes. These are not full-blown troff interpreters, so they can barf on text that uses low-level troff facilities. Wait, people still USE xman? :-) But nevertheless, thanks for your