micro-editor / micro-editor/micro

CTRL+S not working under `screen`

Open
#2,102 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
29.6k
Forks
1.4k
Avg merge
2d 18h
Merged PRs (30d)
10

Description

Description of the problem or steps to reproduce

CTRL+S, CTRL+Q not working with my setting -- The machine is WSL within Win10, and I'm using screen within xterm

I believe that CTRL+S / CTRL+Q are still treated as its original meaning in xterm, i.e., pause / unpause, because they're behaving like that.

Specifications

$ echo $TERM
screen

$ apt-cache policy micro
micro:
  Installed: 2.0.8-1+b3
  Candidate: 2.0.8-1+b3
  Version table:
 *** 2.0.8-1+b3 100
         80 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.6-2~bpo10+1 100
        100 http://ftp.debian.org/debian buster-backports/main amd64 Packages

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Terminal: screen within xterm.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. First reproduce the shortcut behavior in micro running inside screen with TERM=screen, then trace the terminal input handling; done means CTRL+S and CTRL+Q work as editor shortcuts without being intercepted as terminal flow control.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.