eloquence syntax

[macMikey]

syntax for both eloquence program files and eloquence dialog files
https://eloquence.marxmeier.com/

[braver]

Please use the checklist in the PR template to tell us about your package.

[packagecontrol-bot]

Automated testing result: WARNING

Repo link: Eloquence Syntax
Results help

Packages added:
  - Eloquence Syntax

Processing package "Eloquence Syntax"
  - WARNING: '.sublime-syntax' support has been added in build 3092 and there is no '.tmLanguage' fallback file
    - File: eloquence.sublime-syntax

[macMikey]

is this what you mean? i did not see the template, so i copied the template from another PR

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• If my package is a syntax it is named after the language it supports (without suffixes like "syntax" or "highlighting").
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

there are no extraneous files or directories in the repo, so, there is no need for .gitattributes

[braver]

Was this intended to be a syntax file too? https://github.com/macMikey/eloquence-sublime-text-syntax/blob/main/dlg-sublime-syntax.yaml

[braver]

In captures, you don't need to put quotes around the indexes. Also please ensure all scopes end with .eq (matching "source.eq"). Also please double check the guidelines, you might be able to specify some of those keywords. E.g.:

captures:
        1: keyword.control.eq
        2: entity.name.function.eq

[macMikey]

Was this intended to be a syntax file too? https://github.com/macMikey/eloquence-sublime-text-syntax/blob/main/dlg-sublime-syntax.yaml

there are two types of eloquence files: eloquence program files (.eq), and eloquence dialog files (.dlg). they are supposed to be included.

[macMikey]

thanks for your patience, i'm a package n00b

[braver]

You'll probably want to rename dlg-sublime-syntax.yaml to dlg.sublime-syntax then.

thanks for your patience, i'm a package n00b

No worries, that's what we're here for 😉

[packagecontrol-bot]

Automated testing result: WARNING

Repo link: Eloquence
Results help

Packages added:
  - Eloquence

Processing package "Eloquence"
  - WARNING: '.sublime-syntax' support has been added in build 3092 and there is no '.tmLanguage' fallback file
    - File: eloquence.sublime-syntax

[macMikey]

You'll probably want to rename dlg-sublime-syntax.yaml to dlg.sublime-syntax then.

thanks for your patience, i'm a package n00b

No worries, that's what we're here for 😉

done. thanks, again.

[braver]

Alright, main thing then remains that all scopes need to end with the identifier of the syntax, ie. keyword.dlg and keyword.eq, etc. This makes it possible for package developers to target your specific syntax.

[macMikey]

so: in the .dlg syntax file, all of the scopes end in .dlg and in the .eq file, all the scopes end in .eq?

[braver]

Yes. Basically your base scope for a syntax is source.XX and then you make sure all the scopes in that syntax also end with .XX

[macMikey]

just pushed 0.0.2. is that what i should be doing? i took every scope line, and ended the label with .eq

[braver]

Almost!

source.dlg.eq should still be source.dlg

Also remember that your captures also assign scopes, so you need to cover those as well.

Have a look at some example syntaxes like https://github.com/sublimehq/Packages/blob/master/CSS/CSS.sublime-syntax#L3216C1-L3224C43

[macMikey]

• source.dlg updated
• captures updated

thanks for all the help.

[braver]

Looks good!

[macMikey]

thanks for all the help.
package-control n00b...out

[braver]

🫡