From: Miles Bader <miles@gnu.org>
Cc: Miles Bader <miles@lsi.nec.co.jp>, "Kim F. Storm" <storm@cua.dk>,
Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: info invisible changes
Date: Wed, 6 Nov 2002 11:32:43 -0500 [thread overview]
Message-ID: <20021106163243.GA9775@gnu.org> (raw)
In-Reply-To: <200211061511.gA6FBfL02691@rum.cs.yale.edu>
On Wed, Nov 06, 2002 at 10:11:41AM -0500, Stefan Monnier wrote:
> > I think a lot of this stuff would become _much_ simpler if you could must
> > munge the buffer instead of using invisible/display properties (with all
> > their associated oddities), perhaps using text properties to store the
> > necessary non-displayed info instead of parsing the buffer for it -- of
> > course this would perhaps be a bigger change, since you'd have to modify
> > the various info-getting functions too, but I don't see why it would be
> > _that_ big a job (presumably the modified code would support both
> > text-property stored info and buffer-parsing, for backward
> > compatibility).
>
> I disagree. Especially since it's all customizable, it's easier and
> safer to keep only one buffer-format and change the appearance
> via properties.
Safer I don't know (though I suspect it doesn't really make all that much
difference), but easier? Modifying a buffer is _far_ more straight-forward
than using display-modification properties (because lots of stuff in emacs
simply doesn't know about them or their effects, and happily proceeds as if
they weren't there).
-Miles
--
P.S. All information contained in the above letter is false,
for reasons of military security.
next prev parent reply other threads:[~2002-11-06 16:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 8:04 info invisible changes Miles Bader
[not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05 4:08 ` Miles Bader
2002-11-05 18:49 ` Stefan Monnier
2002-11-07 4:49 ` Richard Stallman
2002-11-05 23:57 ` Kim F. Storm
2002-11-06 9:51 ` Miles Bader
2002-11-06 12:46 ` Kim F. Storm
2002-11-06 12:30 ` Miles Bader
2002-11-06 15:11 ` Stefan Monnier
2002-11-06 16:32 ` Miles Bader [this message]
2002-11-07 15:08 ` Richard Stallman
2002-11-12 10:11 ` Kim F. Storm
2002-11-12 9:22 ` Miles Bader
2002-11-12 10:59 ` Kim F. Storm
2002-11-12 17:28 ` Robert J. Chassell
2002-11-13 14:37 ` Kim F. Storm
2002-11-13 18:20 ` Robert J. Chassell
2002-11-14 12:17 ` Richard Stallman
2002-11-14 21:38 ` Kim F. Storm
2002-11-12 18:49 ` Stefan Monnier
2002-11-13 23:31 ` Kim F. Storm
2002-11-14 0:39 ` Kim F. Storm
2002-11-14 4:09 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 13:57 Karl Berry
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=20021106163243.GA9775@gnu.org \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=miles@lsi.nec.co.jp \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=storm@cua.dk \
/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).