From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jody <jbruchon@nc.rr.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Sums added
Date: Tue, 23 May 2006 11:01:52 +0100 [thread overview]
Message-ID: <1148378512.25255.1.camel@localhost.localdomain> (raw)
In-Reply-To: <44727112.6050000@nc.rr.com>
On Llu, 2006-05-22 at 22:18 -0400, Jody wrote:
> I'm very slowly transitioning to Linux. My problem is that I want a
> clean system, and of course it takes a lot of work to compile, package,
> and install stuff yourself. My main problem is that I'm so used to
Well yes thats why the distributions have large teams doing it 8)
> Windows key combinations and whatnot that the Linux way of doing things
> keeps beating the tar (no pun intended) out of my productivity.
>
> What maniac designed the cut-and-paste that you use in Xedit anyway?
People in the early 1980s who didnt have enough memory to keep the
cut/paste buffering in the server itself. Xedit is a dinosaur 8)
Alan
next prev parent reply other threads:[~2006-05-23 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 2:18 Sums added Jody
2006-05-23 7:51 ` Hans
2006-05-23 10:01 ` Alan Cox [this message]
[not found] ` <5a4d65ae0605231352s271418d5i6f81140892406f90@mail.gmail.com>
2006-05-24 3:02 ` Jody
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=1148378512.25255.1.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox