Vimdiff counting dark blue lines

Hello,

would there be a command to count the dark blue lines on the vimdiff Bookmarks1 and Bookmarks2 please?

Once I figured out how many extra lines there are, I can then work on some type of merge.

At the bottom of the vimdiff Bookmarks1 and Bookmarks2, there's some information showing:

Bookmarks1  4675,1  Bot and Bookmarks2  4655,1  Bot

I guess this means Bookmarks1 has 20 more lines thank Bookmark2.

However this isn't much help.

What I really need is Bookmarks1 has these dark blue lines for lines of data which isn't in Bookmarks2.

Vice versa too.

Then the fun bit merging or manually diffget and diffput each and every single line, which might be out of the question if too many.

Many thanks for any suggestions.

--
--
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/d45f1eac-39d2-475a-ada1-674df8459cd7n%40googlegroups.com.

Re: Shell Syntax Highlighting - Group bashAdminStatement

The syntax highlighting problems I've faced in the past are with syntaxes that I can't limit to a specific part of a file, such as a markdown file that has a code region in it. The problem syntaxes use the "extend" keyword when they define a region. The "extend" keyword overrides the "keepend" keyword which lets the syntax highlighting continue past the end of the code region. The c.vim, perl.vim, and vim.vim syntaxes all had this problem last I looked at it.

On Thursday, September 18, 2025 at 1:56:06 PM UTC-5 Björn Försterling wrote:

Hello,

ok, I will look into it.

Regards
Björn

On Wed Sep 17, 2025 at 10:31 PM CEST, Christian Brabandt wrote:
> Hi,
> It's not only that, it's also that certain commands (ls cat chmod) are
> only highlighted, if this is a detected bash or ksh script. I think we
> should move those to just Statements.
>
> We don't have a shell runtime file maintainer anymore and I assume
> changing this breaks some existing syntax tests. However, if you'd like
> to give it a try and unify kshStatements with bashStatement and
> bashAdminStatements (for the commands) and possibly keep those status
> keywords then please submit a PR at the Vim repo and please have a look
> at failing syntax tests (we probably just need to regenerate them).
>
> Thanks,
> Chris
>
> On Mi, 17 Sep 2025, 'Björn Försterling' via vim_use wrote:
>
>> Thank you for the answer.
>>
>> The words "daemon", "reload", "restart", "start", "status", and "stop" are
>> neither bash keywords nor external commands.
>> Maybe they were implemented for init scripts, but these are hardly used
>> anymore today.
>>
>> The words "killall", "killproc", and "nice" are external commands which is
>> ok I guess.
>> But I can't really see a pattern why some external programs are
>> highlighted and others are not.
>> They were probably selected on how frequently they are used in bash
>> scripts.
>>
>> For example if you type "systemctl start foo", then "start" is
>> highlighted, but "systemctl" is not.
>> Or for "systemctl daemon-reload" nothing will be highlighted.
>>
>> For external commands you could choose only coreutils or don't highlight
>> external commands at all.
>>
>> On Tue Sep 16, 2025 at 9:39 PM CEST, Christian Brabandt wrote:
>> >
>> > On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:
>> >
>> >> Hello,
>> >>
>> >> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
>> >> The syntax highlighting for these words seems unfitting.
>> >>
>> >> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
>> >>
>> >> Maybe these were designed for init scripts or systemd commands.
>> >> Of course I can disable this syntax group in my own syntax files.
>> >>
>> >> But does someone know why these were implemented?
>> >
>> > So is the problem, that those are not really bash specific builtins but
>> > rather external commands? I suppose the same is true for bashStatement
>> > then.
>> >
>> > Thanks,
>> > Christian
>>
>
> Mit freundlichen Grüßen
> 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/1e24e20b-3b1e-4243-934c-32afedbf979fn%40googlegroups.com.

Re: inconsistent behavior of findfunc and wildchar

I am not sure if it is posted successfully, as I cannot find it in the
google groups: <https://groups.google.com/g/vim_use>.

I created a github issue instead:
<https://github.com/vim/vim/issues/18411>.

--
--
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/aNdMrJPWgLKyLuZM%40ocarina-of-time.

inconsistent behavior of findfunc and wildchar

Hi,

I am recently trying the new findfunc feature. I found that the
arguments passed to findfunc was different in Linux and macOS.

For example, when I type `:find gvim ext` in cmdline, every time I
trigger `wildchar`, in macOS, findfunc receives a full list of arguments,
while in Linux, findfunc only receives the last arguments.

The minimal configuration to reproduce:

```vim
func Find(arg, _)
echom a:arg
if get(s:, 'filescache', []) == []
let s:filescache = systemlist('find . -path "*/.git" -prune -o -type f -print')
endif
return a:arg == '' ? s:filescache : matchfuzzy(s:filescache, a:arg)
endfunc
autocmd CmdlineEnter : let s:filescache = []

set wildoptions=pum
set wildmode=noselect

autocmd CmdlineChanged [:\/\?] call wildtrigger()
```

Run `:messages` after `:find gvim e`. In macOS, I got:

```
g
gv
gvi
gvim
gvim
gvim e
```

While in Linux, I got:

```
g
gv
gvi
gvim

e
```

I compiled the master branch (current commit:
<c05335082adb21d99d96374779856444a3a0688f>) in both macOS and Arch
Linux, with the following steps. (I had never compiled it myself before,
so I am not sure if it is the expected way or not.)

```bash
cd src
./configure --with-features=huge
make -j
```

I got error message `Failed to source defaults.vim` for the self
compiled vim when executing with `vim --clean`. I think it didn't affect
the behavior above.

Thanks,
Guangxiong Lin

--
--
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/aNdA1e8ZdYKgDIeQ%40ocarina-of-time.

Re: Shell Syntax Highlighting - Group bashAdminStatement

Hello,

ok, I will look into it.

Regards
Björn

On Wed Sep 17, 2025 at 10:31 PM CEST, Christian Brabandt wrote:
> Hi,
> It's not only that, it's also that certain commands (ls cat chmod) are
> only highlighted, if this is a detected bash or ksh script. I think we
> should move those to just Statements.
>
> We don't have a shell runtime file maintainer anymore and I assume
> changing this breaks some existing syntax tests. However, if you'd like
> to give it a try and unify kshStatements with bashStatement and
> bashAdminStatements (for the commands) and possibly keep those status
> keywords then please submit a PR at the Vim repo and please have a look
> at failing syntax tests (we probably just need to regenerate them).
>
> Thanks,
> Chris
>
> On Mi, 17 Sep 2025, 'Björn Försterling' via vim_use wrote:
>
>> Thank you for the answer.
>>
>> The words "daemon", "reload", "restart", "start", "status", and "stop" are
>> neither bash keywords nor external commands.
>> Maybe they were implemented for init scripts, but these are hardly used
>> anymore today.
>>
>> The words "killall", "killproc", and "nice" are external commands which is
>> ok I guess.
>> But I can't really see a pattern why some external programs are
>> highlighted and others are not.
>> They were probably selected on how frequently they are used in bash
>> scripts.
>>
>> For example if you type "systemctl start foo", then "start" is
>> highlighted, but "systemctl" is not.
>> Or for "systemctl daemon-reload" nothing will be highlighted.
>>
>> For external commands you could choose only coreutils or don't highlight
>> external commands at all.
>>
>> On Tue Sep 16, 2025 at 9:39 PM CEST, Christian Brabandt wrote:
>> >
>> > On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:
>> >
>> >> Hello,
>> >>
>> >> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
>> >> The syntax highlighting for these words seems unfitting.
>> >>
>> >> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
>> >>
>> >> Maybe these were designed for init scripts or systemd commands.
>> >> Of course I can disable this syntax group in my own syntax files.
>> >>
>> >> But does someone know why these were implemented?
>> >
>> > So is the problem, that those are not really bash specific builtins but
>> > rather external commands? I suppose the same is true for bashStatement
>> > then.
>> >
>> > Thanks,
>> > Christian
>>
>
> Mit freundlichen Grüßen
> 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/DCW5LAWEGPP3.10NWDQX3ZYLQG%40web.de.

Re: Shell Syntax Highlighting - Group bashAdminStatement

Hi,
It's not only that, it's also that certain commands (ls cat chmod) are
only highlighted, if this is a detected bash or ksh script. I think we
should move those to just Statements.

We don't have a shell runtime file maintainer anymore and I assume
changing this breaks some existing syntax tests. However, if you'd like
to give it a try and unify kshStatements with bashStatement and
bashAdminStatements (for the commands) and possibly keep those status
keywords then please submit a PR at the Vim repo and please have a look
at failing syntax tests (we probably just need to regenerate them).

Thanks,
Chris

On Mi, 17 Sep 2025, 'Björn Försterling' via vim_use wrote:

> Thank you for the answer.
>
> The words "daemon", "reload", "restart", "start", "status", and "stop" are
> neither bash keywords nor external commands.
> Maybe they were implemented for init scripts, but these are hardly used
> anymore today.
>
> The words "killall", "killproc", and "nice" are external commands which is
> ok I guess.
> But I can't really see a pattern why some external programs are
> highlighted and others are not.
> They were probably selected on how frequently they are used in bash
> scripts.
>
> For example if you type "systemctl start foo", then "start" is
> highlighted, but "systemctl" is not.
> Or for "systemctl daemon-reload" nothing will be highlighted.
>
> For external commands you could choose only coreutils or don't highlight
> external commands at all.
>
> On Tue Sep 16, 2025 at 9:39 PM CEST, Christian Brabandt wrote:
> >
> > On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:
> >
> >> Hello,
> >>
> >> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
> >> The syntax highlighting for these words seems unfitting.
> >>
> >> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
> >>
> >> Maybe these were designed for init scripts or systemd commands.
> >> Of course I can disable this syntax group in my own syntax files.
> >>
> >> But does someone know why these were implemented?
> >
> > So is the problem, that those are not really bash specific builtins but
> > rather external commands? I suppose the same is true for bashStatement
> > then.
> >
> > Thanks,
> > Christian
>

Mit freundlichen Grüßen
Christian
--
Either one of us, by himself, is expendable. Both of us are not.
-- Kirk, "The Devil in the Dark", stardate 3196.1

--
--
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/aMsavlajYq3Jtvmr%40256bit.org.

Re: Shell Syntax Highlighting - Group bashAdminStatement

Thank you for the answer.

The words "daemon", "reload", "restart", "start", "status", and "stop" are
neither bash keywords nor external commands.
Maybe they were implemented for init scripts, but these are hardly used
anymore today.

The words "killall", "killproc", and "nice" are external commands which is
ok I guess.
But I can't really see a pattern why some external programs are
highlighted and others are not.
They were probably selected on how frequently they are used in bash
scripts.

For example if you type "systemctl start foo", then "start" is
highlighted, but "systemctl" is not.
Or for "systemctl daemon-reload" nothing will be highlighted.

For external commands you could choose only coreutils or don't highlight
external commands at all.

On Tue Sep 16, 2025 at 9:39 PM CEST, Christian Brabandt wrote:
>
> On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:
>
>> Hello,
>>
>> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
>> The syntax highlighting for these words seems unfitting.
>>
>> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
>>
>> Maybe these were designed for init scripts or systemd commands.
>> Of course I can disable this syntax group in my own syntax files.
>>
>> But does someone know why these were implemented?
>
> So is the problem, that those are not really bash specific builtins but
> rather external commands? I suppose the same is true for bashStatement
> then.
>
> 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/DCV9RD79NQKJ.34LS38F2H93K%40web.de.

Re: Shell Syntax Highlighting - Group bashAdminStatement

On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:

> Hello,
>
> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
> The syntax highlighting for these words seems unfitting.
>
> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
>
> Maybe these were designed for init scripts or systemd commands.
> Of course I can disable this syntax group in my own syntax files.
>
> But does someone know why these were implemented?

So is the problem, that those are not really bash specific builtins but
rather external commands? I suppose the same is true for bashStatement
then.

Thanks,
Christian
--
"The number of Unix installations has grown to 10, with more expected."
-- The Unix Programmer's Manual, 2nd Edition, June, 1972

--
--
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/aMm9AZ48kJG3iPt%2B%40256bit.org.

Re: Moderator's spam report for vim_use@googlegroups.com

approve

On Di, 16 Sep 2025, noreply-spamdigest via vim_use wrote:

> This message is being sent to you because you are a moderator of the group vim_use.
>
> The following suspicious messages were sent to your group, but are being held in your moderation queue because they are classified as likely spam messages.
>
> If you take no action, all the messages below will be discarded automatically as spam.
>
> However, if you see any messages that are not spam below, you may approve them individually by going to:
>
> https://groups.google.com/group/vim_use/pendmsg
>
> Please do not mark this notification as spam; this is a service for group moderators. If you do not wish to receive these notifications in the future, you may change your preferences by going to:
>
> https://groups.google.com/group/vim_use/manage_post
>
>
> ------- 1 of 1 -------
> Subject: Shell Syntax Highlighting - Group bashAdminStatement
> From: Björn Försterling <bjoern.foersterling@web.de>
> Date: Sep 16 10:22AM +0200
>
> Hello,
>
> I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
> The syntax highlighting for these words seems unfitting.
>
> syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop
>
> Approve: https://groups.google.com/group/vim_use/pendmsg?view=full&pending_id=6668635236888541789
>
>
> For more information about this message, please visit:
> https://support.google.com/groups/answer/2466386
>

Mit freundlichen Grüßen
Christian
--
Your ignorance cramps my conversation.

--
--
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/aMkvbgKpF2t9gRjY%40256bit.org.

Shell Syntax Highlighting - Group bashAdminStatement

Hello,

I am wondering about the syntax group "bashAdminStatement" in "runtime/syntax/sh.vim".
The syntax highlighting for these words seems unfitting.

syn keyword bashAdminStatement daemon killall killproc nice reload restart start status stop

Maybe these were designed for init scripts or systemd commands.
Of course I can disable this syntax group in my own syntax files.

But does someone know why these were implemented?

Regards
Björn Försterling

--
--
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/DCU2VDAK1TBC.1O9IC6COR82CH%40web.de.

Re: idle question about logs and colors

On So, 14 Sep 2025, Igbanam Ogbuluijah wrote:

> On Sun, Sep 14, 2025 at 4:39 PM tooth pik <toothpik6@gmail.com> wrote:
>
> thank you christian, that works
>
> but i wish it wasn't necessary

I reverted that part of the patch. Should be fine now with v9.1.1759

Thanks
Christian
--
Joe Cool always spends the first two weeks at college sailing his frisbee.
-- Snoopy

--
--
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/aMcGxgRd4XDqNxqq%40256bit.org.

Re: idle question about logs and colors

You can name the file with a .txt extension; version-log.txt maybe?

Igbanam

On Sun, Sep 14, 2025 at 4:39 PM tooth pik <toothpik6@gmail.com> wrote:

thank you christian, that works

but i wish it wasn't necessary

On Sun, Sep 14, 2025 at 10:20 AM Christian Brabandt <cblists@256bit.org> wrote:

On So, 14 Sep 2025, tooth pik wrote:

> i have a module i named 'version.log' where i document versions as they appear
> -- suddenly today it appears with obscene colors that offend and distract
>
> can someone tell me how to make it look like a normal text file?

:set ft=text



Best,
Christian
--
Er, Tom, I hate to be the one to point this out, but your fix list
is starting to resemble a feature list.  You must be human or something.
                -- Larry Wall in <199801081824.KAA29602@wall.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/aMbdUB9zjpHf3A6Z%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/CALfSX1yOWAtuW5_VDCkj1z%3DqFigmL_QYHV-TLTDALYqXZH7CNA%40mail.gmail.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/CAOmRJrfmmrNCZ6nFvUyJkVUjYcwopWs%2BEvQ1mNbdmDx0QTsNiQ%40mail.gmail.com.

Re: idle question about logs and colors

thank you christian, that works

but i wish it wasn't necessary

On Sun, Sep 14, 2025 at 10:20 AM Christian Brabandt <cblists@256bit.org> wrote:

On So, 14 Sep 2025, tooth pik wrote:

> i have a module i named 'version.log' where i document versions as they appear
> -- suddenly today it appears with obscene colors that offend and distract
>
> can someone tell me how to make it look like a normal text file?

:set ft=text



Best,
Christian
--
Er, Tom, I hate to be the one to point this out, but your fix list
is starting to resemble a feature list.  You must be human or something.
                -- Larry Wall in <199801081824.KAA29602@wall.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/aMbdUB9zjpHf3A6Z%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/CALfSX1yOWAtuW5_VDCkj1z%3DqFigmL_QYHV-TLTDALYqXZH7CNA%40mail.gmail.com.

Re: idle question about logs and colors

On So, 14 Sep 2025, tooth pik wrote:

> i have a module i named 'version.log' where i document versions as they appear
> -- suddenly today it appears with obscene colors that offend and distract
>
> can someone tell me how to make it look like a normal text file?

:set ft=text



Best,
Christian
--
Er, Tom, I hate to be the one to point this out, but your fix list
is starting to resemble a feature list. You must be human or something.
-- Larry Wall in <199801081824.KAA29602@wall.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/aMbdUB9zjpHf3A6Z%40256bit.org.

idle question about logs and colors

i have a module i named 'version.log' where i document versions as they appear -- suddenly today it appears with obscene colors that offend and distract

can someone tell me how to make it look like a normal text file?

--
--
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/CALfSX1xiFrCRu3D7g7LR-_Lh_1zcZ2QtoPHxWv%3D_xiQyoeQp6g%40mail.gmail.com.

Re: The screen is not updating after make

You can try async :Make command:

def MakeComplete(_, _, _): string
    return system("make -npq : 2> /dev/null | awk -v RS= -F: '$1 ~ /^[^#%.]+$/ { print $1 }' | sort -u")
enddef

def Make(args: string = "")
    if exists("b:make_jobid") && job_status(b:make_jobid) == 'run'
        echo "There is a make job running."
        return
    endif
    var makeprg = &l:makeprg ?? &makeprg
    setqflist([], ' ', {title: $"{makeprg} {args}"})
    copen
    b:make_jobid = job_start($"{makeprg} {args}", {
        cwd: getcwd(),
        out_cb: (_, msg) => {
            setqflist([], 'a', {lines: [msg]})
        },
        err_cb: (_, msg) => {
            setqflist([], 'a', {lines: [msg]})
        },
        exit_cb: (_, _) => {
            if empty(getqflist())
                timer_start(500, (_) => {
                    if empty(getqflist())
                        cclose
                    endif
                })
            endif
            echo "Make is finished!"
        }
    })
enddef
command! -nargs=* -complete=custom,MakeComplete Make Make(<f-args>)

On Wednesday, September 10, 2025 at 4:09:36 PM UTC+10 Riza Dindir wrote:

Hello

I was thinking that silent was silencing the message output, did not expect it to skip screen refresh... Then it might well be...

I am still using silent, will remove that and try that for a while. But the :redraw! did work.

Regards

On Wed, Sep 10, 2025 at 2:01 AM Marc Chantreux <m...@unistra.fr> wrote:

On Wed, Sep 10, 2025 at 12:21:41AM +0300, Riza Dindir wrote:
> Hello
> Silent should not have been the issue.

well ... as far as I understand, silent makes things silent at the
point vim don't refresh the screen.

It's anyoing but I don't know if it's a bug or a configuration problem
(my terminal, my tmux or something).

regards

--
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+u...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/vim_use/aMCxsikI1Ob49gLe%40prometheus.

--
--
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/8ba983e4-bb34-40e1-a880-4680a55767a9n%40googlegroups.com.

Re: The screen is not updating after make

Hello

I was thinking that silent was silencing the message output, did not expect it to skip screen refresh... Then it might well be...

I am still using silent, will remove that and try that for a while. But the :redraw! did work.

Regards

On Wed, Sep 10, 2025 at 2:01 AM Marc Chantreux <mc@unistra.fr> wrote:

On Wed, Sep 10, 2025 at 12:21:41AM +0300, Riza Dindir wrote:
> Hello
> Silent should not have been the issue.

well ... as far as I understand, silent makes things silent at the
point vim don't refresh the screen.

It's anyoing but I don't know if it's a bug or a configuration problem
(my terminal, my tmux or something).

regards

--
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/aMCxsikI1Ob49gLe%40prometheus.

--
--
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%2Bek4BG6-KiH8SsLWXE-66HhPJ%3D3gB-dLrWYa%2BAtSEig9ne%2BCw%40mail.gmail.com.

Re: The screen is not updating after make

On Wed, Sep 10, 2025 at 12:21:41AM +0300, Riza Dindir wrote:
> Hello
> Silent should not have been the issue.

well ... as far as I understand, silent makes things silent at the
point vim don't refresh the screen.

It's anyoing but I don't know if it's a bug or a configuration problem
(my terminal, my tmux or something).

regards

--
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/aMCxsikI1Ob49gLe%40prometheus.

Re: The screen is not updating after make

Hello

Silent should not have been the issue.

But I forgot about :redraw! :) Hopefully that will solve the problem...

Thanks for all the response.

Regards

On Tue, Sep 9, 2025 at 11:44 PM Igbanam Ogbuluijah <xigbanam@gmail.com> wrote:

Yeah, I was going to hint at :redraw! as well.

Whenever my screen goes blank :redraw! fixes it.

Igbanam

On Tue, Sep 9, 2025 at 7:08 PM Marc Chantreux <mc@unistra.fr> wrote:

On Tue, Sep 09, 2025 at 12:21:32PM +0300, Riza Dindir wrote:
> I have a mapping like this:
>
> command! -nargs=* Make silent make! <args> | if len(getqflist()) > 0 | copen |
> endif

> Whenever I do call this command, the screen does not update. The screen is
> blank (where once was the source code displayed). and the quickfix window is
> sometimes left blank too.

how about:

command -nargs=* Make {
        silent make! <args>
        if len(getqflist()) > 0
                copen
        endif
        redraw!
}

> Does anybody have the same problem?

not since I discovered redraw!

regards

--
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/aMB7FMtP50wtOpNI%40prometheus.

--
--
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/CAOmRJrdgxVSTsEEVW7%2B4f9_nwm%3DsHn4AtYqibJ1DxAnvTsgrfw%40mail.gmail.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/CA%2Bek4BHu%3DB9R511Jf6%2BoyFig_%2B9tj9MjRsViqGMtv7gCUJah8Q%40mail.gmail.com.

Re: The screen is not updating after make

Yeah, I was going to hint at :redraw! as well.

Whenever my screen goes blank :redraw! fixes it.

Igbanam

On Tue, Sep 9, 2025 at 7:08 PM Marc Chantreux <mc@unistra.fr> wrote:

On Tue, Sep 09, 2025 at 12:21:32PM +0300, Riza Dindir wrote:
> I have a mapping like this:
>
> command! -nargs=* Make silent make! <args> | if len(getqflist()) > 0 | copen |
> endif

> Whenever I do call this command, the screen does not update. The screen is
> blank (where once was the source code displayed). and the quickfix window is
> sometimes left blank too.

how about:

command -nargs=* Make {
        silent make! <args>
        if len(getqflist()) > 0
                copen
        endif
        redraw!
}

> Does anybody have the same problem?

not since I discovered redraw!

regards

--
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/aMB7FMtP50wtOpNI%40prometheus.

--
--
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/CAOmRJrdgxVSTsEEVW7%2B4f9_nwm%3DsHn4AtYqibJ1DxAnvTsgrfw%40mail.gmail.com.

Re: The screen is not updating after make

On Tue, Sep 09, 2025 at 12:21:32PM +0300, Riza Dindir wrote:
> I have a mapping like this:
>
> command! -nargs=* Make silent make! <args> | if len(getqflist()) > 0 | copen |
> endif

> Whenever I do call this command, the screen does not update. The screen is
> blank (where once was the source code displayed). and the quickfix window is
> sometimes left blank too.

how about:

command -nargs=* Make {
silent make! <args>
if len(getqflist()) > 0
copen
endif
redraw!
}

> Does anybody have the same problem?

not since I discovered redraw!

regards

--
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/aMB7FMtP50wtOpNI%40prometheus.

Re: The screen is not updating after make

On Di, 09 Sep 2025, Riza Dindir wrote:

> That silent in the command is the vim silent command/annotation (or whatever
> that is)

So maybe you shouldn't use silent then?

Thanks,
Christian
--
A sadist is a masochist who follows the Golden Rule.

--
--
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/aMB5kLsfnwNmAaOJ%40256bit.org.

Re: The screen is not updating after make

Hello

That silent in the command is the vim silent command/annotation (or whatever that is)

On Tue, Sep 9, 2025 at 3:02 PM jr <creature.eternal@gmail.com> wrote:

hi,

> I have a mapping like this:
> command! -nargs=* Make silent make! ...
> Whenever I do call this command, the screen does not update. The screen is blank (where once was the source code displayed). and the quickfix window is sometimes left blank too.
> This was the case when I was using :make with this.

I do not use a mapping, sorry not to answer your question, but, out of
interest, does '.SILENT;'  in the 'Makefile' not work for you ?
('make' also has a CLI option to "silence" it).

--
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-dBgr4qu-1jdanm4kbV82avJOT3aoCyWp3vs3P%2BKHrf0i3BA%40mail.gmail.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/CA%2Bek4BEWmLW0AwW61M0EpWBQ4krqJVAiEnZus-nqyy_d5jht0w%40mail.gmail.com.

Re: The screen is not updating after make

hi,

> I have a mapping like this:
> command! -nargs=* Make silent make! ...
> Whenever I do call this command, the screen does not update. The screen is blank (where once was the source code displayed). and the quickfix window is sometimes left blank too.
> This was the case when I was using :make with this.

I do not use a mapping, sorry not to answer your question, but, out of
interest, does '.SILENT;' in the 'Makefile' not work for you ?
('make' also has a CLI option to "silence" it).

--
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-dBgr4qu-1jdanm4kbV82avJOT3aoCyWp3vs3P%2BKHrf0i3BA%40mail.gmail.com.

The screen is not updating after make

Hello,

I have a mapping like this:

command! -nargs=* Make silent make! <args> | if len(getqflist()) > 0 | copen | endif

Whenever I do call this command, the screen does not update. The screen is blank (where once was the source code displayed). and the quickfix window is sometimes left blank too.

This was the case when I was using :make with this.

I am using vim version 9.0.

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Nov 24 2023 12:59:56)
Included patches: 1-2127

Does anybody have the same problem?

Regards

--
--
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%2Bek4BHXqem54RbAwUCDqr52miWTOxwXS9kb394t%3DAaRm-N-4Q%40mail.gmail.com.