mac os 맥에서 한영전환키를 shift-space 로 변경하기 위해 찾아본 몇 가지 자료 나중에 또 필요할 것 같아서 기록함.
'이전 입력 소스 선택'이 아니라 '입력 메뉴에서
version: '2' | |
services: | |
myapp: | |
build: . | |
container_name: "myapp" | |
image: debian/latest | |
environment: | |
- NODE_ENV=development | |
- FOO=bar | |
volumes: |
mac os 맥에서 한영전환키를 shift-space 로 변경하기 위해 찾아본 몇 가지 자료 나중에 또 필요할 것 같아서 기록함.
'이전 입력 소스 선택'이 아니라 '입력 메뉴에서
유니코드에서 한글을 어떻게 다루는지를 정리하였다.
Sometimes you may want to undo a whole commit with all changes. Instead of going through all the changes manually, you can simply tell git to revert a commit, which does not even have to be the last one. Reverting a commit means to create a new commit that undoes all changes that were made in the bad commit. Just like above, the bad commit remains there, but it no longer affects the the current master and any future commits on top of it.
git revert {commit_id}
Deleting the last commit is the easiest case. Let's say we have a remote origin with branch master that currently points to commit dd61ab32. We want to remove the top commit. Translated to git terminology, we want to force the master branch of the origin remote repository to the parent of dd61ab32:
""" Trains an agent with (stochastic) Policy Gradients on Pong. Uses OpenAI Gym. """ | |
import numpy as np | |
import cPickle as pickle | |
import gym | |
# hyperparameters | |
H = 200 # number of hidden layer neurons | |
batch_size = 10 # every how many episodes to do a param update? | |
learning_rate = 1e-4 | |
gamma = 0.99 # discount factor for reward |
#!/bin/bash | |
# | |
# Highligh Nginx config file in Vim | |
# Download syntax highlight | |
mkdir -p ~/.vim/syntax/ | |
wget http://www.vim.org/scripts/download_script.php?src_id=19394 -O ~/.vim/syntax/nginx.vim | |
# Set location of Nginx config file | |
cat > ~/.vim/filetype.vim <<EOF |
<?php | |
/** | |
* I was having trouble with socket connections timing out reliably. Sometimes, | |
* my timeout would be reached. Other times, the connect would fail after three | |
* to six seconds. I finally figured out it had to do with trying to connect to | |
* a routable, non-localhost address. It seems the socket_connect call would | |
* not fail immediately for those connections. This function is what I finally | |
* ended up with that reliably connects to a working server, fails quickly for | |
* a server that has an address/port that is not reachable and will reach the |
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward
discussions repo
TODO: Add price informations
TODO: Add App Store Addresses
###Chrome
One browser for your computer, phone and tablet