Try using manedit, it's quite friendly :) gtk/gnome, multi-windowed stuff.
http://wolfpack.twu.net/ManEdit/
but you better check the syntax of your manpages after !
i used it to create a manpage for my package.
it would be great to have this software in debian too :))
(i dont use it much, i don't
Try using manedit, it's quite friendly :) gtk/gnome, multi-windowed stuff.
http://wolfpack.twu.net/ManEdit/
but you better check the syntax of your manpages after !
i used it to create a manpage for my package.
it would be great to have this software in debian too :))
(i dont use it much,
Othmar Pasteka [EMAIL PROTECTED] cum veritate scripsit:
Hmm... anyone going to package manedit ?
I tried it. It was rather fun to play with. It edits in roff.
Should I upload it ?
regards,
junichi
--
[EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
-BEGIN GEEK CODE BLOCK-
On Sat, May 12, 2001 at 01:27:04AM +0900, Junichi Uekawa wrote:
Othmar Pasteka [EMAIL PROTECTED] cum veritate scripsit:
Hmm... anyone going to package manedit ?
I tried it. It was rather fun to play with. It edits in roff.
Should I upload it ?
IIRC, [EMAIL PROTECTED] is maintainer for
Othmar Pasteka [EMAIL PROTECTED] cum veritate scripsit:
Hmm... anyone going to package manedit ?
I tried it. It was rather fun to play with. It edits in roff.
Should I upload it ?
regards,
junichi
--
[EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
-BEGIN GEEK CODE BLOCK-
When you use debmake (the first thing you run on the clean source dir, if
I'm not mistaken), it will create the debian directory. Check in there for
a manpage.1.ex file that serves as a good template for the process.
~Warren
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
I usually just edit one directly (in roff).
I'm pretty sure dh_make installs a sample. If it doesn't, look
at /usr/share/debhelper/dh_make/debian/manpage.1.ex
There's
Eduardo Trapani [EMAIL PROTECTED] writes:
The software I am packaging does not have a man page.
What programs should I use to create one?
Try using help2man to get a good template, and edit it by hand.
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
hi,
On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote:
What programs should I use to create one?
the normal groff and the an macro (on the commandline that's the
-man ;)) ... read the manpage howto as a start and also read man
7 man ...
so long
Othmar
--
To UNSUBSCRIBE,
En réponse à Eduardo Trapani [EMAIL PROTECTED]:
The software I am packaging does not have a man page.
What programs should I use to create one?
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see
hi,
On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote:
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see http://qa.debian.org/man-pages.html for pointers to documentations).
haven't dealt
Y el jueves 10 de mayo, Eduardo Trapani escribió:
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
My suggestion:
Use perldoc, you will write a txt file like this and you will get a
pretty manpage with only one command:
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
When you use debmake (the first thing you run on the clean source dir, if
I'm not mistaken), it will create the debian directory. Check in there for
a manpage.1.ex file that serves as a good template for the process.
~Warren
On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
the best, but definitely not the easiest one, is to just get an example page
and edit it by hand. there are programs like manedit
Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
I usually just edit one directly (in roff).
I'm pretty sure dh_make installs a sample. If it doesn't, look
at /usr/share/debhelper/dh_make/debian/manpage.1.ex
There's
Eduardo Trapani [EMAIL PROTECTED] writes:
The software I am packaging does not have a man page.
What programs should I use to create one?
Try using help2man to get a good template, and edit it by hand.
Falk
En réponse à Eduardo Trapani [EMAIL PROTECTED]:
The software I am packaging does not have a man page.
What programs should I use to create one?
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see
hi,
On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote:
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see http://qa.debian.org/man-pages.html for pointers to documentations).
haven't dealt
Y el jueves 10 de mayo, Eduardo Trapani escribió:
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
My suggestion:
Use perldoc, you will write a txt file like this and you will get a
pretty manpage with only one command:
On Thu, Dec 14, 2000 at 01:45:25PM +1100, Drew Parsons wrote:
It's still writing drew into the Followup-To header. I'll try unsetting
the mutt variable this time.
Try:
set nofollowup_to
I think this might be buggy, in that it's prolly never correct to send a
'MFT: UserWithNoMailDomain' .
hi,
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
What's the "best" way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess
* "Drew" == Drew Parsons [EMAIL PROTECTED] wrote:
Drew What's the "best" way of maintaining or creating a man page?
I create a perl pod file and translate it to to a man page. The syntax
is very easy, so I prefer this. See perldoc perlpod and the equivs
package for an example.
Ciao,
On Wed, Dec 13, 2000 at 10:24:01AM +1100, Drew Parsons wrote:
If you don't want to do SGML, you could always edit the nroff source directly.
This is what has been done historically.
I wouldn't necessarily mind using SGML, but which tools exactly do you use.
For creating man pages I mean
* Drew Parsons
| I wouldn't necessarily mind using SGML, but which tools exactly do you use.
I use emacs with psgml.
| For creating man pages I mean. How do you generate them from SGML?
docbook-to-man is what I use.
--
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about
On Thu, Dec 14, 2000 at 12:34:33PM +1100, Drew Parsons wrote:
As for the Mail-Followup-To being set to just "drew", that's a mutt problem,
isn't it? Setting the "followup-to" variable? I'll try changing it right
now. It might take some experimenting. It looks as though mutt is putting
On Thu, Dec 14, 2000 at 12:34:33PM +1100, Drew Parsons wrote:
[snip about man page editing]
sounds good.
As for the Mail-Followup-To being set to just "drew", that's a mutt
problem, isn't it? Setting the "followup-to" variable? I'll try
changing it right now. It might take some
On Thu, Dec 14, 2000 at 02:17:30PM +1100, Drew Parsons wrote:
On Wed, Dec 13, 2000 at 09:51:11PM -0500, Josh Huber wrote:
The problems with the sender are most likely fixable by
set envelope_from=yes
which calls /usr/sbin/sendmail with -f to set the Sender: field based
on your
On Thu, Dec 14, 2000 at 03:26:46PM +1100, Drew Parsons wrote:
It still doesn't seem to have affected the Sender header though, which
persistently has this gandi.net reference. Reading through the exim docs,
it says the -f option can only be used properly by a "trusted user". I'll
try
necessarily mind using SGML, but which tools exactly do you use.
For creating man pages I mean. How do you generate them from SGML?
As for editing nroff source, that's what I meant with my first question. Is
there no editor for this sort of thing? For handling all the fiddly things
like section breaks
hi,
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
What's the best way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is
On Wed, 13 Dec 2000, Othmar Pasteka wrote:
What's the best way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is there's a simple
Hi,
On Wed, Dec 13, 2000 at 09:35:09AM +0100, Adrian Bunk wrote:
If you are are writing nroff I'd suggest using gmanedit:
well, vi{,m}/emacs/any other editor is also good enough for it
:). depends what you like.
so long
Othmar
Drew Parsons wrote:
As for editing nroff source, that's what I meant with my first question. Is
there no editor for this sort of thing? For handling all the fiddly things
like section breaks and bold text, etc, so I don't have to learn nroff itself.
If you use dh_make, the manpage example
* Drew == Drew Parsons [EMAIL PROTECTED] wrote:
Drew What's the best way of maintaining or creating a man page?
I create a perl pod file and translate it to to a man page. The syntax
is very easy, so I prefer this. See perldoc perlpod and the equivs
package for an example.
Ciao,
Martin
On Wed, Dec 13, 2000 at 10:24:01AM +1100, Drew Parsons wrote:
If you don't want to do SGML, you could always edit the nroff source
directly.
This is what has been done historically.
I wouldn't necessarily mind using SGML, but which tools exactly do you use.
For creating man pages I mean
* Drew Parsons
| I wouldn't necessarily mind using SGML, but which tools exactly do you use.
I use emacs with psgml.
| For creating man pages I mean. How do you generate them from SGML?
docbook-to-man is what I use.
--
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about
On Wed, Dec 13, 2000 at 10:24:01AM +1100, Drew Parsons wrote:
I wouldn't necessarily mind using SGML, but which tools exactly do you use.
For creating man pages I mean. How do you generate them from SGML?
I use emacs/psgml to edit, and the docbook-to-man package to generate nroff
Summarising what people have said, seems to me the easiest thing for
occasional tweaking of existing man pages is to use a text editor, with
guidance from the HOW-TO, man 7 man and example man pages. The gui editor
gmanedit may be helpful too, I'll have a look at that when X4 gets working.
For
On Thu, Dec 14, 2000 at 12:34:33PM +1100, Drew Parsons wrote:
As for the Mail-Followup-To being set to just drew, that's a mutt problem,
isn't it? Setting the followup-to variable? I'll try changing it right
now. It might take some experimenting. It looks as though mutt is putting
both me
On Thu, Dec 14, 2000 at 12:34:33PM +1100, Drew Parsons wrote:
[snip about man page editing]
sounds good.
As for the Mail-Followup-To being set to just drew, that's a mutt
problem, isn't it? Setting the followup-to variable? I'll try
changing it right now. It might take some experimenting.
On Wed, Dec 13, 2000 at 09:51:11PM -0500, Josh Huber wrote:
The problems with the sender are most likely fixable by
set envelope_from=yes
which calls /usr/sbin/sendmail with -f to set the Sender: field based
on your From: field.
make sure you set your from field properly though:
On Thu, Dec 14, 2000 at 02:17:30PM +1100, Drew Parsons wrote:
On Wed, Dec 13, 2000 at 09:51:11PM -0500, Josh Huber wrote:
The problems with the sender are most likely fixable by
set envelope_from=yes
which calls /usr/sbin/sendmail with -f to set the Sender: field based
on your
On Thu, Dec 14, 2000 at 03:26:46PM +1100, Drew Parsons wrote:
It still doesn't seem to have affected the Sender header though, which
persistently has this gandi.net reference. Reading through the exim docs,
it says the -f option can only be used properly by a trusted user. I'll
try making
What's the "best" way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is there's a simple manpage editor out there, or a
sensible emacs
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
What's the "best" way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess
What's the best way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is there's a simple manpage editor out there, or a
sensible emacs mode,
On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote:
What's the best way of maintaining or creating a man page?
I'll be needing to do that with some of my packages, but it just occurred to
me I don't actually know how, apart from cutting and pasting in a text
editor. My guess is
On Thu, Jun 17, 1999 at 11:44:22PM +0100, John Travers wrote:
Is there a way to make manpages or texinfo files from .dvi or .tex files?
From .dvi? No. You're asking for a decompiler.
From .tex? Possibly, but only manually. The process cannot be automated
easily: it requires too much
49 matches
Mail list logo
