unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Damien Cassou <damien@cassou.me>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: hierarchy
Date: Mon, 23 Oct 2017 08:03:56 -0400	[thread overview]
Message-ID: <jwvd15ejcul.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87po9ewaoz.fsf@cassou.me> (Damien Cassou's message of "Mon, 23 Oct 2017 10:05:48 +0200")

>> How would it work if you wanted to use it to navigate your local
>> file-system (where the complete hierarchy might be extremely and
>> costly to create)?

> This is implemented here
> https://github.com/DamienCassou/hierarchy/blob/master/examples/hierarchy-examples-fs.el.

> But, as you expect, this is not usable for a complete file system
> (displaying ~/.emacs.d takes 4 seconds on my fast computer).

>> Is there some way to construct (and display) it
>> lazily?

> could you please share your ideas at
> https://github.com/DamienCassou/hierarchy/issues/49?

I don't really have any precise idea in this respect.  I'm just thinking
it should be able to display the top-level nodes without looking at the
subtrees if they're not themselves displayed (yet).  Basically, design
it on the assumption that your hierarchy might be your complete
filesystem, yet it should respond "instantaneously".

>> Looking at the code I get the impression that it would be nice to split
>> it into 3 parts:
> by parts, you mean files?

Not necessarily, no: AFAICT your code is currently split into 2 parts,
so my proposal is to add an API based on generic functions between the
two so the display code can be used with other representations of
a tree.


        Stefan



  reply	other threads:[~2017-10-23 12:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 18:15 [ELPA] New package: hierarchy Damien Cassou
2017-10-17 21:17 ` Stefan Monnier
2017-10-23  7:47   ` Damien Cassou
2017-10-23 11:55     ` Stefan Monnier
2017-10-20 20:26 ` Stefan Monnier
2017-10-20 21:05   ` John Wiegley
2017-10-20 21:54   ` Clément Pit-Claudel
2017-10-21  8:52   ` João Távora
2017-10-23  8:17     ` Damien Cassou
2017-10-23  8:28       ` João Távora
2017-10-23  8:05   ` Damien Cassou
2017-10-23 12:03     ` Stefan Monnier [this message]
2017-10-21  7:27 ` Eli Zaretskii
2017-10-22 13:20   ` Damien Cassou
2017-10-22 14:39     ` Eli Zaretskii
2017-10-22 15:23       ` Damien Cassou
2017-10-22 19:41         ` John Wiegley
2017-10-22 20:25           ` Damien Cassou
2017-10-23  2:49             ` Eli Zaretskii

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=jwvd15ejcul.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=damien@cassou.me \
    --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).