Skip to content

Conversation

@laxsjo
Copy link
Contributor

@laxsjo laxsjo commented Jun 22, 2025

This PR adds support for the ".lbm" file extension, prefering it over the old ".lisp" as the latter is less precise.

It also changes all places which refer to LispBM as "Lisp" to instead use
the full capitalized form "LispBM". This aligns the UI with the above preference. This is of a slightly more opinionated change, so if you have any worries about it I can move it to a separate PR or remove it.

All identifiers in the codebase which refer to "lisp" are left as is.

laxsjo added 3 commits June 22, 2025 15:26
Adds support for the ".lbm" file extension, prefering it over the old
".lisp".

Concretely, this commit adds support for ".lbm":
- in all file dialogs
- when creating lbm and vesc packages
- when reducing lbm files
- when packing LispBM imports.

The LispBM file info dialog's text is updated to reflect this.

It also adds preference for the ".lbm" extension in the "From VESC.lbm"
filename and in some debug files' names.
Changes the extensions of the LispBM examples from ".lisp" to ".lbm".
Also renames the containing folder to "LispBM" because it feels more
consistent (and I'm renaming them all anyway).
Changes all places which refer to LispBM as "Lisp" to instead use
the full capitalized form "LispBM" to be more precise. This aligns the
UI with the change to prefer the ".lbm" extension over ".lisp".

Also removes incorrectly hyphens in compound nouns which include "lisp".
For example, "LispBM-scripts" is changed to "LispBM scripts".

Additionally changes the Discord channel name referenced in pagelisp.cpp to
match the name in the official Discord.
@vedderb
Copy link
Owner

vedderb commented Jun 25, 2025

Nice work, thanks for this one!

@vedderb vedderb merged commit 4ad4d37 into vedderb:master Jun 25, 2025
1 check passed
@github-actions github-actions bot locked and limited conversation to collaborators Jun 25, 2025
@laxsjo laxsjo deleted the feat/support-lbm-extension branch June 25, 2025 18:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants