yagihiro

#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/workqueue.h>

static void mykmod_work_handler(struct work_struct *w);

static struct workqueue_struct *wq = 0;
static DECLARE_DELAYED_WORK(mykmod_work, mykmod_work_handler);
static unsigned long onesec;

nebiros

group :production do
  gem "unicorn"
end

emil10001

The accidental clicks while in crouton (chrooted Ubuntu) on my Pixel are kind of annoying. The touchpad is super sensitive, resulting in a lot of extra clicks on stuff when I'm typing. In XFCE, there's a pretty easy way to deal with this.Simply go to Settings -> Mouse -> Touchpad and un-check 'Tap touchpad to Click'. Optionally, also 'Disable touchpad while typing'. I had been using the 'disable touchpad while typing' option for a bit, but I still get accidental clicks. I'm hoping that disabling the ultra-sensitive taps will give a better result

mitsutaka

#! /bin/sh

USER=mitz
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="Aerofs CLI Client"
NAME=aerofs
START_DAEMON="/usr/bin/aerofs-cli"
STOP_DAEMON="/usr/bin/aerofs-sh shutdown"
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME

macintux

This is not intended to be comprehensive or authoritative, just free online resources I've found valuable while learning more about Erlang.

Similar lists

• 0xAX's list of Erlang bookmarks
• Federico Carrone, Erlang Spawned Shelter
• Ivan Uemlianin's list of resources on various BEAM languages
• David Robakowski's curated list of awesome Erlang libraries, resources and shiny things
• Julius Beckmann's curated list of amazingly awesome Elixir and Erlang libraries, resources and shiny things

Instruction

tsubaki

using UnityEngine;
using System.Collections;
using System.Collections.Generic;
using UnityEngine.Assertions;
using System;

public class SkinnedMeshUpdater : MonoBehaviour
{
	[SerializeField]
	SkinnedMeshRenderer original;

mandarinx

Unity3D optimization tips

Some code allocates memory when running in the editor and not on the device. This is due to Unity doing some extra error handling so possible error messages can be output in the console. Much of this code is stripped during build. It's therefore important to profile on device, and do it regularly.

Optimizations often makes code more rigid and harder to reason. Don't do it until you really need to.

When profiling, wrap methods or portions of a method in Profiler.BeginSample(string name) and Profiler.EndSample() to make them easier to find in the profiler.

public class SomeClass {

mrdoob

/**
 * @author mrdoob / http://mrdoob.com/
 */

function html2canvas( element ) {

	var range = document.createRange();

	function getRect( rect ) {

TarasOsiris

public static void ShowToast(string text)
{
	if (Application.platform == RuntimePlatform.Android)
	{
		AndroidJavaClass unityPlayer = new AndroidJavaClass("com.unity3d.player.UnityPlayer");
		AndroidJavaObject activity = unityPlayer.GetStatic<AndroidJavaObject>("currentActivity");

		activity.Call("runOnUiThread", new AndroidJavaRunnable(
		  ()=> 
		  {

irokhes

clock = sinon.useFakeTimers(new Date(2016,11,1).getTime());
new Date(); //=> return the fake Date 'Sat Nov 01 2016 00:00:00'

clock.restore();
new Date(); //=> will return the real time again (now)