From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Nicolas Petton <nicolas@petton.fr>, 58904@debbugs.gnu.org
Subject: bug#58904: [PATCH] Handle buffer streams that operate on lines, pages, etc.
Date: Thu, 7 Sep 2023 13:36:17 -0700 [thread overview]
Message-ID: <CADwFkmk6YR1PuHbc7+t7Os9oJ999OEfQzdV_xxrJjYE4rxFyew@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmmp+uscGU13JO_2C=nhdg4N2cVbLLqoiVn=KgqUM8urg@mail.gmail.com> (Stefan Kangas's message of "Thu, 24 Nov 2022 11:40:02 -0800")
Philip,
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> The commentary for stream.el mentions that the following streams are
>> supported:
(That's the `stream' package on GNU ELPA, to be clear.)
>>> ;; - buffers (by character)
>>> ;; - buffers (by line)
>>> ;; - buffers (by page)
>>
>> But I couldn't find anything beyond charachter-streams. The following
>> patch would implement that and more, by re-using thingatpt to define any
>> kind of stream one would want.
>
> Copying in Nicolas Petton, in case he has any comments.
Nicolas didn't seem to have any comments, so please go ahead and install
this if you think it makes sense.
I guess you could also bump the version, if you think that makes sense.
>> -;; Copyright (C) 2016-2020 Free Software Foundation, Inc.
>> +;; Copyright (C) 2016-2020, 2022 Free Software Foundation, Inc.
It's okay to write it like this: 2016-2023
next prev parent reply other threads:[~2023-09-07 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 21:30 bug#58904: [PATCH] Handle buffer streams that operate on lines, pages, etc Philip Kaludercic
2022-11-24 19:40 ` Stefan Kangas
2023-09-07 20:36 ` Stefan Kangas [this message]
2023-09-08 7:46 ` Philip Kaludercic
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmk6YR1PuHbc7+t7Os9oJ999OEfQzdV_xxrJjYE4rxFyew@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=58904@debbugs.gnu.org \
--cc=nicolas@petton.fr \
--cc=philipk@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.