🚀 go-pugleaf

In article <1438@opus.cs.mcgill.ca> bajan@opus.UUCP (Alan Emtage) writes:
} 
} (1) Is there currently any way of feeding mush the header of the mail you
} want to send and then have it drop into its usual "sending" mode. The
} reason I ask is that I would like to use mush as my mailer when replying
} or following up to usenet articles.

I sent Alan the Rnmush script via E-mail.  If there's anybody else out
there who missed it, and who wants it, drop me a note -- if I get enough of
them in the next week or so, I'll repost it, otherwise I'll mail copies.

} (2) Is there a bug in changing the variables "ignore and alwaysignore"
} after initialization? It seems that I can't get the effect of turning
} them off an on and getting the right things to happen (maybe this is an
} RTFM).

Well, first of all, "ignore" is not a variable, it's a command.  You
"turn it off" with the command

	unignore *

and you set ignored headers with (for example)

	ignore Status Received Message-Id ....

Ignore is a command rather than a variable for compatibility with ucbMail.

Second, watch this newsgroup for a discussion of the inadequacies of
"alwaysignore".  The only significant command whose behavior is changed
by setting $alwaysignore is "lpr", which normally prints the headers.

What you probably would rather do is set and unset $show_headers.
Setting $show_headers is sort of the inverse of ignore; you tell mush
which headers you would *like* to see, rather than the ones you don't
want to see.

} (3) Are there any plans in the future to allow the curses (I don't use
} the suntool mode at the moment) mode to deal with 2 folders at once?

Yes.

} I constantly have to refer to mail people have previously sent me (and
} now stored in another folder) or mail I have previously written (saved by
} "record"). I would really like to have it that you could "split" the
} screen in two and deal with both folders at once.

Well, not yet.  In the meantime, you can use the "merge" command to read
the contents of another folder into the current one, and then refer to
whatever messages you like.  You can do something like this:

    merge +other | set other_msgs
    (... do something with messages from +other ...)
    delete $other_msgs
    (... update the original folder or whatever ...)

This makes use of the special property of the "set" command when piped-to.
The message numbers of the merged-in messages are recorded in $other_msgs
so they can easily be deleted as a group.  The only thing you have to
remember is, DO NOT SORT the folder without excluding the merged messages
from the sort!  If you sort, the message numbers recorded in $other_msgs
are no longer valid, and you will have to delete the messages "by hand."
It is best to "delete $other_msgs" as soon as you are done using them.

} -----------------------------------------------------------------------------
} Alan Emtage,                    "It's currently a problem of access to
} McGill University,CANADA        gigabits through punybaud." -  Licklider
-- 
Bart Schaefer           "And if you believe that, you'll believe anything."
                                                            -- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer