There is no one federal agency that specifically regulates the radioactivity brought to the surface by oil-and-gas development,” an EPA representative says. In fact, thanks to a single exemption the industry received from the EPA in 1980, the streams of waste generated at oil-and-gas wells — all of which could be radioactive and hazardous to humans — are not required to be handled as hazardous waste.
190 notes
·
View notes
okay I was scrolling through your blog (a normal amount? too much? I'm sorry if this is weird I don't know if dragging up old posts in acceptable on this site!) and saw one where you said you use vim and I am curious about that! I tried it a while ago and was like... okay I can see how this might be faster once you get REALLY good at it, and it would definitely be useful to have the ability to export easily in multiple formats because I have realized suddenly that it seems like AO3's downloads frequently mess up the formatting? (Or maybe just fail to fix messed-up formatting that the browser smooths over?) Sooo yeah do you use it to write or just for code or what? is it worth it to become a Vim Person?
HELLO this is actually one of the things I most love to talk about because vim is my Favorite Piece Of Software. I love it well beyond a normal amount. That being said it's ummm not for everyone and not for everything. I'm putting this under a readmore because this is too long to inflict on poor unsuspecting souls who are just here for Hannibal content.
Section 1: The ways in which vim is useful
Vim is most useful when the stuff you're working on is more structured and what you're doing is more rote. So something like code (which, yes, is what I learned it for) is very formally structured, and something like html is sort of vague scaffolding around text, which is pretty much a blobby mush where really nothing means very much of anything. (The number of times I ct. only to get pulled up short by an honorific is very high, and I am grouchy.)
Part of the thing that makes structure good is that vim is more useful (relative to a traditional editor) when you can precisely define the action you want to take. Getting better at vim is really about improving your vim-vocabulary so that you are more able to make precise statements about what it is that you want vim to do. I use a "normal" markdown editor for drafting, because what I want to do is "write the next bit" which is not a very vim-interesting action and obviously not very precise. I do use vim for editing, though, because often the things I want to do are, like: "replace this word with some other word" (cw), "delete the end of this paragraph" (D), "rewrite this bit of dialogue" (ci"), "remove this whole paragraph" (dd)--you get the idea.
Also, the place that vim goes from "ok, this seems pretty good" to "this is invaluable" is really when you want to repeat stuff. Something like "the compiler is giving me 25+ pedantic warnings because the file I'm working on was written prior to the introduction of the C++ override keyword" or "I'm rewriting an API so I need to fix the function name in these dozen callsites, remove the first argument, and swap the places of args 2 & 4." These examples are programming-related because I haven't found a use for macros in writing yet. (I live in hope.)
Section 2: If you want to learn vim, here are my tips
I don't really want to tutorialize because there are a lot of those out there already. I do wish to dispense some general philosophical wisdom. (!!!!!)
First of all, keep in mind that the bar is very low. Normal editors are not really that productive. Fancy WYSIWYG editors (which I hate, equal and opposite to my vim-love) are negatively productive for me, because I will get distracted and/or distressed by all the available buttons, formatting options, and whether I accidentally italicized any of the spaces. You don't need to be maximally productive in vim to make use of it, and you don't really need to know that much to match the capabilities of a normal plaintext editor.
If you want to learn vim, I would pick a small set of keys to understand first. Like, i and I (capital-i) to enter insert mode, <Esc> to get back to normal mode. bwhjkl as basic movement options. u and <ctrl>r for undo/redo. If you must, y and d for copy/cut, p and P for paste. (System clipboard--I'm sorry--accessed with "+, so "+y or "+p for example.) That is probably well over enough.
After you get a handle on the basics, the fun part of vim is figuring out where your inefficiencies are and learning how to improve them. Realizing that you're pushing more buttons than you want to be pushing, figuring out how to describe the thing you want to do in a google search, and then finding out that vim has a key to do that. gg G } { c % $ ^ zz . ; and so on, and so on. The world is your oyster &c. (The sheer delight I felt when, more than half a decade after starting to use vim, I found the aforementioned ci"? Indescribable.)
Section 3: In which I address the actual ask
Ok ok okokok sorry. I've written all of this to tell you that I don't actually know what the weird formatting stuff you're talking about is. I read pretty much all long fic on an ereader after downloading as epub and I haven't noticed anything bizarre with the formatting? When I do want to go in and poke around in an epub I usually just use calibre's built-in editor.
In terms of exporting your own plaintext/markdown writing to multiple formats, I use pandoc. I've been very happy with it, but it isn't anything that couldn't be done by hand (and also doesn't require you to start from Vim In Particular). I would love to talk about pandoc but aaaggggh this is already way too long (sorry).
I do have strong feelings about writing in plaintext (glorious! small! no weird formatting distractions! what you see is what's in the actual file you're really writing it there's no secrets) versus WYSIWYG (too many buttons! what do they do! am i using it wrong if i don't push them! why is the filesize so big! what are your secrets, renamed .zip file!) but vim isn't the only choice if you want to go the plaintext route only the best one no, look, I spent the whole of section 1 talking about this, I am not allowed to go backwards. Honestly, though, if you're interested I'd say go for it! Vim is fun to learn and very clever! Knowing vim feels a little like knowing a weird, hyper-specialized little language.
6 notes
·
View notes
I got my hair cut the other day and of course I had to draw the dca boys running a hair salon:
Sun would be so effortlessly charming. Always chatting away with customers, explaining each product he uses and how to best maintain and style their hair.
Moon I can see being popular with the less chattier customers (like me) but over time they begin to open up. I imagine he hums while working. Otherwise, he's all ears for the newest gossip.
(The clipped up hat idea came from @bamsara's solar lunacy doodles!)
Also I love the popular headcanon that the dca can speak other languages, so I can imagine them being a hit with the aunties.
The full sketch page under cut! And some of my other thoughts
Other thoughts about this... AU? Can I call it an AU? Feels kinda small for an AU, but whatever:
Eclipse works there too! Haven't decided if it would be canon or fanon Eclipse, though I really like the image of 4-armed Eclipse working on 2 clients at once (plus, the nickname Clip is perfect for this scenario)
of course they're great with kids! They'd be able to console kids that get scared of getting their hair cut. Sun would do a little trick and tell them how good and brave they are all the way through. Moon would console them and hum a soothing song (or hey maybe they notice the kid's wearing a disney shirt and starts humming some showtunes). Every kid gets a candydrop and a balloon on their way out.
y/n works at the hair salon as a part-timer and does tasks around the salon like sweeping, arranging bookings, washing hair, etc. They don't really care too much about their own hair, but the boys are always offering to style it, dye it, braid it. With y/n's permission, the boys always toy with their hair—patting it, combing their hands through it, brushing it over y/n's ear, ruffling it.
3K notes
·
View notes