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/f08f35f5-3b75-4634-848f-2af06fa09e8en%40googlegroups.com.
