Replies: 10 comments
-
|
On Sat, Feb 8, 2025, 04:57 mcctuxic ***@***.***> wrote:
Hi Travis,
previously I used wezterm to run picocom to access my Raspberry Pi Pico 2
W, which runs Zeptoforth to run forth programs I wrote.
(Q: Is this sentence iterative of recursive ? ;) )
The drawback was, that picocom needs some time to connect to the
/dev/ttyACM0, or the terminal needs some time to
understand, what picocom wants or...whatever... it lags before it finally
connects.
I found another GPU-driven terminal, which seems to be better suitable for
this task:
https://ghostty.org/
https://github.com/ghostty-org/ghostty
It is open source, written in ZIG (v0.13.0) and really easy to compile and
quite fast.
One thing: If you want to create a config file for it yourself: Only set
things, you want to change...
The developers, which are quite responsive, pointed me to this, because I
had problems setting some keybindings.
I had redefined the whole default settings a second time....
--
Next week I will hopefully receive my Pimoroni Pico Plus 2 W :)
Cheers!
Have a nice weekend!
With regard to the delay issues, I will note that the upcoming zeptoforth
release, 1.10.0, will contain a new USB CDC console driver for the RP2040
and RP2350 which should fix the USB CDC console (the old USB CDC console
has known issues).
1.10.0 should come out this weekend but if you really do not want to wait
all the changes that are projected to go into it are in the master and
devel branches so you can build it yourself.
Travis
… |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On 02/08 08:26, tabemann wrote:
On Sat, Feb 8, 2025, 04:57 mcctuxic ***@***.***> wrote:
> Hi Travis,
>
> previously I used wezterm to run picocom to access my Raspberry Pi Pico 2
> W, which runs Zeptoforth to run forth programs I wrote.
> (Q: Is this sentence iterative of recursive ? ;) )
>
> The drawback was, that picocom needs some time to connect to the
> /dev/ttyACM0, or the terminal needs some time to
> understand, what picocom wants or...whatever... it lags before it finally
> connects.
>
> I found another GPU-driven terminal, which seems to be better suitable for
> this task:
> https://ghostty.org/
> https://github.com/ghostty-org/ghostty
>
> It is open source, written in ZIG (v0.13.0) and really easy to compile and
> quite fast.
>
> One thing: If you want to create a config file for it yourself: Only set
> things, you want to change...
> The developers, which are quite responsive, pointed me to this, because I
> had problems setting some keybindings.
> I had redefined the whole default settings a second time....
>
> --
>
> Next week I will hopefully receive my Pimoroni Pico Plus 2 W :)
>
> Cheers!
> Have a nice weekend!
>
With regard to the delay issues, I will note that the upcoming zeptoforth
release, 1.10.0, will contain a new USB CDC console driver for the RP2040
and RP2350 which should fix the USB CDC console (the old USB CDC console
has known issues).
1.10.0 should come out this weekend but if you really do not want to wait
all the changes that are projected to go into it are in the master and
devel branches so you can build it yourself.
Travis
>
--
Reply to this email directly or view it on GitHub:
#177 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Hi Travis,
OH WHOW! :) A new release!
I will preheat my flasher to get ready for the new release! 8)
I am quite happy with Ghostty. Wezterm has some other issues like
problems with copy'n'paste which I can avoid this way.
Together with the new driver my console learns to fly, I think... ;)
Another thing:
Is there an example code, how to parse an input string...I assume that
one needs to use the words token-start, token-end and token for that?
Cheers!
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On Sat, Feb 8, 2025 at 10:39 AM mcctuxic ***@***.***> wrote:
On 02/08 08:26, tabemann wrote:
> On Sat, Feb 8, 2025, 04:57 mcctuxic ***@***.***> wrote:
>
> > Hi Travis,
> >
> > previously I used wezterm to run picocom to access my Raspberry Pi
Pico 2
> > W, which runs Zeptoforth to run forth programs I wrote.
> > (Q: Is this sentence iterative of recursive ? ;) )
> >
> > The drawback was, that picocom needs some time to connect to the
> > /dev/ttyACM0, or the terminal needs some time to
> > understand, what picocom wants or...whatever... it lags before it
finally
> > connects.
> >
> > I found another GPU-driven terminal, which seems to be better suitable
for
> > this task:
> > https://ghostty.org/
> > https://github.com/ghostty-org/ghostty
> >
> > It is open source, written in ZIG (v0.13.0) and really easy to compile
and
> > quite fast.
> >
> > One thing: If you want to create a config file for it yourself: Only
set
> > things, you want to change...
> > The developers, which are quite responsive, pointed me to this,
because I
> > had problems setting some keybindings.
> > I had redefined the whole default settings a second time....
> >
> > --
> >
> > Next week I will hopefully receive my Pimoroni Pico Plus 2 W :)
> >
> > Cheers!
> > Have a nice weekend!
> >
>
> With regard to the delay issues, I will note that the upcoming zeptoforth
> release, 1.10.0, will contain a new USB CDC console driver for the RP2040
> and RP2350 which should fix the USB CDC console (the old USB CDC console
> has known issues).
>
> 1.10.0 should come out this weekend but if you really do not want to wait
> all the changes that are projected to go into it are in the master and
> devel branches so you can build it yourself.
>
> Travis
>
> >
>
> --
> Reply to this email directly or view it on GitHub:
>
#177 (comment)
> You are receiving this because you authored the thread.
>
> Message ID: ***@***.***>
Hi Travis,
OH WHOW! :) A new release!
I will preheat my flasher to get ready for the new release! 8)
I am quite happy with Ghostty. Wezterm has some other issues like
problems with copy'n'paste which I can avoid this way.
Together with the new driver my console learns to fly, I think... ;)
Another thing:
Is there an example code, how to parse an input string...I assume that
one needs to use the words token-start, token-end and token for that?
Cheers!
There are a number of ways to parse an input string:
The most common way, if you want just a space/tab/newline-delimited token,
is to call TOKEN ( "token" -- c-addr bytes ). Note that TOKEN will return 0
for bytes if it cannot find a token. Note that no data is copied by this
word, so the returned string is only valid as long as the current contents
of the evaluation buffer is valid.
There is also a convenience word, TOKEN-WORD ( "name" -- word ), which is
equivalent to calling TOKEN FIND except that exceptions are raised if no
token is present or the word by that name cannot be found. Note that it,
like zeptoforth FIND and unlike ANS FIND, returns a word header and not an
xt; to get an xt from the word header one then calls >XT on it.
The third, most difficult way, is to manually parse the evaluation buffer
yourself. There are a number of primitives used to enable this,
particularly SOURCE ( -- eval-buffer-addr eval-size ), which returns the
address of the start of the evaluation buffer and the current size of the
data in the evaluation buffer, and >PARSE ( -- eval-index-addr ), which
returns the address containing the index of the current evaluation point
(which can be modified by the user). About TOKEN-START and TOKEN-END,
TOKEN-START ( -- i ) returns the index of the start of the next
space/tab/newline-delimited token (or end of line if there is no token),
and TOKEN-END ( i1 -- i2 ) takes an index in a space/tab/newline-delimited
token and returns the index of the end of the token.
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12104093@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Zeptoforth runs on a Raspberry Pi Zero 2 W? Did I miss the memo? I have a fair number of them and would love to run Zeptoforth on them. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On Sat, Feb 8, 2025 at 1:05 PM M. Edward (Ed) Borasky < ***@***.***> wrote:
previously I used wezterm to run picocom to access my Raspberry Pi Pico 2
W, which runs Zeptoforth to run forth programs I wrote. (Q: Is this
sentence iterative of recursive ? ;) )
Zeptoforth runs on a Raspberry Pi Zero 2 W? Did I miss the memo? I have a
fair number of them and would love to run Zeptoforth on them.
There is a major difference between a Raspberry Pi Pico 2 W and a Raspberry
Pi Zero 2 W ─ the Pico 2 W is an RP2350 board with a CYW43439 WiFi chip on
it which is supported by zeptoforth, the Zero 2 W is a single-board
computer that zeptoforth does not run on because it is not based on an ARM
Cortex-M microcontroller. BTW, I would recommend getting a Pico 2 W,
because it has 512K of SRAM, which leaves plenty of space for applications
even with the buffers for zeptoIP taken into account (even though I'm still
miffed by the GPIO pad bug in the RP2350 and the RPi people's handling of
it).
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12104787@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On 02/08 08:26, tabemann wrote:
On Sat, Feb 8, 2025, 04:57 mcctuxic ***@***.***> wrote:
> Hi Travis,
>
> previously I used wezterm to run picocom to access my Raspberry Pi Pico 2
> W, which runs Zeptoforth to run forth programs I wrote.
> (Q: Is this sentence iterative of recursive ? ;) )
>
> The drawback was, that picocom needs some time to connect to the
> /dev/ttyACM0, or the terminal needs some time to
> understand, what picocom wants or...whatever... it lags before it finally
> connects.
>
> I found another GPU-driven terminal, which seems to be better suitable for
> this task:
> https://ghostty.org/
> https://github.com/ghostty-org/ghostty
>
> It is open source, written in ZIG (v0.13.0) and really easy to compile and
> quite fast.
>
> One thing: If you want to create a config file for it yourself: Only set
> things, you want to change...
> The developers, which are quite responsive, pointed me to this, because I
> had problems setting some keybindings.
> I had redefined the whole default settings a second time....
>
> --
>
> Next week I will hopefully receive my Pimoroni Pico Plus 2 W :)
>
> Cheers!
> Have a nice weekend!
>
With regard to the delay issues, I will note that the upcoming zeptoforth
release, 1.10.0, will contain a new USB CDC console driver for the RP2040
and RP2350 which should fix the USB CDC console (the old USB CDC console
has known issues).
1.10.0 should come out this weekend but if you really do not want to wait
all the changes that are projected to go into it are in the master and
devel branches so you can build it yourself.
Travis
>
--
Reply to this email directly or view it on GitHub:
#177 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Hi Travis,
I flashed my Pi Picos 2 Ws, that I own, with the new version of
ZeptoForth.
What a difference the new CDC driver is! Ghostty is even more faster!
Thank you very much for all the effort and work you put into this
project! The FORTH is (definitely) with you! :)
Cheers!
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On Sun, Feb 9, 2025 at 12:21 PM mcctuxic ***@***.***> wrote:
On 02/08 08:26, tabemann wrote:
Hi Travis,
I flashed my Pi Picos 2 Ws, that I own, with the new version of
ZeptoForth.
What a difference the new CDC driver is! Ghostty is even more faster!
Thank you very much for all the effort and work you put into this
project! The FORTH is (definitely) with you! :)
Cheers!
Well, I can't exactly take credit for the new USB CDC console driver ─
serialcomms did most of the work on it. Still, you're welcome!
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12110298@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On 02/09 12:07, tabemann wrote:
On Sun, Feb 9, 2025 at 12:21 PM mcctuxic ***@***.***> wrote:
> On 02/08 08:26, tabemann wrote:
> Hi Travis,
>
> I flashed my Pi Picos 2 Ws, that I own, with the new version of
> ZeptoForth.
> What a difference the new CDC driver is! Ghostty is even more faster!
>
> Thank you very much for all the effort and work you put into this
> project! The FORTH is (definitely) with you! :)
>
> Cheers!
>
Well, I can't exactly take credit for the new USB CDC console driver ─
serialcomms did most of the work on it. Still, you're welcome!
Travis
> Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12110298@
> github.com>
>
--
Reply to this email directly or view it on GitHub:
#177 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Hi Travis,
....ZeptoForth does not consists of the new CDC driver alone... :) :) :)
Cheers!
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On Sun, Feb 9, 2025 at 8:22 PM mcctuxic ***@***.***> wrote:
On 02/09 12:07, tabemann wrote:
> On Sun, Feb 9, 2025 at 12:21 PM mcctuxic ***@***.***> wrote:
>
> > On 02/08 08:26, tabemann wrote:
> > Hi Travis,
> >
> > I flashed my Pi Picos 2 Ws, that I own, with the new version of
> > ZeptoForth.
> > What a difference the new CDC driver is! Ghostty is even more faster!
> >
> > Thank you very much for all the effort and work you put into this
> > project! The FORTH is (definitely) with you! :)
> >
> > Cheers!
> >
>
>
> Well, I can't exactly take credit for the new USB CDC console driver ─
> serialcomms did most of the work on it. Still, you're welcome!
>
> Travis
>
> > Message ID:
<tabemann/zeptoforth/repo-discussions/177/comments/12110298@
> > github.com>
> >
>
>
> --
> Reply to this email directly or view it on GitHub:
>
#177 (comment)
> You are receiving this because you authored the thread.
>
> Message ID: ***@***.***>
Hi Travis,
....ZeptoForth does not consists of the new CDC driver alone... :) :) :)
Cheers!
BTW, there's a new release, 1.10.0.1, because I had missed a stupid bug in
the line editor which caused it to crash upon exiting mass upload mode, but
had failed to try out mass upload mode despite having modified the line
editor in a previous version (which had introduced the bug).
Travis
… Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12112705@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On 02/09 08:29, tabemann wrote:
On Sun, Feb 9, 2025 at 8:22 PM mcctuxic ***@***.***> wrote:
> On 02/09 12:07, tabemann wrote:
> > On Sun, Feb 9, 2025 at 12:21 PM mcctuxic ***@***.***> wrote:
> >
> > > On 02/08 08:26, tabemann wrote:
> > > Hi Travis,
> > >
> > > I flashed my Pi Picos 2 Ws, that I own, with the new version of
> > > ZeptoForth.
> > > What a difference the new CDC driver is! Ghostty is even more faster!
> > >
> > > Thank you very much for all the effort and work you put into this
> > > project! The FORTH is (definitely) with you! :)
> > >
> > > Cheers!
> > >
> >
> >
> > Well, I can't exactly take credit for the new USB CDC console driver ─
> > serialcomms did most of the work on it. Still, you're welcome!
> >
> > Travis
> >
> > > Message ID:
> <tabemann/zeptoforth/repo-discussions/177/comments/12110298@
> > > github.com>
> > >
> >
> >
> > --
> > Reply to this email directly or view it on GitHub:
> >
> #177 (comment)
> > You are receiving this because you authored the thread.
> >
> > Message ID: ***@***.***>
>
>
> Hi Travis,
>
> ....ZeptoForth does not consists of the new CDC driver alone... :) :) :)
>
> Cheers!
>
>
BTW, there's a new release, 1.10.0.1, because I had missed a stupid bug in
the line editor which caused it to crash upon exiting mass upload mode, but
had failed to try out mass upload mode despite having modified the line
editor in a previous version (which had introduced the bug).
Travis
> Message ID: <tabemann/zeptoforth/repo-discussions/177/comments/12112705@
> github.com>
>
--
Reply to this email directly or view it on GitHub:
#177 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Hi Travis,
already flashed on my board...:) Thanks a lot for the update!
Cheers!
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Travis,
previously I used wezterm to run picocom to access my Raspberry Pi Pico 2 W, which runs Zeptoforth to run forth programs I wrote.
(Q: Is this sentence iterative of recursive ? ;) )
The drawback was, that picocom needs some time to connect to the /dev/ttyACM0, or the terminal needs some time to
understand, what picocom wants or...whatever... it lags before it finally connects.
I found another GPU-driven terminal, which seems to be better suitable for this task:
https://ghostty.org/
https://github.com/ghostty-org/ghostty
It is open source, written in ZIG (v0.13.0) and really easy to compile and quite fast.
One thing: If you want to create a config file for it yourself: Only set things, you want to change...
The developers, which are quite responsive, pointed me to this, because I had problems setting some keybindings.
I had redefined the whole default settings a second time....
--
Next week I will hopefully receive my Pimoroni Pico Plus 2 W :)
Cheers!
Have a nice weekend!
Beta Was this translation helpful? Give feedback.
All reactions