inquiry

So, for example, I copy/paste the second paragraph, above, into a vi (editor) session.

Then I copy the URL to the post containing it.

Then, in the editor, in "command mode", I execute these keystrokes with the cursor on the line containing the text:

!!y1 https://miso.town/post?id=29

which transforms the text to the right sequence of text and tags to result in this when displayed to you:

Take creating a multi-line "quote" of some lines of > content, with the option to associate a URL with it, doing > so in a way that helps the Midnight Pub post rendering > code path "do the right thing" (i.e. what I want it to > do) with respect to keeping the text to no more than 60 > columns, while having line breaks that *don't* cause the > aforementioned code path to essentially double line break > the lines by wrapping then all in html paragraph tags.... > >                              - https://miso.town/post?id=29

Fun!

("y1" is the name of the script... the '!!' tells vi to run the script against selected standard input, replacing it with the standard output of the command)

m15o

WOOOW! This looks absolutely amazing! I love how it's simple to read with the columns being cut when too long, and how the link to the post stands out to see more. All of that done in vi with bash + lua? Darn. If you ever feel like, I'd love to see the script so I could use it as well. Cheers sir, you made my day!

inquiry

Put the latest here: https://miso.town/reply?id=46

Sorry for all the clutter in this thread, but that's kind of how it goes when trying this and that.

inquiry

This is to see of code/pre tags work in Midnight Pub posts.

So here are the two pieces of code whose high-level description (when combined) transforms text into Mignight Pub friendly text/tags (huh... but I see I used two Lua scripts - not one Lua and one bash as first reported);

The "y1" script:

<pre><code>#! /usr/bin/env lua local lines = {} for line in io.stdin:lines() do table.insert(lines, line) end local url = '' if arg[1] then url = ' ' .. arg[1] end local handle = io.popen('fmt -60 | quote-br' .. url, 'w') handle:write(table.concat(lines, ' ')) handle:close() local num_url_spaces = 30 if arg[1] then io.stdout:write('> >') for i=1,num_url_spaces do io.stdout:write(' ') end print('- ' .. arg[1]) end </code></pre>

The "quote-br" script called by the "y1" script:

<pre><code>#! /usr/bin/env lua local lines = {} for line in io.stdin:lines() do table.insert(lines, '> ' .. line .. ' ') end io.stdout:write(table.concat(lines, '')) </code></pre>

inquiry

Okay, trying it one more time, this time with a bit more attention to lines beginning with whitespace:

y1:

<pre><code>#! /usr/bin/env lua local lines = {} for line in io.stdin:lines() do   table.insert(lines, line) end local url = '' if arg[1] then   url = ' ' .. arg[1] end local handle = io.popen('fmt -60 | quote-br' .. url, 'w') handle:write(table.concat(lines, ' ')) handle:close() local num_url_spaces = 30 if arg[1] then   io.stdout:write('> >')   for i=1,num_url_spaces do     io.stdout:write(' ')   end   print('- ' .. arg[1]) end </code></pre>

quote-br:

<pre><code>#! /usr/bin/env lua local lines = {} for line in io.stdin:lines() do   if arg[1] then     local whitespace,rest = string.match(line, '^(%s+)(.*)$')     if whitespace then       whitespace = string.gsub(whitespace, ' ', '  ')       whitespace = string.gsub(whitespace, '\t', '  ')       if rest then         rest = string.gsub(rest, '<', '<')         rest = string.gsub(rest, '>', '>')       else         rest = ''       end       line = whitespace .. rest     end   end   if arg[1] then     table.insert(lines, line .. ' ')   else     table.insert(lines, '> ' .. line .. ' ')   end end io.stdout:write(table.concat(lines, '')) </code></pre>

inquiry

Hmmm.

So I needed to add tags to the end of all the code lines, then much all the code lines into a single line to make it work. Not too convenient.

And then I'd need to go a step further and convert tab characters (which I prefer for indentation) to good 'ole "nbsp" entities....

inquiry

And then there's the "deceptivity" of leaving around replies that refer to stuff that changed.. or refer to stuff implying a relative screen location, which also might change... it's... it's... <panting> oh my gosh, the insanity of it all... :-)