[GH-ISSUE #568] Feature: Run Vim inside a widget #415

Closed
opened 2026-03-04 01:04:47 +03:00 by kerem · 2 comments
Owner

Originally created by @nickw8 on GitHub (Feb 17, 2021).
Original GitHub issue: https://github.com/rivo/tview/issues/568

This is kinda related to issue #164 where I would like to interact with vim, but instead of leaving my go program, opening vim, editing, leaving vim and opening up the go program again, I would just like to have Vim open in one of the widgets so it looks something like this:

Screen Shot 2021-02-17 at 3 14 30 PM

Originally created by @nickw8 on GitHub (Feb 17, 2021). Original GitHub issue: https://github.com/rivo/tview/issues/568 This is kinda related to issue #164 where I would like to interact with vim, but instead of leaving my go program, opening vim, editing, leaving vim and opening up the go program again, I would just like to have Vim open in one of the widgets so it looks something like this: ![Screen Shot 2021-02-17 at 3 14 30 PM](https://user-images.githubusercontent.com/1335600/108275255-521f8400-7133-11eb-93cf-a95962f1fac4.png)
kerem closed this issue 2026-03-04 01:04:47 +03:00
Author
Owner

@rivo commented on GitHub (Feb 20, 2021):

It's unlikely this is going to be part of tview any time soon. This would require reimplementing a lot of control sequences that vim uses to draw its screen and tcell (on which tview is built) follows a very different model. This cannot be mapped easily. I already implemented ANSI colouring sequences (which was a lot of work already) so you can at least pipe some coloured output into tview but making it interactive is a whole different ballgame.

If someone familiar with this can demonstrate that the whole thing can be done with just a few simple escape sequences, I might look at it and put it on the roadmap. But if that's not the case, you're probably better off using screen or tmux or suspend your application to make edits.

<!-- gh-comment-id:782754826 --> @rivo commented on GitHub (Feb 20, 2021): It's unlikely this is going to be part of `tview` any time soon. This would require reimplementing a lot of control sequences that `vim` uses to draw its screen and `tcell` (on which `tview` is built) follows a very different model. This cannot be mapped easily. I already implemented ANSI colouring sequences (which was a lot of work already) so you can at least pipe some coloured output into `tview` but making it interactive is a whole different ballgame. If someone familiar with this can demonstrate that the whole thing can be done with just a few simple escape sequences, I might look at it and put it on the roadmap. But if that's not the case, you're probably better off using `screen` or `tmux` or suspend your application to make edits.
Author
Owner

@rivo commented on GitHub (Mar 13, 2021):

A quick note before I close this issue: Please fill out #578, I've put this request in the wish list you can vote for.

<!-- gh-comment-id:798788596 --> @rivo commented on GitHub (Mar 13, 2021): A quick note before I close this issue: Please fill out #578, I've put this request in the wish list you can vote for.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tview#415
No description provided.