Lightnews — Scholar-powered news

noClaps @zerolimits.dev · 5h

for cities, every 24 hours, a day passes. together, we can stop this

noClaps @zerolimits.dev · 5h

are you the one panting

noClaps @zerolimits.dev · 2d

im getting deja vu

1

noClaps @zerolimits.dev · 2d

i genuinely thought this was a github link for a sec lol

1

noClaps @zerolimits.dev · 3d

what happens

2

noClaps @zerolimits.dev · 4d

i also think people dont utilise advanced techniques like "fact-checking" and "looking things up" enough

1

noClaps @zerolimits.dev · 4d

its almost as if 300 characters isnt enough to fit enough nuance and detail to have a proper discussion or something

that's why i usually prefer reading/writing blog posts for detailed information over <insert microblogging platform here> posts, or just have a chat in a chatroom about it

1 1

noClaps @zerolimits.dev · 5d

top is original img tag, bottom is inline svg. safari 26.0.1

1

noClaps @zerolimits.dev · 5d

i wonder if its the <img> tag that's causing issues, because i see it on safari too, but the svgs themselves are fine, and if i inline them using devtools it works fine too

1 1

noClaps @zerolimits.dev · 5d

who is the absolute and how may i get in touch with them

1 1

noClaps @zerolimits.dev · 6d

i dont mind making big changes early on, i just dont want this project to be a waste of my and everyone else's time if almost no one ends up using it, which is why im being cautious with simply implementing one editor's standard and calling it a day

noClaps @zerolimits.dev · 6d

having looked at the queries for nvim and helix, im very aware lol. if you'd like to propose a new set of capture groups that you can be reasonably sure that all editors will be willing to adopt, you can open an issue or pull and maybe other people interested in the project can weigh in too

2

noClaps @zerolimits.dev · 6d

P.S. i know that's not strictly true, the different editors have different feature sets, but it would be nice if, at least with the tree-sitter stuff, they didnt need to reimplement the common features like highlighting in their own way

noClaps @zerolimits.dev · 6d

i myself like helix's format, but if neovim and zed arent willing to adopt it then that kinda defeats the purpose of this project, right? because at that point i've just extracted the runtime/queries directory from the helix repo into its own repo, and the ecosystem is just as fragmented as before

noClaps @zerolimits.dev · 6d

regardless, i think tree-sitter-highlight's `STANDARD_CAPTURE_NAMES` (that's what it's called in the code) is a good baseline, and capture groups can be added and removed as needed to support something that can be used in all editors, while still not being preferential to any one editor

2

noClaps @zerolimits.dev · 6d

agreed. my thinking is that a lot of these editors have reimplemented almost the same thing in different ways, whereas if upstream tree-sitter is the one dictating the "standard", then it can be extended and modified to accommodate for that. it would lead to better portability for themes/features

2

noClaps @zerolimits.dev · 6d

okay i've added all the standard capture names into `CONTRIBUTING.md`. i know that basically none of the editors actually follow it, but they probably ought to so if this is the thing that pushes them to do it then im happy lol

1

noClaps @zerolimits.dev · 6d

actually it seems like tree-sitter-highlight has a set of standard capture names, we could just use that tbh

github.com/tree-sitter/...

github.com

1

noClaps @zerolimits.dev · 6d

i mean if the ecosystem is converging towards helix-style queries (at least based on your comment and the nvim-treesitter issue) then im happy to use that. i had a skim through the helix docs and their standard looked quite nice

1

noClaps @zerolimits.dev · 6d

im leaning towards the zed standard because its simpler, both for people writing queries and people writing themes

zed.dev/docs/extensi...

but if people have a different preference, im happy to switch while its still relatively early

Language Extensions | Zed Code Editor Documentation

Learn how to use and customize Zed, the fast, collaborative code editor. Official docs on features, configuration, AI tools, and workflows.

zed.dev

1

noClaps @zerolimits.dev · 6d

hmm i didnt realise that the different editors supported different styles, that might be a problem. i suppose themes could support any standard they like though, so maybe it wont be as big of an issue, so long as old themes dont break *too* much

1

noClaps @zerolimits.dev · 6d

if you have any questions, im in the @tangled.org discord, or you can open an issue on the repo, and i'll try to respond asap

1

noClaps @zerolimits.dev · 6d

i'm making a central repository for tree-sitter queries at tangled.org/@zerolimits..... i want projects like nvim-treesitter and helix to use it, but for that we're gonna need a lot more languages, and proof that the repo is maintained. i'd love to have all the help i can get!

2 3 14

noClaps @zerolimits.dev · 6d

close enough i tried my best

3

noClaps @zerolimits.dev · 6d

stinkers?

1 4