#spacemacs

[tariqk]

me: okay, let's try this new Spacemacs layer

me: types in layer name

Spacemacs: HORK

Spacemacs: symbol-definition is void: (package-name)

me: what

me: Spacemacs, locate-library (package-name)

Spacemacs: found it!

me: so why can't you find it in the first round

Spacemacs: idk

me: fine, I'll go check on Google

me: Google!

Google: hi there! how may I help you?

me: Here's the error message I received. What can you find?

Google: absolutely nothing of relevance!

me:

me: okay, before I start complaining, let's look at how far behind I am in the dev branch

me: Github!

Github: Happy to help!

me: How many commits am I behind the bleeding-edge Spacemacs commit?

Github: 11 commits!

me: wait what? but I updated last Friday!

Github: well, MAYBE if you updated MORE DILIGENTLY—

me: okay fine, never mind, never mind... (mutters)

me:

me:

me: oh shit

me: how do I sync my fork with the mainline Spacemacs fork?

Github: we recommend `git pull`!

me:

me:

me: (remembers screwing up git)

me: (shudders)

me: Google!

Google: Happy to serve!

me: which should I use, `git pull` or `git fetch`?

Google: the difference between `git pull` and `git fetch` are—

me: never mind that, isn't there an opinion of it?

Google: sure! check out this StackOverflow question.

StackOverflow: for the love of god there are 66 ANSWERS here.

me: yikes

StackOverflow: If you have a fucking opinion, PLEASE read the rest and make sure you're not repeating someone.

me: I'm okay, I'm okay, thank you! (backs away)

me:

me: Google! Give me... the SECOND PAGE of the results

(THUNDER AND LIGHTNING)

Google: (visibly shaken)

Google: Are you sure??? remember what happened the LAST time?

me:

me: (closes eyes, a single tear falls down)

me: I'll just... have to... RISK it

Google: Oh, you poor soul! Here, take it, take it before I regret it!

me: okay, let's see

some random blog: IF YOU MUST SYNC WITH YOUR REPO, YOU SHOULD USE GIT FETCH

some random blog: AND THEN YOU MERGE

me: why

some random blog: BECAUSE THAT WAY YOU WILL BE IN CONTROL OF THE GIT EXPERIENCE™

me:

me:

me: that's a terrible reason, but okay

(SEVERAL HEART-STOPPING MOMENTS AND CURSING LATER)

me: okay Spacemacs, restart.

Spacemacs: done!

me: you're okay?

Spacemacs: yep!

me: wait, none of the files affected by the package changed.

Spacemacs: yep!

me: so what happened?

Spacemacs:

Spacemacs: ¯\_(ツ)_/¯

[jkresearch]

A Vimmer’s Emacs Prerequisites

[tariqk]

I spent the night tossing and turning over this stupid problem with one of the spacemacs packages, and this morning I posted this comment on how to (possibly) fix it.

[tariqk]

me: okay spacemacs, turn on fancy-battery

spacemacs: roger dodger

fancy-battery: Current battery status: No battery

me: dey macha how can liddat. this is a laptop, can see or not

fancy-battery: ¯\_(ツ)_/¯

me: o, liddat issit. spacemacs, SPC h d v fancy-battery-last-status

spacemacs: (provides an alist with numbers as keys, the first key-value pair being (76 . "on-line"))

me:

me: what is this

spacemacs: i got this alist from battery-status-function

me: spacemacs, where does battery-status-function get this value from

spacemacs: from something called w32-battery-status

me: spacemacs, bukak ielm

spacemacs: wokeh boss

ielm: prompt ready

me: ielm, (w32-battery-status)

ielm: (provides the same alist from fancy-battery-last-status)

me: wait, is that right? I thought it was supposed to be an alist where the car is supposed to be letters, not numbers

spacemacs: look again please. see, at the docstring for battery-status-function. it says "character code"

me:

me:

me: ok, so yang itu betul.

me: that means that character code 67 (which is b, which corresponds to %b) is the battery status, which, since it's plugged in, means that it's "on-line". which... makes sense, I guess??

me:

me: Ok Google, look up the fancy-battery emacs package?

Google: here you go!

fancy-batter emacs package repository: THIS PACKAGE IS NO LONGER MAINTAINED SORRY

me: wtf?

spacemacs website: yeah don't worry we incorporated fancy-battery into our codebase directly

me: ...okay, seems kind of fucked up, but okay...

me:

MUCH FRUITLESS SEARCHING OVER PACKAGES LIKE SPACELINE AND FANCY BATTERY LATER

me: ...okay, spacemacs

me: open up spaceline-segments.el

spacemacs: here you go!

me: okay, spacemacs, /battery RET

spacemacs: here's the first occurrence of that word!

me: cool, cool. [n]ext.

SEVERAL [n] key-presses later

spacemacs: here's occurrence #8, in a function called spaceline--fancy-battery-mode-line

me: okay, what do you do again, mate?

spaceline--fancy-battery-mode-line docstring: "Assemble a mode line string for Fancy Battery Mode."

me: neato, maybe we can get at the bottom of this.

me: mmhmm, let's just look past the let* form...

spaceline--fancy-battery-mode-line: (cond ((string= "on-line" type) " No Battery"...

me:

me: wait, what? hang on a minute...

me:

me: are you telling me that when you get a string that says "on-line", you output " No Battery"?

spaceline--fancy-battery-mode-line: yep, mate. 'sat a problem?

me:

me:

me: lahabau

me: siapa yang tulis w32-battery-status ni? aku nak cekik dia.

[tariqk]

I've been quietly noodling with Spacemacs these past few months, and thanks to the judicious use of reading up, have finally embarked in:

Creating a whole series of custom org-capture commands, which now let me log meetings, tasks, follow-ups and anything else, really for both work and personal items.

And I did it while using separate org-files to define templates, instead of using strings with escape sequences, allowing me to just change the contents of the templates without having to dig through code.

Made a couple of functions that allowed me to create timestamped files for said meeting notes, so that meetings are now logged on a weekly basis.

Kind of made a way to quickly search through those meetings using helm and ripgrep (except that ripgrep on occasion will choke badly, so I don't use it regularly yet).

Set up a bunch of org-agenda-custom-commands for stuff I wanna see. I've managed to make one for work overviews, and I'm in the middle of doing one for my work tasks.

After reading up a whole series of blog posts and stack-overflow and stack-exchange sites, realized that some of the functions that interface with org-agenda-skip-function all kind of looked similar...

...so I'm in the middle of making a macro (yes, using defmacro) to generalize it.

I'm also in the middle of trying to get quelpa to work properly with spacemacs on Windows, but that's slow going, so I'm taking a break from that one.

Otherwise it's pretty good tho!

[tariqk]

I was tweaking the color schemes for my org-agenda todo keywords, and I looked at this color scheme, thought to myself: “hey, that's pretty good.”

[tariqk]

things I like about spacemacs' vim mode: hey, the key combinations make a LOT of sense. SPC b b for the buffer list, SPC g s for magit status, this is pretty good

things I dislike about spacemacs' vim mode: HOW THE FUCK DO I DELETE ENTRIES IN THE EVIL REGISTER

[tariqk]

me: oh man, my emacs config is getting pretty unwieldy, shit's taking too long to load. maybe it's time to wipe the slate clean and start over?

me: ooo, maybe I should start using Spacemacs

me: oh, but I don't want to make a sudden jump

me: maybe I should look up how to make the configurations live together

me: oh, but it requires me to change the $HOME variable? That's bogus, surely there's a better way.

me: why is everything MacOS and Linux-oriented? Surely there must be something for Windows...

me: I wonder if I could make it cross-platform...

me:

me: oh no