From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Trimming strings and Lua string.trim question
Date: Wed, 05 Mar 2014 18:00:59 -0500 [thread overview]
Message-ID: <5317ACAB.4050904@rik.users.panix.com> (raw)
In-Reply-To: <C28C48AF-CC11-44C5-A257-7AB2DD50A3FB@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]
On 2014-03-05 10:54, Wolfgang Schuster wrote:
>
> Am 05.03.2014 um 16:18 schrieb Wolfgang Schuster
> <schuster.wolfgang@gmail.com <mailto:schuster.wolfgang@gmail.com>>:
>
>>
>> Am 05.03.2014 um 16:07 schrieb Rik Kabel <context@rik.users.panix.com
>> <mailto:context@rik.users.panix.com>>:
>>
>>>> striplong
>>>>
>>>
>>> It would be nice if striplong worked, but the example fails when
>>> string.striplong is used in place of string.strip. The log says:
>>>
>>> ! LuaTeX error [string "\directlua "]:1: attempt to call field
>>> 'striplong' (a nil value)
>>> stack traceback:
>>> [string "\directlua "]:1: in main chunk.
>>>
>>> Is the format of the call different than shown in the wiki, or is a
>>> different mechanism required to quote a potentially long string?
>>
>> The name of the function is "strings.striplong".
>
> This should be "utilities.strings.striplong" but it has no effect
> because when take a look
> at the saved string in Lua you can see that blank lines are removed
> from the text.
>
> Wolfgang
Indeed. This does build without error, but the
utilities.strings.striplong result is worse than the string.strip
result, with some additional whitespace at the end of the test string
from the earlier example.
So, is this a confirmed bug?
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 3265 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-03-05 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 4:45 Rik Kabel
2014-03-05 8:24 ` Hans Hagen
2014-03-05 15:07 ` Rik Kabel
2014-03-05 15:18 ` Wolfgang Schuster
2014-03-05 15:54 ` Wolfgang Schuster
2014-03-05 23:00 ` Rik Kabel [this message]
2014-03-06 10:38 ` Hans Hagen
2014-03-06 15:04 ` Rik Kabel
2014-03-06 15:27 ` Wolfgang Schuster
2014-03-05 16:28 ` Rik Kabel
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=5317ACAB.4050904@rik.users.panix.com \
--to=context@rik.users.panix.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).