Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Linden Script Language (LSL) as built-in language in Notepad++ #245

Open
Kimpa-Tammas opened this issue Apr 29, 2024 · 6 comments
Open
Labels
new lexer Request for a new lexer

Comments

@Kimpa-Tammas
Copy link

The LSL language is used in the Second Life Metaverse to make scripts. These scripts are added in various objects to create interactions and lot of features. Currently, the LSL isn't a built-in langage of Notepad++. There's already an auto-completion on GitHub as userDefinedLang.xml, but it's no longer updated. Some developers could use Notepad++ for coding in LSL, but it's not a native language.

I propose to provide and maintain an auto-completion file with descriptions of functions, events and constants, as well as syntax highlighting.

Official LSL portal

@nyamatongwe nyamatongwe added the new lexer Request for a new lexer label Apr 29, 2024
@nyamatongwe
Copy link
Member

Only the syntax highlighting part is implemented within Lexilla. Auto-completion and similar data are application concerns.

@Kimpa-Tammas
Copy link
Author

Thank you for this clarification. And, can I send here a highlighting syntax file?

@nyamatongwe
Copy link
Member

Lexilla lexers are written in C++ and aren't Notepad++ UDL files.

@Kimpa-Tammas
Copy link
Author

Ah! I don't develop in C++, so forget it. Thank you your informations.

@pryrt
Copy link

pryrt commented May 20, 2024

@Kimpa-Tammas,

I propose to provide and maintain an auto-completion file with descriptions of functions, events and constants, as well as syntax highlighting.

Feel free to submit a UDL definition, auto-completion list, and functionList definition into the Notepad++ UDL Collection -- we don't do the "maintaining" for you, but we provide the central location, and allow users to submit PR to update the definitions, so that they can stay as "up to date" as the users of those UDL are able and willing to keep them.

@Kimpa-Tammas
Copy link
Author

I will do this. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new lexer Request for a new lexer
Projects
None yet
Development

No branches or pull requests

3 participants