Re: new release?

[David Levine]

> Ken wrote:
>
> > What I'd like is to have mhical simply
> > edit out everything that makes the iCal file a REQUEST (which I think
> > is just the METHOD:REQUEST, or whatever that thing is, plus the list
> > of attendees)
>
> The convert_to_reply() function does close to that, converting
> REQUEST to REPLY.
>
> > and then I can feed that to Apple Calendar.  I'd do that
> > myself, but I haven't had the time.  Would that be hard to add?
>
> If a REPLY could be fed to Calendar, all we'd need to do is save it.
> Maybe provide something analogous to the Fcc: of email messages?

So we already have that, see below.  I don't know how you use
mhical.  The pair of alternatives are intended for discussion.  If
they're not suitable (assuming they even work with Apple calendar),
they might help guide us towards something that is.

The calaccept alias in docs/contrib/replaliases uses repl(1)
(simplified a little):

    \repl -noformat -editor mhbuild \
          -convertargs text/calendar "-reply accept -contenttype" \
          "$@"

Fcc's are stored as usual based on any profile settings, replcomps,
or -fcc on the command line.  mhstore(1) can then be used to extract
the .ics file from the fcc.

Another approach, assuming use of repl -convertargs text/calender,
would be to wrap what mhbuild-convert-text/calendar does in
mhn.defaults with a script that stores the output from nhical.  This
profile addition would override the default in mhn.defaults:

    mhbuild-convert-text/calendar: <path>/store_mhical_output %F

where store_mhical_output contains sonething like:

    mhical -infile "$@" | tee /tmp/response.ics

David