From: "David Chmelik" <dchmelik@nwinfo.net>
Subject: (offtopic?) making gnus easier
Date: Sun, 12 Feb 2006 06:33:35 -0800 (PST) [thread overview]
Message-ID: <50683.66.243.248.177.1139754815.squirrel@mail.nwinfo.net> (raw)
It would be nice if gnus was "easy" as gui; it seems hard as old things
like tin, but I will not use gui except when writing more prose than than
code. Is a lisp authors' book recommended, or is gnu doc enough? Gnus
bewilders me (and non-coders in many more ways likely:)
many help sections, little toc description
many variables, little variable descriptiveness
I am joking about this descriptiveness; it is overdone like xemacs (i
should try emacs "menus.") Maybe it is easier for syadmins, or Sage helps
(no one near me does.) but from the pov. of a not total hard computer
scientist, even using gnus oneself is a problem (I relearned how to skip
gnus' "reading..," but 1/2 the time it usually will not unsubscribe: after
marking read & unsubscribing a couple times: it ignores you, or keeps
doing it like read-only grouplist:)
gnus vs gnus-unplugged (rarely unplugs)
gnus-activate-level (i did not check: unrelated to vga)
gnus-agent (overkill for users; 'J' does nothing)
gnus-cacheable-groups (this & next 2 in docs supposedly prevent loading)
gnus-check-new-newsgroups
gnus-read-active-file
gnus-secondary-select-methods (someone on #gnus implied secondaries do not
immediately load.)
gnus-use-cache (not near its' group list?)
I take cs technical writing class next; this part is ignorant comments on
help; now skip if you want. You have to know texinfo and emacs lisp.
like: "the summary 'buffer::'" "... posting ..."
"the article 'buffer'::" "... handling articles ..."
"composing messages::" "... sending ..."
I use the buffer, but others will also not know the difference in chapter
descriptions: which go on like this for 50. Undefined is ok in doshelp; not
texinfo.
I offered to donate/pay for docs/help to solve this, but "make" also needs
free software docs comparing Bsd & gnu make. I will not write much; as
without discussion i struggle into summer break to even use glibc & make;
unless i can help and someone else who prefers console & posix over 9 yr
thinks so. But, i will ignore extra groups; gnus-mail will solve things if it
is nice. I only studied lisp to write exercises, but may get the book.
sincerely, David Chmelik
(Darwin at the fsf)
next reply other threads:[~2006-02-12 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 14:33 David Chmelik [this message]
2006-02-13 19:19 ` Ted Zlatanov
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=50683.66.243.248.177.1139754815.squirrel@mail.nwinfo.net \
--to=dchmelik@nwinfo.net \
/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).