micro-editor / micro-editor/micro
Output pane
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
I like how Zachary solved showing keybindings using Alt+G shortcut. Not because I need these shortcuts, but it reminds me the output window in Sublime Text. What if micro would have such output pane? Where command outputs by example build results instead of switching to terminal?
I have something like "runner" plugin, this is part of it:
function mode1()
local buf = CurView().Buf -- The current buffer
if buf:FileType() == "go" then
HandleShellCommand("go run " .. buf.Path, true, true)
elseif buf:FileType() == "php" then
HandleShellCommand("php " .. buf.Path, true, true)
elseif buf:FileType() == "tcl" then
HandleShellCommand("jimsh " .. buf.Path, true, true)
elseif buf:FileType() == "lisp" then
HandleShellCommand("newlisp " .. buf.Path, true, true)
elseif buf:FileType() == "lua" then
HandleShellCommand("lua " .. buf.Path, true, true)
end
end
Than I run appropriate program using shortcut:
"Alt-r": "Save,runner.mode1"
Having scrollable output directly in micro pane would be perfect. It works particularly when I set openTerm param to false but whole output is in single line (in command line)
As a bonus horizontal or vertical orientation of the output pane would be configurable.
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 reading the runner plugin example, especially HandleShellCommand and the openTerm behavior, then inspect how micro currently displays command output. Done would mean a scrollable output pane integrated into micro, with configurable horizontal or vertical orientation, without switching to a terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, lua
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100