From: David Chmelik <darwin@elltel.net>
Subject: Re: gnus automation & mail?
Date: Wed, 19 Apr 2006 15:40:40 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0604191530450.4119@kosmos.nwinfo.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0604180530150.4273@kosmos.nwinfo.net>
Never mind, I put nntpserver in after news method, and then both in yet
another area besides gnus-group/.el-files. Though one may always have to
go to the server screen, I must attend to many more critical little-documented
bugs, so bye. Just keep in mind that emacs, etc. is philosophically best
in ethics, but try to make its' scientific coherence equal its' religious
one.
???--
> I posted earlier asking 4 - 5 reasons why gnus & gnus-unplugged
> automation; & maybe nnmail, are pain. Most unfortunate that people want it.
> I, reject suggestion that I or people asking for help should use Thunderbird
> (worse becuase of bugs and the one called gui to top them off;) and I am
> replying. I learned enough lisp to make emacs send from any e-address I say;
> then yet another built-in forced/redundant variable ruined it.
> Lisp makes clear that the 3 variables controlling news dling are unclear
> (or I must learn more, or "interface is no better than I would make" and
> maybe different per system.) The gnus-unplugged command to enable a server /
> group in some window works not in slackware; is this a variant undocumented?
> Sorry for no reply to who wrote me, consequential to using trash & web
> mailers (I always preferred rmail, 'til it destroyed mail:) I do not even
> know this is the right listserv. You know I could say xemacs for friends,
> but it is not gnu, and neither is the os (never mind learning it...) those
> friends use, so... I still post this about emacs & xemacs.
> from David
prev parent reply other threads:[~2006-04-19 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 5:51 David Chmelik
2006-04-19 22:40 ` David Chmelik [this message]
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=Pine.LNX.4.63.0604191530450.4119@kosmos.nwinfo.net \
--to=darwin@elltel.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).