Hello,
the link
http://plan9.bell-labs.com/sys/doc/troff.html
on the web site
http://plan9.bell-labs.com/wiki/plan9/Using_troff/index.html
does not work. There is a lot of information about troff but I am interested
in special plan9 troff extensions.
Is there someone maintaining pla
> I've just generated the html version on http://9grid.fr/sys/doc/troff.html
> and there are indeed some issues.
Thank you!
If I'am able to reproduce a major issue should I report to the list? Or to you?
Or is there currently no maintenance of plan9 troff?
--Carsten
> > If I'am able to reproduce a major issue should I report to the list? Or to
> you? Or is there currently no maintenance of plan9 troff?
>
> Sending bug reports to 9fans should be fine.
There seems to be a first bug in the manual ;)
On page 24 section 12.4. "Line drawing" there is underlining
> Please correct me if I'm wrong, but I don't think there's
> any bug here :
>
> The .ul internal command draw an underline when possible,
> and use italics when it's not possible. For example, on a
> terminal without underlining capabilities, italics are used.
>
> .us is just an example of an ha
> Please remember that the document applies to both nroff and troff.
> For nroff (terminals, printers), .ul does underlining. For typesetters
> (includes laser printers) troff .ul does italics. The .us macro shows
> how to get real underlining on a typesetter device.
Please read that paragraph car
Hello,
does someone know why the TAB token case is commented out in the eqn(1) lexer?
I wonder why tab alignment of equations doesn't work, then I found the comment
in lex.c. E.g. solaris troff has exactly the same lex.c (with few changes),
but there the line is not commented.
Did someone wo
Hello,
I'm somewhat disappointed about the troff software in Plan9.
I did few initial tests with eqn(1) and in addition to the TAB problem I saw
that the root sign line and large brackets are not aligned. The attached file
shows these problems. It can be processed to PostScript with
eqn eqn.tr
> It is a shame if there are bugs in eqn - tbl has one or two also
> but the source is there and it is all fixable. You could submit a patch.
I'm working on it. But not just eqn--on a DWB port in general (to current
UNIX versions). So it may take some time but I'll work on a fix.
Is there a pla
> first, I don't understand German (I am Czech), but I used google translate,
> hopefully getting the meaning.
Sorry for that!
> Second, it's generally better (unless it's really personal or highly
> technical)
> to keep the discussion within the mailing list, since then other people
> can also c
> >> http://9fans.net/archive/?q=sykora+eqn&go=Grep
> >
> > I can't believe that TeX should not produce better results, but
> > thats really OT...
>
> I don't understand what you mean.
I refer to http://9fans.net/archive/2011/12/113. I would expect
TeX to produce the best math results. But this
> Does anyone know if there has been any effort to use TeX and al. for the
> system typesetting i.e. the manpages and docs? (Translation of the troff
> macros to TeX ones etc.---not to mention that for TeX (kerTeX), it needs
> to be converted for utf-8 input; that's on my TODO list but I need to
>
> Still I don't get what you mean. In that message we say
> 1) quality of TeX typesetting is better,
> 2) the way the equation is written (the syntax) in eqn feels
> better to me.
Ok, I got that wrong.
> Just to be sure. I don't mean readability of documents to be typeset.
> I mean the source cod
> I still use troff and tbl on plan9, occasionally I use eqn, last week
> for the first time in ages.
What are the bugs in tbl you found? (I think it had been you who mentioned
it.)
> I know there are some bugs but I find it much easier to generate a simple
> document in troff than with MS Word,
> Mmm, I was worried you might ask that.
:-)
> I will dig through my venti and see if I can find an old copy
> which exhibits the problem...
Ok. If possible the lines between .TS/.TE to reproduce it (you may change the
text if its confidential).
--Carsten
Hello,
in bio.h there is a
struct Biobuf
{
Biobufhdr;
uchar b[Bungetsize+Bsize];
};
where Biobufhdr is declared as
typedef struct Biobufhdr Biobufhdr;
To make it compile with gcc under UNIX I changed the struct to
struct Biobuf
{
Biobufhdr Biobufhdr;
> Otherwise, your change is fine, but "hdr" would probably be
> a better name than "Biobufhdr". Also, don't forget to update
> your code to use b->hdr.fid instead of b->fid, and so on.
Thanks for all answers!
(They also helped to find a short documentation in /sys/doc/compiler)
Carsten
Hello,
in sys/src/cmd/eqn/text.c a function definition starts with
int
trans(int c, char *)
{
What does that mean (i.e. how is the second function parameter referenced?
Carsten
> int
> trans(int c, char *)
> {
That parameter seems not to be used inside. That may answer the question...
Carsten
Hello,
is there no neqn on Plan9?
Carsten
Hello,
where is the type field of libc struct Dir documented? In source I found a
compare of field type with the char 'M'. Where can I loop up what 'M' means?
Carsten
> On 19 October 2014 16:36, Charles Forsyth
> wrote:
>
> What I really meant was that few programs care about Dir.type since most
> don't care what serves the names
> as long as they behave as expected. Relatively few programs use the # names
> directly in bind(2) calls:
> it's more common to set
Russ Cox wrote:
> i have moved the plan9port sources from mercurial to git. the instructions
> [...]
Good thing!
Will pull requests be supported? Codereview didn't seem to work that
reliable...
Carsten
Russ Cox wrote:
> i have moved the plan9port sources from mercurial to git. the instructions
There had been two repositories, one on swtch and one on google. There had not
always been synchronized, that on google was more up-to-date. I don't know why
it had been necessary to have two reposit
23 matches
Mail list logo
