On 12:33 Wed 28 May 2025, Ven Tadipatri wrote:
>How do I see what plugin is opening the csv file and open
>it using the raw format (or if possible, fix the plugin)?
>
>call vundle#begin()
>Plugin 'VundleVim/Vundle.vim'
>Plugin 'preservim/nerdtree'
>Plugin 'ctrlpvim/ctrlp.vim'
>Plugin 'airblade/vim-gitgutter'
>Plugin 'tpope/vim-surround'
>Plugin 'tpope/vim-fugitive'
>Plugin 'sheerun/vim-polyglot'
>Plugin 'cosminadrianpopescu/vim-sql-workbench'
>Plugin 'unkiwii/vim-nerdtree-sync'
>call vundle
Thursday, May 29, 2025
Wednesday, May 28, 2025
Re: Vim plugin for csv files
On Wed, 28 May 2025, Ven Tadipatri wrote:
> Hi,
> When I open up CSV files with vim, I get an error message:
>
> CSV Syntax:Invalid column pattern, using default pattern \%([^,]*,\|$\)
>
> CSV Syntax:Or ftplugin hasn't been sourced before the syntax script
>
> But I don't see any plugins in my vimrc that could be causing this. How do I see what plugin is opening the csv file and open it using the raw
> format (or if possible, fix the plugin)?
>
>
> call vundle#begin()
> Plugin 'VundleVim/Vundle.vim'
> Plugin 'preservim/nerdtree'
> Plugin 'ctrlpvim/ctrlp.vim'
> Plugin 'airblade/vim-gitgutter'
> Plugin 'tpope/vim-surround'
> Plugin 'tpope/vim-fugitive'
> Plugin 'sheerun/vim-polyglot'
> Plugin 'cosminadrianpopescu/vim-sql-workbench'
> Plugin 'unkiwii/vim-nerdtree-sync'
> call vundle
> Hi,
> When I open up CSV files with vim, I get an error message:
>
> CSV Syntax:Invalid column pattern, using default pattern \%([^,]*,\|$\)
>
> CSV Syntax:Or ftplugin hasn't been sourced before the syntax script
>
> But I don't see any plugins in my vimrc that could be causing this. How do I see what plugin is opening the csv file and open it using the raw
> format (or if possible, fix the plugin)?
>
>
> call vundle#begin()
> Plugin 'VundleVim/Vundle.vim'
> Plugin 'preservim/nerdtree'
> Plugin 'ctrlpvim/ctrlp.vim'
> Plugin 'airblade/vim-gitgutter'
> Plugin 'tpope/vim-surround'
> Plugin 'tpope/vim-fugitive'
> Plugin 'sheerun/vim-polyglot'
> Plugin 'cosminadrianpopescu/vim-sql-workbench'
> Plugin 'unkiwii/vim-nerdtree-sync'
> call vundle
Re: Vim plugin for csv files
On Wed, May 28, 2025, 11:34 AM Ven Tadipatri <vtadipatri@gmail.com> wrote:
Hi,When I open up CSV files with vim, I get an error message:CSV Syntax:Invalid column pattern, using default pattern \%([^,]*,\|$\)
CSV Syntax:Or ftplugin hasn't been sourced before the syntax script
But I don't see any plugins in my vimrc that could be causing this. How do I see what plugin is opening the csv file and open it using the raw format (or if possible, fix the plugin)?
It would be sheerun/vim-polyglot, I think.
call vundle#begin()
Plugin 'VundleVim/Vundle.vim'
Plugin 'preservim/nerdtree'
Plugin 'ctrlpvim/ctrlp.vim'
Plugin 'airblade/vim-gitgutter'
Plugin 'tpope/vim-surround'
Plugin 'tpope/vim-fugitive'
Plugin 'sheerun/vim-polyglot'
Plugin 'cosminadrianpopescu/vim-sql-workbench'
Plugin 'unkiwii/vim-nerdtree-sync'
call vundle
Vim plugin for csv files
Hi,
When I open up CSV files with vim, I get an error message:CSV Syntax:Invalid column pattern, using default pattern \%([^,]*,\|$\)
CSV Syntax:Or ftplugin hasn't been sourced before the syntax script
But I don't see any plugins in my vimrc that could be causing this. How do I see what plugin is opening the csv file and open it using the raw format (or if possible, fix the plugin)?
call vundle#begin()
Plugin 'VundleVim/Vundle.vim'
Plugin 'preservim/nerdtree'
Plugin 'ctrlpvim/ctrlp.vim'
Plugin 'airblade/vim-gitgutter'
Plugin 'tpope/vim-surround'
Plugin 'tpope/vim-fugitive'
Plugin 'sheerun/vim-polyglot'
Plugin 'cosminadrianpopescu/vim-sql-workbench'
Plugin 'unkiwii/vim-nerdtree-sync'
call vundle
Plugin 'VundleVim/Vundle.vim'
Plugin 'preservim/nerdtree'
Plugin 'ctrlpvim/ctrlp.vim'
Plugin 'airblade/vim-gitgutter'
Plugin 'tpope/vim-surround'
Plugin 'tpope/vim-fugitive'
Plugin 'sheerun/vim-polyglot'
Plugin 'cosminadrianpopescu/vim-sql-workbench'
Plugin 'unkiwii/vim-nerdtree-sync'
call vundle
Friday, May 23, 2025
Re: inoremap and typing pace?
Hi Marc,
On Thu, 17 Apr 2025 10:07:41 +0200 Marc Chantreux wrote:
> hi Steven,
>
> I just realized I haven't replied this one. I read it but I'm in rush
> time for the moment so I'll investigate later.
I just wonder if you had the time to have a look at this.
If you need more time, that's fine. Sorry to bother.
Thank you.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/20250523172146.33920af4%40localhost.
On Thu, 17 Apr 2025 10:07:41 +0200 Marc Chantreux wrote:
> hi Steven,
>
> I just realized I haven't replied this one. I read it but I'm in rush
> time for the moment so I'll investigate later.
I just wonder if you had the time to have a look at this.
If you need more time, that's fine. Sorry to bother.
Thank you.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/20250523172146.33920af4%40localhost.
Sunday, May 11, 2025
syntax highlighting
Hi there. I'm working on some custom themes. I'm having an issue with the
Operator field not coloring properly for syntax highlighting. In .vim files, it
does highlight properly, but in any other filetype, it doesn't. I've been trying
to debug this for days and haven't made any progress.
What would be the best way to go about this, paste the colorscheme .vim file in
a message here? It's only about 100 lines, as I haven't finished all of it yet,
but this one thing is really bugging me. Any help would be really appreciated.
If it helps, I'm not a Vim power user (yet). I've been digging through the docs
for the past couple of days and going through some more advanced tutorials.
Thanks so much! Ben
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/D9TDK3D7FKVF.1DPHSZ5F34WWY%40gmail.com.
Operator field not coloring properly for syntax highlighting. In .vim files, it
does highlight properly, but in any other filetype, it doesn't. I've been trying
to debug this for days and haven't made any progress.
What would be the best way to go about this, paste the colorscheme .vim file in
a message here? It's only about 100 lines, as I haven't finished all of it yet,
but this one thing is really bugging me. Any help would be really appreciated.
If it helps, I'm not a Vim power user (yet). I've been digging through the docs
for the past couple of days and going through some more advanced tutorials.
Thanks so much! Ben
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/D9TDK3D7FKVF.1DPHSZ5F34WWY%40gmail.com.
Wednesday, May 7, 2025
Re: Scrolling window "1 screen line" up or down
On Wed, May 7, 2025 at 12:25 PM Christian Brabandt <cblists@256bit.org> wrote:
On Wed, 07 May 2025, Arun E wrote:
> Hi,
>
> Context: when viewing text files with long lines, along with 'linebreak' on.
>
> I see that Ctrl-E/Ctrl-Y scrolls one line at a time, but jumps a few screen
> lines (depending on how long the line is) upon encountering a long line. This
> is a bit awkward. I could set 'wrap' to avoid this, but that defeats the
> purpose of reading. Is there any way to make the scrolling smoother with long
> lines present?
>
> gk/gj is nice to go up/down longer lines. It would be nice to have a g_CTRL-Y/
> g_CTRL-E to do something similar in idea over longer lines.
Can you try :h 'smoothscroll' ?
Perfect! Thanks Christian.
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJUkyiGTdHVJjR8RgoUs35xfF2tuay9-LgWYAQ%3DgcEBGi1ZVug%40mail.gmail.com.
Re: Scrolling window "1 screen line" up or down
On Wed, 07 May 2025, Arun E wrote:
> Hi,
>
> Context: when viewing text files with long lines, along with 'linebreak' on.
>
> I see that Ctrl-E/Ctrl-Y scrolls one line at a time, but jumps a few screen
> lines (depending on how long the line is) upon encountering a long line. This
> is a bit awkward. I could set 'wrap' to avoid this, but that defeats the
> purpose of reading. Is there any way to make the scrolling smoother with long
> lines present?
>
> gk/gj is nice to go up/down longer lines. It would be nice to have a g_CTRL-Y/
> g_CTRL-E to do something similar in idea over longer lines.
Can you try :h 'smoothscroll' ?
Thanks,
Christian
--
"OK, now let's look at four dimensions on the blackboard."
-- Dr. Joy
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBuzjdrZW%2B1ORoBy%40256bit.org.
> Hi,
>
> Context: when viewing text files with long lines, along with 'linebreak' on.
>
> I see that Ctrl-E/Ctrl-Y scrolls one line at a time, but jumps a few screen
> lines (depending on how long the line is) upon encountering a long line. This
> is a bit awkward. I could set 'wrap' to avoid this, but that defeats the
> purpose of reading. Is there any way to make the scrolling smoother with long
> lines present?
>
> gk/gj is nice to go up/down longer lines. It would be nice to have a g_CTRL-Y/
> g_CTRL-E to do something similar in idea over longer lines.
Can you try :h 'smoothscroll' ?
Thanks,
Christian
--
"OK, now let's look at four dimensions on the blackboard."
-- Dr. Joy
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBuzjdrZW%2B1ORoBy%40256bit.org.
Scrolling window "1 screen line" up or down
Hi,
-- Context: when viewing text files with long lines, along with 'linebreak' on.
I see that Ctrl-E/Ctrl-Y scrolls one line at a time, but jumps a few screen lines (depending on how long the line is) upon encountering a long line. This is a bit awkward. I could set 'wrap' to avoid this, but that defeats the purpose of reading. Is there any way to make the scrolling smoother with long lines present?
gk/gj is nice to go up/down longer lines. It would be nice to have a g_CTRL-Y/g_CTRL-E to do something similar in idea over longer lines.
Regards,
-Arun
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJUkyiFB7FPy34w5wFXtPKOmkeN0ErR%3Dy6Tt_Cuud0eWAXH8TQ%40mail.gmail.com.
Monday, May 5, 2025
Re: vim seems to have problems rendering this utf8 sequence : හොඳ විනෝදයක්
Of course you can use any font in your (Vim) terminal or program, it's
just a matter of taste. Fixed width fonts cause least trouble in putting
everything on screen.
When you use Vim only for text writing and editing, and do pre print in
a separate route eg. with pandoc, you can control the font that way.
Printed text are better using proportional fonts. But they are awful for
just writing and editing.
//meine
On Thu, May 01, 2025 at 03:44:54PM -0400, Eric Marceau wrote:
> I have to *confirm* my similar experience, that some characters seem to be
> using a width which is a multiple greater (and sometimes smaller) than 1
> (unity), and that for those characters (specified via Unicode reference),
> there is overlap.
>
> Without knowing the guts of *GVim*, or *MATE terminal* (my environment), it
> seems that the System-default (or Application-default) font for each of
> those is applied universally, and *NOT on an individual character basis*. I
> assume that that is because of programmer assumptions that people would NOT
> use *mixed-width characters*, and so impose a single character width on the
> entire content display. Obviously, that is an incorrect assumption, because
> you never know what width the Creators of various fonts might use, and the
> rendering engine should, in my estimation, be smart enough to recognize
> character-by-character width (a.k.a. old poured-lead typography plates) and
> apply those correctly where those are used.
>
> And then again, being a text editor which could conceivably by definition
> not concern itself with variable width characters, if GVim had a "mode"
> selector that would permit the setting of display rendering to one of the
> two modes
>
> - universal fixed-width, or
>
> - typesetting variable-width,
>
> then Gvim could offer the best of both worlds. 🙂
>
> Just my own two cents worth!
>
>
> Eric
>
> 69, retired Mechanical Engineer
>
>
> On 2025-05-01 00:02, brickviking wrote:
> > On my computer at least, the characters each appear to be double-wide,
> > and as a result of how gvim works, I get the left-hand side of the
> > characters presented, which makes all the characters look all squashed
> > up and overlapping. That's with the Terminus font on an earlier Fedora
> > Linux.
> >
> > Regards, brickviking
> >
> >
> > On Wed, 30 Apr 2025 at 05:26, 'Frank Schwidom' via vim_use
> > <vim_use@googlegroups.com> wrote:
> >
> > It is on all terminals with vim and nvim but gvim cannot display
> > the characters.
> >
> > On 2025-04-29 17:20:01, 'Paul' via vim_use wrote:
> > > Is it only Vim, or is it anything in your terminal (ie. your
> > font)? Does gvim show it OK?
> > >
> > > --
> > > --
> > > 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+unsubscribe@googlegroups.com
> > <mailto:vim_use%2Bunsubscribe@googlegroups.com>.
> > > To view this discussion visit
> > https://groups.google.com/d/msgid/vim_use/aBD8Mcfi69hUOsTR%40kitt.
> > >
> >
> > -- -- 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 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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBh6D6d312IqaD1G%40trackstand.
just a matter of taste. Fixed width fonts cause least trouble in putting
everything on screen.
When you use Vim only for text writing and editing, and do pre print in
a separate route eg. with pandoc, you can control the font that way.
Printed text are better using proportional fonts. But they are awful for
just writing and editing.
//meine
On Thu, May 01, 2025 at 03:44:54PM -0400, Eric Marceau wrote:
> I have to *confirm* my similar experience, that some characters seem to be
> using a width which is a multiple greater (and sometimes smaller) than 1
> (unity), and that for those characters (specified via Unicode reference),
> there is overlap.
>
> Without knowing the guts of *GVim*, or *MATE terminal* (my environment), it
> seems that the System-default (or Application-default) font for each of
> those is applied universally, and *NOT on an individual character basis*. I
> assume that that is because of programmer assumptions that people would NOT
> use *mixed-width characters*, and so impose a single character width on the
> entire content display. Obviously, that is an incorrect assumption, because
> you never know what width the Creators of various fonts might use, and the
> rendering engine should, in my estimation, be smart enough to recognize
> character-by-character width (a.k.a. old poured-lead typography plates) and
> apply those correctly where those are used.
>
> And then again, being a text editor which could conceivably by definition
> not concern itself with variable width characters, if GVim had a "mode"
> selector that would permit the setting of display rendering to one of the
> two modes
>
> - universal fixed-width, or
>
> - typesetting variable-width,
>
> then Gvim could offer the best of both worlds. 🙂
>
> Just my own two cents worth!
>
>
> Eric
>
> 69, retired Mechanical Engineer
>
>
> On 2025-05-01 00:02, brickviking wrote:
> > On my computer at least, the characters each appear to be double-wide,
> > and as a result of how gvim works, I get the left-hand side of the
> > characters presented, which makes all the characters look all squashed
> > up and overlapping. That's with the Terminus font on an earlier Fedora
> > Linux.
> >
> > Regards, brickviking
> >
> >
> > On Wed, 30 Apr 2025 at 05:26, 'Frank Schwidom' via vim_use
> > <vim_use@googlegroups.com> wrote:
> >
> > It is on all terminals with vim and nvim but gvim cannot display
> > the characters.
> >
> > On 2025-04-29 17:20:01, 'Paul' via vim_use wrote:
> > > Is it only Vim, or is it anything in your terminal (ie. your
> > font)? Does gvim show it OK?
> > >
> > > --
> > > --
> > > 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
> > > Groups "vim_use" group.
> > > To unsubscribe from this group and stop receiving emails from
> > it, send an email to vim_use+unsubscribe@googlegroups.com
> > <mailto:vim_use%2Bunsubscribe@googlegroups.com>.
> > > To view this discussion visit
> > https://groups.google.com/d/msgid/vim_use/aBD8Mcfi69hUOsTR%40kitt.
> > >
> >
> > -- -- 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 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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBh6D6d312IqaD1G%40trackstand.
Saturday, May 3, 2025
Profiling Vim9 scripts
What is the status of profiling for Vim9 scripts?
I'm trying to profile a somewhat complex script using
profile start test.prof
profile func *
and getting:
E1271: Compiling closure without context: <lambda>65
Using a more restrictive pattern (e.g., *Foo*, where Foo matches the
name of some method) does not give errors, but the profile is empty.
I do get a profile with `profile! file path/to/some/script.vim` if
I source the script. But I am interested in profiling code from imported
scripts. Is that possible at all?
Life.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/vv5uhb%246u1%241%40ciao.gmane.io.
I'm trying to profile a somewhat complex script using
profile start test.prof
profile func *
and getting:
E1271: Compiling closure without context: <lambda>65
Using a more restrictive pattern (e.g., *Foo*, where Foo matches the
name of some method) does not give errors, but the profile is empty.
I do get a profile with `profile! file path/to/some/script.vim` if
I source the script. But I am interested in profiling code from imported
scripts. Is that possible at all?
Life.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/vv5uhb%246u1%241%40ciao.gmane.io.
Re: vim 9.1 does not hide screen when ! command is given
hi,
On Sat, 3 May 2025 at 06:43, Riza Dindir <riza.dindir@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.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAM-dBgqJGLKruDMN31iB%2BoXreYTnJbQsh9DVS72SjaV%2BRyNwnQ%40mail.gmail.com.
On Sat, 3 May 2025 at 06:43, Riza Dindir <riza.dindir@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.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAM-dBgqJGLKruDMN31iB%2BoXreYTnJbQsh9DVS72SjaV%2BRyNwnQ%40mail.gmail.com.
Friday, May 2, 2025
Re: vim 9.1 does not hide screen when ! command is given
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
On Sat, May 3, 2025 at 6:32 AM Riza Dindir <riza.dindir@gmail.com> wrote:
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.RegardsRizaOn Fri, May 2, 2025 at 8:04 PM Riza Dindir <riza.dindir@gmail.com> 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 -lgpmOn Fri, May 2, 2025 at 6:03 PM Christian Brabandt <cblists@256bit.org> 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 <riza.dindir@gmail.com> 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 <cblists@256bit.org>
> 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 vim_use+unsubscribe@googlegroups.com.
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BG6QnYO7fTxzFb7%3D3NsHk_ugKEnuY1%3Dt8ocMh5RT5dc5A%40mail.gmail.com.
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 <riza.dindir@gmail.com> 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 -lgpmOn Fri, May 2, 2025 at 6:03 PM Christian Brabandt <cblists@256bit.org> 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 <riza.dindir@gmail.com> 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 <cblists@256bit.org>
> 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 vim_use+unsubscribe@googlegroups.com.
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BFzj%2B38Ytf%3Dc31SXxEMmgVeXO-%3DAWfn17%3DsweSPPd9pOA%40mail.gmail.com.
Re: vim 9.1 does not hide screen when ! command is given
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
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 <cblists@256bit.org> 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 <riza.dindir@gmail.com> 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 <cblists@256bit.org>
> 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 vim_use+unsubscribe@googlegroups.com.
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BFRW8WCJcnHhGi8jVQ8N4_C6bU9Mu%3DJq3cVApvu-gCkJg%40mail.gmail.com.
Re: vim 9.1 does not hide screen when ! command is given
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 <riza.dindir@gmail.com> 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 <cblists@256bit.org>
> 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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBTevXUxGHlEQO1Z%40256bit.org.
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 <riza.dindir@gmail.com> 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 <cblists@256bit.org>
> 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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBTevXUxGHlEQO1Z%40256bit.org.
Re: vim 9.1 does not hide screen when ! command is given
And my XTERM value is xterm-256color, which did not change...
On Fri, May 2, 2025 at 5:42 PM Riza Dindir <riza.dindir@gmail.com> wrote:
Hello ChristianMy t_ti and t_te are as sucht_ti=^[[?1049h^[[22;0;0t
t_te=^[[?1049l^[[23;0;0tThe old vim version was (9.1.0366) where the patch number is 0366 on my system, the new one is 9.1.0794Regards,RizaOn Fri, May 2, 2025 at 12:57 PM Christian Brabandt <cblists@256bit.org> 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
--
An optimist is a man who looks forward to marriage.
A pessimist is a married optimist.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBSXCcqLBHAAmhRx%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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BFzzLrLHn1_fT_sB-msswy8OQfWhv8%3DX-auzytLxqfD5A%40mail.gmail.com.
Re: vim 9.1 does not hide screen when ! command is given
Hello Christian
My t_ti and t_te are as such
t_ti=^[[?1049h^[[22;0;0t
t_te=^[[?1049l^[[23;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 <cblists@256bit.org> 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
--
An optimist is a man who looks forward to marriage.
A pessimist is a married optimist.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBSXCcqLBHAAmhRx%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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BEAGFAY8P658rcuwFw29Dvx%3DngunG97imSt3bWsy4Zipg%40mail.gmail.com.
Re: vim 9.1 does not hide screen when ! command is given
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
--
An optimist is a man who looks forward to marriage.
A pessimist is a married optimist.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBSXCcqLBHAAmhRx%40256bit.org.
> 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
--
An optimist is a man who looks forward to marriage.
A pessimist is a married optimist.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBSXCcqLBHAAmhRx%40256bit.org.
vim 9.1 does not hide screen when ! command is given
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
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CA%2Bek4BExD8eNYknWtgaqS-N41QZfktuNyshVbpDUgExhvtz8BA%40mail.gmail.com.
Thursday, May 1, 2025
Re: vim seems to have problems rendering this utf8 sequence : හොඳ විනෝදයක්
I have to confirm my similar experience, that some characters seem to be using a width which is a multiple greater (and sometimes smaller) than 1 (unity), and that for those characters (specified via Unicode reference), there is overlap.
Without knowing the guts of GVim, or MATE terminal (my environment), it seems that the System-default (or Application-default) font for each of those is applied universally, and NOT on an individual character basis. I assume that that is because of programmer assumptions that people would NOT use mixed-width characters, and so impose a single character width on the entire content display. Obviously, that is an incorrect assumption, because you never know what width the Creators of various fonts might use, and the rendering engine should, in my estimation, be smart enough to recognize character-by-character width (a.k.a. old poured-lead typography plates) and apply those correctly where those are used.
And then again, being a text editor which could conceivably by definition not concern itself with variable width characters, if GVim had a "mode" selector that would permit the setting of display rendering to one of the two modes
- universal fixed-width, or
- typesetting variable-width,
then Gvim could offer the best of both worlds. 🙂
Just my own two cents worth!
Eric
69, retired Mechanical Engineer
On 2025-05-01 00:02, brickviking wrote:
On my computer at least, the characters each appear to be double-wide, and as a result of how gvim works, I get the left-hand side of the characters presented, which makes all the characters look all squashed up and overlapping. That's with the Terminus font on an earlier Fedora Linux.
Regards, brickviking
--On Wed, 30 Apr 2025 at 05:26, 'Frank Schwidom' via vim_use <vim_use@googlegroups.com> wrote:
It is on all terminals with vim and nvim but gvim cannot display the characters.
On 2025-04-29 17:20:01, 'Paul' via vim_use wrote:
> Is it only Vim, or is it anything in your terminal (ie. your font)? Does gvim show it OK?
>
> --
> --
> 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+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBD8Mcfi69hUOsTR%40kitt.
>
--
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aBEKl7H80UmI76Hk%40debian64.
--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAHWye84xfOgHfW52t91Do_bm9eLOKNMby1bB3FCgYH%2BpM2gh8g%40mail.gmail.com.
Subscribe to:
Posts (Atom)