Re: vim and FORTH-"IDE"-ish environment

Hi Jason,

thanks a lot. That's really neat! :)

What's about the other way around: How can get something
like the serial terminal inside vim?

Thanks a lot in advance!
Cheers!
Meino



On 05/29 12:39, Jason Felice wrote:
> In Vim, it should be as easy as `:w /dev/ttyACM0`, and you could map
> something like so: `nmap <F12> :w /dev/ttyACM0<CR>`.
>
> On Tue, May 29, 2018 at 12:24 PM, <tuxic@posteo.de> wrote:
>
> > Hi,
> >
> > (I am on Linux.)
> >
> > just for fun, entertainment and doing something new, I installed
> > Mecrisp-Stellaris FORTH on a STM32F103C8T6 ( aka "Blue Pill" )
> > micorcontroller board.
> >
> > FORTH is interactive (has a REPL) and is a interpretive
> > (interpretative?) and compiler language at the same time.
> >
> > For ceating new compiled code on the microcontroller is
> > as easy as cat-ting the sourcecode this way:
> >
> > cat sourcecode.fs > /dev/ttyACM0
> >
> > Now you can execute your program via the prompt you get
> > with a serial terminal which is connected via /dev/ttyACM0.
> >
> > But what has all this to do with vim?
> >
> > I want to write code in FORTH with vim (what else? ;), send
> > the code to the microcontroller and - if possible - want to
> > replace the extern console of the serial terminal with something
> > inside vim. I not neccessarily want to avoid the serial terminal --
> > I want to avoid the "external"...the switching between windows.
> >
> > I found some rudimentary attempts of something like that (still
> > in need of an external something), which call 'cat' to transfer
> > the code to the microprocessor.
> > But those posts are from a long time ago.
> >
> > Since vim got tasks and pipes and subprocesses I would like to ask
> > for some keywords or pointers to start with to acchieve what I have
> > described above.
> >
> > Where should I start while trying to read the wheel a second time...?
> > :)
> >
> > Thank you very much in advance for any help!
> > Cheers!
> > Meino
> >
> >
> > --
> > --
> > You received this message from the "vim_use" maillist.
> > Do not top-post! Type your reply below the text you are replying to.
> > For more information, visit http://www.vim.org/maillist.php
> >
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "vim_use" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to vim_use+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.