Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Glyn Millington <wistanswick@linuxmail.org>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Thu, 08 Jun 2006 09:09:44 +0100	[thread overview]
Message-ID: <878xo8gjav.fsf@nowhere.org> (raw)
In-Reply-To: <lNidnVTid9QgjBrZnZ2dnUVZ_q2dnZ2d@comcast.com>

notbob <notbob@nothome.com> writes:

> I don't use emacs for everything, but it's very good for some things.
> It's a great file manager and editor.  I used to prefer jed as my
> editor, but recently discovered emacs highlights .foorc files,
> something jed doesn't.  OTOH, I don't like gnus over slrn.  I've been
> told a million times it can be configured to do everything slrn can,
> and more.  But, I'm not into spending 12.8% of my remaining lifetime
> learning how.  

Customising Gnus and/or (X)Emacs is addictive :-) Great sport for that
time of life when rock-climbing or sumo-wrestling are no longer an option
but you need to fight off senility by any available means ... 



> And what's with xemacs?  I downloaded and discovered all the usual apps
> I was expecting are now optional add ons requiring more time scaling
> the curve to learn how.  

Download the latest xemacs packages bundle and the mule bundle (multi-lingual
stuff) (both called sumo! the first is about 23MB) from 

 ftp://ftp.xemacs.org/packages/      or your friendly neighbourhood
 mirror


extract them in /usr/local/lib/xemacs and you should get two directories

xemacs-packages and mule-packages

XEmacs will find them when you restart.


Some packages like Dired will work out of the box.  Some you will have
to start up from your ~/.xemacs/init.el file, the XEmacs equivalent of
~/.emacs 

C-h i will get you into the info reader and you can usually find the code
for starting your desired package by reading the relevant entry.  There
is masses of good documentation.


You can keep your packages up to date with the package handling system -
that's another story, documented here

http://www.xemacs.org/Documentation/packageGuide.html

This is no worse than getting slrn and jed to play is it? :-)


> Not now.  Maybe later.

Fair enough!

atb




Glyn

  reply	other threads:[~2006-06-08  8:09 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
2006-06-07 15:49 ` Robert D. Crawford
2006-06-07 17:49   ` notbob
2006-06-08  8:09     ` Glyn Millington [this message]
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=878xo8gjav.fsf@nowhere.org \
    --to=wistanswick@linuxmail.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 NNTP newsgroup(s).