unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Chong Yidong" <cyd@stupidchicken.com>
Cc: David Reitter <david.reitter@gmail.com>, emacs-devel@gnu.org
Subject: Re: longlines-mode: font-lock fails (in outline-mode)
Date: Tue, 28 Jun 2005 22:36:13 -0400 (EDT)	[thread overview]
Message-ID: <1091.220.255.171.130.1120012573.squirrel@www.stupidchicken.com> (raw)
In-Reply-To: <E1DnL6a-0004td-HA@fencepost.gnu.org>

>     *** bla bla bla blu blu blu er er er yeah yeah yeah wow wow wow yup
>     yup yup see here it went black not so good
>
>     Enter enough text for it to be wrapped around. The first line shown
>     is in purple color, the next line is black, as are the following
>     lines. Because it's still part of the headline, it should be purple
>     as well. outline-mode should look for the hard end of the line, not
>     the 'soft' or wrapped end.
>

That's no different from what you get without longlines mode.  For
instance, look at the NEWS file; a typical entry is

  ** New translations of the Emacs Tutorial are available in the
  following languages: Brasilian Portuguese, Bulgarian, Chinese (both
  with simplified and traditional characters), French, and Italian.
  Type `C-u C-h t' to choose one of them in case your language setup
  doesn't automatically select the right one.

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.

  reply	other threads:[~2005-06-29  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2005-06-29 23:38 David Reitter

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1091.220.255.171.130.1120012573.squirrel@www.stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).