Regarding Python code: what you want makes sense, and could be a useful feature. But it is a completely different feature from the one longlines mode is trying to implement.
Regarding LaTeX, I find it incomprehensible that you want to record each paragraph as a single long line. I can't argue with your tastes, but I will certainly not make that the recommended way to edit LaTeX code in Emacs. Forget it! What I am suggesting is that the original representation in the file is respected. No conversion. That is an interesting idea, and I can see what it would mean in the cases you want to use (paragraph = one long line).] I don't see what this would mean, concretely, in the case where you edit a file composed of filled paragraphs. Editing should result once again in filled paragraphs. This means that the number of lines in the paragraph has to change as you edit it. And what you save it, the file should contain newlines where you see newlines on the screen. I am aware of the unwanted linebreaks introduced when you use visual wrapping together with a hard wrapped text file. Other editors do that, too, and it's not bad. It just means that one shouldn't mix the two editing modes. "Mixing modes" is a side issue. I'm talking about using just one mode, the mode with no hard newlines inside a paragraph. That must not be one long line in the file. _______________________________________________ Emacs-pretest-bug mailing list Emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug