pithy | An internal DSL for generating HTML in JavaScript | JSON Processing library

There is a very pithy method for bootstrap table filtering on W3Schools: https://www.w3schools.com/bootstrap/tryit.asp?filename=trybs_filters_table&stacked=h

Here is the jQuery/Javascript portion (uses a text box to filter the table):

This is mostly to geek out on how awesome Raku is.

Question

Are there built-in methods that will take a list and cycle through it indefinitely, producing, say, the lazy list

I am attempting to use [slug].js to render pages adjacent to index.js via getStaticProps and getStaticPaths. Upon navigation to a page using the dynamic route I get a mismatch error. This error occurs even when the provided path does in fact match the page slug and page props content.

When the index.js is duplicated and renamed to page-name.js (e.g. "about.js") the page renders fine, so I believe the issue lies with how I am using getStaticPaths. In reality, I do not fully comprehend the relationship between getStaticProps and getStaticPaths. Is there some mapping which occurs to allow the engine to look up the appropriate props given whatever path in the map?

Index.js

df with a text column 'DescCol' that has been entered variously with no consistent but, somewhat similar patterns. I need to:

• (a) extract all substrings within parentheses
• (b) if the extracted substring contains numbers then:
• (b.i) if (b) the beginning text is in ('Up to', '<', 'Tolerance') - so mark a boolean column 'isToleranceSpec' Yes for 'Tolerance', No otherwise
• (b.ii) extract the digit following the beginning text of the substring (which may or may not have comma separator) into a column called 'BandLimit'
• (b.iii) then check if there is further follow-on text ('thereafter' AFAIK)
• (b.iv) if (b.iii) then extract the number following 'thereafter' into a column called 'Marginal' else continue
• (c) if not (b): continue

So the result df will look like below ('Remarks' columns highlights some of the peculiarities I've noticed in the data so far):

Is there a pithy way to get the shape of a multidimensional array in Scala? I'm thinking of something equivalent to the following using Numpy in Python:

Whenever I accidentally fat-finger C-x C-c (or Cmd-Q on a Mac), GNU Emacs exits right away unless shells are open or buffers, backed by files, are modified -- in which case it prompts as to how to proceed.

Unfortunately, if I've got no shell sessions open and have saved my files, but am in the midst of composing a brilliant, yet perhaps not entirely pithy, git log message (in the *vc-log* buffer), that won't prevent me exiting in one fell, promptless, swoop -- thus losing that draft, which apparently doesn't get autosaved anywhere that I've been able to find.

What's the best way to address this issue? I would think it's best for *vc-log*, and any other such buffer that provides for "on-the-fly" composition not backed by a traditional file (such as a commit/checkin message or email), to nevertheless be backed by a "pending draft" file. That would not only help avoid accidentally exiting Emacs, but allow restoring of such a draft if Emacs (or the computer itself) crashed.

If that's a reasonable approach, how should it be implemented?

Other approaches I've considered (which seem less than ideal):

• Somehow convince the pertinent Emacs exit hook to always prompt before exiting, even if there are no shell sessions nor modified, file-backed, buffers
• Use a fresh Emacs session, auto-invoked by (e.g.) git commit (with no -m option and assuming GIT_EDITOR=emacs in the environment), so the file-backed COMMIT_EDITMSG buffer is used to compose the commit message -- which prevents that new Emacs session from quitting without prompting and avoids accidentally quitting the original Emacs session (typically "fatter" with many buffers and other context)
• Use git commit -m ... for single-line commit messages
• Always keep a shell session open (within Emacs), so quitting always prompts first

Any recommendations?

An Observable - a collection over time - is a useful thing to be able to request over the web. A feed is best modeled as an Observable, not a static array that you must poll and diff to request.

My question - if I wanted to create a web endpoint that would let you do

So I'm learning about pipes in bash and I found this pithy description:

A Unix pipe connects the STDOUT (standard output) file descriptor of the first process to the STDIN (standard input) of the second. What happens then is that when the first process writes to its STDOUT, that output can be immediately read (from STDIN) by the second process.

Source

Given this understanding, let's connect the STDOUT of printf to the STDIN of ls. For simplicity, print the parent directory (printf ..).