micro-editor / micro-editor/micro
Copy/paste, SSH, Tmux
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 putting this here in the hope that it will help others in a similar situation. We're going all in on Micro for our shared cloud development environment and wanted to get copy/paste working well. After reading the micro help docs, stackoverflow etc, we finally came up with the following solution to get Micro over SSH inside tmux all working nicely. We're using Ubuntu on our local machines, as well as on the server:
- close the ssh connection to your remote machine
- create/edit
.ssh/configon your local machine - add the line
ForwardX11 yes - ssh into your remote machine
- install xclip if it isn't already
- close all your tmux sessions; unfortunately the above won't get through to existing sessions
- start a new tmux session
- do a check:
echo "test" | xclipthenxclip -o - likewise, check the 'bridge' with your local machine's clipboard by copying text from a local app like a browser and then running
xclip -oon your remote tmux session - you can also do
echo "something" | xclipand paste it somewhere on your local machine - check copy/paste works inside a single Micro instance by using the stanard Micro copy/paste keybindinds; i.e. ctrl+c, ctrl+v
- check copy/paste works across Micro instances in different tmux panes
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
Start by reviewing the Micro help docs and the SSH, xclip, and tmux workflow described in the issue. Verify the listed clipboard checks on Ubuntu, including Micro keybindings and copying between tmux panes; done means this workaround is documented clearly for similar users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100