From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Vim module - different settings for inline and block code
Date: Wed, 16 Jan 2013 16:58:38 +0100 [thread overview]
Message-ID: <FD0AE4A5-B38C-42CD-ADAD-93E494F5902E@gmail.com> (raw)
In-Reply-To: <20130116153906.GC29592@homerow>
Am 16.01.2013 um 16:39 schrieb Marco Patzer <homerow@lavabit.com>:
> On 2013–01–16 Wolfgang Schuster wrote:
>
>> \definevimytping
>> [C]
>> […,
>> before={\ifhmode\startInlineBackground\else\startDisplayBackground\fi},
>> after={\ifhmode\stopInlineBackground\else\stopDisplayBackground\fi},
>> …]
>
> That's a good idea and it seems to work.
>
>> You could also ask Aditya to use different keys for display (e.g. before/aftter)
>> and inline (e.g. left/right) code blocks.
>
> That's not necessary. I think your solution is clean enough.
The test doesn’t work when you use \inlineC at the beginning of a paragraph because
TeX it at this moment still in vertical mode and you have to add a \dontleavehmode
to force horizontal mode.
<example>
\def\TestMode
{\ifhmode
\bold{Horizontal Mode}%
\else
\bold{Vertical Mode}%
\fi}
\starttext
\TestMode\ Inline \TestMode
\dontleavehmode\TestMode\ Inline \TestMode
\stoptext
</example>
Wolfgang
___________________________________________________________________________________
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:[~2013-01-16 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 14:51 Marco Patzer
2013-01-16 15:02 ` Wolfgang Schuster
2013-01-16 15:39 ` Marco Patzer
2013-01-16 15:58 ` Wolfgang Schuster [this message]
2013-01-16 15:51 ` Aditya Mahajan
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=FD0AE4A5-B38C-42CD-ADAD-93E494F5902E@gmail.com \
--to=wolfgang.schuster@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).