ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: juh+ntg-context@mailbox.org
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: configuring spitter
Date: Tue, 8 Oct 2024 20:29:06 +0200	[thread overview]
Message-ID: <7b66d299-2940-1986-5112-ec8d760ff9c9@gmail.com> (raw)
In-Reply-To: <1ce07c87-f799-4e3a-952e-06670c14f0d9@mailbox.org>

juh+ntg-context@mailbox.org schrieb am 08.10.2024 um 20:10:
> Am 08.10.24 um 19:16 schrieb Wolfgang Schuster:
>> You can change the separator when you create a custom splitter.
>>
>> local csvsplitter = utilities.parsers.rfc4180splitter{ separator = ";" }
> 
> Thanks a lot.
> 
> Just curious. I often wonder in pure ConTeXt when to use curly bracets 
> and when square brackets
> 
> In this lua code I would think we would need simple rounded ones.
> 
> Like in your first example where you call the splitter without options:
> 
> local csvsplitter = utilities.parsers.rfc4180splitter()
> 
> I am sure that this is some lua convention, but, nevertheless, it 
> puzzles me.


It's explained in the Lua manual:

%%%% begin quotation
Lua 5.4 Reference manual

[...]

3.4.10 -- Function calls

[...]
A call of the form f{fields} is syntactic sugar for f({fields}); that 
is, the argument list is a single new table.
[...]
%%%% end quotation

Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-10-08 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  7:48 [NTG-context] separatedlist with header repeating processing csv to table juh+ntg-context--- via ntg-context
2024-10-02 11:49 ` [NTG-context] " Henning Hraban Ramm
2024-10-02 12:29   ` Henning Hraban Ramm
2024-10-03  8:49     ` juh+ntg-context--- via ntg-context
2024-10-03 10:06       ` vm via ntg-context
2024-10-03 12:15       ` Wolfgang Schuster
2024-10-03 14:33         ` vm via ntg-context
2024-10-03 16:18           ` Wolfgang Schuster
2024-10-08 16:13         ` [NTG-context] configuring spitter (was: separatedlist with header repeating processing csv to table) juh+ntg-context--- via ntg-context
2024-10-08 17:10           ` [NTG-context] Re: configuring spitter Henning Hraban Ramm
2024-10-08 17:16           ` Wolfgang Schuster
2024-10-08 18:10             ` juh+ntg-context--- via ntg-context
2024-10-08 18:29               ` Wolfgang Schuster [this message]
2024-10-03  8:47   ` [NTG-context] Re: separatedlist with header repeating processing csv to table juh+ntg-context--- via ntg-context

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=7b66d299-2940-1986-5112-ec8d760ff9c9@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=juh+ntg-context@mailbox.org \
    --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).