From: "Peter 'Luna' Runestig" <peter@runestig.com>
Cc: emacs-devel@gnu.org
Subject: Re: "nmake info" Windows patch
Date: Fri, 29 Aug 2003 13:35:40 +0200 [thread overview]
Message-ID: <3F4F3A8C.6090202@runestig.com> (raw)
In-Reply-To: <3405-Fri29Aug2003132020+0300-eliz@elta.co.il>
On 2003-08-29 13:20, Eli Zaretskii wrote:
>> 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.
No, I'm saying the opposite. I started out, offering a patch that adds
"info" as a useable make target to the Windows port, for the first time
pretty precise a year ago. I recently posted it again when my copyright
assignment paper to FSF was cleared. Then comments were made on stuff in
the new makefiles I introduced, that didn't work on the Windows
platform. All those comments were about targets in the makefiles, that
wasn't used by the "info" targets, but were left in there by me anyway
(I used the unix makefile.in's as templates). So I'm now wondering, what
you guys want me to do about it, so this patch can go into the sources.
All I want is a working "info" make target.
>> > 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'?
No idea, I just don't agree on that the NTFS support for hard link is
"useless".
Cheers,
- Peter
--
Peter 'Luna' Runestig (fd. Altberg), Sweden <peter@runestig.com>
PGP Key ID: 0xD07BBE13
Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13
AOL Instant Messenger Screen name: PRunestig
Yahoo! Messenger profile name: altberg
next prev parent reply other threads:[~2003-08-29 11:35 UTC|newest]
Thread overview: 34+ 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
2003-08-29 11:35 ` Peter 'Luna' Runestig [this message]
2003-08-29 15:11 ` "nmake info" Windows patch 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
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 11:28 "nmake info" Windows patch Peter 'Luna' Runestig
2003-02-21 21:54 Peter 'Luna' Runestig
2003-02-21 23:14 ` Peter 'Luna' Runestig
2003-02-22 9:21 ` Eli Zaretskii
2003-02-22 9:53 ` Peter 'Luna' Runestig
2003-02-22 11:40 ` Juanma Barranquero
2003-02-22 19:08 ` Eli Zaretskii
2003-05-20 9:08 ` Peter 'Luna' Runestig
2003-05-20 11:14 ` Jason Rumney
2003-05-20 13:10 ` Juanma Barranquero
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:46 ` Jason Rumney
2003-02-22 10:13 ` Jason Rumney
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:44 ` Jason Rumney
2002-09-03 7:42 Peter 'Luna' Runestig
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=3F4F3A8C.6090202@runestig.com \
--to=peter@runestig.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.