On 29-Dec-09 00:39:11, Werner LEMBERG wrote:
>> The following draws a pretty picture, which I send you
>> with all my best wishes, hoping you had a good Christmas
>> and will have a good New Year.
>
> Nice! I wish everybody the same.
>
> A small caution: Everyone who wants to try Ted's code shou
On 29/12/09 20:15:42, ted.hard...@manchester.ac.uk wrote:
> > A small caution: Everyone who wants to try Ted's
> > code should strip trailing whitespaces.
> Sorry for the trailing spaces! They were not in the
> original, and must have been introduced when I pasted
> from the source file into the em
Hello Ted and all,
Werner LEMBERG wrote on 29.12.09:
>
> > The following draws a pretty picture, which I send you with all my best
> > wishes, hoping you had a good Christmas and will have a good New Year.
>
> Nice! I wish everybody the same.
>
> A small caution: Everyone who wants to try Ted'
Chuck Robey wrote:
> ... I was
> stating that I have no problem whatsoever with the mm macros when they're
> going
> to postscript or ascii, but when I have them as html output, the mm list
> macros
> show up very, very, badly. It looks like there isn't any leading spacing
> allowed after I u
Jan-Herbert Damm wrote:
> I removed trailing whitespace saved as "picture" and processed simply with
> groff picture > picture.ps
>
> it shows some text and some ellipsises, probably not what is intended.
>
> Sorry for this ignorant novice question:
> How do I invoke groff correctly for this
> I removed trailing whitespace saved as "picture" and processed
> simply with
>
> groff picture > picture.ps
>
> it shows some text and some ellipsises, probably not what is
> intended.
>
> Sorry for this ignorant novice question: How do I invoke groff
> correctly for this?
Add the -p command lin
Thanks to both of you, now i see: it *is* beautiful!
Werner LEMBERG wrote on 29.12.09:
> BTW, the necessary command line options for groff for
> file `foo' can be guessed with the `grog foo' command.
oh, good! it did show me the correct command.
jan
Miklos Somogyi wrote:
>
> My bible is a well-worn photocopy of "Using nroff & troff" from 1990.
> I wish that a pdf of it would float around somewhere to download and
> search ...
I'm forever interested in new sources of roff info ... so could you please
amplify on that reference? I mean, exact
Meg McRoberts wrote:
> I just checked and Amazon has 9 used copies available, two for
> less that $10:
>
> http://www.amazon.com/gp/offer-listing/0810462915/ref=dp_olp_used?ie=UTF8&condition=used
>
> Six are available at half.com:
>
> http://product.half.ebay.com/Unix-Text-Processing_W0QQtgZinfo
Larry Kollar wrote:
> Chuck, did you see my response on 9 Dec?
> http://lists.gnu.org/archive/html/groff/2009-12/msg8.html
>
> One way or another, you have to get an HTML list wrapper to appear in the
> output, that should give you the break you need.
No, I hadn't seen that, it occurred (ap
On 29-Dec-09 16:27:32, Jan-Herbert Damm wrote:
> Thanks to both of you, now i see: it *is* beautiful!
>
> Werner LEMBERG wrote on 29.12.09:
>> BTW, the necessary command line options for groff for
>> file `foo' can be guessed with the `grog foo' command.
> oh, good! it did show me the correct comm
I need to have (for an html project of mine, which you all know about by now) a
stack data structure. I know one *really* klugy way to do it, by having a
number register which counts the depth of my stack, and then having a variable
which is concatenated to form a name like "name0", "name1", etc,
> I need to have [snip] a stack data structure.
Here's a very rudimentary implementation using strings -- items
on the stack cannot contain spaces, and no error checking is
performed, but you get the idea. If necessary, the macros
can be generalized to accept the name of the stack string as
argu
Tadziu Hoffmann wrote:
>> I need to have [snip] a stack data structure.
>
> Here's a very rudimentary implementation using strings -- items
> on the stack cannot contain spaces, and no error checking is
> performed, but you get the idea. If necessary, the macros
> can be generalized to accept the
> [...] Second, he tells me that his opinion is that instead of me
> worrying about trying to repair his macros (which was my first
> impulse, to fix them, and then add calls to them in a little adapter
> macro package), I should instead try to see if I can fit my fixes
> all directly into the mm
> I need to have (for an html project of mine, which you all know
> about by now) a stack data structure. I know one *really* klugy way
> to do it, by having a number register which counts the depth of my
> stack, and then having a variable which is concatenated to form a
> name like "name0", "nam
16 matches
Mail list logo
