What about prepending the line numbers on the way into [text]?
From: Pd-list on behalf of Derek Kwan
Sent: 05 December 2016 03:48
To: pd-list@lists.iem.at
Subject: [PD] [text] editor window line numbers?
Hi list,
Is there an "easy" way of getting line numbers
Hi list,
Is there an "easy" way of getting line numbers in the editor window for
[text] (the one that pops up with the "click" method), perhaps via tcl
plugin or adding/editing methods in pdtk_textwindow.tcl? It'd be
particularly helpful in jumping to specific line numbers when using
[text sequenc
> The character is not invisible. In an editor it manifests with an endline
> plus an indentation in the following line which actually visually helps parse
> things out inside a plaintext file like .pd.
I think the example you mentioned, while possible, is contrived because if a
user is read
To make things clearer, I should have written "canvas" instead of "window".
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
Hello list,
I wanted to know if someone ever managed to make a Pd window scroll (or
pan) using a Pd patch, or a plugin that is activated by Pd. I don't know
enough from Tcl/Tk to try it myself.
Best,
jmmmp
___
Pd-list@lists.iem.at mailing list
UNSUBSCR
2016-12-03 23:27 GMT-02:00 Jonathan Wilkes :
> Why not just use the built-in comment?
>
So, why use cyclone/comment instead of pd’s comment?
It does offer advantages as it is, such as setting a different font type,
different font size and colors. It is still not updated to the latest
version
The character is not invisible. In an editor it manifests with an
endline plus an indentation in the following line which actually
visually helps parse things out inside a plaintext file like .pd.
I think the example you mentioned, while possible, is contrived because
if a user is reading a co
> What about people parsing Pd files in Pd? If they're searching for symbol
> "foo", are they going to have to deal with the edge case of symbol "foo\v"?
Ivica,Just to give an example-- suppose someone is using a patch to store
configuration data for their project. They type the config data a
This only pertains to comments and as such should not make any
difference elsewhere (unless you want to live-code something by hacking
comments :-). Also, Pd-L2Ork inherited from extended search in patch
option that offers match full or a subset of a string which should cover
all the cases.
Please excuse this question not entirely being related to Pure Data.
If i feed values 0-1 from linear [hsl] into either
[expr sqrt(1-$f1); sqrt($f1)]
or
[expr cos(1.57 * $f1); sin(1.57 * $f1)]
i essentially get the same set of output values, but with different input
values. Obviously 0.5 puts
On 12/04/2016 07:57 PM, Jonathan Wilkes via Pd-list wrote:
> [11(|[makefilename %c]|[symbol foo$1(|[select foo]|[bng]
ah, i misread your question - i was thinking of regexes (parsing the
file outside of Pd)
Pd itself doesn't provide any ways to *search* for a string; the best
you can get is to it
From: IOhannes m zmölnig
To: pd-list@lists.iem.at
Sent: Sunday, December 4, 2016 1:48 PM
Subject: Re: [PD] cyclone comment and cross platform (was Re: Purr Data rc1)
On 12/04/2016 07:13 PM, Jonathan Wilkes via Pd-list wrote:
>> If they're searching for symbol "foo", are they going
On 12/04/2016 07:13 PM, Jonathan Wilkes via Pd-list wrote:
> If they're searching for symbol "foo", are they going to have to deal with
> the edge case of symbol "foo\v"?
hmm, how does "foo" not match "foo\v"?
grdsa
IOhannes
signature.asc
Description: OpenPGP digital signature
__
On 12/04/2016 03:10 AM, Liam Goodacre wrote:
> Spaces work in labels in L2Ork because they are escaped with a backslash. But
> this is creating an incompatibility with Vanilla, which then can't read the
> object's properties.
are you sure?
my impression is, that Pd can parse any labels with back
> Another thing that pd-l2ork's comment does that makes it theoretically
> incompatible with vanilla, it recognizes line breaks and saves them. It uses
> ASCII 11 to save it into the .pd file which is vertical tab that is by and
> large unused. While vanilla shows line breaks when creating an ob
Another thing that pd-l2ork's comment does that makes it theoretically
incompatible with vanilla, it recognizes line breaks and saves them. It
uses ASCII 11 to save it into the .pd file which is vertical tab that is
by and large unused. While vanilla shows line breaks when creating an
object, c
16 matches
Mail list logo
