???
What does "multi-user aware at runtime" mean?
What does "even two copies running off the same user" mean?
Can you explain more about "outgoing mail/news loss"?
Can you explain how multiple users causes "corruption to various parts of the
system"?
>What I often want to be able to do is, while editing, go and look at
>another article or email. That's what a GUI gets you.
Don't need a GUI for this...just an asynchronous editing capability.
Something that would spawn off the editor in a separate console window
and then monitor that process/session to see when it finishes so the
temp message file can get posted. With a warning when you exit yarn
if any edits are still pending.
>As stated, it is unsafe running multiple copies of Yarn, so I have
>disabled the capability. My normal MO now is to edit any reply
>in GUI text editor, allowing me to look at any mail or posts I wish
>to while doing so, and then to paste that reply into the Yarn window
>
>The filter program that comes with yarn is also extremely crappy, as
>it can't match more than one rule ay a time. (so if you have a letter
>addressed to two local users, it only get to the one whose rule appears
>first) But that part is easily fixed.
Anybody feel like porting procmail 8-)
>A more annoying flaw (IMO) is that it dosen't handle local mail
>locally, you have to send local mail up to your SMTP host and back
>again to get it delivered.
I'm a little confused here...I thought yarn was supposed to be an *offline*
reader. Do you mean "mail inbetween users of yarn on the same machine" when
you say "local mail"? You could write a program to deliver "local" mail that
you would run as part of a compress= script that would go through your replies
and pull out any it recognized as going to local users, based on a simple
config file with lines like:
addr@ess=inboxpath
addr@ess2=inboxpath2
>The non-multi-user capability is a fundamental flaw caused by lack of
>of proper (if any) semaphoring on common files.
Again not sure what you mean. AFAIK the only programs that *write* to common
files (expire, import, rebuild) should be run exclusively.
(Hmmm, can you do two newgroups at once? Or a newgroup/rmgroup?)
[remainder snipped]