As configured in my dotfiles.
start new:
tmux
start new with session name:
// inside your beforeEach hook | |
spyOn(window, 'setTimeout').andCallFake(function(fn){ | |
fn.apply(null, [].slice.call(arguments, 2)); | |
return +new Date; | |
}); | |
... |
# First install tmux | |
brew install tmux | |
# For mouse support (for switching panes and windows) | |
# Only needed if you are using Terminal.app (iTerm has mouse support) | |
Install http://www.culater.net/software/SIMBL/SIMBL.php | |
Then install https://bitheap.org/mouseterm/ | |
# More on mouse support http://floriancrouzat.net/2010/07/run-tmux-with-mouse-support-in-mac-os-x-terminal-app/ |
As configured in my dotfiles.
start new:
tmux
start new with session name:
<android xmlns:android="http://schemas.android.com/apk/res/android"> | |
<tool-api-level>16</tool-api-level> | |
<manifest android:installLocation="preferExternal" | |
android:versionCode="3" android:versionName="1.0.2"> | |
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="16"/> | |
<application android:theme="@android:style/Theme.Holo"> | |
<activity | |
android:configChanges="keyboardHidden|orientation" | |
android:name="org.appcelerator.titanium.TiActivity" | |
android:screenOrientation="portrait" |
;(function(){ | |
var text = [ | |
[ | |
"Right from the beginning, it appeared to us that designing the new" | |
, "When we first thought about it, we understood that designing the new" | |
] | |
, [ | |
" iPhone" | |
, " iMac" |
define(function(require, exports, module) { | |
'use strict'; | |
var Ember = require('ember'); | |
var App = Ember.Application.create({ | |
rootElement: 'main', | |
Router: require('router') | |
}); |
// when you're trying to use `position:sticky` on an element | |
// you'll have trouble if any parent/ancestor element has | |
// overflow set to anything other than "visible" (such as: auto,hidden,overlay,scroll) | |
// & turns out if a parent is `display:flex` it might need some love | |
// (to remedy this you can set the `align-self` of your sticky element) | |
// see here for how the display & align-self properties affect: http://bit.ly/2ZaRu4o | |
// so, to find those troublesome parents... | |
// copy & paste this into Chrome Inspector/Dev Tools console | |
// (and be sure to change the #stickyElement below, if needed) |
Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.
You use Next.js router like normally, but don't define getStaticProps
and such. Instead you do client-only fetching with swr
, react-query
, or similar methods.
You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)
Don't like Next? Here's how to do the same in Gatsby.