all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
Cc: cyd@stupidchicken.com
Subject: Re: longlines-mode: font-lock fails (in outline-mode)
Date: Thu, 30 Jun 2005 00:38:21 +0100	[thread overview]
Message-ID: <13A5DB2D-289D-40A6-88C8-D2DEE72F5BFF@gmail.com> (raw)

Chong Yidong wrote:

> Only the "New translations... in the" part is highlighted.  If this  
> is not
> a problem, neither should it be a problem when longlines-mode is  
> turned
> on.\

I can't quite agree: if you have a soft-newline, that means that the  
headline (to be marked) continues in the next line. The user has not  
pressed return! It's like a normal line-wrap.
The syntax highlighting should take into account what the compiler  
(eventually) gets to see (in the case of source code) or what gets  
written to file.

Given that longlines-mode shows that kind of behavior in other major  
modes as well (e.g. python mode - i reported a bug recently), I think  
that Richard's suggestion about making '.' match  soft-newlines might  
be a good idea and a general solution to this class of problems. One  
would obviously want to make sure that the newlines-indicator (I  
don't know how this is implemented) is unique so that the change of  
regexp matching doesn't have knock-on effects in other contexts.

-D

             reply	other threads:[~2005-06-29 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 23:38 David Reitter [this message]
     [not found] <C89C5C51-0CD1-47B1-91DD-DD38749F14EF@gmail.com>
     [not found] ` <E1DmwkF-0005HF-OH@fencepost.gnu.org>
     [not found]   ` <F95FE268-D989-45BC-AFDB-3BA9FBB912ED@gmail.com>
2005-06-28 18:46     ` longlines-mode: font-lock fails (in outline-mode) Richard M. Stallman
2005-06-29  2:36       ` Chong Yidong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13A5DB2D-289D-40A6-88C8-D2DEE72F5BFF@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.