From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: context --autopdf and --showdirectives
Date: Mon, 31 Oct 2022 23:01:49 +0100 [thread overview]
Message-ID: <e0844a9c-542d-602a-0e97-319a94a6fb09@fiee.net> (raw)
I’d like to configure the default behaviour of "context --autopdf";
since on my Mac I must always write "--autopdf=auto", otherwise context
tries to call
wine "sumatrapdf.exe" -reuse-instance -bg-color 0xCCCCCC
instead of e.g. "open".
There’s a hint about "directives_pdfview_method", so I wanted to find
out more about directives:
"context --showdirectives" looks promising;
it tells me "result saved in file:
.../texmf-context/tex/context/base/mkiv/mtx-context-setters.pdf", but
that file isn’t there; it is actually in the current directory, but broken.
* How can I configure the command for --autopdf ? (Something in
texmfcnf.lua?)
* Can we add additional options ("pdfview methods: auto default okular
pdfxcview sumatra"), e.g. open (should be default on Mac), xdg-open
(could be default on Linux)...
* What’s wrong with --showdirectives?
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-10-31 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 22:01 Henning Hraban Ramm via ntg-context [this message]
2022-11-01 22:22 ` Hans Hagen via ntg-context
2022-11-02 8:33 ` Henning Hraban Ramm via ntg-context
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=e0844a9c-542d-602a-0e97-319a94a6fb09@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).