Re: timer_start to refresh rulerformat

and then it worked, after update I guess to vim 9.2 (including patch 1-1011) \o/ 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/14308c5f-ff74-4430-9d91-9d221b9888f8%40sfr.fr.

Re: ShellCmdPre autocommand ?

hello, On Mon, Sep 07, 2026 at 05:30:56PM -0700, Maxim Kim wrote: > What about  > :!<CTRL-R><CTRL-f> ? worth to mention but something like :r!dpkg -r <cfile> is reusable from history so you can type it once and use it repeatedly and <cfile> updated. not only :r!dpkg -r $c is faster to type and less error prone but as it is a environment variable, I can use it it a custom script. I can also imagine exporting more informations like getline(), line(), col() ... anyway: I never use <c-r><c-f> but it's worth to mention the <c-r>* during the talk. Thank you! -- Marc Chantreux ☎ 03.68.85.60.79 -- -- 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/ap-aW3-HCOwXGhX-%40prometheus.

Re: ShellCmdPre autocommand ?

What about 

:!<CTRL-R><CTRL-f>

?

On Sunday, September 6, 2026 at 8:33:53 PM UTC+10 Marc Chantreux wrote:

hello vimmers,

A. The problem

* the use of expansions like <cfile> is very powerful but typing
those are boring and error prone ( < cfile> is a shell redir)
* sometimes it can be really usefull to have the content of <cfile>
as an exported variable.
* environment variables have autocompletion, vim expansions doesn't

:r!dpkg -r <cfile>

B. The solutions

There are many but I came to the idea that the most reusable feature
would be the ShellCmdPre autocommand (ShellCmdPost already exists).

I have no time to dive into vim developpement but if needed, I'll be
happy to sponsor it (I think Christian Brabandt asked for financial help
so he can spend more time on vim)

thanks for any feedbacks.


C. The context

In few months, I'll give a new version of the talk "acme changed my life"
https://github.com/eiro/talk-acme-changed-my-life in which I explain
that "!" by far the most underated feature of vi and all its clone and
the basics of it.

In this new version, I'll instist on another underated features: vim
expansions with expressions like

:e <cfile>/README
:r!dpkg -r <cfile>

and the way it can interact with features outside of vim. as exemple:
if you have suffix aliases set up in your ~/.zlogin, you can just type

:!<cfile>

to open a file. you can possibly map it to something like <space>x as
it's really generic.

but there the problem I mentionned before and what I really would like
is to introduce something like

au ShellCmdPre {
$f = expand('<cfile>')
$F = expand('<cFILE>')
$w = expand('<cword>')
$W = expand('<cWORD>')
}

so now I just need to type

:!$f

--
Marc Chantreux

--
--
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/ffcfb07a-ff6c-402c-aaf8-839bae034effn%40googlegroups.com.

ShellCmdPre autocommand ?

hello vimmers, A. The problem * the use of expansions like <cfile> is very powerful but typing those are boring and error prone ( < cfile> is a shell redir) * sometimes it can be really usefull to have the content of <cfile> as an exported variable. * environment variables have autocompletion, vim expansions doesn't :r!dpkg -r <cfile> B. The solutions There are many but I came to the idea that the most reusable feature would be the ShellCmdPre autocommand (ShellCmdPost already exists). I have no time to dive into vim developpement but if needed, I'll be happy to sponsor it (I think Christian Brabandt asked for financial help so he can spend more time on vim) thanks for any feedbacks. C. The context In few months, I'll give a new version of the talk "acme changed my life" https://github.com/eiro/talk-acme-changed-my-life in which I explain that "!" by far the most underated feature of vi and all its clone and the basics of it. In this new version, I'll instist on another underated features: vim expansions with expressions like :e <cfile>/README :r!dpkg -r <cfile> and the way it can interact with features outside of vim. as exemple: if you have suffix aliases set up in your ~/.zlogin, you can just type :!<cfile> to open a file. you can possibly map it to something like <space>x as it's really generic. but there the problem I mentionned before and what I really would like is to introduce something like au ShellCmdPre { $f = expand('<cfile>') $F = expand('<cFILE>') $w = expand('<cword>') $W = expand('<cWORD>') } so now I just need to type :!$f -- Marc Chantreux -- -- 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/ap1BfcqicUzqw5IA%40prometheus.

[ANN] vimls-go 0.1.0: a language server for Vim script and Vim9 script

Hi all,

I've released version 0.1.0 of vimls-go, an open-source language server written in Go for legacy Vim script and Vim9 script.

Source and setup instructions:
https://github.com/neoclide/vimls-go

Prebuilt binaries:
https://github.com/neoclide/vimls-go/releases/tag/v0.1.0

The server provides completion, hover documentation, signature help, definitions, references, diagnostics, semantic highlighting, and rename support. It includes cross-file analysis for autoload functions and Vim9 imports.

It also indexes Vim files on runtimepath and extracts documentation from doc/*.txt. Hover can show installed plugin help for variables, functions, and commands, with the source file path and line number. Runtimepath changes are handled incrementally.

In Vim, it can be used with an LSP client such as coc.nvim or vim-lsp. The server is a standalone binary; the README includes client configuration examples.

This is the first release. Formatting currently focuses on indentation, and static analysis has limitations around execute and dynamically generated names. Feedback from people working on Vim scripts and Vim9 plugins would be very helpful, especially small reproductions of false diagnostics or missing completions.

Thanks,
Qiming (chemzqm)

--
--
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/9ffbd0cd-2fa0-4e25-83c3-d6bd2497ef10n%40googlegroups.com.

Re: $VIMRC over .vimrc ?

$MYVIMRC is unset when `vim -u foo` is used. Use `type vim` to see if you/someone else set an alias/func.
$MYVIMDIR is set to the last `runtimepath=` appended/set, so if you try to do oldschool plugin loading this can change it.

This is covered in :help VIMINIT but often missed. 

Personally I think it would make sense if $MYVIMRC was set by "-u", but it could be it is used as a deterministic searchpath and manual set would interfere - I haven't checked.

On Monday, March 30, 2026 at 9:57:19 PM UTC+2 Christopher wrote:

On Friday, March 20, 2026 at 10:58:21 AM UTC-4 D. Ben Knoble wrote:

On Fri, Mar 20, 2026 at 9:58 AM Christopher <crestchr...@gmail.com> wrote:
>
>
>
> On Thursday, March 19, 2026 at 8:44:22 PM UTC-4 Marvin Renich wrote:
>
> * Christopher <crestchr...@gmail.com> [260319 19:14]:
> > On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > > The user's vimrc file _must_ be one of the files listed above, unless
> > > you specify the -u option. The only way to specify the vimrc file in an
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > > before (or while) starting vim.
> >
> > You mention, the only way to specify a vimrc in a environment variable; I
> > assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> > file. If my vimrc file was located in the system path then that would be;
> > VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> > ?
>
> You need to read carefully and for exact syntax and content:
>
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Remember that VIMINIT specifies an ex command to execute, not a file
> name. If you want to source a file using VIMINIT, you must specify the
> source command itself, not just the file name.
>
> Also, when testing this, know that :scriptnames is your friend.
>
> Also note that if your vimrc file is the system vimrc file (/etc/vimrc
> on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
> use:
>
> VIMINIT=':' vim
>
> or
>
> export VIMINIT=':'
> vim
>
> as the system vimrc is sourced even if you specify a VIMINIT. Setting
> VIMINIT=':' simply disables reading of the user vimrc file, but not the
> system vimrc file. (':' is an empty ex command.)
>
> Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.
>
> ...Marvin
>
>
> What do you mean by :scriptnames ?

":scriptnames" is an Ex command supported by Vim that announces what
scripts have been executed in the current session. (":help
:scriptnames").

> Within vim I run the command; VIMIT=: (colon) and that takes my system vimrc assigns it the variable $MYVIMRC or that has to be done after ?

I get the sense you may not be reading very carefully, but let me try
to clear up some confusion:

- "VIMINIT=: vim" is an example shell command that would disable
initializations from vimrc files other than the system vimrc.
(Notably, this does _not_ disable user-local plugins.)
- Vim will assign MYVIMRC if and when it finds and executes a user
vimrc. It never (AFAIK) assigns MYVIMRC to the path of the system
vimrc.
- The above point is moot if you set VIMINIT; then nothing sets MYVIMRC
- MYVIMRC is never _read_ by Vim to take any action (unless a plugin
or script uses it)

I wanted to clarify that it's now clear. In order to use the environment variable $MYVIMRC you must have a user; .vimrc file created, typically at the $HOME path for the installed nix version.

--
--
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/120999f4-42cf-4cc2-ab1b-b0a1200f157bn%40googlegroups.com.

Re: Vim installer for Windows is 3 weeks old

Looks like something wrong with Windows build again. It is few days old, but in vim/vim/ I see new commits.

--
--
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/7d09d304-1446-4b74-b2be-377c86385457n%40googlegroups.com.

Algol 68 - was AW: AW: Synchronize syntax highlighting

I'll answer your question but suggest to continue this topic in Usenet (comp.lang.misc) if you're interested in more details. Von: vim_use@googlegroups.com <vim_use@googlegroups.com> im Auftrag von arocker@Vex.Net <arocker@Vex.Net> Gesendet: Dienstag, 11. August 2026 21:07 An: vim_use@googlegroups.com > I'm curious to know why anyone is editing Algol 68 code in 2026. Simply; I'm *editing* it because I am _writing programs_ in Algol 68. The question was probably meant as why one would write programs in an old (legacy) language like Algol 68. - The answer is not simple. In the past 50 years I've programmed in a lot of languages, Algol 68 was amongst the cleanest, yet very powerful, and safe! It was not my first and certainly not my last language, but other languages with all these properties were long rare, even non-existing. When I found a high-quality Algol 68 interpreter lately I was glad to refresh my old programming skills in a language that was by far more enjoyable to program in than, say, in "C" (or similar), or in one of the many more languages (that are sometimes even hyped, for reasons beyond me). > Are there even functioning compilers available any more? The "Genie" compiler "a68g" is the one that I found, and used since then. It's of very high quality (as I said), and effectively a "complete" implementation of that very large language. In addition it has quite some powerful extensions (for math, plotting, databases, functions and methods we know Unix systems, etc.). I think it was developed in the 1990's and made public (with source code) for free use in the late 1990's (IIRC). A 700-pages PDF documentation comes with it. It is still maintained by its original author, Marcel van der Veer, and releases are still published. In addition there's a much more recent GNU project to release an Algol 68 compiler, "ga68", as part of the GNU Compiler Collection. It's probably too fresh - maybe even incomplete, can't tell - to say anything about it. But its recent development is an indication that there seems to be still some interest in the Algol 68 language. The Vim syntax file is a small contribution to support that interest. Janis -- -- 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/AS2SPRMB0054D02866ECB10097A6AB8EF3DD2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

New privacy settings for Search services and Google Play

rebbe.malachi.mailfeed@blogger.com Hello R' Russell, We’re updating our settings to give you even more control over saved history and personalized recommendations across Google Search services and Google Play. Search services include Search, Maps, Shopping, Hotels, Flights, Translate, and News. You’ll see this change in your Google Account in the next few days. What’s changing Previously, saving history and personalization were managed by Web & App Activity. Going forward, you can better tailor your Search services experience using your new Search Services History and Personalized Recommendations settings. These settings let you revisit your past searches and decide if you want your experience to be personalized. As people increasingly search in new ways, like searching a photo with Lens, Search Services History now includes media from your interactions, which you can stop saving at any time. For Google Play, you'll have new Play History and Personalization in Play settings, even if you’ve never used this service. You can turn these settings on or off at any time. How this affects your account New history and personalization settings: Your new settings for Search services and Google Play will reflect your most recent choices for Web & App Activity and Search Personalization settings. If Web & App Activity is currently off, these new settings will stay off. After the transition, the Web & App Activity setting will be separate from Search services’ and Play’s personalization and history settings. Changes to one setting won’t affect the others. Auto-delete: Your prior choice from Web & App Activity for how long your history is saved will also apply to Search Services History and Play History. As always, you can change how long history is saved, choose an auto-delete period, and review or delete history manually at any time. Your media is saved when Search Services History is on: Saved media includes your images, files, audio and video from your interactions with Search services to help improve your experience. For example, this lets you revisit your past visual searches with Lens or continue a Search Live conversation about a song you heard. To support these types of interactive product experiences, Google will now save your media to your Search Services History, applying robust privacy and security protections. Like your Search Services History, your saved media is also used to develop and improve Google services and technologies, including AI models and safety measures. With this transition, if your Web & App Activity setting is currently turned on, this new Save Media subsetting will also be turned on along with your Search Services History. You can turn off your Save Media subsetting at any time, and you can also delete individual pieces of media from your history. You can manage these preferences by visiting My Activity and your Personalization settings pages. Learn more about your Search services settings and Google Play settings.    © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043    You received this email to let you know about important changes to your Google Account and services.

Urgent: Sign in to your Google Account if you want to keep it

Sign in to your Google Account rebbe.malachi.mailfeed@blogger.com Your Google Account has not been used within a 2-year period. If you want to keep your Google Account, sign in to your Google Account before September 15, 2026. To protect user privacy and account data, Google will delete Google Accounts that are not used. Learn more Learn how to download your Google data. Sign in You received this email to let you know about important changes to your Google Account and services. © 2026 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

Re: AW: Synchronize syntax highlighting

See:

https://algol68genie.nl/en/algol-68-genie/

W dniu wt., 11 sie 2026 o 21:07 <arocker@vex.net> napisał(a):

I'm curious to know why anyone is editing Algol 68 code in 2026. Are there
even functioning compilers available any more?

--
--
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/083783b13ffab75485ad6631a4033ad1.squirrel%40webmail.vybenetworks.com.

--
--
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/CAEHV%2Btbs0hxnhNBoziqiv7HzuUqcHpvBWGPT4RUErANk8tJKTQ%40mail.gmail.com.

Re: AW: Synchronize syntax highlighting

I'm curious to know why anyone is editing Algol 68 code in 2026. Are there even functioning compilers available any more? -- -- 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/083783b13ffab75485ad6631a4033ad1.squirrel%40webmail.vybenetworks.com.

AW: Synchronize syntax highlighting

Hi Christian! > > I've tried various suggestions (minlines, synmaxcol, etc.), > > read the manual for information about possible tweaks > > searched the web, ... - to no avail! > > > > Trying with various numbers in configs like > > set smc=9000 > > syntax sync minlines=1000 maxlines=1000 > > > > I'm still getting no sync in a (even non-demanding) test case: > > opening a 476 line file, max. columns 84 => highlighting okay, > > searching for a text that appears in line 438 => NO SYNC here! > > (After scrolling 3 pages up the sync was okay again.) > > > > More testing... > > Opened a 80x25 terminal window. > > Same testcase as above. => highlighting okay!!! > > Resized the terminal window to 120x50. > > Opened the file again, same testcase => NO SYNC ! > > Resized the terminal window back to 80x25. > > Opened the file again, same testcase => highlighting okay > > > > This is strange!!! > > Highlighting depends on the terminal size, not on the actual text! > > does > :syn sync fromstart > > help? I've meanwhile extended my file and the effect wasn't seen then any more, but with an old version this trick indeed re-established the sync. - Thanks! > > This depends on the current syntax script and file being used, but it is > worth a try when this happens. I suppose this happens with algol68 > files? This has a hard-coded limit of 500 lines. While I had observed this effect in the past also with other languages or text data in this case it's indeed an Algol 68 source. After your hint I've meanwhile also noticed the hard-coded limit. Do these limits make sense? (They appear to be quite small anyway!) Would it hurt to remove those limits? (Or define higher values?) The parameters are defined as: syn sync minlines=250 maxlines=500 which I think means a context of +/- 250 lines considered for syncing? - That's not much given that the sync is obviously not done on language-specific syntax sync points. - I've now changed my local ~/.vim/syntax/algol68.vim and adjusted these values to 1000 each[*]; this solved the issue - at least locally, and for this specific source; let's see how far I get with those values. [*] Is that sensible or should 'maxvalue' be twice as large to to obtain the +/- 1000 context range? (The parameter names are a bit confusing to me; a "sync-lines-before" and "sync-lines-after" semantics might be clearer.) Though I'm wondering that a user-specific setting (in .vimrc) cannot override the system setting here. (But that may be an effect of this syntax file is in my system also locally below ~/.vim/syntax, and therefore it takes precedence?) And the dependency of the effect on the window size is still a mystery to me! (To me that smells like a bug or design problem in this specific case.) > It is not generally recommended to use syn sync fromstart in syntax > script, because it comes with a performance penalty, but in cases when > you notice syntax being off, it is worth a try. Yes, that's certainly useful and good to know! With Vim I've never had any performance problem editing program's text. (Only on *very* large textual data there's regularly a performance issue.) I'd think an increase of (hard-coded) sync values for program texts would generally not hurt. (Or are people really writing _monolithic code_ of tens of thousands line of code in one file without structuring it in files?) There's a couple questions raised in this post; can you tell me whether you think some of these needs attention to be changed? Thanks again! Regards, Janis -- -- 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/AS2SPRMB0054C3CAB8CDA9B45BF0E344F3DD2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Re: Synchronize syntax highlighting

On Mo, 10 Aug 2026, Janis Papanagnou wrote: > I've tried various suggestions (minlines, synmaxcol, etc.), > read the manual for information about possible tweaks > searched the web, ... - to no avail! > > Trying with various numbers in configs like > set smc=9000 > syntax sync minlines=1000 maxlines=1000 > > I'm still getting no sync in a (even non-demanding) test case: > opening a 476 line file, max. columns 84 => highlighting okay, > searching for a text that appears in line 438 => NO SYNC here! > (After scrolling 3 pages up the sync was okay again.) > > More testing... > Opened a 80x25 terminal window. > Same testcase as above. => highlighting okay!!! > Resized the terminal window to 120x50. > Opened the file again, same testcase => NO SYNC ! > Resized the terminal window back to 80x25. > Opened the file again, same testcase => highlighting okay > > This is strange!!! > Highlighting depends on the terminal size, not on the actual text! does :syn sync fromstart help? This depends on the current syntax script and file being used, but it is worth a try when this happens. I suppose this happens with algol68 files? This has a hard-coded limit of 500 lines. It is not generally recommended to use syn sync fromstart in syntax script, because it comes with a performance penalty, but in cases when you notice syntax being off, it is worth a try. Best, 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/anoekP02s6s1AliB%40256bit.org.

AW: Synchronize syntax highlighting

I've tried various suggestions (minlines, synmaxcol, etc.), read the manual for information about possible tweaks searched the web, ... - to no avail! Trying with various numbers in configs like set smc=9000 syntax sync minlines=1000 maxlines=1000 I'm still getting no sync in a (even non-demanding) test case: opening a 476 line file, max. columns 84 => highlighting okay, searching for a text that appears in line 438 => NO SYNC here! (After scrolling 3 pages up the sync was okay again.) More testing... Opened a 80x25 terminal window. Same testcase as above. => highlighting okay!!! Resized the terminal window to 120x50. Opened the file again, same testcase => NO SYNC ! Resized the terminal window back to 80x25. Opened the file again, same testcase => highlighting okay This is strange!!! Highlighting depends on the terminal size, not on the actual text! $ vi --version VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Jul 13 2026 17:17:48) Included patches: 1-16, 647, 678, 697 Modified by team+vim@tracker.debian.org If you have some more config options to try out I'd be keen to hear. Thanks! Janis ________________________________________ Von: vim_use@googlegroups.com <vim_use@googlegroups.com> im Auftrag von Christian Brabandt <cblists@256bit.org> Gesendet: Sonntag, 9. August 2026 17:17 An: vim_use@googlegroups.com Betreff: Re: Synchronize syntax highlighting On So, 09 Aug 2026, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. > > Can someone point me to the name of that parameter, please, > so that I can re-establish a better highlighting-sync behavior. :h 'synmaxcol' Best, Christian -- QOTD: "I drive my car quietly, for it goes without saying." -- -- 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/aniZ/O7l6XfNFoal%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/AS2SPRMB00541D5B0B40A1B43A60A99CF3DE2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Re: Synchronize syntax highlighting

On So, 09 Aug 2026, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. > > Can someone point me to the name of that parameter, please, > so that I can re-establish a better highlighting-sync behavior. :h 'synmaxcol' Best, Christian -- QOTD: "I drive my car quietly, for it goes without saying." -- -- 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/aniZ/O7l6XfNFoal%40256bit.org.

Re: Synchronize syntax highlighting

On 2026-08-09 10:48, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. I think you're looking for the minlines= and maxlines= values described here: :help syn-sync-maxlines :help syn-sync-third -tim -- -- -- 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/aniHL3avVmnNL3nP%40thechases.com.

Synchronize syntax highlighting

Sometimes, for some files, the sync of syntax-highlighting fails (i.e. all text gets uniformly colored). In the past, to tackle that, I've adjusted some vim parameter, increased a value from something like 3000 to 10000, or so. On my new system that setting got lost, unfortunately, and I cannot find it. Can someone point me to the name of that parameter, please, so that I can re-establish a better highlighting-sync behavior. Thanks! Janis -- -- 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/AS2SPRMB0054888E7352B5254DA6384EF3DF2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

AW: Synchronize syntax highlighting

Sorry, John, somehow my mail-client sent my email to you instead of the mailing list. ________________________________________ Von: Janis Papanagnou <janis_papanagnou@hotmail.com> Gesendet: Sonntag, 9. August 2026 12:48 An: 'John Jackson' via vim_use Betreff: Synchronize syntax highlighting Sometimes, for some files, the sync of syntax-highlighting fails (i.e. all text gets uniformly colored). In the past, to tackle that, I've adjusted some vim parameter, increased a value from something like 3000 to 10000, or so. On my new system that setting got lost, unfortunately, and I cannot find it. Can someone point me to the name of that parameter, please, so that I can re-establish a better highlighting-sync behavior. Thanks! Janis -- -- 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/AS2SPRMB0054564FC119CABBF1BAC3EFF3DF2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Re: Re: Vim on Debian Mint Linux

 

------ Original Message ------
From: eajmarceau@gmail.com
To: vim_use@googlegroups.com
Sent: Friday, August 7th 2026, 18:15
Subject: Re: Vim on Debian Mint Linux
 

    "Does it do PDFs as on Windows?"

If you mean, edit the PDF as a text file, leaving the encoded elements as is, the response is yes.

 

For any Debian-based system, the method to install is to open a shell in a terminal and enter the command,

• sudo apt-get install vim-gtk3 (vim-gui-common)

Or look for the vim-gtk3 package from within Synaptic, and install that way.

 

Eric

 

On 2026-08-07 11:53, 'c.willis111 ' via vim_use wrote:
 

Hi

 

how do I install vim on debian mint Linux?

 

Does it do PDFs as on Windows?

 

regards - Chris

 

 

-- 
-- 
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 unsubscribe@googlegroups.com" class="moz-txt-link-freetext">vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/344fdc93.1e04.19fdcede606.Webtop.1%40btinternet.com.
 

 

-- 
-- 
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 unsubscribe@googlegroups.com">vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/22082605-9693-43f2-a059-18f1ea3a408f%40gmail.com.
Hi

 

thanks both Eric and Marco

 

Eric, in Windows Vim on a PDF preprocesses the file using PdfTk,, and restores the compression afterwards, likewise. This shows the content streams as clear text. I suspect that PdfTk doesn't work on Linux?

 

The post processing sorts out the length attributes that the compression and edits have changed.

 

regards - Chris

--
--
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/79d0729e.72fff.19fde4ec6a2.Webtop.227%40btinternet.com.