summary refs log tree commit diff
diff options
context:
space:
mode:
authorWayne Davison <wayned@users.sourceforge.net>2005-10-14 09:23:57 +0000
committerWayne Davison <wayned@users.sourceforge.net>2005-10-14 09:23:57 +0000
commite95a5a116447db42790a4daebad80bd26d26f637 (patch)
tree90b60d3c0f36eb5fdb1e330e9997866d3bf68687
parent2dac435d8aabc6d0133017ab5c9aad777fbcd971 (diff)
downloadzsh-e95a5a116447db42790a4daebad80bd26d26f637.tar.gz
zsh-e95a5a116447db42790a4daebad80bd26d26f637.tar.xz
zsh-e95a5a116447db42790a4daebad80bd26d26f637.zip
One more tweak to a sentence in the PROMPT_SP section.
-rw-r--r--Etc/FAQ.yo8
1 files changed, 4 insertions, 4 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index bd1d214c2..528afa876 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -1670,10 +1670,10 @@ sect(How do I prevent the prompt overwriting output when there is no newline?)
     fi
   )
   That precmd function will only bump the screen down to a new line if there
-  was output on the prompt line, otherwise the extra spaces get removed by
-  the tt(PROMPT_CR) action.  Although this typically looks fine it may result
-  in the preceding spaces being included when you select a line of text with
-  the mouse.
+  was output on the prompt line, otherwise the extra chars get removed by
+  the PROMPT_CR action.  Although this typically looks fine, it may result
+  in the spaces preceding the prompt being included when you select a line
+  of preserved text with the mouse.
 
   One final alternative is to put a newline in your prompt -- see question
   link(3.13)(313) for that.