[vim/vim] silent echom should silently populate messages. (Issue #19376)

0 views
Skip to first unread message

ubaldot

unread,
Feb 9, 2026, 3:30:18 PM (20 hours ago) Feb 9
to vim/vim, Subscribed
ubaldot created an issue (vim/vim#19376)

Sometimes you want to silently log messages in :messages (i.e. place it in :messages without being displayed on screen) but it seems that currently there is no way to do it - though one can think to some not-so-nice workaround.

The obvious candidate for me should be echom, that is, silent echom "foo" does not display foo but it silently place it messages.

I am pretty sure that such a feature will come handy for many plugin authors.


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19376@github.com>

Christian Brabandt

unread,
Feb 9, 2026, 4:00:48 PM (19 hours ago) Feb 9
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19376)

There is :unsilent and the help even gives an example use case (which does not help for your particular ask). However I'd argue, if you want the message be part of the message history, it should have - well - been messaged to the user first. Or else he won't know that he should look into the :messages list and assume everything went well, because Vim stayed silent.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19376/3873826449@github.com>

ubaldot

unread,
2:24 AM (9 hours ago) 2:24 AM
to vim/vim, Subscribed
ubaldot left a comment (vim/vim#19376)

Not necessarily. There are many use-case where you want to log some information without explicitly notifying the user.
For example, loggers work exactly in that way.

If you want to both notify user and log in :messages use echom, if you want to only notify the user without logging, use echo, if you want to log a message without notify the user use... nothing is in place today and silent echom seems to nicely fit here.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19376/3875813184@github.com>

zeertzjq

unread,
2:33 AM (9 hours ago) 2:33 AM
to vim/vim, Subscribed
zeertzjq left a comment (vim/vim#19376)

This has been discussed and rejected in #12249


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19376/3875855111@github.com>

ubaldot

unread,
6:10 AM (5 hours ago) 6:10 AM
to vim/vim, Subscribed
ubaldot left a comment (vim/vim#19376)

I see. I thought that ch_log() only works with channels and jobs, but it can be used as a generic logger.

Nevertheless, if someone is interested in basic logging which is not necessarily connected to channels and jobs, it would be impossible to find it in the docs.

Also, an improvement could be to change the signature with:

ch_log({msg} [, {level}, {handle}])

Where level can be any of "debug", "info", "warning", "level", but that is another story. I may open a dedicated feature improvement issue if you believe the feature is worth (I believe it is).


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19376/3876948000@github.com>

ubaldot

unread,
6:11 AM (5 hours ago) 6:11 AM
to vim/vim, Subscribed

Closed #19376 as not planned.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/19376/issue_event/22670810517@github.com>

Reply all
Reply to author
Forward
0 new messages