|
From: | martin rudalics |
Subject: | Re: Patch: Syntax and Hard Newlines |
Date: | Sun, 19 Nov 2006 12:11:39 +0100 |
User-agent: | Mozilla Thunderbird 1.0 (Windows/20041206) |
> That way lies madness... ... yet there is method in 't. I nearly spent an hour analyzing longlines-mode and writing my proposal. Please spend a few minutes on the following questions: - longlines-mode substitutes newlines for spaces. This means that any function based on scan_newline (like `goto-line') may get me results that are inconsistent with those of tools analyzing the file my buffer visits. How can I treat compiler or grep output with longlines-mode? - Matching against the regexp "." may get me different results for the same buffer with longlines-mode disabled and enabled. Ignore that? - longlines-mode may wrap a regexp like "[ \t]*" at the space character. How can I evaluate a wrapped regexp like that? - How can I avoid that longlines-mode wraps a Lisp or Perl expression at a space preceding a left paren (with the left paren ending up at bol and messing up `beginning-of-defun-raw' and thus font-locking)? - How can I avoid that longlines-mode wraps a C string and `c-font-lock-invalid-string' complains? - I put an arbitrary text property on a space character. longlines-mode wraps the line at that character. How can I restore that property when turning off longlines-mode? - I use two windows of different widths to simultaneously show one and the same buffer. How can I adapt longlines-mode to wrap at the right borders of my windows?
[Prev in Thread] | Current Thread | [Next in Thread] |