aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-04-09 06:42:10 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-04-09 06:42:10 +0000
commitaf388addc609a8b7993f73b980daf61fd567fe6d (patch)
tree6c7777a50d914c4cf32b613bfd177597a6207459 /doc
parent121c3b9139fc11e1a43975b1d4a46bdd869a9d78 (diff)
downloadikiwiki-af388addc609a8b7993f73b980daf61fd567fe6d.tar
ikiwiki-af388addc609a8b7993f73b980daf61fd567fe6d.tar.gz
web commit by JoshTriplett: Response: please, no. Client-side wrapping of selections possibly OK.
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/word_wrap.mdwn10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/bugs/word_wrap.mdwn b/doc/bugs/word_wrap.mdwn
index 4aefb4bda..95cfc1538 100644
--- a/doc/bugs/word_wrap.mdwn
+++ b/doc/bugs/word_wrap.mdwn
@@ -5,4 +5,12 @@ friend here). Is there any way to improve this?
> See "using the web interface with a real text editor" on the [[tips]]
> page. --[[JoshTriplett]]
->> Would it be useful to allow a "max width" plugin, which would force on commit the split of long lines ? \ No newline at end of file
+>> Would it be useful to allow a "max width" plugin, which would force on commit the split of long lines ?
+
+>>> Please, no. That would wreak havoc on code blocks and arguments to
+>>> preprocessor directives, and it would make bulleted lists and quoted
+>>> blocks look bogus (because the subsequent lines would not match), among
+>>> other problems. On the other hand, if you want to propose a piece of
+>>> client-side JavaScript that looks at the active selection in a text area
+>>> and word-wraps it, and have a plugin that adds a "Word-Wrap Selection"
+>>> button to the editor, that seems fine. --[[JoshTriplett]]