A typical use case would be $(HOME)/.cache/cpm/somelib/file.h.
Special care is needed to avoid filtering out dot-dot path elements: /../
While these have been normalized for some time now on the client-side, old
traces might still contain the dot-dot elements.
Before this commit, vertical scroll was always discrete. At least on
Wayland, this caused extremely fast scrolling on touchpads (that send
lots of small axis events) and on mice with high-resolution wheels (that
also send lots of small axis events). After this commit, all of this
scrolling works correctly, at a speed matching regular wheels.
Regular mice send a value of 15 for one wheel tick, not 8.
This currently doesn't change anything about vertical scrolling since
it's handled discretely, but that will change in the next commit.
In most cases this is not needed. However, some models, like Gemma3 or
Devstral require that user and assistant messages alternate.
The only case where this can happen in Tracy is when an attachment is added:
[
{
"role": "user",
"content": "<attachment>\n..."
},
{
"role": "user",
"content": "Tell me something about..."
}
]
It is trivial to glue these messages together. This is only done when sending
the data in the REST request, as the chat rendering logic expects these to be
separate and it would be too much work unnecessary work to do it "proper".
Nemotron 3 Nano outputs these spaces in the text. The currently used font
(or is it ImGui?) is not able to render this, and draws replacement character
instead.
Previously reasoning and tool calls were rendered first, followed by
content. The tool call response was then rendered in the second reasoning
section. This made the tool call and response disjoint and, with the
current reasoning hiding logic, not visible at the same time.
