unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeff Norden <jnorden@tntech.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: eliz@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: A question about overlays and performance.
Date: Tue, 28 Jul 2020 11:43:30 -0500	[thread overview]
Message-ID: <fdime7fv4d.fsf@norden.tntech.edu> (raw)
In-Reply-To: <87tuxttda9.fsf@localhost> (message from Ihor Radchenko on Mon, 27 Jul 2020 19:20:30 +0800)

> I am currently working on re-implementing org-mode folding from using
> overlays to text-properties.

It's interesting that you are working to change org's overlays back to
text properties, while I'm considering doing exactly the opposite for
the project that I've been playing with.  Do org buffers routinely wind
up with thousands of overlays?

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> ...
>> And the way I recommend to avoid this problem is to stay clear of
>> indirect buffers (which I consider as an attractive nuisance).

From what little I've seen of them, I'm quite inclined to agree with
Stefan's opinion about indirect buffers.  Is their main use in org to
provide multiple views of a buffer with different foldings?

I wonder if it might be possible to implement a "window-invisibility-spec",
that would override the buffer-spec when set.  It would have to be done
in C, not lisp.  You might even want to add a new field in the window
structure.  I have no real clue as to whether this is possible, feasible,
or a good idea.  But it might provide a nice way to display a single buffer
in two different windows with different levels of hidden text.  It seems
like it would be a lot simpler than using indirect buffers, but I'm
certainly no expert on this.

Regards,
-Jeff



  reply	other threads:[~2020-07-28 16:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 16:40 A question about overlays and performance Jeff Norden
2020-07-25 16:53 ` Eli Zaretskii
2020-07-25 17:24   ` Jeff Norden
2020-07-25 17:29     ` Eli Zaretskii
2020-07-26  1:33   ` Ihor Radchenko
2020-07-26 13:56     ` Eli Zaretskii
2020-07-26 14:19       ` Ihor Radchenko
2020-07-26 14:44     ` Stefan Monnier
2020-07-27 11:20       ` Ihor Radchenko
2020-07-28 16:43         ` Jeff Norden [this message]
2020-07-28 16:58           ` Yuan Fu
2020-07-28 17:05             ` Eric Abrahamsen
2020-07-29  1:52           ` Ihor Radchenko
2020-07-30 18:21             ` Jeff Norden
2020-07-28 23:53         ` Juri Linkov
2020-07-29  1:36           ` Ihor Radchenko
2020-07-30 23:04             ` Juri Linkov

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=fdime7fv4d.fsf@norden.tntech.edu \
    --to=jnorden@tntech.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@gmail.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 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).