Midnight Pub

omg, have mercy!

~tffb

~


inquiry

A few years ago I wrote a Lua script I called "comp" in honor of the thusly named "mh mail" subcommand.. which opens a vim session... and when you back out of that see a prompt that'll take either a post title, or ctrl-d to exit. Supplying a title appends the post to a accumulator file.

But since the title one composed the post in sticks around, one can open a new browser tab and ctrl-o therein to bring up the file selector to cause the file to appear in that tab, from which one does a ctrl-a to select all, then ctrl-c to copy... then of course ctrl-v to paste into the post/reply creation buffer in Midnight Pub.

Sure, one could also just "less" the file in a terminal, but then we're talking multiple copy/pastes.. and sometimes newlines don't work in the browser form submission buffer the way you'd hope, e.g. you somehow wind up on the paste with either no line breaks... or two when in your vim session it was just one.

(Don't worry... I've never had a problem with hating on graphical browsers.... ;-) )

I wrote an 'all' command to show the entire accumulator file (to find things again)... can't remember if that was based on something else, or.... hmmm.

Anyway, it's a few extra steps than just grinding a post into the form and submitting, but it completely avoids the misery of losing something - and of course Murphy's Law demands that the only content that'll happen to is something one is exceptionally pleased with....

While it's in mind... anyone know of a linux command that somehow puts a file's content in the Chrome copy/paste buffer? I really can't stand having to use the trackpad... and I'm imagining spending too much time trying out web search terms/combinations to finally maybe sorta kinda be directed to useful information....

reply

tffb

Inquiry, honestly, I understood about 4% of that post, but I 100% appreciate the detail within it. I have not done much (if any) writing via the command line, though I have seen entire diary/journal "apps" that can be used with the command line, and I thought: "there's some hackery stuff that I should get myself into!"

But yea, the copy/paste scenario of writing off-blog and then putting it into a blog editor, I didn't pick up on that when I started out years ago, and now I am Long In The Tooth, and it would take a metaphorical stick of dynamite to get me to "change (or see the error of) my ways".

Fun stuff, though

reply

inquiry
> Inquiry, honestly, I understood about 4% of that post,

Good thing it wasn't important, then! :-)

but I 100% appreciate the detail within it.

In the spirit of

~yretek's
glorious post,

I'm glad my love of (okay, I'll be honest.. obsession with..) typing is benefiting someone!

> I have not done much (if any) writing via
> the command line, though I have seen entire
> diary/journal "apps" that can be used with
> the command line, and I thought: "there's some
> hackery stuff that I should get myself into!"

Should the bug (heh.. bad joke..) ever bite you sufficiently deeply, I highly recommend

Lua.
> I didn't pick up on that when I started out years
> ago, and now I am Long In The Tooth, and it would
> take a metaphorical stick of dynamite to get me
> to "change (or see the error of) my ways".

Just so happens I'm good at lighting matches. ;-)

reply

tffb

Lua. Noted. I looked at the "about" page (which I hear good things can come from doing so) and it seems it may be a bit above my blog grade. Mind you, I am a novice (very novice) dev who stumbles through a Ghost software install on my VPS , and still have to take step-by-step notes on PlainText in order to remember how to `cd` into the right file (folder?) to run Ghost updates.

But, should I delve into the world of living The Command Line Life, I will re-examine Lua and see what I can get from it :)

Thank you for the resource, and the word(s) of encouragement.

And I will double-backup what I said about yretek's post - a motto/manifesto all the way.

:)

reply

inquiry

On second thought, don't ever waste your time learning to write code. It's a miserable endeavor, a place/space where entropy really comes into its own - endless ream(ing)s of not-well-thought-out fixes, workarounds, and all other manner of homage to haste making waste.

Just. Don't.

Read a book. Draw. Hike. Dance. Become a regular in a coffee-shop/bar/tavern/pub... ANYTHING but said modern day version of seeing how long you can add binary straws to a binary pile of shit before it collapses more upon you than upon itself.

Just sayin'.... ;-)

(Of course, the above could actually be more a round-about testament to how feeble my own mind/skills have become in said space....)

reply

yretek

Back in... too olden times, I used a plain text editor to avoid this issue.

(In fact, I used MS Word... but I don't want to confess that!)

reply

tffb

Yes, for years people have been telling me to write posts in a text editor and then copy/paste them into the blog editor, and it's a wonder I didn't adopt that method when I lost my 10th, 50th, and even 100th blog post on Blogger with Internet Explorer and a virus-ridden version of Windows XP in 2006. But, I persisted and *still* write everything out in the blog editor, itself. I live, I learn, I lose writing blurbs from time to time. Haha.

reply

tatterdemalion

There are browser extensions that simplify this, but I suspect today in the age of WebExtensions they are not what they once were.

reply

yretek

Oh, Peat & Diesel have released a new video, so all it's well.

But

for the love of the puffins

write long posts on an editor

pretty please

reply

m15o

Ohh so sorry to read that tmo >< sometimes there’s a good surprise and the browser “remembers” what was written when we hit the back button. Not always the case though… That’s a good suggestion, I’ll think of ways to address that. Great to have you around!

reply

tffb

TYSM m15o :):)

Yes, I tried a few different methods to "reclaim" the entry in the browser, but after a click here and there, I knew that the text was gone (😭).

No big deal, though. I will write up something different to respond to said person with. Hope you're good 👍

reply