ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: About xstring and ConTeXt
Date: Tue, 7 Jul 2020 13:40:07 -0500	[thread overview]
Message-ID: <CAKyqqaa9pq4raMUT43ckJ4bvgxQxCWXAKx9=gCivVmKRJRP6RQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]

Reading about macro bundles meant to be generic (format agnostic), some of
them work in plain/LaTeX, but crash when loaded on ConTeXt. The following
happens with xstring.tex

tex error > tex error on line 372 in file xstring.tex: ! Illegal parameter
number in definition of \xs_reserved_C


<to be read again>

1

\xs_newlines ->\unexpanded {}\xs_def \xs_arg_i {##1

}

\xs_newmacro_ ...name \xs_myarg }\edef \xs_reserved_C {\unexpanded
\expandafter {\xs_newlines

}\edef \noexpand \xs_call }\edef \xs_reserved_D {...

l.372 \xs_newmacro\StrRemoveBraces{}{1}{1}

{%


<empty file>


You meant to type ## instead of #, right? Or maybe a } was forgotten
somewhere

earlier, and things are all screwed up? I'm going to assume that you meant
##.

I've tried changing the catcode regime, but with no effect.

Don't misunderstand me. I'm aware of ConTeXt capabilities and string
manipulation via Lua. My question is more like: "Why doesn't xstring.tex?"

Sorry if my question is outside the scope of ConTeXt
developers/maintainers. Thank you very much.

Jairo :)

[-- Attachment #1.2: Type: text/html, Size: 2415 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2020-07-07 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 18:40 Jairo A. del Rio [this message]
2020-07-07 18:53 ` Phelype Oleinik
2020-07-07 20:08   ` Jairo A. del Rio
2020-07-07 20:19   ` Wolfgang Schuster
2020-07-07 20:25     ` Phelype Oleinik
2020-07-07 21:21     ` Jairo A. del Rio
2020-07-07 21:30       ` Phelype Oleinik
2020-07-07 22:00         ` Jairo A. del Rio
2020-07-08 10:15           ` Hans Hagen
2020-07-08 17:47           ` Hans Hagen

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='CAKyqqaa9pq4raMUT43ckJ4bvgxQxCWXAKx9=gCivVmKRJRP6RQ@mail.gmail.com' \
    --to=jairoadelrio6@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).