Carriage line, return feed.
Carriage line, return feed.
$ git commit -m 'Add excitement!'
“The short answer is ‘yes’. The long answer is ‘no, not really’.”
“Sorry, something went wrong with editing your message. We threw away your edited message for your convenience. Happy retyping!”
I love #374! 🐉
half tough cuff puff huff rough tar car war tour core pour wore roar her cur sap tap cap rap sop top cop hop pep cup pup tab cap rap sop top cop hop pep cup pub rub pal toll poll roll sell tell well hell cull pull hull sag tag wag rag cog hog keg peg keg tug pug hug rug sat cat
[Obligatory “you should use –fixup instead”-reply]
But yes, that sounds like a nice add-on. I’m wondering how you’d implement something like that, though. 🤔
Exactly. I simply stop taking the time to write everything down and check tasks off my list, which causes out-of-date todo lists and me keeping everything in my head again. 🐒
I don’t really switch techniques aside from switching from being enthusiastic about GTD and trying to keep everything in my head again. 🐒
I was advised to be more strict about weekly reviews, which I’ll try.
And because I own my content now, I tagged all Vim tips and set up an index to list all of them. https://updates.jeffkreeftmeijer.com/
That sounds like a great case study!
I think distrusting the list hits the nail on the head. I’ll try properly planning a weekly review. Thanks, both!
Since I have your attention: any tips for which tool to use? :)
Oh, that’s a familiar feeling. Remember that your readers have a different experience level than you. You’ve spent time researching your subject, and they didn’t.
Also, I like the scenario article, because it shows the flaws using nested contexts and provides a clean solution to overcome them.
If you have time to work on it, let’s get one of your drafts published this month. Which one’s the most done? :)
Aw, thanks! 🤗
Are you stuck on those articles because you can’t find the time to finish them, or because you need input/editing from somebody? Please let me know if I can help!
As with the Pomodoro technique, Getting Things Done works wonders for me for a couple of weeks. Then I just… stop doing it. Any tips to making it stick?
Do I understand correctly that this would always squash all fixup commits, meaning any fixup commit would be immediately amended and would never leave any “fixup!”-commits behind?
Actually, it’s a demo for an article where I implement a minimal HTTP server in Elixir. It needs some setup to work out at the end of the article, so I’m constantly changing past commits.
I do admit, though, I swapped the commits and amended out of laziness. 🙊
Yes, but that’d require me to write “edit” in the rebase file instead of
ddp to swap the commits. Properly rebasing is a better idea, this was just laziness.
That’s exactly it, thanks! Will check it out.
Having 500 available characters is better than 280, and I have no idea how we ever fit these in 140.
Yes, I definitely underuse
--fixup, and that would probably be the proper way to do it indeed. However, I’m currently grooming an example repository to show clear steps for an article I’m writing, so there’s a lot of rebasing going on. I tend to lose track of the fixup commits, and autosquashing them is another step to take.
Yes, that’s the nicer way to do it. I tend to lose track with all those fixup commits (and would prefer not to have to autosquash), especially if I’m grooming an example repository like this. Any way to squash them immediately when committing the fixup?
Almost used “penultimate” there. Almost.
git rebase -i HEAD~2, then flipping the commit order and
git commit --amend is just the most convenient way to amend the second last commit. 🤷♀️
I haven’t taken the plunge yet, but I’ll be borrowing an unused one from a colleague for a bit. I’m very excited about trying it out and will report back!
Are you looking to get a new keyboard yourself? :)