Change minicom terminal type
For some reason, minicom likes to default to VT102 (I haven't worked with any DEC gear in 35 years). Is there anyway to change to ANSI? According to what I found on the 'net, adding "pu rtscts Yes" to the minirc.dfl file is supposed to make it default to ANSI, but that doesn't seem to work. Even real DEC terminals could be configured to run ANSI. Suggestions? tnx jk
Hello, In the Message; Subject : Change minicom terminal type Message-ID : <cfbdde26-c383-4278-bf5e-34d983bf7fe0@jknott.net> Date & Time: Tue, 14 May 2024 16:40:34 -0400 [JK] == James Knott <james.knott@jknott.net> has written: JK> For some reason, minicom likes to default to VT102 (I haven't worked with any JK> DEC gear in 35 years). Is there anyway to change to ANSI? JK> According to what I found on the 'net, adding "pu rtscts Yes" to JK> the minirc.dfl file is supposed to make it default to ANSI, but JK> that doesn't seem to work. Even real DEC terminals could be JK> configured to run ANSI. In your minicom config file (/etc/minirc.x or .minirc.x) put: pu rtscts Yes where Yes fot ANSI, No for VT102. HTHs. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices — and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
On 5/15/24 05:45, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Change minicom terminal type Message-ID :<cfbdde26-c383-4278-bf5e-34d983bf7fe0@jknott.net> Date & Time: Tue, 14 May 2024 16:40:34 -0400
[JK] == James Knott<james.knott@jknott.net> has written:
JK> For some reason, minicom likes to default to VT102 (I haven't worked with any JK> DEC gear in 35 years). Is there anyway to change to ANSI? JK> According to what I found on the 'net, adding "pu rtscts Yes" to JK> the minirc.dfl file is supposed to make it default to ANSI, but JK> that doesn't seem to work. Even real DEC terminals could be JK> configured to run ANSI.
In your minicom config file (/etc/minirc.x or .minirc.x) put:
pu rtscts Yes
where Yes fot ANSI, No for VT102.
As I mentioned, I did that and it didn't work.
On 5/15/24 05:45, Masaru Nomiya wrote:
In your minicom config file (/etc/minirc.x or .minirc.x) put:
pu rtscts Yes
where Yes fot ANSI, No for VT102.
Here's what it currently is: #more minirc.dfl # Machine-generated file - use "minicom -s" to change parameters. pu port /dev/ttyUSB0 pu baudrate 115200 pu bits 8 pu parity N pu stopbits 1 pu backspace BS pu rtscts Yes
Hello, Sorry for late reply. In the Message; Subject : Re: Change minicom terminal type Message-ID : <fa35395c-7c23-4563-8572-0c61801e66c1@jknott.net> Date & Time: Wed, 15 May 2024 11:07:21 -0400 [JK] == James Knott <james.knott@jknott.net> has written: JK> On 5/15/24 05:45, Masaru Nomiya wrote: MN> > In your minicom config file (/etc/minirc.x or .minirc.x) put: MN> > pu rtscts Yes MN> > where Yes fot ANSI, No for VT102. JK> Here's what it currently is: JK> #more minirc.dfl JK> # Machine-generated file - use "minicom -s" to change parameters. JK> pu port /dev/ttyUSB0 JK> pu baudrate 115200 JK> pu bits 8 JK> pu parity N JK> pu stopbits 1 JK> pu backspace BS JK> pu rtscts Yes The specification has been changed so that what you want should start up as follows; $ minicom -l [DEVICE] Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices — and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
On 5/16/24 00:10, Masaru Nomiya wrote:
The specification has been changed so that what you want should start up as follows;
$ minicom -l [DEVICE]
From man minicom: -l, --ansi Literal translation of characters with the high bit set. With this flag on, minicom will try to translate the IBM line characters to ASCII. Many PC-unix clones will display character cor- rectly without translation (Linux in a special mode, Coherent and SCO). I have tried -l, -l ansi, -l --ansi, --ansi and none of them work. I always get VT102. The only way to get ansi is to go into the menu for terminal settings, to select ansi. What would possess whoever created minicom to not make it a setting that could be set? I guess he worked for DEC and assumed everyone worked on DEC gear. Well, I used to do a lot more on Data General than DEC.
Hello, In the Message; Subject : Re: Change minicom terminal type Message-ID : <133276f1-0cfc-4831-a1e2-5028f1ca6c4f@jknott.net> Date & Time: Thu, 16 May 2024 13:41:54 -0400 [JK] == James Knott <james.knott@jknott.net> has written: [...] MN> > $ minicom -l [DEVICE] JK> From man minicom: [...] JK> I have tried -l, -l ansi, -l --ansi, --ansi and none of them JK> work. I always get VT102. The only way to get ansi is to go into the JK> menu for terminal settings, to select ansi. What would possess JK> whoever created minicom to not make it a setting that could be set? I JK> guess he worked for DEC and assumed everyone worked on DEC gear. JK> Well, I used to do a lot more on Data General than DEC. I don't know when, but this must be the reason for the change; https://flokoe.github.io/bash-hackers-wiki/scripting/terminalcodes/#the-tput... you should avoid using the ANSI codes directly - use the tput command! Regards & Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Distinguish between what is meaningful to me and what is meaningless, and forget what is meaningless to me. This is where individuality comes into play. This is a function that computer cannot perform." -- Shigehiko Toyama (in Japanes) --
participants (2)
-
James Knott -
Masaru Nomiya