Line editing & history problem
See original GitHub issueTrying to scroll through history lines, the 1st line is not displayed until hitting the up key again or CTRL-L
.
While edititing a line, the cursor often is displaced by 1 position, again CTRL-L
helps.
This happens while being connected serially or over websocket running mpfshell
in an xterm
with screen
.
It does not happen when connecting using webrepl.html or using screen /dev/ttyUSB0 115200
inside the same xterm
like above.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
zsh command line editing problems when reverse-searching ...
In zsh, using oh-my-zsh and the robby-russell theme, under Fedora Core 23, I noticed that when I reverse-searched for commands in the command ......
Read more >What is Line Editing and How Can It Help Your Book?
Line editing is a part in the book editing process where the editor aims to improve the clarity of a piece of writing....
Read more >Using history and command line editing | Computerworld
History is more than just the ability to recall previous commands; it lets you recall commands and edit them before they are executed....
Read more >10 Things To Look Out For When Line Editing by Adriana ...
1. Make sure your sentences make sense · 2. Syntax should be easy to follow and understand · 3. Eliminate any words that...
Read more >Strange line editing behavior on darwin Apple Silicon #162
When I use ghci I'm finding issues when trying to edit the current line with the standard Emacs shortcut keys, C-a M-f ,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is a fix for this problem in pyserial/miniterm. It’s not yet part of an official release but you can get the patched version of miniterm.py here
https://github.com/pyserial/pyserial/blob/cab3dabc81ecbf010d81ff38433db99c1f6d667c/serial/tools/miniterm.py
I consider this bug fixed.
Final remark: On March 8th the patch has been released as part of the official version 3.3 of pyserial. There is no longer a need to download miniterm.py - just updated the package with pip (or your favorite package manager).