> > So I noticed that vim has :terminal. I have compiled myself 8.1.0026 and
> > started to experiment. There are two major drawbacks for me and so this
> > email - a plea for considering updating them. I would like to have the
> > ability to modify the terminal contents and I would like the terminal to
> > behave more like regular buffer with regards to text highlight.
> >
> > My use case for running terminal in vim is to run debugging window
> > alongside windows showing source code. I happen to debug core dumps from
> > binaries without debug info so there is lot of hex numbers around. To
> > visually distinguish the "important" hex numbers I use Ingo's beautiful
> > plugin Mark[1]. When I list a stack trace I immediately see the
> > important hex numbers highlighted. In :terminal I can see the highlight
> > only if the terminal is in "normal" mode.
> >
> > Second feature I use is to edit the history of the terminal window.
> > Running debugger commands to investigate core dump I get a lot of output
> > I don't need. Long structures, long stack traces, repeated commands,
> > etc. The buffer can get long and it's difficult to search for what I
> > need. On the other side it's handy to add comments for specific
> > registers, assembly instructions etc.
> >
> > I have in the past hacked myself a clone of ConqueShell which does what I
> > need[2]. I have not been able to merge my changes into ConqueShell
> > itself[3]. I don't remember whether it was that I got no reply from
> > maintainer or they didn't want my changes. It would be great if I could
> > dump my plugin in favor of :terminal as it has it's drawbacks too (slow,
> > can't read text if the cursor is outside of the visible area, funny
> > problems when trying to run 'graphical' things like mc.)
>
> What you ask for is not possible in an interactive terminal.
I do not see why. Both the application executed in :terminal and vim
changing the buffer at the same time. But worth implementing? Probably
not.
> But if the job only does line-by-line input and output, we could
> perhaps separate the area that the job is done with and will never
> change, from the last couple of lines, which the job can change.
That would work for me perfectly. As long as the 'dead' zone has colors
no matter if the buffer is in insert or normal mode.
> This does not even require the terminal feature, works without PTYs.
> That makes it work on MS-Windows better (no need to install winpty).
> I'm looking into adding a "prompt buffer" that does something like this.
That's very generous, thank you!
--
Vlad
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
