Ok, let me try this. (I finally got 'git diff' to work.)
diff --git a/C:/Users/marke/Documents/GitHub/vim/runtime/syntax/c.vim
b/C:/Program Files (x86)/Vim/vim91/syntax/c.vim
index c217c23d8..3bd2ec963 100644
--- a/C:/Users/marke/Documents/GitHub/vim/runtime/syntax/c.vim
+++ b/C:/Program Files (x86)/Vim/vim91/syntax/c.vim
@@ -459,6 +459,58 @@ else
exec "syn sync ccomment cComment minlines=" . b:c_minlines
endif
+"
+" Standard C Library Functions Table, By Name
+" Put in by Mark Manning on July 12th, 2025.
+"
+syn keyword cStdCLibFunctions abort abs acos asctime asctime_r asin assert
atan
+syn keyword cStdCLibFunctions atexit atof atoi atol bsearch btowc calloc
catclose
+syn keyword cStdCLibFunctions catgets catopen ceil clearerr clock cos cosh
ctime
+syn keyword cStdCLibFunctions ctime64 ctime_r ctime64_r difftime
difftime64 div
+syn keyword cStdCLibFunctions erf erfc exit exp fabs fclose fdopen feof
ferror
+syn keyword cStdCLibFunctions fflush fgetc fgetpos fgets fgetwc fgetws
fileno
+syn keyword cStdCLibFunctions floor fmod fopen fprintf fputc fputs fputwc
fputws
+syn keyword cStdCLibFunctions fread free freopen frexp fscanf fseek fsetpos
+syn keyword cStdCLibFunctions ftell fwide fwprintf fwrite fwscanf gamma
getc
+syn keyword cStdCLibFunctions getchar getenv gets getwc getwchar gmtime
gmtime64
+syn keyword cStdCLibFunctions gmtime_r gmtime64_r hypot isalnum isalpha
isascii
+syn keyword cStdCLibFunctions isblank iscntrl isdigit isgraph islower
isprint
+syn keyword cStdCLibFunctions ispunct isspace isupper iswalnum iswalpha
iswblank
+syn keyword cStdCLibFunctions iswcntrl iswctype iswdigit iswgraph iswlower
iswprint
+syn keyword cStdCLibFunctions iswpunct iswspace iswupper iswxdigit isxdigit
+syn keyword cStdCLibFunctions j0 j1 jn labs ldexp ldiv localeconv
localtime localtime64
+syn keyword cStdCLibFunctions localtime_r localtime64_r log log10 longjmp
malloc
+syn keyword cStdCLibFunctions mblen mbrlen mbrtowc mbsinit mbsrtowcs
mbstowcs mbtowc
+syn keyword cStdCLibFunctions memchr memcmp memcpy memmove memset mktime
mktime64
+syn keyword cStdCLibFunctions modf nextafter nextafterl nexttoward
nexttowardl
+syn keyword cStdCLibFunctions nl_langinfo perror pow printf putc putchar
putenv puts
+syn keyword cStdCLibFunctions putwc putwchar qsort quantexpd32 quantexpd64
quantexpd128
+syn keyword cStdCLibFunctions quantized32 quantized64 quantized128
samequantumd32
+syn keyword cStdCLibFunctions samequantumd64 samequantumd128 raise rand
rand_r
+syn keyword cStdCLibFunctions realloc regcomp regerror regexec regfree
remove
+syn keyword cStdCLibFunctions rename rewind scanf setbuf setjmp setlocale
setvbuf
+syn keyword cStdCLibFunctions signal sin sinh snprintf sprintf sqrt srand
sscanf
+syn keyword cStdCLibFunctions strcasecmp strcat strchr strcmp strcoll
strcpy strcspn
+syn keyword cStdCLibFunctions strerror strfmon4 strftime strlen
strncasecmp strncat
+syn keyword cStdCLibFunctions strncmp strncpy strpbrk strptime4 strrchr
strspn strstr
+syn keyword cStdCLibFunctions strtod strtod32 strtod64 strtod128 strtof
strtok strtok_r
+syn keyword cStdCLibFunctions strtol strtold strtoul strxfrm swprintf
swscanf system
+syn keyword cStdCLibFunctions tan tanh time time64 tmpfile tmpnam toascii
tolower toupper
+syn keyword cStdCLibFunctions towctrans towlower towupper ungetc ungetwc
va_arg va_copy
+syn keyword cStdCLibFunctions va_end va_start vfprintf vfscanf vfwprintf
vfwscanf
+syn keyword cStdCLibFunctions vprintf vscanf vsprintf vsnprintf vsscanf
vswprintf
+syn keyword cStdCLibFunctions vswscanf vwprintf vwscanf wcrtomb wcscat
wcschr wcscmp
+syn keyword cStdCLibFunctions wcscoll wcscpy wcscspn wcsftime wcslen
wcslocaleconv
+syn keyword cStdCLibFunctions wcsncat wcsncmp wcsncpy wcspbrk wcsptime
wcsrchr
+syn keyword cStdCLibFunctions wcsrtombs wcsspn wcsstr wcstod wcstod32
wcstod64 wcstod128
+syn keyword cStdCLibFunctions wcstof wcstok wcstol wcstold wcstombs
wcstoul wcsxfrm4
+syn keyword cStdCLibFunctions wctob wctomb wctrans wctype wcwidth wmemchr
wmemcmp
+syn keyword cStdCLibFunctions wmemcpy wmemmove wmemset wprintf wscanf y0
y1 yn
+
" Define the default highlighting.
" Only used when an item doesn't have highlighting yet
hi def link cFormat cSpecial
@@ -501,6 +553,8 @@ hi def link cPreConditMatch cPreCondit
hi def link cPreCondit PreCondit
hi def link cType Type
hi def link cFunction Function
+hi def link cStdCLibFunctions StdCLibFunctions
hi def link cConstant Constant
hi def link cCommentString cString
hi def link cComment2String cString
@@ -523,5 +577,3 @@ let &cpo = s:cpo_save
unlet s:cpo_save
" vim: ts=8
-
-
On Tuesday, July 15, 2025 at 2:24:50 PM UTC-5 Mark Manning wrote:
> Ok. I went online, read the instructions on doing a pull
> request, and it said I should download the repository and
> work from there. I did that so I had it on my system. I
> put in the changes and said to push those back to the
> repository. However, GitHub responded that I do not have
> privileges to push to the master repsoitory. So should I
> just fork the repository at markem/vim? Or do you want me
> to do something else? I used to use subversion at NASA
> but that was the early 2000's. I use GitHub for my own
> projects but I really-really don't want to muck up the
> VIM repository. So if you can let me know what I should
> do I'd appreciate it.
>
> By changing the name to cStdCLibFunctions - this can now be
> used in a contain=cStdCLibFunctions clause or just used on
> the "hi def link" command like other names are also used.
>
> I'd also like to include a cSymbols command. Like so:
>
> syn match cSymbols "[\+\-\=\|\*\/\>\<\%\()[\]\!\^\{\}]"
>
> First, I have not put this into the repository. This
> is just a "would you like me to put this into the same
> file?" question. I, personally, like colorful layouts. It
> is easier on my eyes but some people would probably not
> like it. So give me a yes or no on this if you will and
> I'll put it in or leave it out. :-)
> On Monday, July 14, 2025 at 4:16:30 PM UTC-5 Mark Manning wrote:
>
>> Sorry - I decided that name was way too long and shortened it to
>>
>> cStdCLibFunctions
>>
>>
>> On Monday, July 14, 2025 at 4:09:56 PM UTC-5 Mark Manning wrote:
>>
>>> @Doug Kearns,
>>>
>>> Ok. How about if I made it something like
>>>
>>> cStandardCLibraryFunctions
>>>
>>> as the name and then the list could then be included into a
>>> later cFunction command? Would that be a good idea? Also,
>>> I think I'm going to have to try the command that is in the
>>> "still to be released" c.vim that you posted about. I want
>>> to test it out to see if it is better than what I put into
>>> my c.vim file. If it is - then I'll take mine back out of
>>> what I have.
>>>
>>> On Monday, July 14, 2025 at 6:57:08 AM UTC-5 Doug Kearns wrote:
>>>
>>>> Mark,
>>>>
>>>> Re: https://www.vim.org/scripts/script.php?script_id=6159
>>>>
>>>> On Sun, 13 Jul 2025 at 16:30, Mark Manning
>>>> <mark.euge...@gmail.com> wrote:
>>>> >
>>>> > Using Vim 9.1
>>>> >
>>>> > Hi everyone! I got a C source file and started to edit it and did not
>>>> see my colors come up like normal. So for the last five hours I have been
>>>> working on making changes to the C.VIM syntax file. I was wondering if it
>>>> can be included into the next release. I uploaded it to my account on the
>>>> VIM website (Bram's website). But I can upload it here if you want.
>>>> >
>>>> > Things I have done to the file:
>>>> >
>>>> > 1. I went to the IBM webpage on the Standard C functions and
>>>> copy/pasted all of them into the C.VIM file. Edited the list to just get
>>>> the function names and built a "syn keyword" list of the functions.
>>>> > 2. I took the generic function code I had put into the iwbasic.vim
>>>> syntax file and put it at the end of the list of functions so now all
>>>> functions are captured. (I might need to try some weird function names to
>>>> make sure I got everything.)
>>>> > 3. Added in the:
>>>> >
>>>> > hi def link cFunction Function
>>>> >
>>>> > so the functions will now show up as functions.
>>>> >
>>>> > 4. Put a blurb in about what I did. I put this at the top of the list
>>>> of functions.
>>>> >
>>>> > Let me know if you want me to upload it here.
>>>>
>>>> We already have general function call highlighting,
>>>> https://github.com/vim/vim/blob/master/runtime/syntax/c.vim#L551-L557,
>>>> but it hasn't made a release yet.
>>>>
>>>> I had a quick look at your additions and it seems that the library
>>>> functions should be defined with :syn-contained and contained in the
>>>> general function call syntax group. I'm not sure this should be
>>>> enabled by default and it could, optionally, be configured per
>>>> library.
>>>>
>>>> My assumption is that this was not an oversight but a preference of
>>>> Bram's given the nature of C.
>>>>
>>>> Thanks,
>>>> Doug
>>>>
>>>
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/vim_dev/fa1f9fb0-e63f-44b9-a80a-5e85e0ef28a1n%40googlegroups.com.
