I tried something based on your original suggestion:
$ export VIM=/usr/share/vim
which seems to 'work' (no longer any interruption when opening a file with vim, and syntax highlighting is working). How would I set this to always be implemented whenever cygwin is run?
Thanks,
John
On Fri, Feb 16, 2024 at 6:43 PM Salman Halim <salmanhalim@gmail.com> wrote:
In my Windows environment, VIM and VIMRUNTIME are regular environment variables that I can edit like any others. If that doesn't work, maybe they're defined in your shell's RC file?Salman--On Fri, Feb 16, 2024, 17:18 John Cordes <john.cordes@dal.ca> wrote:--Thanks for the thought. In Cygwin echo $PATH shows all forward slashes. Did you mean to somehow edit things like $VIMRUNTIME? I'm not sure how that would be done.JohnOn Fri, Feb 16, 2024 at 6:11 PM Salman Halim <salmanhalim@gmail.com> wrote:This may be too simple, but have you tried changing the environment variables variables to have forward slashes instead of back slashes?Salman--On Fri, Feb 16, 2024, 16:46 John Cordes <John.Cordes@dal.ca> wrote:--I'm hoping someone can help with a problem. I've had cygwin64 installed for at least a couple of years, with Vim v8 running just fine. I also have Windows Vim running; this is all under Win 10.I've just updated the cygwin64 installation and vim is now v9.0. When I start the cygwin vim I get these lines:
===========================Error detected while processing /etc/vimrc:line 90:E484: Can't open file C:UsersOwner_vim/vim90/syntax/syntax.vimError detected while processing /home/Owner/.vimrc:line 6:E484: Can't open file C:UsersOwner_vim/vim90/syntax/syntax.vimPress ENTER or type command to continue===========================
Pressing ENTER allows me to continue, editing files, etc. but not surprisingly with no syntax highlighting.
:echo $VIMRUNTIME = C:\Users\Owner\_vim/vim90
Note the mixed up forward and backward slashes in that path. Note also the lack of slashes in the paths reported above as E484.
It seems clear that there is some sort of clash between Unix and Windows path conventions going on but I haven't been able to figure out how to fix it.
The file syntax.vim does exist and is in the right location (I think):$ ls -l /usr/share/vim/vim90/syntax/syntax.vim-rw-r--r-- 1 Owner Administrators 1.4K Dec 20 01:57 /usr/share/vim/vim90/syntax/syntax.vim
vim --version includes these lines:VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 20 2023 06:57:02)
Included patches: 1-2155system vimrc file: "/etc/vimrc"user vimrc file: "$HOME/.vimrc"2nd user vimrc file: "~/.vim/vimrc"user exrc file: "$HOME/.exrc"defaults file: "$VIMRUNTIME/defaults.vim"fall-back for $VIM: "/usr/share/vim"One more item::scriptnames1: /etc/vimrc2: ~/.vimrc3: ~/.vim/keymap/insert_only_capslock.vim4: ~/.vim/bufferlist.vim5: ~/.vim/plugin/matchit.vim
Thanks for any help!
John Cordes
--
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/QB1PR01MB29933933E4C6D2C0145DDA0B9E4C2%40QB1PR01MB2993.CANPRD01.PROD.OUTLOOK.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 on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEeF0f_A2%2BfXGS6oZRn_%3Ds17W7yDfyCORm3D68AD2GjAZw%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 on the web visit https://groups.google.com/d/msgid/vim_use/CAGZBEdTa-CCta_7kJNcDxzwcSn%3DsTu_45OSx%2B3zwZjs%2BDPRZbA%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 on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcRM15OLaxHs03cW6drhxa7zyK4eMYV2vT6jufHZ6R9hA%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 on the web visit https://groups.google.com/d/msgid/vim_use/CAGZBEdTrH%3DzEK7XgnZ-EELN15YrAXKY14-vndOTdcCFnOmxQaw%40mail.gmail.com.
No comments:
Post a Comment