Am Freitag 03 August 2007 01:41:24 schrieb andlabs:
> Why do you need it in a circle when you can just use the ms .IP or mm's
> built-in numbering along with a normal number?
I used the numbers in a circle in a screenshot to highlight some points. I
thought, using the same numbers in circles in t
I use Cygwin on a PC running Windows 98. It has groff version
1.18.1.
Does anyone have a clue about when Cygwin will update
to the 1.19 version?
Clarke
Werner LEMBERG wrote:
This has been fixed 4½ years ago (starting with 1.19). The incorrect
metric files (this is, adding negative left and
> I'm trying to overcome an eqn "phenomenon" -- in some ways a
> "feature", in others a "bug".
It's a bug. However...
> You will see that the "=" signs do not line up.
This has been fixed 4½ years ago (starting with 1.19). The incorrect
metric files (this is, adding negative left and right ita
> OK, I figured it out - it was the wrapper for another of the macros
> that overwrote ms.
To find such problems easier, get the CVS and say:
groff -mtrace -ms foo > foo.ps 2> foo.log
It sometimes fails under some circumstances, but for `standard' macros
it works quite well.
Werner
OK, I figured it out - it was the wrapper for another of the macros that
overwrote ms.
andlabs wrote:
>
> Actually, it turns out this isn't the error. :-( Weird. I'll figure it out
> soon.
>
>
> andlabs wrote:
>>
>> Great, thanks. Then that isn't the source of my problem:
>>
>> x.troff:11:
Actually, it turns out this isn't the error. :-( Weird. I'll figure it out
soon.
andlabs wrote:
>
> Great, thanks. Then that isn't the source of my problem:
>
> x.troff:11: fatal error: input stack limit exceeded (probable infinite
> loop)
>
> But I just figured it out: ms requires .TL before
Great, thanks. Then that isn't the source of my problem:
x.troff:11: fatal error: input stack limit exceeded (probable infinite loop)
But I just figured it out: ms requires .TL before anything else (and after
.RP). The way I have the code starts with something that is not .TL. And
thus, the abov
On Thu, 2007-08-02 at 16:44 -0700, andlabs wrote:
> Hello. I'm working with code that amends to ms' PP. The code uses a number
> register 1t - that is the number 1 followed by lowercase t. First, is such
> an identifier legal in groff? Second, what happens if a register is not
> defined with .nr an
Hello. I'm working with code that amends to ms' PP. The code uses a number
register 1t - that is the number 1 followed by lowercase t. First, is such
an identifier legal in groff? Second, what happens if a register is not
defined with .nr and used with \n(xx - would it be 0 or would it be an
error
Why do you need it in a circle when you can just use the ms .IP or mm's
built-in numbering along with a normal number?
If you can't work with the above, then get ready, because either you need
graphics commands and absolute placement - which are both HARD (especially
absolute placement).
Ruedig
On 02-Aug-07 08:26:39, Ted Harding wrote:
> On 01-Aug-07 22:35:29, Ralph Corderoy wrote:
>> [...]
>> Hmm, don't know about that. I did however have a look at eqn's
>> output and I think it's the \, that's causing the effect.
>>
>> $ cat ted.tr
>> .nr DD 0
>> .EQ I
>> 21 ~~=~~ 3 ti
On 01-Aug-07 22:35:29, Ralph Corderoy wrote:
>
> Hi Ted,
>
>> What I'm referring to can be seen if you set the following in Times,
>> using a fairly large point size (say 15) (I'm using ms macros here):
>>
>> .nr DD 0
>> .EQ I
>> 21 ~~=~~ 3 times 7
>> .EN
>> .EQ I
>> 22 ~~=~~ 2 times 11
>> .EN
>
12 matches
Mail list logo
