[m-users.] Spawning external process

[Volker Wysk]

I also had a look at this, and "mmc-doc -i ref" doesn't work for me, because
it incorrectly guesses the path of the installed Mercury documentation.

Volker

Am Samstag, dem 16.07.2022 um 15:06 +0100 schrieb Sean Charles
(emacstheviking):
> Yes, I realised the same!
> 
> > On 16 Jul 2022, at 14:54, Zoltan Somogyi <zoltan.somogyi at runbox.com> wrote:
> > 
> > 
> > 2022-07-16 23:37 GMT+10:00 "Sean Charles (emacstheviking)" <objitsu at gmail.com>:
> > > J Fondren: https://github.com/jrfondren/mmc-doc <https://github.com/jrfondren/mmc-doc>
> > 
> > I just had a look at this tool, and I see that
> > 
> > - it contains a baked-in list of the modules of the Mercury standard library, but
> > - this list has not been updated this year, so it is missing the new modules such as io.call_system.
> > 
> > It looks like this tool will be able to tell you about new standard library modules
> > only when one or the other is fixed.
> > 
> > Zoltan.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.mercurylang.org/archives/users/attachments/20220716/a86205ed/attachment.sig>