leleat

7 ms·

1.
by leleat 11d ago
You don't need to put the scratch directory in the committed gitignore file. gitignore files are recursive. So a common approach is to use a gitignore with * in the scratch directory.
2.
by leleat 20d ago
I don't think this really addresses GP's comment as far as I understood it. Your resource mostly describes how to make keyboard-based workflows accessible. But just because the full functionality of an app is keyboard accessible,
3.
by leleat 2mo ago
Someone posted their AGENTS.md some time ago, that is used in practice to teach their students[1]. That might be useful to you in this context as well. [1]: https://news.ycombinator.com/item?id=48359858
4.
by leleat 3mo ago
> Shared CEF runtime across apps. Every app currently bundles its own CEF copy. A managed shared runtime would drop binary sizes to a few MB per app. On the roadmap. This[0] sounds interesting. I am not familiar with CEF, so I wonder how
5.
by leleat 3mo ago
There is also git update-index --[no]-skip-worktree for files that are already tracked. This can be useful for some local experimentation... it's just a bit annoying to use because it's not really surfaced anywhere by git (
6.
by leleat 5mo ago
If I understood you correctly, you want to propagate changes in a branch to other branches that depend on it? Then --update-refs is for you[1]. That way, you only need to update the "latest" branch. [1] https://andrewlo
7.
by leleat 7mo ago
https://github.com/Leleat/git-forge From the README: "[git-forge is a] simple CLI tool for basic interactions with issues and pull requests across GitHub, GitLab, Gitea, and Forgejo". Right now, I am looking
8.
by leleat 9mo ago
On the other hand, we had this story[^1], where the maintainer of curl mentions a a bunch of actual useful reports by someone using AI tools. [^1]: https://news.ycombinator.com/item?id=45449348
9.
by leleat 11mo ago
Technically, deno supports https imports as well https://docs.deno.com/runtime/fundamentals/modules/#https-im...
10.
by leleat 1y ago
The problem is that the extension experience can be really bad. There is no extension API; instead Extensions have (almost) full access to GNOME Shell's code. This makes them incredibly powerful and flexible... but also fragile. Exte