> > Don't sweat it; your English is better than that of many native
> > speakers.
>
> I was going to say as much myself, but you beat me to it Larry. Had
> this not been in published documentation, I probably wouldn't even
> have bothered to correct it, for the meaning is perfectly clear
> eith
On Saturday 04 October 2008 21:59:10 Larry Kollar wrote:
> Werner LEMBERG wrote:
> >> "With other words" is a direct translation of the German idiom.
> >> It seems stilted in English, where the idiomatically correct
> >> expression is "In other words".
> >
> > Aah, I wasn't aware of this, thanks!
> I've (mostly) gotten it to work (I think) with the following package
> switcher, to be used instead of andoc.tmac.
An extended and cleaned-up version is now in the CVS. Thanks a lot
for this contribution, and please test.
Werner
Werner LEMBERG wrote:
Is there a workaround I can use to force groff/soelim to read foo.ms
in the current directory?
I'm very sorry about this, it's a documentation error on my side --
I've never touched the logic of the related source code.
No problem, I realized after sending my report th
Werner LEMBERG wrote:
"With other words" is a direct translation of the German idiom. It
seems stilted in English, where the idiomatically correct expression
is "In other words".
Aah, I wasn't aware of this, thanks!
Don't sweat it; your English is better than that of many native
speakers
> "With other words" is a direct translation of the German idiom. It
> seems stilted in English, where the idiomatically correct expression
> is "In other words".
Aah, I wasn't aware of this, thanks!
Werner
On Saturday 04 October 2008 12:15:40 Werner LEMBERG wrote:
> > > What do you expect? Current reality is that troff bombs out
> > > with
> > >
> > > xxx:7: fatal error: input stack limit exceeded (probable
> > > infinite loop)
> >
> > I didn't expect this, and set out writing this email to say it
> So what you're saying is that if I have
>
> .als bar foo
>
> then
>
> .de bar
>
> will redefine the common object to which *both* "foo" and "bar"
> point (so "foo" will also see the new definition), but
>
> .rm bar
>
> will *not* remove the object, just the link (unless it's the only
So what you're saying is that if I have
.als bar foo
then
.de bar
will redefine the common object to which *both* "foo" and "bar"
point (so "foo" will also see the new definition), but
.rm bar
will *not* remove the object, just the link (unless it's the
only link to the object, in whic
> > 1. directories given with the -M command line option
> > 2. directories given in the GROFF_TMAC_PATH environment variable
> > 3. the current directory (only if in unsafe mode)
> > 4. the home directory
> > 5. a site-dependent directory, e.g. /usr/local/lib/groff/site-tmac
> > 6. a l
> > What do you expect? Current reality is that troff bombs out with
> >
> > xxx:7: fatal error: input stack limit exceeded (probable infinite loop)
>
> I didn't expect this, and set out writing this email to say it was
> wrong, but having thought about it, it's understandable.
Yeah. Here is
Hi Werner,
> look at this minimal example file `xxx':
>
> .de foo
> ..
> .als bar foo
> .de bar
> . foo
> ..
> .bar
>
> What do you expect? Current reality is that troff bombs out with
>
> xxx:7: fatal error: input stack limit exceeded (probable infinite loop)
I didn't expec
12 matches
Mail list logo
