diff options
| author | Luke Shumaker <LukeShu@sbcglobal.net> | 2014-01-25 22:59:27 -0500 |
|---|---|---|
| committer | Luke Shumaker <LukeShu@sbcglobal.net> | 2014-01-25 22:59:27 -0500 |
| commit | 2413c4d35298a603adb42140a64d68cbbd2be1fb (patch) | |
| tree | ae608b9a3beea7fb5700698d7073b9b2a974f422 | |
| parent | 47324331076bd3427c2781802e21f8f546b082b1 (diff) | |
Tidy up, use unicode … when appropriate.
| -rw-r--r-- | public/emacs-shells.md | 2 | ||||
| -rw-r--r-- | public/git-go-pre-commit.md | 2 | ||||
| -rw-r--r-- | public/java-segfault.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/public/emacs-shells.md b/public/emacs-shells.md index 66848bb..d7ff44e 100644 --- a/public/emacs-shells.md +++ b/public/emacs-shells.md @@ -53,7 +53,7 @@ shell-mode The name is a misnomer; shell-mode is a terminal emulator, not a shell; it's called that because it is used for running -a shell (bash/zsh...). The idea of this mode is to use an external +a shell (bash, zsh, …). The idea of this mode is to use an external shell, but make it Emacs-y. History is not handled by the shell, but by Emacs; `M-p` and `M-n` access the history, while arrows/`C-p`/`C-n` move the point (which is is consistent with other Emacs REPL-type diff --git a/public/git-go-pre-commit.md b/public/git-go-pre-commit.md index 98e7b28..b9d4389 100644 --- a/public/git-go-pre-commit.md +++ b/public/git-go-pre-commit.md @@ -31,7 +31,7 @@ that is staged for commit; here's my `.git/hooks/pre-commit`: # This would only loop over files that are already staged for commit. # git diff --cached --numstat | # while read add del file; do - # ... + # … # done shopt -s globstar diff --git a/public/java-segfault.md b/public/java-segfault.md index 4a4e32e..48a6872 100644 --- a/public/java-segfault.md +++ b/public/java-segfault.md @@ -70,7 +70,7 @@ executed doesn't access any other methods or properties of `o`, then it will go ahead and consider `o` eligible for garbage collection before `m()` has finished running. -That is normally a safe optimization to make... except for when a +That is normally a safe optimization to make… except for when a destructor method (`finalize()`) is defined for the object; the destructor can have side effects, and Java has no way to know whether it is safe for them to happen before `m()` has finished running. |