From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: What's wrong with *roff, anyway? (Was: Um... what format are Cygwin manpages?)
Date: Thu, 10 Aug 2006 22:26:00 -0000 [thread overview]
Message-ID: <ebgbpd$ptp$1@sea.gmane.org> (raw)
In-Reply-To: <20060810213052.GB11554@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> On Thu, Aug 10, 2006 at 04:21:13PM -0500, mwoehlke wrote:
>> Christopher Faylor wrote:
>>> On Thu, Aug 10, 2006 at 03:41:12PM -0500, mwoehlke wrote:
>>>> Christopher Faylor wrote:
>>>>> On Thu, Aug 10, 2006 at 03:20:21PM -0500, mwoehlke wrote:
>>>>>> Anyway, if it turns out I have to patch an info file, then I guess I'm
>>>>>> stuck doing that. Assuming anyone on newlib pays attention to me. So
>>>>>> far, zilch.
>>>>> Yes, you definitely have to *patch* the *source* of the documentation
>>>>> that
>>>>> you want changed if you want someone to apply it.
>>>> I think the point is that I would hope they would accept a flat-out new
>>>> file, if it was that major a re-working (which IMO it should be; I find
>>>> the layout of glibc's manpage a lot easier to understand, in addition to
>>>> being more accurate).
>>>>
>>>> But... if I'm to do anything with the texinfo source, I have to *find*
>>>> it first. Sigh. I am losing enthusiasm for this project.
>>> Come on, mwoehlke, you know the drill by now. It isn't that hard to
>>> find the source and you don't get to choose your own method for
>>> providing patches. It's pretty standard to supply patches against
>>> source code.
>>>
>>> I imagine that the source code in question is in libc.info. The web site
>>> for newlib is http://sourceware.org/newlib/ .
>> I do. You misunderstood :-). (Then again, I didn't specify what I'd
>> done, did I? Shame on me :-).)
>>
>> What I meant to say was that I went and poked around the web CVS
>> interface at http://sourceware.org/cgi-bin/cvsweb.cgi/src/?cvsroot=src
>> and *still* couldn't find it. And... having gone and poked around
>> further, I think you meant "sprintf.def". Whew, for a while I was afraid
>> I was going to have to syn the whole *tree* and use 'find'. :-)
>>
>> Now... where is "sprintf.def"? :-)
>> (Don't worry, I'm still looking for it.)
>
> Actually, on some further digging it is, most likely, in sprintf.c
> So, no texinfo editing required.
Hey! Now I found that /all//by//myself/, thank you! ;-)
(See, I told you I'd keep looking.)
And... now I understand why the ->nroff converter works so poorly. Eek.
Do you really do the indentation and line length *by hand*, or am I
missing something?
--
Matthew
vIMprove your life! Now on version 7!
next prev parent reply other threads:[~2006-08-10 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ebd0om$gjh$1@sea.gmane.org>
[not found] ` <cb51e2e0608092159t14175e52jeb656ffd2cc123a1@mail.gmail.com>
[not found] ` <ebfiu4$4pn$1@sea.gmane.org>
[not found] ` <cb51e2e0608101108g41c88386wd7219aaead8ca396@mail.gmail.com>
[not found] ` <ebg4e5$39g$1@sea.gmane.org>
[not found] ` <20060810202721.GC935@trixie.casa.cgf.cx>
2006-08-10 20:45 ` Um... what format are Cygwin manpages? mwoehlke
2006-08-10 20:54 ` Christopher Faylor
2006-08-10 21:21 ` mwoehlke
2006-08-10 21:31 ` Christopher Faylor
2006-08-10 22:26 ` mwoehlke [this message]
2006-08-11 8:34 ` What's wrong with *roff, anyway? (Was: Um... what format are Cygwin manpages?) Corinna Vinschen
2006-08-11 15:30 ` mwoehlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ebgbpd$ptp$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).