On Tue, 2022-03-29 at 10:55 +0200, Christof Ressi wrote:
>
> How am I supposed to know that
>
> 1 2 3, a b c, foo bar baz;
> actually counts as 3 "lines"?
>
> I think a more proper term would be "message". I think the
> documentation has to be improved. @porres to the rescue!! :-)
+1
Roman
Another side note: it would be nice if a negative field count for
[text get] would output all fields up to the next seperator (comma or semi).
I agree and it does so already.
I don't think so:
1 2 3 a b c d e f;
[0 3 -1( -> [text get]
gives me: "text get: bad field count (-1)"
You cannot _create_ lists ending with a comma, however. I propose a
'type' inlet in [text set] and [text insert], just for completeness and
consistency.
[11 12 13( [2( [1( <- type
| / /
[text insert ]
with above text buffer example would create:
1 2 3, foo bar baz, 11 12 13,
On 28.03.2022 22:43, Roman Haefeli wrote:
```
eins;
zwei;
drei, vier;
fuenf;
```
[text size] returns 5. [2(-[text get] returns 'symbol drei'. The
message after that is accessed with [3(-[text get].
Wow, you're right of course! *big facepalm* In all these years I never
realized that comma
On Sun, 2022-03-27 at 22:39 +0200, Christof Ressi wrote:
> On 27.03.2022 18:22, Christof Ressi wrote:
> > I guess you should be able to do [3 3( -> [text get] to get the
> > second
> > sublist, but [3 4( -> [text get] should probably trigger an
> > out-of-range error.
>
> I meant to write [0 3
On Sun, 2022-03-27 at 18:22 +0200, Christof Ressi wrote:
> > There is no way to get the rest of the message. I think [text get]
> > could simply output all sublists consecutively. By checking the
> > right outlet you know if a message spans a whole line (= 0), or is
> > part of a comma seperated
On Sun, 2022-03-27 at 18:04 +0200, Christof Ressi wrote:
> On 27.03.2022 11:01, Roman Haefeli wrote:
> > On Sun, 2022-03-27 at 01:10 +0100, Christof Ressi wrote:
> > > In my experience, commas in [text] are broken... Best not to use
> > > them
> > > :-)
> >
> > What is the purpose of 'type' in
On 27.03.2022 18:22, Christof Ressi wrote:
I guess you should be able to do [3 3( -> [text get] to get the second
sublist, but [3 4( -> [text get] should probably trigger an
out-of-range error.
I meant to write [0 3 3( -> [text get] and [0 3 4( -> [text get]...
Another side note: it would be
There is no way to get the rest of the message. I think [text get]
could simply output all sublists consecutively. By checking the right
outlet you know if a message spans a whole line (= 0), or is part of a
comma seperated list of messages (= 1).
To be more precise: it should output all
On 27.03.2022 11:01, Roman Haefeli wrote:
On Sun, 2022-03-27 at 01:10 +0100, Christof Ressi wrote:
In my experience, commas in [text] are broken... Best not to use them
:-)
What is the purpose of 'type' in [text] then? I find your advice of not
using a feature because it is broken - frankly -
On Sun, 2022-03-27 at 01:10 +0100, Christof Ressi wrote:
> In my experience, commas in [text] are broken... Best not to use them
> :-)
What is the purpose of 'type' in [text] then? I find your advice of not
using a feature because it is broken - frankly - disconcerting. If it's
broken, then it
In my experience, commas in [text] are broken... Best not to use them :-)
On 26.03.2022 23:20, Roman Haefeli wrote:
Anyone?
Roman
On Tue, 2022-03-22 at 22:33 +0100, Roman Haefeli wrote:
Hi
[text get] has a second outlet for the type of the message. There is
a
distinction between messages
Anyone?
Roman
On Tue, 2022-03-22 at 22:33 +0100, Roman Haefeli wrote:
> Hi
>
> [text get] has a second outlet for the type of the message. There is
> a
> distinction between messages terminated by semicolon and messages
> terminated by comma.
>
> Is there also a way to add messages of
13 matches
Mail list logo
