From af388addc609a8b7993f73b980daf61fd567fe6d Mon Sep 17 00:00:00 2001 From: joey Date: Mon, 9 Apr 2007 06:42:10 +0000 Subject: [PATCH 1/1] web commit by JoshTriplett: Response: please, no. Client-side wrapping of selections possibly OK. --- doc/bugs/word_wrap.mdwn | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) 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]] -- 2.45.0