response 203 of 870:

Jan 3 19:57 UTC 2005

Re resp:127,resp:179: Pine uses those "internal data" messages to store
various information, I think.  I don't know what happens if you delete one.

Re resp:157: In BSD, filesystems have an area that's reserved for only
the root user.  The percentage full takes into account only the
user-accessable part of the filesystem.  So if the filesystem is filled
by a user, then root (or a process owned by root) puts some stuff on it,
it will be over 100%.

Re resp:201: The 'Byte abcd' problem isn't really a "problem", it's just
a different prompt.  more is telling you how many bytes into the file
you are, instead of giving an information-free 'More' prompt.

response 205 of 870:

Jan 4 10:57 UTC 2005

So I was wrong: vi on on the old machine did give the file name, number of
lines and number of characters.  On OpenBSD and linux (2.4.26, I don't know
which distribution), it doesn't.

I note that the man page here, as well as on the Linux machine I now use, is
for the "nex/nvi" versions.  According to the man page, "Nex/nvi  are
intended as bug-for-bug compatible replacements for the original  Fourth
Berkeley  Software  Distribution (4BSD)  ex  and vi programs."

The man pages for vi and nvi do not hint at how to change the initial
information.  For what's worth, <CTRL>G still reports the current line number
and the total number of lines in the file.

response 207 of 870:

Jan 4 14:20 UTC 2005

What about the ^H that I get on my screen instead of the backspace?
With OldGrex, I was told upon login that abackspace was ^H, but
it never appered on my screen.

response 209 of 870:

Jan 4 15:49 UTC 2005

Re #207: Dave, you can set your backspace character to be either
/------------------\
|  ^H (ascii 8) or |
| DEL (ascii 127). |
\------------------/
Some people use one, and some people use another.  It only matters that what
your terminal program sends is what your account on Grex expects to receive.

I have my terminal program set to send ^H, and I have a line in my .login
file which says:
/-------------------------------------\
| stty intr '^C' kill '^K' erase '^H' |
\-------------------------------------/
to tell Grex (among other things) that ^H is my erase key.

When you see those ^Hs on the screen it means your terminal is sending ^H
but Grex is expecting DEL.  So you can either tell your terminal to send
DEL, or tell Grex to expect ^H.

response 211 of 870:

Jan 4 17:09 UTC 2005

Is DEL ^?   Thanks for explaining that I need to login back to my own account
rather than exiting to it.  But I set up an alias to use ssh instead.
In .procmailrc can I use | to set up one long filter instead of many short
ones, for instance    v.agra|vi.?agra|viag.?ra  (to catch v1agra and vi.agra
and viaggra)?  In fact is there some way to not have to use three lines
starting with :0: to filter on each subject, but put everything on one line,
and have one filter for Subject, one for From, one for To, one for message
body (0B)?  Or even one that combines Subject, From and To:  

My filter, now that I removed the white list, has been rejecting roughly every
other mail from each person so I am turning on the verbose log again but it
produces pages of text for each spam and someone just sent seven nearly
identical ones.  So I would like to shorten .procmailrc.  
Is anyone working on a grex-wide spam filter yet, that people could modify
(for instance spamassassin throws out all my electric bills for five causes).

response 213 of 870:

Jan 4 17:22 UTC 2005

I just got a tel   'help  ^U help  EOF (honeycut), in response to my offer
of help via tels since talk was not working.  My guess is vandalism but still,
talk is not working.

response 215 of 870:

Jan 4 17:38 UTC 2005

I
s
t
i
l
l
c
a
n
'
t
t
a
b
o
r

response 217 of 870:

Jan 4 22:44 UTC 2005

Discussions of regular expression syntax probably belong in another
item, but I'll answer one more here.  h.?g.?h would match the word high,
for example, or highest (the first two I think of).  Yes, .? means 0-1
instances of any character.

The H flag checks the header and the B flag the body; HB would check
both.  (The default is H.)

From the Procmail Tips website
(http://pm-doc.sourceforge.net/pm-tips.html):

5.2 Flags HB at top of recipe (warning)
[Philip] Version 3.22 has a bug that keeps the 'H' flag from being
cleared, such that once you use it, it never gets cleared. Using the 'H'
flag will therefore cause problems with latter recipes that use just the
'B' but not the 'H' flag. Either way, the only time you should use the
'H' flag is on recipes that needs to match against both the header and
the body. If you want a recipe to match only against the body and you're
using 3.22, use the "B ??" modifier on the conditions. See message
<http://mailman.rwth-aachen.de/pipermail/procmail/2002-February/008355.html>
. So to be most pportable possible, convert all previously used condition lines
from:

      :0 B
      * body-check-here
    

to use this format:

      :0
      * B ?? body-check-here

response 219 of 870:

Jan 4 22:51 UTC 2005

I set up a test filter with either :0 or :0: on the line before the subject
and it worked both ways.  man procmail also lists samples with or without the
colon.  Does anyone else want to start an item on how to use procmail as a
spam filter?  

response 221 of 870:

Jan 5 03:38 UTC 2005

Dave, the problem was that your .profile had two characters, ^ and H, where
it should have had only one, <CTRL>H.  I've taken the liberty of fixing
that problem.  (I also fixed the interrupt and kill keys, which had the smae
problem.)  I also changed the path of the tset command from /usr/ucb/tset to
/usr/bin/tset.

Tim, you had the same problems with .login.  I've fixed them.

I don't know why your tab key isn't working.
                Mine works for me.
See:            Two tabs, on both this line and the line one above it.

response 223 of 870:

Jan 5 04:35 UTC 2005

It is, as long as you're not using a shell which does something special
with '^', in which case you might need to surround the ^H with single quotes.

response 225 of 870:

Jan 5 18:50 UTC 2005

This is more like a little niggle than a problem, but why won't colour work
in programs like "most" when I have my terminal set to xterm (I don't know
of any other terminal settings where it might work)?

response 227 of 870:

Jan 5 20:14 UTC 2005

 Have you tried "ansi"?