From: raman <raman@google.com>
To: emacs-devel@gnu.org
Subject: Re: [ANN] New library stream.el in ELPA
Date: Wed, 14 Oct 2015 17:42:02 -0700 [thread overview]
Message-ID: <p91r3kxc691.fsf@google.com> (raw)
In-Reply-To: <m2a8rl6sta.fsf@newartisans.com> (John Wiegley's message of "Wed, 14 Oct 2015 14:31:13 -0700")
Speaking from the perspective of building Emacspeak, I only feel
comfortable using modules that are already in Core, since I dont want
the average emacspeak user to have to pull things from elpa to get the
system started up. From that perspective, I would prefer to see
streams.el in Master --- though I could likely implement some of what I
was thinking of e.g., rapid interactive browsing of content by chunks,
where the chunk can be interactively determined etc using think.el just
as much as streams.el -- though streams is likely closer to what I
would use than the lower level thunk in that case.
--
next prev parent reply other threads:[~2015-10-15 0:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 11:43 [ANN] New library stream.el in ELPA Nicolas Petton
2015-10-14 12:37 ` Michael Heerdegen
2015-10-14 13:20 ` Nicolas Petton
2015-10-14 13:33 ` Michael Heerdegen
2015-10-14 13:30 ` Nicolas Petton
2015-10-14 22:13 ` Michael Heerdegen
2015-10-15 7:38 ` Nicolas Petton
2015-10-14 16:09 ` John Wiegley
2015-10-14 16:20 ` Nicolas Petton
2015-10-14 16:40 ` John Wiegley
2015-10-14 19:31 ` Nicolas Petton
2015-10-14 21:31 ` John Wiegley
2015-10-14 21:51 ` Nicolas Petton
2015-10-15 0:42 ` raman [this message]
2015-10-15 0:48 ` John Wiegley
2015-10-18 18:29 ` Daniel Colascione
2015-10-19 4:38 ` Stephen J. Turnbull
2015-10-20 6:55 ` John Wiegley
2015-10-20 7:02 ` Daniel Colascione
2015-10-20 15:18 ` John Wiegley
2015-10-20 16:16 ` Jay Belanger
2015-10-20 10:20 ` Stephen J. Turnbull
2015-10-20 12:07 ` David Kastrup
2015-10-23 11:30 ` Nicolas Petton
2015-10-23 19:21 ` John Wiegley
2015-10-15 10:08 ` Michael Heerdegen
2015-10-15 18:25 ` John Wiegley
2015-10-15 22:13 ` Nicolas Petton
2015-10-15 20:28 ` John Mastro
2015-10-15 22:02 ` Nicolas Petton
2015-10-24 19:16 ` Michael Heerdegen
2015-10-24 20:52 ` Nicolas Petton
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=p91r3kxc691.fsf@google.com \
--to=raman@google.com \
--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).