micro-editor / micro-editor/micro

Copy/Paste Breaks Between Micro and External Program

Open
#2,146 3 comments 6 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

There are several situations where Micro's copy-paste support apparently fails, especially when attempting to copy from or paste to locations outside the terminal, such as copying from a webpage or pasting to an external text editor.

Case 1 | From: Micro | To: Micro | Result: works for both Shift/Ctrl+Ins and Ctrl+C/V
Case 2 | From: Terminal Window | To: Micro | Result: works only for Shift/Ctrl+Ins (terminal only supports that shortcut)
Case 3 | From: External Program (eg, webpage) | To: Micro | Result: works only for Shift+Ins on paste; works for Ctrl+C or Ctrl+Ins on copy
Case 4 | From: Terminal Window | To: External Program | Result: works only for Ctrl+Ins on copy; works for either on paste
Case 5 | From: Micro | To: External Program | Result: Does not work for any shortcut
Case 5 | From: Micro | To: Terminal Window | Result: Does not work for any shortcut

Cases 3 and 5 are the most frustrating. It's easy to imagine cases where I might want to copy text from files in Micro to paste elsewhere, especially since I use Micro on a remote machine and direct downloading of files is a hassle. Since Micro promises access to the system clipboard, I'm annoyed that it seems to break when I want to copy text from Micro to anywhere else.

This occurs regardless of whether or not I set the "clipboard" setting to external or terminal.

Specifications

Clarification on specs: I use my home PC running Win10 with Git Bash for Windows to ssh in to the Stampede2 supercomputer, which runs CentOS 7. I have micro installed to my home directory on Stampede2 and use it to edit code to be run there.

Commit hash: 6bc498e6
OS (local machine): Windows 10 Build 19042
OS (ssh machine): CentOS Linux 7 (Core)
Terminal: Git Bash for Windows (xterm-256 mode)

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 file or test is named. Reproduce Cases 3 and 5 using the reported Windows 10 Git Bash to CentOS 7 SSH setup, comparing the terminal and external clipboard settings at commit 6bc498e6. Trace Micro's clipboard handling and verify that copying from Micro reaches both external programs and terminal windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.