From: Christian Jönsson FOA 72 <chj@lin.foa.se>
To: egcs@egcs.cygnus.com
Subject: About makeinfo under WIN32
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <199903150746.IAA23730@arnljot.lin.foa.se> (raw)
Message-ID: <19990331234600.Yxa_x6qUKETXk4Urlz-pejbq0yFzarayMq-LjxKlUSw@z> (raw)
Hello all!
Perhaps this is not the correct place to send comments like this, but I do it
anyway and if someone thinks I shouldn't, please let me know. I'm not sure if
the makeinfo part is built under win32 environments. If it isn't, and we would
like to see it, perhaps someone could look at the work available with xemacs
for NT.
OK, I should perhaps take it on myself, but you know... Anyway, I wanted to
mention this possibility. Hopefully it's usable and someone's got the time...
This was also fed, by the original e-mailer, to the texinfo-bugs mail list.
Is the egcs dev tree following the texinfo/makeinfo development? Are there
``snapshots'' available of texinfo/makeinfo? If so, to what ``audience''?
/ChJ
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 23:46 Christian Jönsson FOA 72 [this message]
1999-03-31 23:46 ` Christian Jönsson FOA 72
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199903150746.IAA23730@arnljot.lin.foa.se \
--to=chj@lin.foa.se \
--cc=egcs@egcs.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).