micro-editor / micro-editor/micro
Clipboard from SSH
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
I'm sure this isn't a new problem but it is new to me.
I installed micro on Raspberry Pi 4 just this week using:
curl https://getmic.ro | bash
Up to date PI OS and up to date Windows - all works PERFECTLY - and I use the editor in an SSH session from Windows - the clipboard from Windows to the editor is failing completely. Yet on the main MICRO page we see:
As its name indicates, micro aims to be somewhat of a successor to the nano editor by being easy to install and use. It strives to be enjoyable as a full-time editor for people who prefer to work in a terminal, or those who regularly edit files over SSH.
Nano copies and pastes back and forth to Windows no problem..
Ideas?
Specifications
Commit hash:
OS:
Terminal:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a source file or test. First reproduce clipboard transfer from Windows into micro over SSH on the reported Raspberry Pi setup, then trace the terminal clipboard handling involved. Done means Windows clipboard content can be pasted into micro over SSH, with a regression test or documented reproduction if the project supports one.
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
- Needs clarification
- Newbie friendliness
- 25/100