Hi Werner,
> > And .whilex? If we've a new .ifx, which I think is a bit clunky,
> > maybe we should bear in mind having a .elif and .else too that don't
> > need the .ifx to be .iex. (Or .elsif; Python use elif, Perl elsif.
> > elsif at least sounds like `else if'.)
>
> I could live with that.
> [...] maybe we should bear in mind having a .elif and .else
> too that don't need the .ifx to be .iex.
I don't think that's possible. Since the code can't look ahead,
it will not know whether an else is coming or not, so the "if"
has to know whether (.ie) or not (.if) to save the test outcome
On Sun, 16 Nov 2014 15:17:14 +0100
Tadziu Hoffmann wrote:
> > [...] maybe we should bear in mind having a .elif and .else
> > too that don't need the .ifx to be .iex.
>
> I don't think that's possible. Since the code can't look ahead,
> it will not know whether an else is coming or not, so the
On 11/14/14, Dale Snell wrote:
> I have in my personal Groff macros:
>
> .char \[:] \^:\|\: \&
>
> for an old-fasioned colon.
That doesn't seem to do what you would presumably want when the colon
ends a line:
.ps 36
.vs 36
.char \[:] \^:\|\:
x x x x x x x x x x x x x x\[:] x x x x x x x x x
On 11/15/14, Werner LEMBERG wrote:
>> BTW--something I've never figured out is whether it's possible to
>> set up kern pairs in groff font files that have "space" as the first
>> element of the pair.
>
> This is not possible.
Is it worth adding as a feature request in the tracker? It would seem