Weirdest randomly generated GitHub codespace name I've got so far...
What's yours?
Weirdest randomly generated GitHub codespace name I've got so far...
What's yours?
And the only reason I know about this release is because I've started to maintain a TOML parser in 2025.
I still don't see this new syntax being used a lot as goes against the usual style of a TOML file, but we'll see.
github.com/DecimalTurn/...
How I felt when I discovered TOML v1.1's release...
I guess if you can't beat them, join them!
Nice documentary. It's always good to have a term to qualify what you aspire to: local-first.
The cloud-only approach is still going strong, but the next wave is already brewing...
www.youtube.com/watch?v=10d8...
The nice thing about the determinism believers club is that you don't have to say sorry when you're late to the meeting.
I think in your case, the simplest solution to make the warning disappear is to turn off core.autocrlf with:
git config --global core.autocrlf false
A good read on the topic:
blog.popekim.com/en/2025/08/2...
I'm sure the impact is negligible unless you have an enormous amout of files. Still annoying thought, for sure.
And by all means, if you were going to look up what this is about, don't let my previous comment stop you...
You don't really have to worry about that warning unless the software you use for sprite data is picky about line endings.
The vast majority of modern softwares on Windows can handle both LF and CRLF without a problem.
No worries, I've been thinking of raising an issue about this in the GitHub Desktop repo for some times now and seing your post has revived my motivation to do so.
Unfortunately, GitHub Desktop is not really helpful in that situation. I'm assuming that you are getting the error: "fatal: LF would be replaced by CRLF in...".
The easiest solution to this is to open a terminal window and run the following command: git config core.autocrlf false
This one should fix it for VS Code:
github.com/oxc-project/...
Looks like they even removed the weekly download count.
Could that be to make it difficult for hackers to know which project to target next?
It feels like it's still 2001 everytime I open the VBA editor and the logo still checks out
This demo tells me the real gain in productivity is not quite there yet. Also it makes rookie mistakes like merging cells π€’
www.youtube.com/watch?v=-wgu...
This demo tells me the real gain in productivity is not quite there yet. Also it makes rookie mistakes like merging cells π€’
www.youtube.com/watch?v=-wgu...
I'm happy to see that the repo is categorised correctly as "Assembly" unlike the GW-BASIC repo that still indicates "C++" due to the presence of NUL characters at the end of the .ASM files causing an issue with language detection: github.com/github-lingu...
The fact that ZΓΌrich's Zoo is not called Zoorich is such a missed opportunity!
Mom update. She used #Copilot to learn how use the Developer tab in #Excel and started recording tons of #VBA macros. She said she took a task that would take her hours down to seven minutes.
βIt gives me confidence to try new things, Iβm watching a lot less YouTube nowβ
Times are a changinβ
Some people are working on that, but the VBA open source community is not well known unfortunately.
github.com/sancarn/stdVBA
The link for "full methodology is described here" seems broken.
I've said it before and I'll say it again: it
Hopefully, one day we won't have to even think about line endings, but I'm not holding my breath on this one.
I tried to summarize how line endings normalization work in Git and this was the best I could do.
Have you considered using Cloudflare to avoid DDOS attacks?
Sorry if I beat you to the punch, guess I was too excited to waitπ . Btw, have you thought of adding the vba tag to your repo? It would be nice having more actual VBA projects in github.com/topics/vba
Programming language rankings (April 2025) from plrank.com
plrank.com is a programming language ranking that aggregates other rankings and VBA has been performing surprisingly well lately, slowly climbing up the top 20.
The main driving force for VBA's popularity remains the number of new questions on Stack Overflow.
Congrats to @jonathanleroux.bsky.social for achieving 1k β on GitHub with IguanaTex!
Always be careful before opening a .dogm that you received by email, they could bite if you let them run loose
Finally some DevOps tooling for VBA developers
github.com/DecimalTurn/...
#DevOps #VBA #CICD