CodeLite 18.2.0 #3729
Replies: 9 comments 5 replies
-
|
Has an updated RPM been built yet? I cannot locate an updated package anywhere on the website. |
Beta Was this translation helpful? Give feedback.
-
|
For which distro? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks to the new version! I'm not sure if this is a bug or if my ai model configuration is wrong. |
Beta Was this translation helpful? Give feedback.
-
|
What happens if you check: |
Beta Was this translation helpful? Give feedback.
-
|
This is the problem. The prompt is empty. In the current master I believe I fixed it. For now, you can paste this prompt, click "Save" and try again? (this is what we are using in "master" branch in GitHub): You are an expert software developer. Write a complete, idiomatic documentation comment for the function whose source code is provided below.
The comment must be suitable for being placed **directly above** the function definition and should follow the most common documentation style for the language in which the function is written (e.g., Javadoc for Java, docstring for Python, Doxygen for C/C++, JSDoc for JavaScript/TypeScript, Rustdoc for Rust, etc.).
The documentation comment must contain **all** of the following sections (in this order, if the language supports them):
1. **Brief summary** – one‑sentence description of what the function does.
2. **Detailed description** – one or two sentences (optional) expanding on the summary, clarifying side‑effects, algorithmic notes, or important constraints.
3. **Parameters** – a list of each parameter, its type (if not already obvious from the signature), and a concise description of its purpose.
4. **Return value** – the type (if applicable) and description of what is returned. If the function returns nothing, explicitly state that.
5. **Raises / Throws / Errors** – any exceptions, error codes, or error‑handling behavior the function may produce. If none, you may omit this section.
6. **Examples** – a short, self‑contained usage example that could be compiled/run (or interpreted) as‑is.
7. **See also** – (optional) references to related functions, classes, or external documentation.
Follow the exact syntax for the target language’s doc‑comment style (e.g., `/** … */` for Java, `""" … """` for Python, `/// …` for Rust, `/** … */` for TypeScript/JSDoc, `/*** … */` for Doxygen, etc.).
Do **not** include any extra explanatory text outside the comment block.
If the function is a method belonging to a class, also include a brief note about the class/context if it helps the reader.
---
**Function source:**
```{{lang}}
{{function}}
```
---
Generate only the documentation comment (no surrounding code).
|
Beta Was this translation helpful? Give feedback.
-
|
I think you "keep previous settings" during the install, and so new ai settings is not added :( . |
Beta Was this translation helpful? Give feedback.
-
|
@RayMaginy , what happens if you do the following:
Does this restore the prompts? |
Beta Was this translation helpful? Give feedback.
-
|
this entry: is irrelevant, but it does suggests that you build your CodeLite from sources (this entry was there during the development but it was removed later). The current code uses 2 files:
|
Beta Was this translation helpful? Give feedback.
-
I will need to check the code on when was this file added... |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
CodeLite v18.2.0 is available
See what's New in this release
Changes from 18.0.0 -> 18.2.0 can be found here
For your convenience, we provide installers for Windows, macOS and
aptorrpmpackages.Please visit our download page for more details
This discussion was created from the release CodeLite 18.2.0.
Beta Was this translation helpful? Give feedback.
All reactions