From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: two issues with \sciteinlinebuffer
Date: Sat, 9 Jul 2022 10:05:16 +0200 [thread overview]
Message-ID: <efda5c62-03c8-a744-1686-edef0d0db887@gmx.es> (raw)
In-Reply-To: <e9f354c9-e6c6-4eaf-d6da-95dbfcf95a99@freedom.nl>
On 7/9/22 08:42, Hans Hagen via ntg-context wrote:
> On 7/8/2022 7:51 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Excuse my ignorance, but it is \sciteinlinebuffer the misbehaving
>> command in my code.
> \unexpanded\def\module_scite_buffer_inline[#1][#2]%
> {\dontleavehmode
> \begingroup
> \lettypingparameter\c!margin\zeropoint
> \setcatcodetable\ctxcatcodes % needed in xml
> \ifsecondargument
> \clf_scitelexbuffer{#2}{#1}%
> \else
> \clf_scitelexbuffer{#1}{tex}%
> \fi
> \tt
> \installscitecommandsinline
> \module_scite_inherit_typing
> \dontcomplain
> \getbuffer[lex]%
> \removeunwantedspaces
> \endgroup}
Many thanks for the fix, Hans.
It works perfectly fine now.
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-07-09 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 16:19 Pablo Rodriguez via ntg-context
2022-07-07 21:30 ` Hans Hagen via ntg-context
2022-07-08 17:51 ` Pablo Rodriguez via ntg-context
2022-07-09 6:42 ` Hans Hagen via ntg-context
2022-07-09 8:05 ` Pablo Rodriguez via ntg-context [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=efda5c62-03c8-a744-1686-edef0d0db887@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).