kellpossible

patterns:
- comment: numbers including with decimal places
  name: constant.numeric.eppl
  match: (?<=[^a-zA-Z0-9\.])([\-]{0,1}[\d\.]+)
  
- name: keyword.control.eppl
  match: \b(if|else)\b
  
- comment: match strings
  name: string.eppl

kellpossible

find . -not -path "./.git/*" -type d -exec ls -d {} \; > folder_structure.txt

kellpossible

pub struct Database<'a> {
	pub fixes: Vec<Waypoint<'a>>,
	pub countries: HashMap<String, Country>,
}

impl<'a> Database<'a> {
	pub fn new(navdata_dir: PathBuf, resources_dir: PathBuf) -> Database<'a> {
		let countries_path = resources_dir.join("icao_countries.txt");
	    let countries_path = countries_path.to_str().unwrap();

kellpossible

struct A<'a> {
    s: &'a String
}

struct B<'a> {
    a: A<'a>,
    s: String
}

impl<'a> B<'a> {

kellpossible

[Desktop Entry]
Name=Feh
Name[en_US]=feh
GenericName=Image viewer
GenericName[en_US]=Image viewer
Comment=Fast Imlib2-based Image Viewer
Exec=bash -c "feh -. --start-at ./$(realpath --relative-to=$(dirname %f) %f)"
Terminal=false
Type=Application
Icon=feh

kellpossible

/*
 * I add this to html files generated with pandoc.
 */

html {
  font-size: 100%;
  overflow-y: scroll;
  -webkit-text-size-adjust: 100%;
  -ms-text-size-adjust: 100%;
}

kellpossible

{
    // heading colours matching Emacs Org Mode
    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": "markup.heading.markdown punctuation.definition.heading.markdown",
                "settings": {
                    "foreground": "#8a8888",
                }
            },

kellpossible

(custom-set-faces
 '(markdown-header-face-1 ((t (:inherit markdown-header-face :foreground "chocolate1" :height 1.5))))
 '(markdown-header-face-3 ((t (:inherit markdown-header-face :foreground "#66d9ef" :height 1.15))))
 '(markdown-header-face-4 ((t (:inherit markdown-header-face :foreground "#e6db74" :height 1.1))))
 '(markdown-header-face-5 ((t (:inherit markdown-header-face :foreground "#a1efe4")))))

kellpossible

Perfect Documentation Markup System

I've spent a lot of time over the past few years thinking about markup markup languages and systems in the context of writing documentation for commercial and open source projects. I've had the pleasure of creating a large Sphinx based document for a personal project, and in a user manual for a commercial project. I've also created a number of decent sized MkDocs based documents, and compared them with Sphinx and Hugo based alternatives. I've grappled with the practicalities of introducing such a system into a company that already has established document production workflows, and coming to grips with the fact that document production involves many more people than the original writers, and a system needs to cater for those people also. Throughout all of this, I've come to the conclusion that the current markdown based systems, as good as they are, still have a number of fundamental fl

kellpossible

#!/bin/sh

# A git script to make commits with messages prepended with issue number
# extracted from the current branch name.

# Config Values
ISSUE_TRACKER_URL="http://your-issue-tracker/issues/"
EDITOR_COMMAND="vi -c 'set ft=gitcommit'"

# Issue Number Extraction