From: Lee Sau Dan <danlee@informatik.uni-freiburg.de>
Subject: Re: Emacs Texts
Date: 20 Jan 2003 08:50:33 +0100 [thread overview]
Message-ID: <m34r86hlsz.fsf@mika.informatik.uni-freiburg.de> (raw)
In-Reply-To: 84of6knbph.fsf@lucy.is.informatik.uni-duisburg.de
>>>>> "Kai" == Kai Großjohann <kai.grossjohann@uni-duisburg.de> writes:
Kai> Do you know that Emacs comes with its manual? Type C-h i d m
Kai> Emacs RET. You can order this manual from the FSF in printed
Kai> form, as well.
The full texinfo source is available under GPL (or GPL for docs?).
So, if you know how to compile texinfo files to Postscript, you can
print it yourself. :)
Of course, it is not very environment-friendly, given the thinkness of
the full manual. Just print a few important chapters and read the
rest from within Info/Emacs.
--
Lee Sau Dan 李守敦(Big5) ~{@nJX6X~}(HZ)
E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee
prev parent reply other threads:[~2003-01-20 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 11:18 Emacs Texts Mark Woodward
2003-01-13 15:50 ` Charles Muller
2003-01-13 18:31 ` Kai Großjohann
2003-01-20 7:50 ` Lee Sau Dan [this message]
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=m34r86hlsz.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).