Hi @LeeTownsend,

I don't have permission to edit the issue, so would you mind changing the name of the issue to VB/VBA Support, or something like that? It makes it easier to identify the issue in a list.

Separately, if I were to help you get set up, would you be willing to take a stab at contributing the Mode yourself? I can give you the basic template and walk you through getting started. Otherwise, we unfortunately need to find someone who is well-versed in VB/VBA before we can get to this.

I don't understand what you want me to do. Also, I don't remember what the product is to which I wanted to add VBA. I doubt I have the knowledge necessary to contribute the mode myself. I am a Fortran programmer turned Excel VBA programmer.

Hi @LeeTownsend,

Well the first thing I'd like you to do is just change the name of this issue to "VB/VBA Support". "Missing language" is just not a great name for a bug in a list. I would do this myself but I don't have permissions to change the title of the bug. I believe you, the author, do.

Aside from this, I didn't necessarily want you to "do" anything. I was simply offering my time to walk you through the creation of a Syntax Mode file to allow you to add the VB/VBA support to SubEthaEdit that satisfied your needs, which we could then add to the standard set provided by SubEthaEdit by default. Syntax Modes are plugins that allow SubEthaEdit to support new languages. They can be as straight forward as listing the file extensions SubEthaEdit should recognize as "VB" files, and the keywords to highlight. They can be as complex as defining code folding areas and much more. Given that I am not a VB/VBA programmer, I am not terribly well suited to providing this plugin myself, and generally members of the individual programming communities do a better job, so I was simply asking if you were interested in having me help you set one up.