ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trimming strings and Lua string.trim question
Date: Thu, 6 Mar 2014 16:27:44 +0100	[thread overview]
Message-ID: <B18C6039-AC4D-4A3C-B1DE-5F8FA27C9C3E@gmail.com> (raw)
In-Reply-To: <53188E93.9060408@rik.users.panix.com>


Am 06.03.2014 um 16:04 schrieb Rik Kabel <context@rik.users.panix.com>:

> Could you please ensure that this handles text in buffers the same way that it handles other strings? I noticed that this is handled a bit differently, as the following shows,but perhaps it is my clumsy coding. The buffer result is closer to what I expect in terms of internal whitespace, but still does not show expected trimming of leading and trailing whitespace. That trimming, of course, is the point of the exercise.

This can’t work because \getbuffer is a unexpandable command and what you pass to Lua is the string

  \getbuffer[testbuffer]

and not the content of the buffer. When you want to manipulate the content of a buffer you have to access the content at the Lua side with the buffers.getcontent(…) function.

BTW: You don’t need \long in MkIV because definitions use it by default.

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
___________________________________________________________________________________


  reply	other threads:[~2014-03-06 15:27 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
2014-03-06 10:38           ` Hans Hagen
2014-03-06 15:04             ` Rik Kabel
2014-03-06 15:27               ` Wolfgang Schuster [this message]
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=B18C6039-AC4D-4A3C-B1DE-5F8FA27C9C3E@gmail.com \
    --to=schuster.wolfgang@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).