From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing ConTeXt users list for <ntg-context@ntg.nl>
Subject: maybe OT? ConTeXt on an EEEPC
Date: Sat, 19 Apr 2008 11:42:26 +0200 [thread overview]
Message-ID: <67A3F6C6-B778-49DD-8201-68FF8B66AA35@uni-bonn.de> (raw)
Dear all,
maybe this is off-topic, but I just wanted to tell you about my
experiences (and sorry if this sounds like a sales pitch, it isn't!).
Since I have a fairly long commute to work, I spend a lot of time on
the train and like/need to do serious work there. When you have to
schlepp it almost every day, a normal laptop seems pretty heavy after
a while, that's why I got me one of those eeepc thingies. Its tiny
screen and small keyboard scream "I'm just a mobile device, not a
replacement for a real computer," and it's not the fastest machine
around. However, my joy is great whenever I stuff the little thing in
my bag and lift it.
I got the 8GB variant. To do work, I always want all my documents with
me (so I can easily sync my entire Documents directory between work,
home, and laptop) and, of course, my TeX installation. My texlive-
texmf tree now is 1.6 G, so I needed a bit more space than the 4G
model offers (models with larger screens and hard disks will be
available soonish). It has a SDHC card reader, so I copied my
Documents and the TeX installation to the internal disk (a SSD) and
have my linux installation on a card from which I boot. With a shell
script, I set the $PATH so I can mount the internal disk and run
ConTeXt off of it. Everything works wonderfully. As I said, it's a
slow machine, so you don't want to compile very long documents too
often, but it does run every flavor of ConTeXt. I often prepare my
presentations on the train, and this works great: I have the
environment to which I'm used for editing the source files (emacs +
ConTeXt) and a pdf viewer open in another workspace. This setup is one
of the reasons why I prefer a texlive installation to a minimal
ConTeXt tree: that way, I have to maintain it only once and can sync
it between my computers. So whoever has to travel a lot: I find it
wonderful to have such a small and light computer on the road.
All best, have a nice weekend
Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2008-04-19 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 9:42 Thomas A. Schmitz [this message]
2008-04-19 12:46 ` Hans Hagen
2008-04-19 19:05 ` Thomas A. Schmitz
2008-04-19 19:18 ` Olivier Guéry
2008-04-19 20:49 ` Hans Hagen
2008-04-20 7:57 ` luigi scarso
2008-04-20 10:34 ` Hans Hagen
2008-04-19 20:48 ` Hans Hagen
2008-04-20 11:21 ` Otared Kavian
2008-04-20 13:18 ` Hans Hagen
2008-04-20 14:33 ` Thomas A. Schmitz
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=67A3F6C6-B778-49DD-8201-68FF8B66AA35@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).