From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: Learning emacs
Date: 20 Jan 2003 16:47:08 +0100 [thread overview]
Message-ID: <m3vg0j7rib.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: Pine.WNT.4.52.0301191006340.1932@quetzalcoatl
>>>>> "Sören" == Sören Vogel <soeren.vogel@phil.tu-chemnitz.de> writes:
Sören> You're right.
>> I don't want to download typing tutorial software.
Sören> Are there tutorials for typing computer keyboards? AFAIK
Sören> there's only material for typewriter.
And obviously none for Emacians! :(
--
Lee Sau Dan 李守敦(Big5) ~{@nJX6X~}(HZ)
E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee
next prev parent reply other threads:[~2003-01-20 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 8:12 Learning emacs Paul O'Donnell
2003-01-19 8:23 ` matt
2003-01-19 9:10 ` Paul O'Donnell
2003-01-19 19:46 ` A. L. Meyers
2003-01-19 21:10 ` Jonathon Isaac Swiderski
2003-01-20 15:46 ` Lee Sau Dan
2003-01-19 9:09 ` Sören Vogel
2003-01-20 15:47 ` Lee Sau Dan [this message]
2003-01-19 14:37 ` Kai Großjohann
2003-01-20 15:45 ` Lee Sau Dan
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=m3vg0j7rib.fsf@mika.informatik.uni-freiburg.de \
--to=danlee@informatik.uni-freiburg.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).