mirror of
https://github.com/rivo/tview.git
synced 2026-04-26 21:35:54 +03:00
[GH-ISSUE #746] ANSI writer - cursor movement to history #547
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tview#547
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dcrystalj on GitHub (Jul 18, 2022).
Original GitHub issue: https://github.com/rivo/tview/issues/746
I would like to have an option to move cursor back and forth? just like writing to terminal does.
Can ansi writer modify something that was already written with characters like
\ror\b? If I am redirecting terminal output to ANSI writer a lot of things are broken because of this.for example writing
\bcharacter should move cursor one char back, so effectively next written character should override the last one.@rivo commented on GitHub (Aug 11, 2022):
The ANSI writer will convert basic text and colour escape codes. But it won't translate any control sequences. In short, piping another program's output into
tviewis doable in many cases, but running another interactive application insidetviewis not possible. At this point,tviewis not like tmux/screen.Btw, this is one of the suggested (major) features in the questionnaire (#578) but demand for it is low. There are other features that seem to be much more important to many users.
@dcrystalj commented on GitHub (Aug 13, 2022):
ok, thank you. Currently I am using tview to display other programs output and it's quite annoying when there is some kind of loading.
I have submitted the questionnaire now, but didn't know that there was any. Maybe you should consider linking it in root readme.md to get more realistic feedback?
I hope this feature will eventually be added to tview 🙏
@rivo commented on GitHub (Aug 13, 2022):
The questionnaire was pinned to the top of the issues page for quite a long time. I think I have a good idea now what people need. I might post an updated questionnaire at some point.