hat uses "match" alone
doesn't?
The "containedin=ALL" may be significant too.
Best regards,
Dave
On Fri, Feb 24, 2023 at 4:13 AM 'Jürgen Krämer' via vim_dev <
vim_dev@googlegroups.com> wrote:
> [Quoting re-ordered]
>
> Hi Dave,
>
> ben.k...@gmai
Hello,
I recently added the following autocommands to my _vimrc file:
:hi ExtraWhiteSpace ctermbg=58 " Orange4 = #5f5f00
autocmd BufWinEnter,InsertLeave * syntax match ExtraWhiteSpace /
\+\ze\t\|\t\zs \+\|^ \+\|\s\+$/ containedin=ALL
autocmd InsertEnter * syntax match ExtraWhiteSpace / \+\ze\t\|
Many vim users, myself included, learn about filetype plugins
and autocommands only in an effort to disable a filetype plugin's
behavior of overriding settings specified in _vimrc.
For example, my _vimrc contains the following autocmd:
autocmd FileType * setlocal iskeyword=@,48-57,_,192-255
More
On Mon, Sep 26, 2022 at 8:38 AM Christian Brabandt
wrote:
>
> On So, 25 Sep 2022, Dave McCooey wrote:
>
> > Hi Christian,
> >
> > The file with the problem is _vimrc itself, which is how I noticed it.
> >
> > Here is a line from my _vimrc that shows the
wrong,
because if I copy _vimrc to xxx.rc, then xxx.rc does not have the problem.
Best regards,
Dave McCooey
On Sun, Sep 25, 2022 at 10:37 AM Christian Brabandt
wrote:
>
> On So, 25 Sep 2022, Dave McCooey wrote:
>
> > Hello,
> >
> > There is a problem with synt
ult ones included in the distribution.
This problem is seen with vim version 8.2 (included patches 1-4372)
on Cygwin, and also with version 8.2 (included patches 1-2072) on Linux.
I have version 7.3 running on a Mac that does not have the problem.
Best regards,
Dave McCooey
--
--
You received t
> diff --git a/src/regexp.c b/src/regexp.c
> --- a/src/regexp.c
> +++ b/src/regexp.c
> @@ -4079,6 +4079,8 @@
> mch_errmsg("(\n");
> }
> #endif
> +if (reg_buf == NUL || reg_buf == NULL)
> + reg_buf = curbuf;
>
> regards,
> Christian
I had th
I love vim's syntax highlighting ... I wish I could say "vim --cat file.c" and
have it just be a "cat file.c" (to stdout) only with all appropriate
highlighting. piping to "less -R" should work too. :)
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply be
case '\300': case '\301': case '\302':
'A' in ebcdic is decimal 193, the same as octal 301. Is it intended
that vim is compiled using the ebcdic code page?
Thanks,
Dave
--
You received this message from the "vim_dev" maillist.
Do not top-post!
It would be nice to be able to ask vim to indent wrapped text under
the first nonblank character of the line to be wrapped, or optionally
n columns to the right of that.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
Bram Moolenaar wrote:
>
> OK, then we would drop the phtml.vim syntax file. But in case someone
> has ":set ft=phtml" we should use php syntax used for phtml.
Sounds good to me. Thank you all!
Dave
--
Save the whales. Co
o use it. (The last change date
inside the file (11 May 2003) is much more recent than I'd expect, though.)
There's a huge amount of source code for PHP 4.x applications inside
organisations and around the Web, but I wouldn't expect to see anything
earlier[1]. Even PHP 4 has had
sion _was_ to some
degree historical, much like ".php3". However, now I believe use of
".phtml" for PHP 5 applications is on the rise. In order to separate
out presentational templates from the rest of an application, people
find there's a psy
Out of courtesy I've emailed Lutz Eymers (last known phtml.vim
maintainer) and Peter Hodge (syntax/php.vim) with a pointer to this
message. However the mail to Lutz failed ("mailbox disabled for this
recipient").
Regards,
Dave
--
Save the w
filetype instead.
3. Amend synmenu.vim so there's only one PHP menu item, just called
"PHP". This might also be a good time to update "Cold Fusion" to
"ColdFusion" (no space in name).
Many Thanks,
Dave
[1] It was released in 1995, the same time
15 matches
Mail list logo
