Edit 2024-12-18:
Support for mouse emulation has now been implemented. See https://zmk.dev/docs/keymaps/behaviors/mouse-emulation
The instructions below are outdated.
Edit 2024-12-18:
Support for mouse emulation has now been implemented. See https://zmk.dev/docs/keymaps/behaviors/mouse-emulation
The instructions below are outdated.
#!/bin/bash | |
PHP_VERSION=7.4.2 | |
# Command lines tools | |
xcode-select --install | |
# Install dependencies | |
brew install wget autoconf openssl lzlib curl imap-uw readline postgresql gettext libxslt libiconv bison pkg-config krb5 bzip2 openldap tidy-html5 | |
# Dirs |
<?php | |
/** | |
* @file | |
* Contains \Drupal\varnish_cache_tag_purger\TagDeletionListener. | |
*/ | |
namespace Drupal\varnish_cache_tag_purger; | |
use Drupal\Core\Cache\NullBackend; |
#!/bin/bash | |
# | |
# The MIT License (MIT) | |
# | |
# Copyright (c) 2014 Mathias Leppich <[email protected]> | |
# | |
# Permission is hereby granted, free of charge, to any person obtaining a copy | |
# of this software and associated documentation files (the "Software"), to deal | |
# in the Software without restriction, including without limitation the rights | |
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell |
Record Auto semicolon macro and bind shortcut to it: | |
1. Edit -> Macros -> Start Macro Recording | |
2. In the editor go to the end of line by pressing End | |
3. put semicolon ';' | |
4. Edit -> Macros -> Stop Macro Recording | |
5. Give a name, for example 'Auto semicolon' | |
6. Open settings (Ctrl + Alt + s), select Keymap | |
7. Expand Macros node | |
8. Select 'Auto semicolon', in the context menu choose Add Keyboard Shortcut | |
9. Set Ctrl + ; as First keystroke |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
var runner = require('child_process'); | |
runner.exec( | |
'php -r \'include("settings.php"); print json_encode($databases);\'', | |
function (err, stdout, stderr) { | |
var connection = JSON.parse(stdout).default.default; | |
console.log(connection.database); | |
// result botdb | |
} |
package main | |
import ( | |
"fmt" | |
"net/http" | |
"time" | |
) | |
var urls = []string{ | |
"https://splice.com/", |
require 'redis' | |
require 'json' | |
class CommentsRepository | |
def initialize | |
@redis = Redis.new | |
end | |
def save(itemId, comment, parentId = nil) |
var parser = document.createElement('a'); | |
parser.href = "http://example.com:3000/pathname/?search=test#hash"; | |
parser.protocol; // => "http:" | |
parser.hostname; // => "example.com" | |
parser.port; // => "3000" | |
parser.pathname; // => "/pathname/" | |
parser.search; // => "?search=test" | |
parser.hash; // => "#hash" | |
parser.host; // => "example.com:3000" |