From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \definedescription and setupdescription options
Date: Fri, 04 Mar 2016 20:00:51 +0100 [thread overview]
Message-ID: <56D9DB63.4040609@gmail.com> (raw)
In-Reply-To: <56D9D3F0.9060401@mailbox.org>
[-- Attachment #1.1: Type: text/plain, Size: 642 bytes --]
> Jan U. Hasecke <mailto:juh+ntg-context@mailbox.org>
> 4. März 2016 um 19:29
> Thank you Wolfgang,
>
> your examples are very helpful.
>
>
> Did you make the pdf with \showsetup{...}?
>
> I am missing setupdescriptions.
\setupdescriptions is a synonym for the \setupdescription command.
> And I get "MISSING SETUP" when I try \showsetup{setupdescription}.
>
> My context installation is: current version: 2016.02.24 11:19
>
> Shall I update to have the newest interface descriptions available?
No, because I used a local version of the interface file where I added
missing entries but it isn’t finished yet.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1924 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-03-04 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 15:25 Jan U. Hasecke
2016-03-04 15:49 ` Aditya Mahajan
2016-03-04 18:36 ` Jan U. Hasecke
2016-03-04 15:52 ` Wolfgang Schuster
2016-03-04 18:29 ` Jan U. Hasecke
2016-03-04 19:00 ` Wolfgang Schuster [this message]
2016-03-04 19:07 ` Jan U. Hasecke
2016-03-06 22:17 ` Alan BRASLAU
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=56D9DB63.4040609@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).