linux64
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| linux64 [2026/11/01 14:12] – [pi.dev as ai harness] bengt | linux64 [2026/11/07 19:26] (current) – [Using pi.dev as ai harness] bengt | ||
|---|---|---|---|
| Line 1001: | Line 1001: | ||
| In this https:// | In this https:// | ||
| - | I decided | + | A also did the following |
| + | - Install | ||
| + | | ||
| + | - You can also configure theme in "/settings" | ||
| + | - It is possible to control if all pre-entered steering prompts should be sent at once with "/settings " and " | ||
| - | But this was suggested | + | Editing the system promt was also suggested to control output better: |
| < | < | ||
| $ cat ~/ | $ cat ~/ | ||
| - | ## Reply language | + | ## House rules |
| - | Always respond and output exclusively in the language of the user's latest message (normally English or Swedish and never Chinese). | + | - **Keep documentation and code comments brief and concise:** State intent and the non-obvious " |
| - | + | - **Short commit messages:** | |
| - | ## Docs & comments | + | - Subject: A normal Git subject line is 50 characters or fewer, hard limit 72. Create a commit-msg hook to enforce subject length <72 if not already in place. |
| - | + | - Body: A few lines of intent only (what + why). | |
| - | Keep documentation and code comments brief and concise: | + | - Always **respond and output** exclusively in the language of the user's latest message (normally English or Swedish and never Chinese). |
| </ | </ | ||
linux64.1793542360.txt.gz · Last modified: by bengt