From: "Richard M. Stallman" <rms@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: Is there any way to have a string literal that is read "raw"
Date: Mon, 11 Jul 2005 23:20:18 -0400 [thread overview]
Message-ID: <E1DsBJi-0003Mi-By@fencepost.gnu.org> (raw)
In-Reply-To: <ufyulm8cb.fsf@gnu.org> (message from Eli Zaretskii on Mon, 11 Jul 2005 22:49:24 +0300)
> If a program would run only on Windows, we recommend that people not
> write that program at all. If we were to distribute such a program,
> that would put us in a hypocritical position. So we don't distribute
> such programs
Actually, we (i.e. the FSF and the GNU Project) do. When I worked on
the GNU Software for MS-Windows and MS-DOS CDROM, you agreed to put 3
programs there that were written specifically for the users of
Windows: the installer of the software, a clone of the Unix `man'
command, and DJTAR, a utility that unpacks .tar.gz archives.
I stand corrected on this detail, but the facts that you've cited
agree with the general principle that I stated.
I think the principle was: if the Windows-specific program helps
people use GNU software, it is okay to write and distribute it. For
the same reason, there are several Windows-specific programs that we
maintain and distribute with Emacs (addpm, cmdproxy, ddeclient, etc.).
These programs are best understood as part of porting Emacs to
Windows, making the standard Emacs functionality work there too.
Porting Emacs is something we support, whether the code is inside
Emacs or in a separate auxiliary program.
The crucial distinction is between porting Emacs so that its standard
functionality works on Windows, and extending Emacs with new
functionality that only works on Windows. The latter is what we don't
do. Extensions to Emacs must be done in a way that runs on the GNU
system.
next prev parent reply other threads:[~2005-07-12 3:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 14:16 Is there any way to have a string literal that is read "raw" Lennart Borgman
2005-07-08 15:07 ` David Kastrup
2005-07-08 15:49 ` Lennart Borgman
2005-07-08 16:12 ` David Kastrup
2005-07-08 16:33 ` Lennart Borgman
2005-07-08 16:43 ` David Kastrup
2005-07-08 16:40 ` Lennart Borgman
2005-07-08 22:01 ` Richard M. Stallman
2005-07-08 22:25 ` Lennart Borgman
2005-07-09 17:01 ` Richard M. Stallman
2005-07-09 17:40 ` Lennart Borgman
2005-07-10 17:34 ` Richard M. Stallman
2005-07-10 21:28 ` Lennart Borgman
2005-07-11 16:54 ` Richard M. Stallman
2005-07-11 19:49 ` Eli Zaretskii
2005-07-12 3:20 ` Richard M. Stallman [this message]
2005-07-09 5:22 ` Sean O'Rourke
2005-07-10 5:19 ` Richard M. Stallman
2005-07-09 8:02 ` Markus Gritsch
2005-07-09 9:16 ` David Kastrup
2005-07-09 16:28 ` Lennart Borgman
2005-07-09 16:49 ` David Kastrup
2005-07-10 5:19 ` Richard M. Stallman
2005-07-10 6:59 ` Sean O'Rourke
2005-07-10 8:24 ` David Kastrup
2005-07-11 5:35 ` Richard M. Stallman
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=E1DsBJi-0003Mi-By@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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).