aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZhiming Wang <zmwangx@gmail.com>2015-09-21 19:02:37 -0700
committerZhiming Wang <zmwangx@gmail.com>2015-09-21 19:04:10 -0700
commitdd9b9d28744d83a0282e080b8d4733200818df96 (patch)
tree93b744793ae28b2bc6526a0d481b71b086d8778f
parent6458fe2de26e181178cf47c026ce989eed815dd1 (diff)
downloadmy_new_personal_website-dd9b9d28744d83a0282e080b8d4733200818df96.tar.xz
my_new_personal_website-dd9b9d28744d83a0282e080b8d4733200818df96.zip
Latest post: correct technical mistake
Unquoted ? in Zsh isn't a syntax error. And = should be quoted too.
Diffstat (limited to '')
-rw-r--r--source/blog/2015-09-21-zsh-51-and-bracketed-paste.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blog/2015-09-21-zsh-51-and-bracketed-paste.md b/source/blog/2015-09-21-zsh-51-and-bracketed-paste.md
index 61e421b6..591a973e 100644
--- a/source/blog/2015-09-21-zsh-51-and-bracketed-paste.md
+++ b/source/blog/2015-09-21-zsh-51-and-bracketed-paste.md
@@ -13,7 +13,7 @@ In short, Zsh 5.1 introduced bracketed paste mode[^1] and turned it on by defaul
https://www.google.com/search?q=zsh
- without typing in a single or double quote first, the `?` won't be backslash-quoted by default, which causes a syntax error when passed unnoticed (out of habit).
+ without typing in a single or double quote first, the `?` and `=` won't be backslash-quoted by default, which causes an error when passed unnoticed (out of habit).
2. The Emacs shell[^2] is littered with `^[[?2004h` and `^[[?2004l` around every prompt.