From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: "nmake info" Windows patch (was: Your Emacs changes)
Date: Fri, 29 Aug 2003 13:20:21 +0200 [thread overview]
Message-ID: <3405-Fri29Aug2003132020+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3F4EFFDC.7000101@runestig.com> (peter@runestig.com)
> Date: Fri, 29 Aug 2003 09:25:16 +0200
> From: "Peter 'Luna' Runestig" <peter@runestig.com>
>
> All this Windows-incompatible stuff in the new makefiles I created, is
> related to building DVI files, not INFO files. So, how should I do this:
> rip out all non-INFO related stuff, or also make DVI building work (if I
> can find a Windows port of texi2dvi...)?
Are you saying that you don't really care about the parts that produce
Info files, only about the DVI stuff? I'd say that Windows users
should be able to produce the on-line Info manuals as well, but if you
cannot work on that, I guess they won't be able to do that.
In any case, IMHO, fix those parts of the Makefile's that you can, and
leave the rest unmodified, don't remove them. Someone else will then
hopefully pick up where you left off. A comment in the Makefile's to
the effect that only some of the targets work reliably would be a good
idea.
> >> On a side note, NTFS does support hard links (AFAIK there's no native
> >> tool for it though, but Cygwin's "ln" works).
> >
> > I knew that, but since native Windows programs don't support links,
> > their presence in NTFS is currently useless unless one works in a
> > Cygwin environment.
>
> As long as you have a "ln" tool, which doesn't need to come from Cygwin,
> they are still quite useful.
What other packages besides Cygwin offer a port of `ln'?
next prev parent reply other threads:[~2003-08-29 11:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 16:04 Your Emacs changes Richard Stallman
2003-08-18 15:21 ` Peter 'Luna' Runestig
2003-08-19 7:51 ` Eli Zaretskii
2003-08-19 7:36 ` Jason Rumney
2003-08-19 17:32 ` Eli Zaretskii
2003-08-22 9:58 ` Jason Rumney
2003-08-22 11:13 ` Peter 'Luna' Runestig
2003-08-19 7:59 ` Peter 'Luna' Runestig
2003-08-19 17:46 ` Eli Zaretskii
2003-08-21 7:45 ` Jason Rumney
2003-08-21 7:59 ` Jason Rumney
2003-08-29 7:25 ` "nmake info" Windows patch (was: Your Emacs changes) Peter 'Luna' Runestig
2003-08-29 11:20 ` Eli Zaretskii [this message]
2003-08-29 11:35 ` "nmake info" Windows patch Peter 'Luna' Runestig
2003-08-29 15:11 ` Eli Zaretskii
2003-08-30 3:10 ` Richard Stallman
2003-08-29 11:40 ` "nmake info" Windows patch (was: Your Emacs changes) Dhruva Krishnamurthy
2003-08-29 11:46 ` Dhruva Krishnamurthy
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3405-Fri29Aug2003132020+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).