Mikhael Goikhman <[EMAIL PROTECTED]> writes:
> On 01 Feb 2002 20:11:42 -0600, FVWM CVS wrote:
> >
> > Log message:
> > * fvwm-menu-xlock.1:
> > * fvwm-menu-headlines.1:
> > * fvwm-menu-directory.1:
> > * fvwm-menu-desktop.1: fvwmrc -> .fvwm2rc
>
> The first 3 man pages are autogenerated from perl scripts.
>
> Actually, fvwmrc was used intentionally to specify any fvwm config file,
> not just .fvwm2rc. Never mind.
I'd like to fix the mess I made, but I'm not clear on the process.
The instruction in fvwm-menu-xlock.in isn't it:
# pod2man -c "Fvwm Utility" fvwm-menu-xlock | nroff -man | less -e
The Changelog mentions the make target, _fvwm-menu-xlock.1 but that
doesn't work in the source or target directory.
The command:
pod2man -c "Fvwm Utility" fvwm-menu-xlock.in > fvwm-menu-xlock.1
in the source directory comes pretty close. We must be running different
versions of pod2man because my .IX records are at the end of
the file and a lot of stuff is indented differently.
> pod2man --version
Unknown option: version
/usr/bin/pod2man: Usage error!
usage: /usr/bin/pod2man [options] podpage
Options are:
--section=manext (default "1")
--release=relpatch (default "perl 5.005, patch 03")
--center=string (default "User Contributed Perl Documentation")
--date=string (default "3/Feb/2002")
--fixed=font (default "CW")
--official (default NOT)
--lax (default NOT)
I understand your point about a generic "fvwmrc" and I wouldn't have
changed this if we didn't get a comment about it being confusing.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED]
Piscataway, NJ 08854 Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
