From: James Freer <jessejazza3.uk@gmail.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS
Date: Tue, 1 Jul 2014 15:38:24 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.10.1407011534030.1914@james> (raw)
In-Reply-To: <87r425qi4t.fsf@debian.uxu>
On Tue, 1 Jul 2014, Emanuel Berg wrote:
> James Freer <jessejazza3.uk@gmail.com> writes:
>
>> I'm very grateful for the time you have spent
>> although now after a couple of weeks I have learnt
>> enough to be happy with. I've found using emacs-nox
>> and forgetting about the gui is worthwhile and taking
>> time to learn from the cheatsheet. It would be nice
>> to have the 'mini manual' in pdf then one could print
>> it out and read on the train (or similar times when
>> one is away from the PC).
>
> Do my ears deceive me?! Finally a guy with class!
> F*ing right!
>
> I haven't seen the particular document, though. I will
> read it tonight and probably get back to the OP with
> some comments.
>
> If you don't like to just print and read the HTML, you
> can use several tools to get it to PDF. You can use
> html2ps, and then ps2pdf - html2ps is in the repos,
> ps2pdf is part of ghostscript, which is likewise in the
> repos. (There are other ways to do this as well.)
html2ps
I'll have to look up
I knew about ps2pdf and pdf2ps as I use it to send faxes. (yes fax still has
a use). Or maybe I need to look at other methods.
When I 'read on a train' - in truth I really meant that I like the pdf to print
out, bind, and then use like a book for bedtime reading. keen beginner eh.
james
next prev parent reply other threads:[~2014-07-01 14:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 4:41 Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS solidius4747
2014-07-01 7:44 ` James Freer
[not found] ` <mailman.4638.1404200703.1147.help-gnu-emacs@gnu.org>
2014-07-01 14:16 ` Emanuel Berg
2014-07-01 14:38 ` James Freer [this message]
[not found] ` <mailman.4649.1404225527.1147.help-gnu-emacs@gnu.org>
2014-07-08 8:36 ` solidius4747
2014-07-08 15:09 ` Emanuel Berg
2014-07-08 16:18 ` Drew Adams
2014-07-08 16:45 ` solidius4747
2014-07-08 21:36 ` Emanuel Berg
2014-07-09 2:41 ` solidius4747
2014-07-09 8:52 ` Robert Thorpe
2014-07-09 17:11 ` Emanuel Berg
2014-08-25 14:05 ` Jude DaShiell
2014-07-08 18:56 ` Robert Thorpe
[not found] ` <mailman.5091.1404836351.1147.help-gnu-emacs@gnu.org>
2014-07-08 21:21 ` Emanuel Berg
2014-07-09 8:44 ` Robert Thorpe
2014-07-10 2:11 ` Bob Proulx
[not found] ` <mailman.5163.1404958319.1147.help-gnu-emacs@gnu.org>
2014-07-10 22:16 ` Emanuel Berg
2014-07-12 14:52 ` Javier
2014-07-12 19:49 ` Emanuel Berg
2014-07-12 23:30 ` Javier
2014-07-13 16:52 ` Emanuel Berg
2014-07-13 1:40 ` Robert Thorpe
2014-07-07 23:12 ` Emanuel Berg
2014-07-08 8:37 ` solidius4747
2014-07-08 15:15 ` Emanuel Berg
2014-07-08 16:48 ` solidius4747
2014-07-08 21:43 ` Emanuel Berg
[not found] <mailman.5117.1404898261.1147.help-gnu-emacs@gnu.org>
2014-07-09 16:55 ` Emanuel Berg
2014-07-11 11:51 ` Robert Thorpe
[not found] <mailman.5279.1405079523.1147.help-gnu-emacs@gnu.org>
2014-07-11 12:07 ` Emanuel Berg
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=alpine.DEB.2.10.1407011534030.1914@james \
--to=jessejazza3.uk@gmail.com \
--cc=embe8573@student.uu.se \
--cc=help-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.
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).