REFERENCES FOR LEARNING & USING APPLESCRIPT Modified: 2018/06/19 18:47
AppleScript is a rather peculiar scripting language to learn.
<?php | |
add_action( 'wp_head', 'custom_genesis_page_builder_styles' ); | |
/** | |
* Echo the necessary "Full Page Width" styles into the head of the page. | |
* Credit for the following CSS goes to the developer of the "Genesis Dambuster" | |
* Plugin as this CSS is an edited version of that Plugin's full-width.css file. | |
*/ | |
function custom_genesis_page_builder_styles() { | |
echo ' | |
<style type="text/css"> |
System process daemons that are system-wide provided by mac os x are described by launchd preference files that can be showed with the command: | |
$ sudo ls -all /System/Library/LaunchDaemons/ | |
Third party process daemons that are system-wide provided by the administrator are described by preference files that can be showed with the command: | |
$ sudo ls -all /Library/LaunchDaemons/ | |
Launch Agents that are per-user provided by mac os x usually loaded when the user logs in. Those provided by the system can be found with: | |
$ sudo ls -all /System/Library/LaunchAgents/ | |
Launch Agents that are per-user provided by the administrator and usually loaded when the user logs in. Those provided by the system can be found with: |
Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.
The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.
Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.
#! /usr/bin/env python | |
# coding: utf-8 | |
''' | |
auto switch keyboard between different applications | |
if you want to change the app list, modify the var 'ignore_list' | |
''' | |
from AppKit import NSWorkspace, NSWorkspaceDidActivateApplicationNotification, NSWorkspaceApplicationKey |
<?php | |
namespace App\Exceptions; | |
use Exception; | |
use Illuminate\Validation\ValidationException; | |
use Illuminate\Auth\Access\AuthorizationException; | |
use Illuminate\Database\Eloquent\ModelNotFoundException; | |
use Symfony\Component\HttpKernel\Exception\HttpException; | |
use Laravel\Lumen\Exceptions\Handler as ExceptionHandler; |
Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.
The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.
Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.
This is a fork of and builds upon the work of Eddie Webb's search and Matthew Daly's search explorations.
It's built for the Hugo static site generator, but could be adopted to function with any json index.
To see it in action, go to craigmod.com and press CMD-/
and start typing.