no more textediting
This commit is contained in:
Deven Blake
parent
0f64f1c2b0
commit
08155068e2
@ -112,7 +112,6 @@ I would much rather talk to you via Signal instead of using something like Disco
|
||||
<P><A HREF="./films">check out my favorite movies</A></P>
|
||||
<P><A HREF="https://www.youtube.com/watch?v=dQw4w9WgXcQ">here's a video of me waterboarding myself with mountain dew</A></P>
|
||||
<P><A HREF="./home">check out a web browser landing page i made</A></P>
|
||||
<P><A HREF="./textediting">here are my opinions on text editing</A></P>
|
||||
<P><A HREF="./thegame">you just lost the game</A></P>
|
||||
<P><A HREF="./git">here's my take on the git main thing</A></P>
|
||||
<P><A HREF="./now">here's what i'm doing right now</A></P>
|
||||
|
||||
@ -27,29 +27,34 @@ Please do not put any stock into what I believe, as most of it is autocontradict
|
||||
<LI>The last powdery bits of the cereal are much better than the initial big bits. A lot of that powder is sugar and it sweetens the milk.</LI>
|
||||
<LI>Bag cereal is just as good as box cereal. Taste-wise they're identical and they're about the same effort to pour because the boxes have bags in them too. The only con to bagged is that a greater amount of cereals are boxed (e.g. there are no off-brand Wheaties where I am) and boxes have cool puzzles on the back (though now that I'm not a wee lass I do have a cellphone on which I play Konami Picross instead).
|
||||
</UL>
|
||||
<LI>Jargon</LI><UL>
|
||||
<LI><B>/bin</B> - pronounced bin
|
||||
<BR />Why? "bine", as in <B>bin</B>ary, sounds stupid. I think of it as a bin in which to place binaries.</LI>
|
||||
<LI><B>/etc</B> - pronounced etsy
|
||||
<BR />Why? It's easier to say than ee tee see or et cetera, and the literal meaning of the phrase is less important when it comes to describing file paths.</LI>
|
||||
<LI><B>/lib</B> - pronounced lib (like in "liberty")
|
||||
<BR />Why? See "bin", except I have no word imagery for its use.</LI>
|
||||
<LI><B>/mnt</B> - pronounced em en tee
|
||||
<BR />Why? It doesn't seem standard on Linux and a user with which I'm speaking may already have a "/mount" - <I>I</I> did when I was young and thought /mnt was reserved.</LI>
|
||||
<LI><B>/opt</B> - pronounced opt (like in "opt-in")
|
||||
<BR />Why? The user is <B>opt</B>ing in to <B>opt</B>ional software.</LI>
|
||||
<LI><B>/proc</B> - pronounced prock
|
||||
<BR />Why? Seems easier to say than "pross" like in <B>proc</B>esses.</LI>
|
||||
<LI><B>/selinux</B> - pronounced ess ee linux
|
||||
<BR />Why? That's what seems intuitive to me. My system doesn't have it.</LI>
|
||||
<LI><B>sudo</B> - pronounced soo doo
|
||||
<BR />Why? It stands for <B>su</B>peruser <B>do</B>.</LI>
|
||||
<LI><B>/sys</B> - pronounced sis
|
||||
<BR />Why? It's easy to say and short for <B>sys</B>tem.</LI>
|
||||
<LI><B>/tmp</B> - pronounced temp
|
||||
<BR />Why? It's where <B>temp</B>orary files go.</LI>
|
||||
<LI><B>vi</B> - pronounced vee eye
|
||||
<BR />Why? That seems to be what everybody says. Personally sometimes I say "vee" instead.</LI>
|
||||
<LI>Computers</LI><UL>
|
||||
<LI><B>Document editor</B>: Wordpad on Windows, Libreoffice elsewhere.</LI>
|
||||
<LI>Jargon</LI><UL>
|
||||
<LI><B>/bin</B> - pronounced bin
|
||||
<BR />Why? "bine", as in <B>bin</B>ary, sounds stupid. I think of it as a bin in which to place binaries.</LI>
|
||||
<LI><B>/etc</B> - pronounced etsy
|
||||
<BR />Why? It's easier to say than ee tee see or et cetera, and the literal meaning of the phrase is less important when it comes to describing file paths.</LI>
|
||||
<LI><B>/lib</B> - pronounced lib (like in "liberty")
|
||||
<BR />Why? See "bin", except I have no word imagery for its use.</LI>
|
||||
<LI><B>/mnt</B> - pronounced em en tee
|
||||
<BR />Why? It doesn't seem standard on Linux and a user with which I'm speaking may already have a "/mount" - <I>I</I> did when I was young and thought /mnt was reserved.</LI>
|
||||
<LI><B>/opt</B> - pronounced opt (like in "opt-in")
|
||||
<BR />Why? The user is <B>opt</B>ing in to <B>opt</B>ional software.</LI>
|
||||
<LI><B>/proc</B> - pronounced prock
|
||||
<BR />Why? Seems easier to say than "pross" like in <B>proc</B>esses.</LI>
|
||||
<LI><B>/selinux</B> - pronounced ess ee linux
|
||||
<BR />Why? That's what seems intuitive to me. My system doesn't have it.</LI>
|
||||
<LI><B>sudo</B> - pronounced soo doo
|
||||
<BR />Why? It stands for <B>su</B>peruser <B>do</B>.</LI>
|
||||
<LI><B>/sys</B> - pronounced sis
|
||||
<BR />Why? It's easy to say and short for <B>sys</B>tem.</LI>
|
||||
<LI><B>/tmp</B> - pronounced temp
|
||||
<BR />Why? It's where <B>temp</B>orary files go.</LI>
|
||||
<LI><B>vi</B> - pronounced vee eye
|
||||
<BR />Why? That seems to be what everybody says. Personally sometimes I say "vee" instead.</LI>
|
||||
</UL>
|
||||
<LI><B>Operating system</B>: Anything POSIX or UNIX-like, nearly always Linux. Windows is unuseable for me.</LI>
|
||||
<LI><B>Text editor</B>: ne or vim (or vi). Notepad on Windows.</LI>
|
||||
</UL>
|
||||
</UL>
|
||||
</BODY>
|
||||
|
||||
@ -1,35 +0,0 @@
|
||||
<!DOCTYPE html>
|
||||
<HTML lang="en">
|
||||
<HEAD>
|
||||
<LINK rel="canonical" href="http://www.trinity.moe/textediting" />
|
||||
<LINK rel="shortcut icon" type="image/x-icon" href="https://raw.githubusercontent.com/devenblake/homepage/main/favicon.ico" />
|
||||
<LINK HREF="" ID="styling" REL="stylesheet" />
|
||||
<META charset="US-ASCII" />
|
||||
<META name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<TITLE>opinions on text editing</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<P><A href="..">~ Return to the rest of the site</A></P>
|
||||
<SCRIPT SRC="/cookies.js" TYPE="application/javascript"></SCRIPT>
|
||||
<SCRIPT SRC="/sheets.js" TYPE="application/javascript"></SCRIPT>
|
||||
<SCRIPT TYPE="application/javascript">window.onload = window.initializesheets;</SCRIPT>
|
||||
<H1>My opinions on text editing</H1>
|
||||
<h3>updated 2020-10-10</h3>
|
||||
<hr size="1" width="25%" align="left" />
|
||||
<p>I write prose in Rich Text Files (RTF) and everything else in UNIX-formatted plaintext.</p>
|
||||
<p>
|
||||
When it comes to RTF editing, I normally use Microsoft Wordpad on Windows and (prefer it to using) Libreoffice on everything else.
|
||||
I like RTF because editors handle everything for me - changing the font and indentations and everything is very easy - and because despite its proprietary-ness it's well supported and converts to plaintext relatively easily.
|
||||
</p>
|
||||
<p>
|
||||
When it comes to code, I only use Linux/UNIX/something with a console. I've tried coding in IDEs many times and every time I've been disappointed.
|
||||
I'm not used to using my mouse when I code and even when I acclimate I still don't like it, though I've never used ACME before and that might change my mind someday.
|
||||
Lately I've been writing C and Python and when I write both I use "ne", the Nice Editor. It's simple and it uses a lot of common keyboard shortcuts.
|
||||
I avoid lines of code longer than 79 characters, and I use tabs for indentation with a tab length of 8.
|
||||
I never use hard word wraps on plaintext if I can catch it and I don't normally use soft word-wrapping in code.
|
||||
I grew up on Microsoft DOS's EDIT.COM and it's still my go-to editor on DOS.
|
||||
</p>
|
||||
<p>My preferred encoding is UTF-8. I don't like Unicode because I disagree with how emoji are being added. I have an ASCII chart on my wall.</p>
|
||||
<p>When I use stock systems I use nano until I install ne. I'm not yet sure how to use ed.</p>
|
||||
</BODY>
|
||||
</HTML>
|
||||
Loading…
Reference in New Issue
Block a user