Instructions: Replace the template text and remove irrelevant text (including this line)
Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Currently vimtex uses vim -v --not-a-term -T dumb -c … to invoke some function as needed. This is invoked inside zathura.
However, if you run in bash
command vim -v --not-a-term -T dumb -c "quitall!" < /dev/null # mess the terminal up
(the terminal is set to raw mode or something.)
Apparently when both stdin and stderr are redirected to /dev/null then it's fine.
command vim -v --not-a-term -T dumb -c "quitall!" < /dev/null 2> /dev/null # okay
command vim -v --not-a-term -T dumb -c "quitall!" 2> /dev/null # okay
Describe the solution you'd like
Vim should return the terminal to normal on exit, or otherwise it should not put the terminal to raw mode in the first place.
Related: #3313
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
(the terminal is set to raw mode or something.)
What does that mean exactly?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Means when I type subsequent bash commands, nothing appears (if I type reset then press enter then things are fixed but I don't see the reset itself.)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
hm, strange. And why are you redirecting stdin? Why not echo | command vim -v --not-a-term -T dumb -c "quitall!"
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
It wasn't exactly something I control, zathura is spawned by vimtex with stdin closed (I think).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()