[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Uninformative comment in files.el
From: |
Richard Stallman |
Subject: |
Re: Uninformative comment in files.el |
Date: |
Mon, 17 Dec 2007 03:24:29 -0500 |
Well, one (and possibly more) whole-buffer overlay(s) is a consequence
of an obvious strategy to implement a top-down parser. Ie, wrap each
non-terminal parsed with an overlay to carry annotations as you return
from recursive levels. At least, it was obvious to me when I did it.
Maybe you're right, but even though one of the many overlays in this
would cover the whole buffer, it would also make other overlays,
smaller than the whole buffer, which would get messed up by reverting.
- Re: Uninformative comment in files.el, (continued)
- Re: Uninformative comment in files.el, Vinicius Jose Latorre, 2007/12/12
- Re: Uninformative comment in files.el, Stefan Monnier, 2007/12/12
- Re: Uninformative comment in files.el, Yoni Rabkin Katzenell, 2007/12/12
- Re: Uninformative comment in files.el, Richard Stallman, 2007/12/13
- Re: Uninformative comment in files.el, Stefan Monnier, 2007/12/13
- Re: Uninformative comment in files.el, martin rudalics, 2007/12/13
- Re: Uninformative comment in files.el, David Kastrup, 2007/12/13
- Re: Uninformative comment in files.el, Richard Stallman, 2007/12/15
- Re: Uninformative comment in files.el, Richard Stallman, 2007/12/15
- Re: Uninformative comment in files.el, Stephen J. Turnbull, 2007/12/16
- Re: Uninformative comment in files.el,
Richard Stallman <=
- Message not available
- Message not available
- Re: Uninformative comment in files.el, Richard Stallman, 2007/12/14
- Re: Uninformative comment in files.el, Stefan Monnier, 2007/12/20
- Re: Uninformative comment in files.el, Richard Stallman, 2007/12/21
- Re: Uninformative comment in files.el, Stefan Monnier, 2007/12/22
Re: Uninformative comment in files.el, Richard Stallman, 2007/12/12