Re: FreeBSD Port: vim-lite-7.3.121
On Thu, Apr 07, 2011 at 10:00:34AM -0400 I heard the voice of Niek Dekker, and lo! it spake thus: > > in my case, I have found that the issue can be avoided by including > the following line in the system-wide vimrc or your user .vimrc: > > nocp Good catch. If I :set compatible, I get a pile of errors from turning :syn on -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
On Thu, Apr 07, 2011 at 10:05:49AM -0400 I heard the voice of Wesley Shields, and lo! it spake thus: > > Are you using syntax highlighting? Yes. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
On Thu, Apr 07, 2011 at 08:27:58AM -0500, Matthew D. Fuller wrote: > On Thu, Apr 07, 2011 at 08:57:12AM -0400 I heard the voice of > Wesley Shields, and lo! it spake thus: > > > > I get a similar problem when editing python files. > > For a data point, I edit .php files all day long, and .py files > occasionally (with both full vim and vim-lite), and have never seen > this with either... Are you using syntax highlighting? -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
For the record, this is with using vim-lite on FreeBSD. I never install full vim. I cannot speak for those who did not encounter this issue. Those who did, however, may take notice of the following: in my case, I have found that the issue can be avoided by including the following line in the system-wide vimrc or your user .vimrc: nocp This prevents vim from using vi compatibility. niek On Thu, Apr 7, 2011 at 9:27 AM, Matthew D. Fuller wrote: > On Thu, Apr 07, 2011 at 08:57:12AM -0400 I heard the voice of > Wesley Shields, and lo! it spake thus: >> >> I get a similar problem when editing python files. > > For a data point, I edit .php files all day long, and .py files > occasionally (with both full vim and vim-lite), and have never seen > this with either... > > > -- > Matthew Fuller (MF4839) | fulle...@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
On Thu, Apr 07, 2011 at 08:57:12AM -0400 I heard the voice of Wesley Shields, and lo! it spake thus: > > I get a similar problem when editing python files. For a data point, I edit .php files all day long, and .py files occasionally (with both full vim and vim-lite), and have never seen this with either... -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
On Wed, Apr 06, 2011 at 10:33:53AM -0700, David O'Brien wrote: > On Wed, Mar 23, 2011 at 11:13:45PM -0400, Niek Dekker wrote: > > Using the "syntax on" command in .vimrc. When opening a php file in Vim, > > a lot of errors are being displayed. The errors are caused by line > > continuation characters in /usr/local/share/vim/vim73/syntax/php.vim. > > Hi I really don't know anything about PHP. Can you point out the line > number (and line content) of an example of this in > /usr/local/share/vim/vim73/syntax/php.vim? > > I found /usr/local/share/doc/antiword/antiword.php on my system and am > assuming it is an OK example of a PHP file. Syntax colouring works OK > with Vim 7.3.121 (non-lite). Have you tried the non-lite build? > > > Somehow, in FreeBSD Vim does not seem to recognize the line continuation > > character and complains about it, resulting in errors when opening a > > syntax file containing these characters. > > > > What is the solution to this, if you know any? > > So that I know what to look at, can you also send the error messages you > are seeing (and any required file(s) to reproduce the issue? I get a similar problem when editing python files. To trigger it all I have to do is have "syntax on" in my .vimrc, then edit a file with the .py extension (it can be a totally new file). The first few errors, and there are more, are: Error detected while processing /usr/local/share/vim/vim73/syntax/python.vim: line 86: E475: Invalid argument: pythonFunction line 87: E10: \ should be followed by /, ? or & line 93: E475: Invalid argument: pythonString line 94: E10: \ should be followed by /, ? or & line 95: E10: \ should be followed by /, ? or & line 96: -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: vim-lite-7.3.121
On Wed, Mar 23, 2011 at 11:13:45PM -0400, Niek Dekker wrote: > Using the "syntax on" command in .vimrc. When opening a php file in Vim, > a lot of errors are being displayed. The errors are caused by line > continuation characters in /usr/local/share/vim/vim73/syntax/php.vim. Hi I really don't know anything about PHP. Can you point out the line number (and line content) of an example of this in /usr/local/share/vim/vim73/syntax/php.vim? I found /usr/local/share/doc/antiword/antiword.php on my system and am assuming it is an OK example of a PHP file. Syntax colouring works OK with Vim 7.3.121 (non-lite). Have you tried the non-lite build? > Somehow, in FreeBSD Vim does not seem to recognize the line continuation > character and complains about it, resulting in errors when opening a > syntax file containing these characters. > > What is the solution to this, if you know any? So that I know what to look at, can you also send the error messages you are seeing (and any required file(s) to reproduce the issue? -- -- David (obr...@freebsd.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: vim-lite-7.3.121
Hi there. This is an issue in FreeBSD with Vim I cannot solve and I am writing you, the port maintainer about this. I have been using Vim in Freebsd for a number of years but have had a problem with syntax coloring ever. I am running FreeBSD 7.x and 8.x on i386 and amd64. Currently using Vim-lite 7.3.121. Using the "syntax on" command in .vimrc. When opening a php file in Vim, a lot of errors are being displayed. The errors are caused by line continuation characters in /usr/local/share/vim/vim73/syntax/php.vim. In Vim command files, the line continuation character is the backslash. However, in contrast to shell scripts, the backslash is at the beginning of the new line and not at the end of the continued line. Are you still with me? The same occurs with the Python syntax coloring file, I just checked. Somehow, in FreeBSD Vim does not seem to recognize the line continuation character and complains about it, resulting in errors when opening a syntax file containing these characters. What is the solution to this, if you know any? Niek ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
