i only really made this so i can link to it on this post on my comment. whatever-
Explanation Time! ⏱
the idea here is that those "code blocks" aren't regular code blocks, but a special syntax which the LM writes so that the UI can present that as verifiable "hyperlinks" with exact text to the actual source.
so here, the LM specified exactly which lines it wants to highlight.
meaning: its not hallucinating, and if it is, you notice it because the highlighting is wrong or doesnt match at all.
we essentially use the LM as a "highlighter" rather than a regurgitator, making mistakes obvious and correct answers immediately verifiably correct, cuz u can see the source.
explanation done-
i like mockups. and godot. so here we are.
this uses the solarized theme which looks somewhat close to the claude theme they use. somewhat close.
whatever something something ai bad or whatever, is this what u need to hear? sigh
i hope u have a nice day <3
this is very much a post i first posted on the Qwen community but then i decided that this stuff doesnt belong on blahaj zone and moved it here... oh well.
I'm not sure if I'm missing something, but can this not be solved with one Linux command?
grepThe command has a
-noption to output line numbers and-C xto providexlines of context.There's no extra software required, doesn't need an LLM, doesn't hallucinate, just a plain search.
What the LLM can do that grep can't is that it can find things by imperfect description. You need to know a text string that's exactly in the file to get grep/ack/etc. to locate it; you can be vague with an LLM and it may still be able to figure it out. It's the difference between searching for
FooBarFactoryalready knowing the exact name and trying to find the file it's in (where grep, etc. are great) and "find the code that instantiates FooBar objects infooproject and tell me what it's called" when you don't know if it was FooBarManager or FooBarFactory or it's actually a function calledmake_foo_bar()instead of factory class or there are actually three different ways to do it because of legacy code.So, a fuzzy search then?
There's several command line tools for that too.
yea no ur right, grep works great fir doin codebase search. dunno what this other peeps is going on about, for the case of file search, grep rules.
More like a conceptual search. e.g. I've used my source code explorer to get a survey of how the template handling works in llama.cpp since the sample chat code doesn't apply the same logic that llama-cli actually does.