Am 19.08.2020 um 21:11 schrieb 'J S' via vim_use:
But I am curious as to why you say that the Vim Developers are trying
to avoid adding options. Is there any intrinsic reason why adding
options is undesirable?
I think it's more about the option in question:
(1) a global silent mode can too easi
So, having worked with it a bit, I'm now content with using "silent" to solve
this issue. Although a little convoluted, it seems pretty straightforward to
put all the commands into a function, and then create a command to call that
function with silent. I.e..:
command! MyCommand silent call M
On Di, 18 Aug 2020, 'J S' via vim_use wrote:
> Actually, I figured out from the help file a workaround, which is to put all
> the commands into a function and then do: silent call Function()
>
> It is funny how often functions are the workaround for a lot of the quirks in
> the Vim ecosystem
Actually, I figured out from the help file a workaround, which is to put all
the commands into a function and then do: silent call Function()
It is funny how often functions are the workaround for a lot of the quirks in
the Vim ecosystem.
Anyway, I think I will go with that - at least for now
On Di, 18 Aug 2020, 'J S' via vim_use wrote:
> Yes! "sil" works well - in the simple case. Thanks for that.
>
> Now, on to the next. Suppose we have another command like:
>
> vim -c '...' -c '...' -c '...' and so on and so forth - a long series of
> commands that modify the text, then finall
Yes! "sil" works well - in the simple case. Thanks for that.
Now, on to the next. Suppose we have another command like:
vim -c '...' -c '...' -c '...' and so on and so forth - a long series of
commands that modify the text, then finally dump me into the editor. I want all
of them silenced - an
vim -c 'sil%!someFilter' someFile
:h :sil
--
--
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 t
I have a line in a shell script like:
vim -c '%!someFilter' someFile
The idea is to run the contents of someFile through someFilter before doing
further editing.
It works fine, except for one thing. After the filter runs, but before
displaying the file onscreen, it displays a message at the b
