You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
A VSCode extension that provides language support for Logtalk. Forked from the [original extension](https://github.com/arthwang/vsc-logtalk) by Arthur Wang.
4
4
5
-
Requires **Logtalk 3.97.0** or later and a supported [Prolog backend](https://logtalk.org/download.html#requirements). As this extension uses supporting code that's part of the Logtalk distribution, use of the latest Logtalk version is strongly recommended.
5
+
Requires **Logtalk 3.99.0** or later and a supported [Prolog backend](https://logtalk.org/download.html#requirements). As this extension uses supporting code that's part of the Logtalk distribution, use of the latest Logtalk version is strongly recommended.
6
6
7
7
🙏 Sponsored by [Permion](https://permion.ai/) and [GitHub Sponsors](https://github.com/sponsors/pmoura).
8
8
@@ -184,6 +184,7 @@ Project (workspace) commands can be triggered from the command palette by typing
184
184
| Open Logtalk | Opens Logtalk in an integrated terminal |
185
185
| Make | Sub-menu with available make targets |
186
186
| Scan Project Dead Code | Recursively scans the workspace root folder for dead code |
| Compute Project Metrics | Recursively computes metrics for the workspace root folder |
188
189
| Profiling | Sub-menu with code profiling commands |
189
190
| Generate Project Documentation | Recursively generates documentation for the workspace root folder |
@@ -198,6 +199,8 @@ The "Load Project" command looks for a `loader.lgt` or `loader.logtalk` file in
198
199
199
200
The "Create Loader File" command creates a `loader.lgt` file from selected Logtalk files or from all Logtalk files in a selected directory. When multiple Logtalk files are selected in the explorer, it creates a loader file containing all selected files. When a directory is selected, it finds all `.lgt` and `.logtalk` files in that directory and also includes any `loader.lgt` files found in immediate subdirectories. The command filters only Logtalk files, removes duplicates, sorts them alphabetically, and prompts for confirmation before overwriting an existing `loader.lgt` file. The created file is automatically opened after creation.
200
201
202
+
The "Check Code Portability" command reloads all files by calling `logtalk_make(force)` with the `portability` flag set to `warning`. But note that all linter warnings will be reported and added to the "Problems" pane, not just portability warnings.
203
+
201
204
The "Scan Project Dead Code", "Compute Project Metrics", "Generate Project Documentation", and "Generate Project Diagrams" commands require that the project code is already loaded. Quick fixes are provided for some of the documentation and dead code linter warnings.
202
205
203
206
The output of the "Run Project Testers" and "Run Project Doclets" commands is displayed in the "OUTPUT" pane "Logtalk Testers & Doclets" channel. The "Run Project Testers" command adds failed tests to the "PROBLEMS" pane.
@@ -217,6 +220,7 @@ These commands can be triggered from the editor/context menu via right-click in
217
220
| Open Parent File | Opens the file that loaded the active source file if any |
218
221
| Make | Sub-menu with available make targets |
219
222
| Scan Dead Code | Scans the active source file directory for dead code |
| Compute Metrics | Computes metrics for all files in the active source file directory |
221
225
| Profiling | Sub-menu with code profiling commands |
222
226
| Generate Documentation | Generates documentation for the active source file directory |
@@ -231,7 +235,7 @@ The "Load Directory" command looks for a `loader.lgt` or `loader.logtalk` file i
231
235
232
236
The "Run Tests" and "Run Tests with Coverage" commands add failed tests to the "PROBLEMS" pane. Quick fixes are provided for some test definition warnings.
233
237
234
-
The "Generate Documentation" and "Scan Dead Code" commands add linter warnings to the "PROBLEMS" pane. Quick fixes are provided for some of the warnings.
238
+
The "Generate Documentation", "Scan Dead Code", and "Check Code Portability" commands add linter warnings to the "PROBLEMS" pane. Quick fixes are provided for some of the warnings.
235
239
236
240
The output of the "Generate Documentation" and "Generate Diagrams" commands assume that the documentation and the diagrams will be browsed locally in VSCode (with the entry point being the main diagram, which can be opened using the "Open SVG in Viewer" command). The default output directories are `xml_docs` for documentation and `dot_dias` for diagrams. To generate documentation and diagrams for publication, define a _doclet_ and run it using the "Run Doclet" command.
0 commit comments