On Friday, December 30, 2022 at 10:17:27 PM UTC-7 ozu...@gmail.com wrote:
Got an update regarding this. As you suggested, I ran vim with --clean option and it is much more reliable and steadier than I have been experiencing for past few months. Could you help with recommending how to proceed with my .vimrc and plugins to find the culprit? I mean how should I start incorporating my settings in?Question 2: If I wanted to updated my vim version to 9, would it be recommended and most importantly safe to use the ppa approach?Thanks a lot in advance.On Monday, December 19, 2022 at 11:03:00 PM UTC-6 3nan....@gmail.com wrote:On Mon, 19 Dec 2022 20:55:23 +0000 (UTC)
"'hilal Adam' via vim_use" <vim...@googlegroups.com> wrote:
> Thanks for your reply. I am not sure what '$ vim --clean' does. Is
> this another way running vim? On Monday, December 19, 2022 at
You have to run it from your shell. It'll open Vim without any
user-level configuration. If the issue persists without your user-level
config, we can be sure it's a bug in Vim. But if it can't be reproduced
without '--clean', then we can be sure the problem is being caused by
your config. Either way, it'll narrow the suspects.
Read ':h --clean' for more details.
--
Enan
3nan....@gmail.com
https://git.sr.ht/~enan/
https://www.github.com/3N4N
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/94a5fd17-7d30-490c-8b89-7af70a0a0fb5n%40googlegroups.com.
No comments:
Post a Comment