Re: vim 9.1 does not hide screen when ! command is given

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

On Fri, May 2, 2025 at 8:04 PM Riza Dindir <[email protected]> wrote:

> 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
>
>
> On Fri, May 2, 2025 at 6:03 PM Christian Brabandt <[email protected]>
> wrote:
>
>> Can you show the output of `:version` for both versions?
>>
>> Thanks,
>> Chris
>>
>> On Fri, 02 May 2025, Riza Dindir wrote:
>>
>> > And my XTERM value is xterm-256color, which did not change...
>> >
>> > On Fri, May 2, 2025 at 5:42 PM Riza Dindir <[email protected]>
>> wrote:
>> >
>> >     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
>> >
>> >     On Fri, May 2, 2025 at 12:57 PM Christian Brabandt <
>> [email protected]>
>> >     wrote:
>> >
>> >
>> >         On Fri, 02 May 2025, Riza Dindir wrote:
>> >
>> >         > 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?
>> >
>> >         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
>>
>> Mit freundlichen Grüßen
>> Christian
>> --
>> Don't relax!  It's only your tension that's holding you together.
>>
>> --
>> --
>> 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 [email protected].
>> To view this discussion visit
>> https://groups.google.com/d/msgid/vim_use/aBTevXUxGHlEQO1Z%40256bit.org.
>>
>

-- 
-- 
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 [email protected].
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BFzj%2B38Ytf%3Dc31SXxEMmgVeXO-%3DAWfn17%3DsweSPPd9pOA%40mail.gmail.com.