* * * a bit long and ranty. Please disregard. ;)
I need Octal support so some formatting exceeds a reasonably wide
terminal margin. I think the Octal hexdump is approaching idk 92
characters in terminal width. I tried to rework that format - I think
it should stand as-is. Terminal itself needs to be wider.
In Linux I already routinely run a terminal to 105 characters by 27 lines.
If I need /dev/ttyACM0 support, I go with 'picocom' in Linux, with a
fairly elaborate setup script to flip the preferred command line switches.
I've used Plan 9 from Bell Labs (
9front.org variant) as a terminal for
other projects, and I like it over something like Raspbian (both run on
RPi4 just fine).
So basically, I'm running an operating system that generates 'windows'
(usually, not always) as its main user interface, and then run a 'shell'
in that window, and then probably run a telecom program such as
hyperterm, procomm, seyon, minicom, TeraTerm, putty .. or my preferred
picocom).
I have used the built-in terminal but it's got that front porch back
porch issue (text shifted off-screen and cannot fix from the LCD setup
menus on the display, so is a no-starter - another display works and
represents all text on-screen but isn't the display I want to work with
- also no copy and paste support at all using that environment, and I'm
not into self-torture for no gain what-so-ever, so I want my copy and
paste function for 'out of band' access to stuff I want to send to the
Altair-Duino.
And in that regard, picocom leverages the ascii-xfr (ascii transfer)
program of 'minicom' in Linux and uses it to ascii upload things like
the contents of a .HEX file, to the A-D. That's a must-have, for my
workflow.
On 9/11/22 04:00, Eightbitswide wrote:
> I'm new to this with having only completed the Altair Sim build a week
> ago.
> I'm testing various options to do VT100 terminal and for the moment have
> settled on the Marco Maccaferri <
https://github.com/maccasoft> build
> of the VT100 terminal for the RC2014
> computer. It's the closest I've come to a decent terminal which can
> be contained
> in the box with the rest of the simulator.
>
> I'm curious what others have come up with for terminals to connect?
> I'm seeing pi zero, PIC, and even pi-pico solutions. Or do folks tend
> to go old school
> and connect to real hardware?
>
> 8b
>
> --
> You received this message because you are subscribed to the Google
> Groups "Altair-Duino" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
altair-duino...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/altair-duino/7c94de23-29a4-4cfd-ba1e-4ab838b2e6f7n%40googlegroups.com
> <
https://groups.google.com/d/msgid/altair-duino/7c94de23-29a4-4cfd-ba1e-4ab838b2e6f7n%40googlegroups.com?utm_medium=email&utm_source=footer>.
On 9/11/22 04:00, Eightbitswide wrote:
> I'm new to this with having only completed the Altair Sim build a week
> ago.
> I'm testing various options to do VT100 terminal and for the moment have
> settled on the Marco Maccaferri <
https://github.com/maccasoft> build
> of the VT100 terminal for the RC2014
> computer. It's the closest I've come to a decent terminal which can
> be contained
> in the box with the rest of the simulator.
>
> I'm curious what others have come up with for terminals to connect?
> I'm seeing pi zero, PIC, and even pi-pico solutions. Or do folks tend
> to go old school
> and connect to real hardware?
>
> 8b
>
> --
> You received this message because you are subscribed to the Google
> Groups "Altair-Duino" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
altair-duino...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/altair-duino/7c94de23-29a4-4cfd-ba1e-4ab838b2e6f7n%40googlegroups.com
> <
https://groups.google.com/d/msgid/altair-duino/7c94de23-29a4-4cfd-ba1e-4ab838b2e6f7n%40googlegroups.com?utm_medium=email&utm_source=footer>.