unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David.Kastrup@t-online.de (David Kastrup)
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Bug#139792: emacs21: Press PageDown, get infinite loop
Date: 16 Apr 2002 12:21:30 +0200	[thread overview]
Message-ID: <x5vgasoset.fsf@tupik.goethe.zz> (raw)
In-Reply-To: <Pine.SUN.3.91.1020416093513.14169I-100000@is>

Eli Zaretskii <eliz@is.elta.co.il> writes:

> On 16 Apr 2002, David Kastrup wrote:
> 
> > >     >   It is distributed under the GNU General Public License - see the
> > >     >   accompanying COPYING file for more details. 
> > > 
> > > The kernel is released under the GNU GPL, but the whole system--the
> > > Unix clone--is not.  It includes components such as X11, GNU libc,
> > > Apache, TeX, etc., which have other licenses.
> > 
> > X11, Apache or TeX are not part of Unix, they just run under it.
> 
> That's debatable.  A system without those components would be much
> less useful than with them.  I.e. it would be much less of ``a
> system''.

Debatable?  For somone that already cried "foul!" if the "Linux"
moniker is extended over more than just the kernel proper, it is
debatable whether "Unix" should not encompass everything that may be
made to run under it?

> In any case, since Debian distributes all of these components as
> part of a whole, that distribution defines a ``system'', even if
> that's not the only possible definition of a system (which seems to
> be the cause of your disagreement).

And Debian calls it GNU/Linux.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de

  reply	other threads:[~2002-04-16 10:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16pNB6-0003ei-00@blackbird.home.nickwillson.com>
2002-04-14  5:22 ` Bug#139792: emacs21: Press PageDown, get infinite loop Rob Browning
2002-04-15 22:00   ` Richard Stallman
2002-04-15 23:20     ` David Kastrup
2002-04-16  6:36       ` Eli Zaretskii
2002-04-16 10:21         ` David Kastrup [this message]
2002-04-16 12:14           ` Eli Zaretskii
2002-04-16 12:39             ` David Kastrup
2002-04-16 14:11               ` Eli Zaretskii
2002-04-17 16:04           ` Richard Stallman
2002-04-17 16:03       ` Richard Stallman
     [not found]     ` <rms@gnu.org>
2002-04-16  3:55       ` Nick
2002-04-17 16:03         ` Richard Stallman
2002-04-16 13:56       ` Peter S Galbraith
2002-04-16 19:25         ` Rob Browning
     [not found]           ` <rlb@defaultvalue.org>
2002-04-17 13:05             ` Peter S Galbraith
2002-04-17 15:22               ` Rob Browning
2002-04-17 16:04         ` Richard Stallman
2002-04-18 15:22           ` Paul Jarc
2002-04-19  5:25             ` Richard Stallman
2002-04-17 17:15       ` Peter S Galbraith
2002-04-19  5:24         ` Richard Stallman
2002-04-19  5:17       ` Nick
2002-04-19  6:53         ` Eli Zaretskii
     [not found]           ` <eliz@is.elta.co.il>
2002-04-20 22:03             ` Nick
2002-04-19 13:43       ` Peter S Galbraith

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=x5vgasoset.fsf@tupik.goethe.zz \
    --to=david.kastrup@t-online.de \
    --cc=bug-gnu-emacs@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).