From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: local command description
Date: Tue, 16 Apr 2019 23:23:35 +0200 [thread overview]
Message-ID: <20190416212335.bjkeailbwlqoulwb@phare.normalesup.org> (raw)
In-Reply-To: <20190416211508.GB7391@valencay.home>
Hi Damien,
On Tue, Apr 16, 2019 at 11:15:08PM +0200, Damien Thiriet wrote:
> mtxrun --script server --auto
>
> [snip]
>
> mtx-server | context services: http://localhost:8088/mtx-server-ctx-startup.lua
> mtxrun --gethelp
> --url=http://localhost:8088/mtx-server-ctx-help.lua?command=%command%
> --command= "\definecolor"
>
> When I run this, I get
> sh: http://localhost:8088/mtx-server-ctx-help.lua?command=definecolor: not found
The first command starts a Web server that you can query with the
second command -- or obviously with a browser, using the URL displayed
(localhost:8088, etc.). In order for the second command to succeed, you
thus need to keep the first one running. In addition, you need to
protect the URL in the second command from the shell, like thus for
example:
mtxrun --gethelp \
--url='http://localhost:8088/mtx-server-ctx-help.lua?command=definecolor' \
--command='\definecolor'
Specifically, it’s the question mark that gives the shell grief.
Best,
Arthur
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-04-16 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 21:15 Damien Thiriet
2019-04-16 21:23 ` Arthur Reutenauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190416212335.bjkeailbwlqoulwb@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).