-
Notifications
You must be signed in to change notification settings - Fork 56
Generate editor keywords #526
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
Conversation
xsebek
commented
Jul 1, 2022
- part of Create command line tools to automate documentation #344
I updated the VS Code plugin to highlight the new keywords: But it could use a bit more love - update the image link, CHANGELOG,... |
"left" "right" "back" "forward" "north" "south" "east" "west" "down" | ||
)) | ||
(x-builtins '( | ||
"if" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@byorgey or @TristanCacqueray, do either of you use EMacs and could check this works, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works great!
@@ -56,7 +56,7 @@ | |||
}, | |||
{ | |||
"name": "keyword.other", | |||
"match": "\\b(?i)(noop|wait|selfdestruct|move|turn|grab|place|give|install|make|has|count|drill|build|salvage|reprogram|say|log|view|appear|create|whereami|blocked|scan|upload|ishere|whoami|random|run|if|inl|inr|case|fst|snd|force|return|try|raise|not)\\b" | |||
"match": "\\b(?i)(noop|wait|selfdestruct|move|turn|grab|harvest|place|give|install|make|has|count|drill|build|salvage|reprogram|say|log|view|appear|create|whereami|blocked|scan|upload|ishere|self|parent|base|whoami|setname|random|run|if|inl|inr|case|fst|snd|force|return|try|undefined|fail|not|format|teleport|as|robotnamed|robotnumbered|knows)\\b" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could check those strings can be found in editor files in the integration test. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done ✔️
editors
VS Code
operators: OK
commands: OK
directions: OK
EMacs
builtin: OK
commands: OK
directions: OK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good, except---and this is being very nitpicky---could we do a search and replace to have Emacs
instead of EMacs
? Emacs
is never written with a capital M
and it looks strange to me.
@@ -214,3 +219,38 @@ printAllLogs g = | |||
mapM_ | |||
(\r -> forM_ (r ^. robotLog) (putStrLn . T.unpack . view leText)) | |||
(g ^. robotMap) | |||
|
|||
-- | Test that editor files are up-to-date. | |||
testEditorFiles :: TestTree |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Weird, what's up with Mergify? 🤨 |
This happened to me once before. It took a while but it eventually worked. |
- part of #344