sgbeal
Joined 13 years ago
Joined 13 years ago
That's is, since only recently, no longer strictly true: the age-old libfossil recently got client sync support, so is now (aside from _serving_ repos) essentially a standalone impl (its own developer still uses fossil(1) stash, patch, and diff -tk features, but otherwise uses libfossil's counterparts).
Also, Dan Mestas has <https://github.com/danmestas/go-libfossil>, a Go library for working and fossil, and he is also working on <https://zeitforge.app/>, a clean-room impl. of fossil (whereas libfossil is largely ported directly from fossil(1)) which even goes so far as to _not_ use an sqlite database for its file storage.
Dan Mestas and Dan Shearer are working on finalizing RFCs for fossil's sync protocol and artifact format, and zeitforge is created by carefully managing LLMs which are reading that draft (but not the source code of libfossil or fossil).
Then you have proven that you are human.
> Fossil has no way to fix it, by design,
As an 18-year-long contributor to fossil i can assure you that this is absolutely not true. Fossil can amend any checkin and it can move checkins to other branches. Go to sqlite.org/src/timeline?r=mistake to see many examples of where human failing has been both demonstrated and accounted for without breaking anything.
Funnily enough, that's collectively fossil's developers' least-favorite part. We make no secret about not liking the ticket system, and we only use it when we need to record a certain ticket for posterity's sake. Aside from that, we use the forum for all ticket-like traffic.
> Since the whole tracker is just a thin front on sqlite ...
Except that it's not: <https://fossil-scm.org/home/doc/trunk/www/fossil-is-not-rela...>
Emacs. Uninterrupted since the 1990s.
That _is_ the refactoring tool in my IDE (emacs). i demonstrated replacing _all_of them at once, not replacing them each by hand.
> ... because it’s the right thing to do and doing it without the tool confers no benefit and is prone to error.
There was nothing in my post done "without the tool." Shell/find/perl _is_ the tool for C refactoring, and has been for decades.
It's long been my experience that that only works with high-level languages (specifically, those with bytecode), not C (especially once symbols are generated from macros). (OTOH, i've not touched an IDE in well more than 10 years.)
Also, it's long been my experience that any half-decent IDE is still a pale shadow of Emacs.
:-?
My "10+ years" was not referring to any specific milestone. It was referring to the general flow of time. It's been 10 years since 2016, twenty since 2006, and more than 40 since writing my first program. Lots has changed every 10 years in that period, both in my skills and the environments i program in, but shell/emacs/makefile remains a staple of that process.
Similar here: CDs and DVDs burned from 2000-2006 or so were, without exception, illegible by 2015. It's sickening.
If you mean using a text editor, a shell, and a makefile, then you're not alone by any stretch of the imagination.
If you mean your skills stagnated 10+ years ago and have not advanced since then, then... yeah, you might be the only one ;).
$ find . -name '*.c' -exec perl -i -pe 's/\btheOldName\b/theNewName/g' \{} \;FWIW, it's long been my experience that floppies (like CDs and DVDs) have a half-life and they degrade quickly upon reaching it. You'd have been lucky to be able to recover those in 2001. Now? If at all, only high-end forensic tools could recover them.
And then google whether the domain is associated with phishing attempts. i've been targeted several times recently by folks with "official" email addresses but whose domains are (per google) strongly associated with phishing.