vim 9.1 does not hide screen when ! command is given

50 views
Skip to first unread message

Riza Dindir

unread,
May 2, 2025, 4:29:48 AMMay 2
to vim...@googlegroups.com
Hello

My system recently updated vim (I think to 9.1). I do not know if it was 9.1 before. But on my system it included/includes patches (patch 794 on my system).

I am seeing something that I did not see before.

I am using git using the ! shell escape from within the editor (for status, commit, and push). When I run a ! command, the editor buffer was hidden, and the xterm was displayed. All the commands that were run previously and their results were seen. And a message "Press ENTER or type command to continue" was displayed. This was normal behavior.

But now when I run a ! command, the editor buffer output is not cleared, and the output of the command is overwritten onto the buffer contents, and the "Press ENTER ..." message is displayed. When you press enter, it just displays the buffer again, correctly

This new behavior happens most of the time.

Does anybody have this issue with VIM version 9.1?

Regards
Riza

Christian Brabandt

unread,
May 2, 2025, 5:57:47 AMMay 2
to vim...@googlegroups.com
Did your $TERM value change? Check also your 't_ti' and 't_te' values.
See also :h xterm-screens for an explanation.

Can you compare your :version output for the old and new Vim versions?

Thanks,
Christian
--
An optimist is a man who looks forward to marriage.
A pessimist is a married optimist.

Riza Dindir

unread,
May 2, 2025, 10:42:58 AMMay 2
to vim...@googlegroups.com
Hello Christian

My t_ti and t_te are as such

  t_ti=^[[?1049h^[[22;0;0t
  t_te=^[[?1049l^[[23;0;0t

The old vim version was (9.1.0366) where the patch number is 0366 on my system, the new one is 9.1.0794

Regards,
Riza

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBSXCcqLBHAAmhRx%40256bit.org.

Riza Dindir

unread,
May 2, 2025, 10:45:05 AMMay 2
to vim...@googlegroups.com
And my XTERM value is xterm-256color, which did not change...

Christian Brabandt

unread,
May 2, 2025, 11:03:41 AMMay 2
to vim...@googlegroups.com
Can you show the output of `:version` for both versions?

Thanks,
Chris
Mit freundlichen Grüßen
Christian
--
Don't relax! It's only your tension that's holding you together.

Riza Dindir

unread,
May 2, 2025, 1:05:30 PMMay 2
to vim...@googlegroups.com
I can only get you the current vim version. And it is (obtained using vim --version)

VIM - Vi IMproved 9.1 (2024 Jan 02, compiled May  2 2025 07:05:12)
Included patches: 1-794
Modified by Gentoo-9.1.0794 (RIP Bram)
Compiled by rdindir@localhost
Huge version without GUI.  Features included (+) or not (-):
+acl               +file_in_path      +mouse_urxvt       -tag_any_white
+arabic            +find_in_path      +mouse_xterm       -tcl
+autocmd           +float             +multi_byte        +termguicolors
+autochdir         +folding           +multi_lang        -terminal
-autoservername    -footer            -mzscheme          +terminfo
-balloon_eval      +fork()            +netbeans_intg     +termresponse
+balloon_eval_term +gettext           +num64             +textobjects
-browse            -hangul_input      +packages          +textprop
++builtin_terms    +iconv             +path_extra        +timers
+byte_offset       +insert_expand     -perl              +title
+channel           +ipv6              +persistent_undo   -toolbar
+cindent           +job               +popupwin          +user_commands
+clientserver      +jumplist          +postscript        +vartabs
+clipboard         +keymap            +printer           +vertsplit
+cmdline_compl     +lambda            +profile           +vim9script
+cmdline_hist      +langmap           -python            +viminfo
+cmdline_info      +libcall           -python3           +virtualedit
+comments          +linebreak         +quickfix          +visual
+conceal           +lispindent        +reltime           +visualextra
+cryptv            +listcmds          +rightleft         +vreplace
-cscope            +localmap          -ruby              +wildignore
+cursorbind        -lua               +scrollbind        +wildmenu
+cursorshape       +menu              +signs             +windows
+dialog_con        +mksession         +smartindent       +writebackup
+diff              +modify_fname      +sodium            +X11
+digraphs          +mouse             +sound             +xattr
-dnd               -mouseshape        +spell             +xfontset
-ebcdic            +mouse_dec         +startuptime       -xim
+emacs_tags        +mouse_gpm         +statusline        -xpm
+eval              -mouse_jsbterm     -sun_workshop      +xsmp_interact
+ex_extra          +mouse_netterm     +syntax            +xterm_clipboard
+extra_search      +mouse_sgr         +tag_binary        -xterm_save
-farsi             -mouse_sysmouse    -tag_old_static    
   system vimrc file: "/etc/vim/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
 3rd user vimrc file: "~/.config/vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: x86_64-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=native -O2 -pipe -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -L/usr/local/lib -o vim -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lcanberra -lsodium -lacl -lattr -lgpm


--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBTevXUxGHlEQO1Z%40256bit.org.

Riza Dindir

unread,
May 2, 2025, 11:33:09 PMMay 2
to vim...@googlegroups.com
Hello All,

When I first start up my xterm and open a file and issue a "!git status" I get the screen in the attachment.

But when I run the "!ls -al" command that has output that will exceed the terminal window height, or if I run "!clear" before any commands, then it will show the terminal window  and will not look like it is overwriting the buffer view content.

I am not sure why this happens. Maybe because of some patches that my system is adding to VIM, or something in the configuration changed.

Regards
Riza
2025-05-03_973x628.png
2025-05-03_994x629.png

Riza Dindir

unread,
May 3, 2025, 1:43:57 AMMay 3
to vim...@googlegroups.com
Hello

I have moved some of my mappings to use functions and commands. In some of those functions I was doing a :redraw! at the end of the function. After that when I did a "!git status" in the editor I was getting the screen inconsistency. I have rewritten the functions that I have so that I do not use a redraw. Now the issue seems to be resolved.

Regards
Riza

jr

unread,
May 3, 2025, 6:08:32 AMMay 3
to vim...@googlegroups.com
hi,

On Sat, 3 May 2025 at 06:43, Riza Dindir <riza....@gmail.com> wrote:
> ... I was doing a :redraw! at the end of the function. ... Now the issue seems to be resolved.

good info, thanks.

--
regards, jr.

You have the right to free speech, as long as you're not dumb enough
to actually try it.
(The Clash 'Know Your Rights')

this email is intended only for the addressee(s) and may contain
confidential information. if you are not the intended recipient, you
are hereby notified that any use of this email, its dissemination,
distribution, and/or copying without prior written consent is
prohibited.
Reply all
Reply to author
Forward
0 new messages