On Thu, 14 Jan 1999 14:11:29 -0500, Al Gilman <[EMAIL PROTECTED]>
wrote:
> I suggest you try harder digging out the positive approach. It's in there.
>
> Check out the various predefined resource variables. You can get From, To,
> Subject and Date values and format your own presentation. Just kill all
> the predefined formatting with excs * and roll your own.
That's the workaround I have in mind if I can't actually fix the problem.
(Semantics, but when I was referring to a positive approach, I meant by
comparison to EXCS, not the fact that I can reject the entire thing and
then build something else that looks the same.)
> At 06:36 PM 1/14/99 +0000, Frank J. Perricone wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >
> >My MHonArc archive for my Crossword PBEM RPG is almost set up to my (for
> >now) satisfaction, and can be previewed (with lots of very old messages) at
> >http://www.pennmush.org/~server/crossword/. It's an unusual situation in
> >that someone else (a former player of the game) is providing the server
> >space that runs MHonArc and a web server for me, so I'm doing my work
> >remotely -- writing an rcfile and then emailing it to him. Makes debugging
> >slow work since I can't drive the poor fellow mad with constant updates.
> >
> >I can't figure out what I'm doing wrong with my EXCS block. Ideally I'd
> >like to get rid of everything but From, To, Subject, and Date. But since
> >EXCS seems to be a negative approach, and I can't find a positive approach,
> >I have to find every field that might appear and exclude it. This is what
> >I have:
> >
> ><EXCS override>
> >apparently
> >comments
> >content
> >errors-to
> >followup
> >forward
> >in-reply-to
> >lines
> >message-id
> >mime-
> >nntp-
> >originator
> >organization
> >path
> >precedence
> >received
> >references
> >replied
> >return-path
> >status
> >via
> >x-
> ></EXCS>
> >
> >The in-reply-to, references, and comments fields just will not go away,
> >though. I've tried shorter versions, with and without a space afterwards,
> >and with and without uppercase, though I don't understand why it wouldn't
> >just simply work. It seems simple enough.
> >
> >I searched the archives and found one other person asked the same question
> >about the in-reply-to and references field, another person just say "works
> >for me", and the thread ended there. (At least that part of it.) Can't
> >find any reference to this in the docs, FAQ, or anywhere else.
> >
> >Any ideas?
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: 2.6.2
> >Comment: public key: finger [EMAIL PROTECTED], or on my web page
> >
> >iQB1AwUBNp45HMyfEemBueK1AQHxsgL+MGnQeq/emqA/PRmgKGTj14wqP284MOw3
> >mOUdHh5GNByWMxjSwkuGz2ZC0mdbL4kpsmGGtOgJoJdjawJslSGqOqN6MSKAi7MY
> >y5EJykfjivkWstdrK9WBxftsOjX/ImUZ
> >=b9pY
> >-----END PGP SIGNATURE-----
> >
> >--
> >* Frank J. Perricone * [EMAIL PROTECTED] * http://www.sover.net/~hawthorn
> >Just because we aren't all the same doesn't mean we have nothing in common
> > Just because we have something in common doesn't mean we're all the same
> >
--
* Frank J. Perricone * [EMAIL PROTECTED] * http://www.sover.net/~hawthorn
Just because we aren't all the same doesn't mean we have nothing in common
Just because we have something in common doesn't mean we're all the same