From: Charles Hallenbeck <2ndsight@taconic.net>
To: Blind Linux Discussions <blinux-list@redhat.com>
Subject: setting biff fixed it
Date: Wed, 2 Dec 1998 20:09:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.981202200759.395C-100000@darkstar.taconic.net> (raw)
Hi all,
The key to my excessive speech was the biff variable, which I set to "n"
and the problem is solved. That one was easy! Many thanks...
Chuck -- Second Sight Software
Now using Linux 2.0.34 and Pine 3.96.
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.3.96.981202200759.395C-100000@darkstar.taconic.net \
--to=2ndsight@taconic.net \
--cc=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).