From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: (again) diferent prefixsegments for different references
Date: Sun, 16 Jan 2022 20:59:21 +0100 [thread overview]
Message-ID: <24451544-ae06-897f-bf7b-dfa989873bc0@gmx.es> (raw)
Dear list,
I asked this some time ago
(https://mailman.ntg.nl/pipermail/ntg-context/2021/102394.html).
Using the following sample:
\starttext
\definereferenceformat[itsc][in]
\setupreferencestructureprefix[itsc][default]
[prefixsegments=section]
\chapter{Chapter}
\section[b]{Section}
\itsc[b] and \in[b]
\stoptext
Is there a way that the prefixsegments for \itsc is only section,
without modifying it for \in?
Many thanks for your help,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2022-01-16 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=24451544-ae06-897f-bf7b-dfa989873bc0@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).