lararosekelley

;; Show current command in modeline
(use-package keycast
  :straight t
  :hook (after-init . keycast-mode)
  :config
  (define-minor-mode keycast-mode
    "Show current command and its key binding in the mode line (modified for doom-modeline use)."
    :global t
    (if keycast-mode
      (progn

lararosekelley

Keybase proof

I hereby claim:

• I am tylucaskelley on github.
• I am tylucaskelley (https://keybase.io/tylucaskelley) on keybase.
• I have a public key ASB6IDPMcRH2TAMwfUwu2xHac6sLr0wOyMXeVSWoXpV9CQo

To claim this, I am signing this object:

lararosekelley

+ files=(~/.aliases ~/.exports ~/.functions ~/.git-prompt.sh ~/.env)
+ for file in "${files[@]}"
+ '[' -f /home/tylucaskelley/.aliases ']'
+ source /home/tylucaskelley/.aliases
++ alias vim=nvim
++ alias vi=nvim
++ alias 'sudo=sudo '
++ alias 'up=cd ..'
++ alias '~=cd ~'
++ alias -- '-=cd -'

lararosekelley

ERROR: nodejs-native-8.12.0-r0 do_compile: oe_runmake failed
ERROR: nodejs-native-8.12.0-r0 do_compile: Function failed: do_compile (log file is located at /home/tylucaskelley/Code/veo-oe/tmp/build-glibc/work/x86_64-linux/nodejs-native/8.12.0-r0/temp/log.do_compile.30036)
ERROR: Logfile of failure stored in: /home/tylucaskelley/Code/veo-oe/tmp/build-glibc/work/x86_64-linux/nodejs-native/8.12.0-r0/temp/log.do_compile.30036
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j4 BUILDTYPE=Release
| make -C out BUILDTYPE=Release V=1
|   LD_LIBRARY_PATH=/home/tylucaskelley/Code/veo-oe/tmp/build-glibc/work/x86_64-linux/nodejs-native/8.12.0-r0/node-v8.12.0/out/Release/lib.host:/home/tylucaskelley/Code/veo-oe/tmp/build-glibc/work/x86_64-linux/nodejs-native/8.12.0-r0/node-v8.12.0/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../.; mkdir -p /home/tylucaskelley/Code/veo-oe/tmp/build-glibc/work/x86_64-linux/nodejs-native/8.12.0-r0/node-v8.12.0/out/Release/obj/gen; python too

lararosekelley

function find-up() {
    path=$(pwd)
    while [[ "$path" != "" && ! -e "$path/$1" ]]; do
      path=${path%/*}
    done
    echo "$path"
  }

  function cdnvm() {
    cd "$@" || return;

lararosekelley

hooks:
    pre-commit:
        - eslint
        - npmtests
    commit-msg:
        - enforecaps

lararosekelley

// Let's say you give this to jQuery on a browser that doesn't support the selectors API
var $element = $(".title p");

// First, Sizzle will break up the query into an array of selectors:
[".title", "p"]

// You might think that Sizzle will go left to right to find our elements!
// Actually, it does the opposite; Sizzle will first try to find all of the "a" tags,
// using it's "find" method.

lararosekelley

$(document).ready(function() {
    // Sizzle is jQuery's internal library for DOM element selection. When does it actually get used?
    
    // modern browser, i.e. Chrome, Firefox, Safari, IE 8+, Edge
    
    $("#title"); // Nope! --> document.getElementById("title");
    
    $(".my-class") // Nope! --> document.getElementsByClassName("my-class");
    
    $("body > div.foo #element"); // Nope! --> document.querySelectorAll("body > div.foo #element");

lararosekelley

$(document).ready(function() { // just like before, it's good practice to wrap your code in this callback function
    // we can select elements by tag name
    var $body = $("body");
    
    // this creates what is called a "jQuery object", which comes with a
    // ton of convenience methods for DOM manipulation. Here's one:
    $body.css("color", "white");
    
    // we can also look for elements using a combination of tag name, class, and ID
    var $title = $("h1.title");

lararosekelley

$(document).ready(function() { // ensure jQuery is loaded before doing anything
    // iterate over an array
    $.each([1, 2, 3, 4], function(index, value) {
        console.log( index + ": " + value );
    });
    
    // parse a JSON-formatted string and return a JS object
    var obj = $.parseJSON('{ "first_name": "Ty-Lucas", "last_name": "Kelley" }');
    
    // get some JSON from an API