skurhse

-- REQ: Configures neovim using lua. <skr 2023-04-30>

-- SEE: https://neovim.io/doc/user/lua-guide.html <>

local call = vim.call
local cmd  = vim.cmd
local set  = vim.o

-- SEE: https://github.com/junegunn/vim-plug <>
cmd [[

skurhse

#!/bin/bash

env 1>&1 |
grep '^PATH=' 1> >(cat) |
cut -c 6- |
awk '
{
  old = ":"
  new = "\n"  
  while ($0 ~ /:/) {

jasemagee

fortune | cowsay  -f "$(ls /usr/share/cowsay/cows | sort -R | head -1)" | lolcat

markbates

If you're writing web applications with Ruby there comes a time when you might need something a lot simpler, or even faster, than Ruby on Rails or the Sinatra micro-framework. Enter Rack.

Rack describes itself as follows:

Rack provides a minimal interface between webservers supporting Ruby and Ruby frameworks.

Before Rack came along Ruby web frameworks all implemented their own interfaces, which made it incredibly difficult to write web servers for them, or to share code between two different frameworks. Now almost all Ruby web frameworks implement Rack, including Rails and Sinatra, meaning that these applications can now behave in a similar fashion to one another.

At it's core Rack provides a great set of tools to allow you to build the most simple web application or interface you can. Rack applications can be written in a single line of code. But we're getting ahead of ourselves a bit.