From: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Console serial terminal/console with command history?
Date: Tue, 22 May 2018 21:00:30 +0200 [thread overview]
Message-ID: <167a8349-19c2-1a00-149e-4fc5f244f88e@alstadheim.priv.no> (raw)
In-Reply-To: <20180522182823.idiggqfrrgaebts2@matica.foolinux.mooo.com>
Den 22. mai 2018 20:28, skrev Ian Zimmerman:
> On 2018-05-22 12:00, Grant Taylor wrote:
>
>> You might also want to check out using vim or emacs as they have
>> terminal emulators built in. They might be able to apply some command
>> line history / editing (in a round about way).
> Indeed, if there isn't a prepackaged way the next easiest is probably
> customizing emacs "comint" mode (which is the base mode behind shell
> mode and various other specialized interpreter modes).
>
Second that, use emacs. Basically you just need to teach emacs to
recognize the prompt. Most likely it will already work.
There are at least three ways to use emacs for this. The best would be
to run emacs on your local machine and then M-x serial-term or M-x
shell. ('M' stands for meta, usually means you can push the 'alt' key
together with a letter, but there are other ways if you have no alt key,
like on a serial connection) . Third way would be to run emacs in text
mode on the remote machine. If you have ssh running on the remote
machine, check out the "tramp" package in emacs.
With no gui, you would need to learn the old tty-commands in emacs, like
push <esc> followed by 'x' instead of using ALT-x, but it should all be
there.
Pro-tip: if running emacs on the remote machine, make sure your
terminal-connection does not interpret Control-S as a STOP signal, i.e.
anything to do with XON/XOFF you do NOT want enabled in your
shell-connection.
next prev parent reply other threads:[~2018-05-22 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 17:39 [gentoo-user] Console serial terminal/console with command history? tuxic
2018-05-22 17:54 ` Grant Taylor
2018-05-22 18:00 ` Grant Taylor
2018-05-22 18:28 ` [gentoo-user] " Ian Zimmerman
2018-05-22 19:00 ` Håkon Alstadheim [this message]
2018-05-22 19:07 ` Grant Taylor
2018-05-22 18:45 ` [gentoo-user] " David M. Fellows
2018-05-22 19:09 ` Grant Taylor
2018-05-22 20:39 ` [gentoo-user] " Grant Edwards
2018-05-22 21:10 ` Grant Taylor
2018-05-22 21:21 ` Grant Edwards
2018-05-22 21:06 ` [gentoo-user] " David M. Fellows
2018-05-22 21:14 ` Grant Taylor
2018-05-22 20:43 ` R0b0t1
2018-05-22 21:03 ` Grant Taylor
2018-05-22 21:44 ` R0b0t1
2018-05-22 22:34 ` Grant Taylor
2018-05-22 23:12 ` [gentoo-user] " Grant Edwards
2018-05-23 0:13 ` Grant Taylor
2018-05-23 1:33 ` [gentoo-user] " tuxic
2018-05-23 1:43 ` Grant Taylor
2018-05-23 13:36 ` [gentoo-user] " Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167a8349-19c2-1a00-149e-4fc5f244f88e@alstadheim.priv.no \
--to=hakon@alstadheim.priv.no \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox