From: Kate F <kate@elide.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: before= and after= for \setuphighlight
Date: Fri, 15 May 2015 22:45:29 +0100 [thread overview]
Message-ID: <CAA36g0UXjioJXSCrymjvpgWKziynjzdc10-w6eoYiA3kZ_FDJw@mail.gmail.com> (raw)
In-Reply-To: <55565DA6.9070403@wxs.nl>
On 15 May 2015 at 21:57, Hans Hagen <pragma@wxs.nl> wrote:
> On 5/15/2015 9:57 PM, Kate F wrote:
>>
>> Hi,
>>
>> I'm looking for something like \definehighlight which I can use to
>> markup various things in inline body text. I want different
>> environments to be able to have their own setups to configure how
>> these appear, just as \setuphighlight would provide.
>>
>> However there's one situation which I can't think how to handle; I'd
>> like to have a setup append and prepend some text, just like before=
>> and after= for various other setups. If \setuphighlight had before=
>> and after=, this would suit me perfectly. But it doesn't.
>>
>> Is there something similar to \setuphighlight which has before= and
>> after=?
>> Or any other ideas?
>
>
> we have before/after in \definestartstop so let's add left/right there for
> the inline variant
>
> you can put this in cont-new.mkiv:
Wonderful! That suits my situation nicely.
Thank you!
--
Kate
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-05-15 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 19:57 Kate F
2015-05-15 20:57 ` Hans Hagen
2015-05-15 21:00 ` Aditya Mahajan
2015-05-15 21:12 ` Hans Hagen
2015-05-15 21:45 ` Kate F [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=CAA36g0UXjioJXSCrymjvpgWKziynjzdc10-w6eoYiA3kZ_FDJw@mail.gmail.com \
--to=kate@elide.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).