From: David Z Maze <dmaze@mit.edu>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Wed, 07 Jun 2006 11:48:20 -0400 [thread overview]
Message-ID: <y68bqt5t1a3.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <muod82ll2kuu82ga5mldcbo5q2ir2en43h@4ax.com>
me@privacy.net writes:
> I'm curious what you do with emacs
>
> and gNus
While this probably isn't the right newsgroup for it...
My computing life is almost entirely under Linux. At work I'm
fortunate enough to use a Red Hat derivative; at home I run KUbuntu, a
KDE-based Debian derivative. Emacs has an incredible amount of power
and I've gotten it configured to do what I like; I've had a lot of
trouble getting other editors and environments (e.g. KDE's "advanced
text editor", Eclipse) to do the same sorts of things that I want.
In the modern world, Emacs is kind of a middle-weight process -- Eight
Megabytes And Constantly Swapping might have been an issue ten years
ago but now it's nothing on PC-class systems where gigabytes of memory
are approaching the norm. I still find it too heavyweight for
command-line use, so I will use vi (or occasionally even ed) for
things like editing configuration files. The flip side of this is
that, since desktop environments now typically make heavy use of
off-white colors and antialiased fonts, Emacs looks barren and jagged
against the rest of my desktop.
What do I use Emacs for? General-purpose text editing, including
especially writing longer things in LaTeX and editing XML (XSLT, XML
Schema, XHTML, ...) files (yay nxml-mode). Any coding happens pretty
exclusively inside Emacs (C, C++, Haskell, make, Python, ...). And of
course all of my non-work email gets read inside Gnus.
My Gnus setup uses an IMAP mail-source fetched into an nnml backend
stored on an AFS networked filesystem. I use spam-stat.el to sort out
spam from ham. This combination of things makes starting up Gnus a
little slow. I also have one nntp server that I read a couple of
newsgroups (including this one) off of.
Right now I have three Emacsen running on three different machines.
One of them is running Gnus. This is a pretty normal daily state of
affairs for me.
--dzm
next prev parent reply other threads:[~2006-06-07 15:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 14:34 me
2006-06-07 14:41 ` Hadron Quark
2006-06-07 15:05 ` me
2006-06-07 15:19 ` Hadron Quark
2006-06-07 15:40 ` Mark T.B. Carroll
2006-06-09 8:17 ` Tim X
2006-06-09 9:46 ` rambam
2006-06-07 15:46 ` Ted Zlatanov
2006-06-07 15:46 ` Malte Spiess
2006-06-09 8:13 ` Tim X
2006-06-09 13:49 ` me
2006-06-07 14:50 ` Mark T.B. Carroll
2006-06-07 15:48 ` David Z Maze [this message]
2006-06-07 15:49 ` Robert D. Crawford
2006-06-07 17:49 ` notbob
2006-06-08 8:09 ` Glyn Millington
2006-06-10 6:41 ` Joe Bush
2006-06-10 9:17 ` Tim X
2006-06-10 20:01 ` Robert D. Crawford
2006-06-12 17:27 ` Joe Bush
2006-06-08 0:57 ` Joe Fineman
2006-06-08 1:17 ` Bastien
2006-06-08 1:40 ` Johan Bockgård
2006-06-08 6:18 ` David Kastrup
2006-06-08 1:59 ` Robert D. Crawford
2006-06-08 3:03 ` me
2006-06-08 14:30 ` David Z Maze
2006-06-08 14:57 ` David Kastrup
2006-06-08 17:58 ` notbob
2006-06-08 18:33 ` David Kastrup
2006-06-08 14:46 ` Eric Eide
2006-06-09 8:27 ` Tim X
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=y68bqt5t1a3.fsf@contents-vnder-pressvre.mit.edu \
--to=dmaze@mit.edu \
/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).