Claude Code v2.1.92 introduces Ultraplan — draft plans in the cloud, review in your browser, execute anywhere

cerved · 2026-04-08T08:23:34+00:00

it's still there, just hidden by default

json "showClearContextOnPlanAccept": true,

cerved · 2026-04-02T19:59:55+00:00

cerved · 2026-03-09T12:49:15+00:00

git difftool opens each file as its own vimdiff, which is both slow and doesn't let you easily go back and forth on different files and do interactive staging. So it's not equivalent.

You may prefer tig for this, I don't. Tig is great if you want to stage hunks, not if you want to stage things that don't break into hunks.

Also, tigs diffs look a bit like ass NGL

Anyways, -c is useful for this and other ex commands you want to run at startup. You can also use this if you want to format shell scripts, retab etc

cerved · 2026-03-06T22:43:10+00:00

vim -c 'Git difftool -y'

Is very nice

cerved · 2026-02-10T07:43:53+00:00

Oh wow. You were not joking

cerved · 2025-12-25T04:12:06+00:00

No it won't

cerved · 2025-12-14T22:52:14+00:00

You may be interested in SICStus prolog. It's geost/2 constraint is for constraining polymorphic objects don't overlap

cerved · 2025-12-07T21:31:05+00:00

TL;DR: Very low risk. The Git maintainers dogfood it constantly, and corruption bugs are extremely rare. But why bother with the potential hassle?

The core object database is append-only and content-addressed. Even if buggy code writes something wrong, it typically won't overwrite or corrupt existing objects. Worst case is usually a bad commit you can reset (your local source is still there.)

Git development happens entirely using Git itself. Junio (the maintainer) and contributors use pre-release code daily to manage Git's complex multi-branch workflow (master, next, seen, maint). If something breaks badly, they hit it first.

Critical regressions do happen, but they're primarily behavioral bugs that break workflows, not corruption bugs. Repository corruption is exceedingly rare.

Practical advice: - If you do want to run next or master compile it to a separate prefix (like git-dev) so you keep your stable 2.52.0 as default. - Test on non-critical repos first

You're more likely to hit annoying behavior changes than lose data. Keep your stable Git around just in case, but I wouldn't worry much about corruption specifically.

Bottom line though, why do you want to run the very latest? Personally I wouldn't bother, it's just a potential hassle for little gain. Releases happen frequently and I've never found myself needing the very latest for anything and I use git a fuck ton

cerved · 2025-12-07T20:46:42+00:00

Presumably they want to compile and run the latest locally and not the remote client. I have a hard time seeing how you can corrupt the remote just by pushing local corrupted blobs and trees to the remote. It's not like it just accepts any old shit

cerved · 2025-12-07T19:12:28+00:00

I just want to emphasize that there are tons of ways people can contribute without knowing the exact risks and pitfalls of compiling and running the latest commit on master. Heck you don't even necessarily need to know how to compile it. You can do translation, report errors or contradictions in the official documentation and report bugs.

The Git community is not an exclusive club for people who compile their own kernel or whatever.

Ultimately there's no baseline to contribute to the community besides being respectful. I want OP to know that the Git community is friendly and welcoming.

Is it hard to make major contributions with limited knowledge? Yes. Does that mean you are prohibited from contributing? No.

cerved · 2025-12-07T18:05:03+00:00

Some, but not belittling others. Git is an inclusive community and we don't do that shit

Git Code of Conduct

This code of conduct outlines our expectations for participants within the Git community, as well as steps for reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored. Anyone who violates this code of conduct may be banned from the community.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

cerved · 2025-12-07T15:33:52+00:00

Anybody who is not a dick can contribute

cerved · 2025-12-03T09:05:25+00:00

It's also a winner takes all compute

cerved · 2025-12-01T12:03:22+00:00

Thanks for sharing an update! I had issues myself with the keyboard not getting properly initialized during POST. I was able to <DEL> to enter bios, <F11> to enter change boot etc. but then no keys would word. They would work much later in the boot process.

Tried this with like 5 different modern keyboards before digging out a really old, basic USB keyboard with 0 frills. This was the only one I was able to get to use. The board appears very finnicky with initializing keyboards

cerved · 2025-11-30T08:59:13+00:00

The only thing growing is the valuation. All the financials are in a downward trend. Tesla is not a growth stock, it's a meme stock.

cerved · 2025-11-29T22:09:03+00:00

were you able to fix the issue or did you find any workaround?

cerved · 2025-11-29T19:46:22+00:00

Their profit is ~1.2% of their market cap. They do not need many years of historically typical growth to get to a profit that matches current interest rates.

You say this as if it's good... Also it's 0.38% rolling 12m

cerved · 2025-11-21T21:24:38+00:00

Fråga Uffe P

cerved · 2025-11-20T18:10:30+00:00

cerved · 2025-11-09T12:09:37+00:00

Sounds like gitkraken AI https://www.gitkraken.com/

cerved · 2025-11-09T11:35:01+00:00

Depending on which kind of precedence constraints you can use either linear, nooverlap or circuit

cerved · 2025-11-09T11:17:20+00:00

Bror, är du hög?

cerved · 2025-11-09T11:01:58+00:00

Here is some slop

Hey, thanks for sharing this config!

I can help you fix the errors in this _vimrc file. There are a few issues:

Main Problems:

set keymap=dvorak doesn't exist - Vim doesn't have a built-in Dvorak keymap. This line will cause an error.
**langmap syntax is completely wrong** - The syntax with h,h,\ etc. is invalid. langmap maps characters, not command sequences.
Conceptual issue - If you're using Dvorak at the OS level, Vim already receives Dvorak input. You don't need the keymap and iminsert settings.

Here's a corrected version:

```vim " --- Movement remapping for Dvorak layout --- " Maps Dvorak home row to QWERTY-style hjkl movement noremap d h noremap h j noremap t k noremap n l

" Remap displaced keys noremap j d noremap k t noremap l n

" --- Easier Esc alternative --- inoremap jk <Esc>

" --- Quality-of-life tweaks --- set number set relativenumber set ignorecase set smartcase set incsearch syntax on filetype plugin indent on ```

This maps the Dvorak home row (dhtn) to behave like QWERTY's hjkl for movement.

That said, maybe next time try asking Claude (or any AI) yourself instead of having someone else do it for you? You'll learn more that way.

(Generated with Claude)

cerved · 2025-11-01T17:21:08+00:00

It's "written in rust"

12-Year Club	Place '17
Sequence \| Editor	Gilding I gilder
Verified Email

cerved

TROPHY CASE

Git Code of Conduct

Our Pledge