Someone asked me a question that led to me wanting to put together a bibliography for the social dynamic at hand: white-coding as retaliation against anti-whiteness displaced into non-white communities. (That might take the prize for longest node name.)
That got me to realizing that I haven’t actually used Org-cite since setting it up in GnoponEmacs. In part, that’s because of anxiety about if I’m going to continue with GnoponEmacs over time: the allure of a bespoke text editor done in Fennel calls to me. “Is it that same song, that lured the young sailors? I think they’re one and the same.” (The Rainbow Connection).
But as I wanted to touch on On the process of making dirt, there’s good reasons to keep improving GnoponEmacs, even as I’m hoping to move past it.
Anyway: I just wanna babble back through how to use Org-cite, to do whatever I need to properly be able to generate the bibliography at the dynamic I mentioned. This’ll be useful too because I’ve been importing my letters to the Web, but I don’t want those to have the hyperlink saturation that the rest of my research tends to have. Instead, I want them to hold more true to the academic genre, with in-line citations and a bibliography at the end.
I think where I ended was that I never got to the step of writing the BibTex entry for a document in that document’s Org-roam node, and figuring out how to bring those all together into a single bibliography file…
So, that’s I think my next work - let me try it with Black Skin, White Masks…
Okay, so between trying that and now, I ended up spinning up a few functions I’ve added to GnoponEmacs. They’re clunky, but they result in me being able to generate my bibliography into a single file, and lets me write :canonical yes into a Org-mode source block that’s using BibTex formatting.
So now I can go and write BibTex entries for the various documents I want to put in the annotated bibliography for this social dynamic, and then I can generate the global bibliography and cite it.
I’d love to improve it so that the BibTex entry code blocks draw on the Org-roam node data to complete itself, rather than be hardcoded in… I might look at that after a short break, because then I can prevent duplicating effort down the line.
(Generally, I’m seeing that i want to encode stuff at the Org-roam node level if I can, at the Org-mode subtree if I can’t, and only if I can’t do that, coding it deeper.)
Unfortunately I think that brings me to a thing I’ve been procastinating, which is writing parsers for handling that stuff! I’ve kind of looked around the idea before, but now it seems clear that i’m going to want a way to have a property that points to the full node - link and anchor - and translate that into just the anchor text, or just the ID text, consistently.