public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: How many of y'all use Emacspeak?
Date: Mon, 19 Jun 2017 01:16:01 -0700	[thread overview]
Message-ID: <87vansqtoe.fsf@the-brannons.com> (raw)
In-Reply-To: <e0d6b226-54f5-17f0-1215-2bcc302a0577@gmail.com> (Linux for blind general discussion's message of "Sat, 17 Jun 2017 12:04:30 -0500")

Linux for blind general discussion <blinux-list@redhat.com> writes:

> The emacs manual is generally easy to understand but I'm having the
> opposite experience with gnus. I don't understand much of the
> terminology, I don't yet know elisp and ATM I'm just trying to figure
> out how to set up gmail.

Yeah, pretty much my experience back in 2004.  If you plan on learning
elisp, I'd suggest the elisp intro.  It's in the info documentation that
comes with emacs.  Well it does on most distros anyway, but Debian puts
it in a separate package in their nonfree repository.  Package is called
emacs24-common-non-dfsg, emacs25-common-non-dfsg, or some other such
thing.  Because politics.  I think it's called eintr.  So if you use C-h
i to get into the info reader,
g (eintr)
will display it.

I could probably send you all my mail-related configs.  They're
scattered across three or four files.

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
 ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion [this message]
     ` Linux for blind general discussion

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=87vansqtoe.fsf@the-brannons.com \
    --to=blinux-list@redhat.com \
    /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).