From: Beni C. <cb...@te...> - 2003-02-18 21:12:47
|
On 2003-02-17, David Goodger wrote: > Is the proposed solution to the problems (empty comments) sufficient? > Such cases *will* arise. Perhaps a runtime setting, allowing or > disabling this convenience, would be appropriate. But that raises > issues too: > > User A, who writes lists indented (and their config file is set up > to allow it), sends a file to user B, who doesn't (and their > config file disables indented lists). The result of processing by > the two users will be different. > That's really bad. It means there will be two dialects of reST and you can't exchange files safely. If you are going to allow both, then allow both always. > It may seem minor, but it adds ambiguity to the parser, which is bad. > Agreed. Lately I'm starting to believe that some source variations belong in the editor. [For example, I'm trying to envision a system for translating python source code into other languages based on identifier replacement by the editor. That should work acceptably(?) for both keywords and the library, even 3-rd party ones.] Which gave me this idea on handle indented lists (I personally prefer them indented and perhaps without empty lines): let emacs do it. All reST documents on disk retain their current format; emacs' reST mode will have options to indent lists (only visually), hide empty lines in some contexts, etc... Of course somebody has to write this mode and it doesn't scratch badly enough for me to do so yet :-). -- Beni Cherniavsky <cb...@tx...> Do not feed the Bugzillas. |