From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: texdoc in ConTeXt standalone
Date: Thu, 5 Apr 2018 01:18:34 +0200 [thread overview]
Message-ID: <87ecfeab-3ef8-8380-75db-f6787eec8f4c@xs4all.nl> (raw)
In-Reply-To: <1522881797.18581.3.camel@gmail.com>
On 4/5/2018 12:43 AM, Henri Menke wrote:
> Dear list,
>
> I'm sure you aware of the very useful "texdoc" command line utility in TeX live
> which brings up the PDF documentation for packages. ConTeXt standalone also
> comes with documentation in
>
> /opt/context/tex/texmf-context/doc/context
>
> However, I find it tedious to always search for the correct subfolder to get to
> the document I need. It would be great if there was something like
>
> mtxrun --script doc metafun
>
> which would open the MetaFun manual. Similarly "mtxrun --script doc gnuplot"
> would open the manual of the gnuplot module, etc.
this is one of these magic features that suddenly is available on your
system
mtxrun --launch metafun*.pdf
mtxrun --launch cld-mkiv.pdf
mtxrun --all --launch "*-mkiv.pdf"
features like that have always been present in the context suite of
programs (i bet even before texdoc) but it might be that i don't call
the right thing on todays linux:
local launchers={
windows="start %s",
macosx="open %s",
unix="$BROWSER %s &> /dev/null &",
}
there's also
mtxrun --edit kpse:cld-mkiv.tex
we can of course extend this feature with some listing but then i'd
rather consult the descriptive files xml but i'm not sure if i
distribute them yet
> See attached for my shitty prototype.
>
> Cheers, Henri
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-04-04 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 22:43 Henri Menke
2018-04-04 23:18 ` Hans Hagen [this message]
2018-04-04 23:28 ` Henri Menke
2018-04-04 23:45 ` Hans Hagen
2018-04-05 0:06 ` Hans Hagen
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=87ecfeab-3ef8-8380-75db-f6787eec8f4c@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).