Pipe terminal buffer to an editor (vim) #11246

Closed
opened 2026-01-31 02:42:28 +00:00 by claunia · 3 comments
Owner

Originally created by @alekstheod on GitHub (Nov 1, 2020).

Description of the new feature/enhancement

Proposed technical implementation details (optional)

Originally created by @alekstheod on GitHub (Nov 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- As a user of the terminal I would like to be able to show the content of the terminal (text after executed commands) in an external editor using only keyboard shortcuts. As I am a vim user I would like to be able to copy-edit the results of of my work in terminal using vim. Similar functionality with what kitty terminal already does with scrollback_pager option. https://sw.kovidgoyal.net/kitty/conf.html This is especially useful when working over ssh and running vim on remote machine but need a possibility to c/p the content of the editor on the local machine without using mouse. --> # Proposed technical implementation details (optional) <!-- Having a function that would forward the buffers content to the defined by user editor -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:42:28 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 2, 2020):

Hey could you give us any more details? Why do you want this feature? How would you expect it to work? How is this different from other open issues on the repo, like:

  • "ability to pipe scrollback buffer to a pager or terminal editor like kitty" #7749
  • "Feature request: export console history as txt" #642

We can't really do anything with a blank issue.

@zadjii-msft commented on GitHub (Nov 2, 2020): Hey could you give us any more details? Why do you want this feature? How would you expect it to work? How is this different from other open issues on the repo, like: * "ability to pipe scrollback buffer to a pager or terminal editor like kitty" #7749 * "Feature request: export console history as txt" #642 We can't really do anything with a blank issue.
Author
Owner

@alekstheod commented on GitHub (Nov 2, 2020):

Hey could you give us any more details? Why do you want this feature? How would you expect it to work? How is this different from other open issues on the repo, like:

* "ability to pipe scrollback buffer to a pager or terminal editor like kitty" #7749

* "Feature request: export console history as txt" #642

We can't really do anything with a blank issue.

Seems to be a /duplicate of #7749
I wanted to ask about exactly this functionality.

@alekstheod commented on GitHub (Nov 2, 2020): > Hey could you give us any more details? Why do you want this feature? How would you expect it to work? How is this different from other open issues on the repo, like: > > * "ability to pipe scrollback buffer to a pager or terminal editor like kitty" #7749 > > * "Feature request: export console history as txt" #642 > > > We can't really do anything with a blank issue. Seems to be a /duplicate of #7749 I wanted to ask about exactly this functionality.
Author
Owner

@ghost commented on GitHub (Nov 2, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 2, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11246