all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: How to use `narrow'?
Date: Wed, 19 Oct 2005 02:11:14 +0000 (UTC)	[thread overview]
Message-ID: <dj4a02$2fad$1@agate.berkeley.edu> (raw)
In-Reply-To: 874q7e1nfz.fsf@robotron.ath.cx

[A complimentary Cc of this posting was sent to
David Hansen 
<david.hansen@gmx.net>], who wrote in article <874q7e1nfz.fsf@robotron.ath.cx>:
> On Tue, 18 Oct 2005 19:41:51 +0000 (UTC) Ilya Zakharevich wrote:
> 
> > No, it does not help.  font-lock widens unconditionally.
> >
> >> ,----[ C-h v font-lock-dont-widen RET ]
> >
> > I would prefer a solution which works in real world, not in some
> > imaginary settings...  However, it is nice that somebody realized that
> > widening is a problem.  When will we see it, in 22.1?

> I'm sorry, i forgot to mention that I'm running emacs from CVS.

Well, I guessed this.  But anyway, just font-lock-dont-widen is not
enough to have robust support for narrowing.  Obviously, there are
cases when this widen() *is* useful.  And there are cases when it is
harmful.

The only way I see which may be usable is a way to mark a *particular*
narrowing operation as requiring (or not) widen() during
fontification.  E.g., one could put some text property on the narrowed
region (as far as widen() is smart enough to remove this text property
afterwards...).

Is there anything like this in CVS?

Thanks,
Ilya

  reply	other threads:[~2005-10-19  2:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:09 How to use `narrow'? Ilya Zakharevich
2005-10-18  8:13 ` Gian Uberto Lauri
     [not found] ` <mailman.11713.1129623266.20277.help-gnu-emacs@gnu.org>
2005-10-18  8:47   ` Ilya Zakharevich
2005-10-18 12:53 ` David Hansen
2005-10-18 19:41   ` Ilya Zakharevich
2005-10-18 22:15     ` David Hansen
2005-10-19  2:11       ` Ilya Zakharevich [this message]
2005-10-21  4:29         ` Stefan Monnier
2005-10-18 16:25 ` Anselm Helbig

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='dj4a02$2fad$1@agate.berkeley.edu' \
    --to=nospam-abuse@ilyaz.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 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.