> Welcome to Wednesday. There are many Wednesdays, but this
> one is now.
Love it!
> I expect some packages today, and tomorrow, and the next
> day, inxl the exact phone I have right now only unlocked
> (bye $150) so I can activate Google Fi which I am smitten
> about. I mention because then and only then can I get back
> to my mostly-cli antics and not have to be mobile only
> (which is a pita, lemme tell ya).
I'd go pub-sane under such conditions. ;-)
> The four window web (4WW(c), ha) sounds like a nice way to
> do things. Makes me want to finally try tmux, as well, just
> as a half-day-long conversation in Ctrl-c chat suggested I
> do the first week I joined up there (and one of the first
> times I used irc, too!). I'd likely have it:
>
> ssh into Ctrl-c
>
> Irssi (irc in cli)
>
> Lynx
>
> Local window for `wget` and other junk
What comes to mind is "no one ever said making things easy would be easy". There was definitely pain to learning tmux, vim, & co. But the effort has sooooo streamlined the mechanics of all this, facilitating focusing more on the fun(ner) stuff now.
But then there's the side-benefit that proficiency therein becomes its own fun/joy/satisfaction.
So let us all raise our glasses to the practice making perfect of getting there!
> Stuff on tttlog as usual later, much like lately. Stay
> good, Inq! If you have a place you'd like to share the
> http[s]/gopher/Gemini reader, I'm all eyes!
I might. But realize there's been so much "nobody reads any of this anyway" over the years that sharing can feel pointless. And then there's the fact it's not standalone. There's the main Lua script, but then there's also a small Lua library I wrote supporting the script. And then there's the fact they leverage "elinks" for https/gopher, and "gemget" for gemini. And then there's the fact that my code tends to be indecipherable to others, because I'm opposed to commenting *and* empty lines in code for these two personal reasons:
1) Both take up screen real estate that arguably become less meaningful over time, to the point where I have to do the hard work of struggling to figure out how the actual executable stuff works *anyway*. So why bother writing stuff that doesn't execute *and* ultimately becomes as unobvious as the stuff that *does*?
2) I've become acclimated to how empty-line-less code looks to the point of preferring it.
Oh, wait! A late-breaking third reason just came to mind!
3) Nobody ever seems to know what I'm talking about anyway, so comments will likely do more to confuse/obfuscate than enlighten.
On empty lines and comments, yes, I realize one can leverage or write editor extensions to toggle "folding" that kind of stuff out of view. But that doesn't fix how its meaning entropy will slowly creep along until I can't figure out what I originally meant, or subsequent understandings of other things cause the original comment verbiage to mean something else without my realizing that's happening.
Words are just soooooooooooooooooo inadequte some... I mean most... I mean all of the time. :-)
Heh... I'm certain I had two reasons before that one... but honestly can't remember what it was (says the fool continuing to type anyway... <coughs>).