From: Steven L Baur <steve@miranova.com>
Subject: Re: rgnus-0.46 and custom.el
Date: 18 Oct 1996 20:32:10 -0700 [thread overview]
Message-ID: <m27mony6h1.fsf@deanna.miranova.com> (raw)
In-Reply-To: Per Abrahamsen's message of 03 Oct 1996 19:03:05 +0200
>>>>> "Per" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
>>>>> "Brent" == Brent B. Powers <powers@ml.com> writes:
Brent> (In fact, the only customization field was "GNUS the all
Brent> singing et cetera".
Per> If you click mouse-2 (or push RET) on the `*' in the beginning of the
Per> line, three more options should be revealed. You can click on the
Per> `**' preceding each of those to see more options. Not all the old
Per> customization options have been reimplemented yet, though.
That is *really* obscure.
(Going through the pain and anguish of updating my environment).
--
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
What are the last two letters of "doesn't" and "can't"?
Coincidence? I think not.
next prev parent reply other threads:[~1996-10-19 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-02 21:25 Brent B. Powers
1996-10-03 17:03 ` Per Abrahamsen
1996-10-04 15:18 ` Lance A. Brown
1996-10-04 16:33 ` Per Abrahamsen
1996-10-19 3:32 ` Steven L Baur [this message]
1996-10-20 21:06 ` Per Abrahamsen
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=m27mony6h1.fsf@deanna.miranova.com \
--to=steve@miranova.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 NNTP newsgroup(s).