From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33179@debbugs.gnu.org
Subject: bug#33179: 26; Doc string of `filter-buffer-substring'
Date: Sat, 27 Oct 2018 22:38:32 +0300 [thread overview]
Message-ID: <83d0rvmb7r.fsf@gnu.org> (raw)
In-Reply-To: <87h8h7jicd.fsf@gmail.com> (message from Noam Postavsky on Sat, 27 Oct 2018 15:32:50 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 33179@debbugs.gnu.org
> Date: Sat, 27 Oct 2018 15:32:50 -0400
>
> For what it's worth, I read it like Drew does. I also think giving
> "characters" as an example doesn't make much sense, because I can't
> really think of characters so "special to a buffer" that they "should
> not be copied into other buffers". Grepping the Emacs source, the only
> example usage I found was in org-indent.el, which uses it to exclude
> text properties, so I propose changing the docstring example
> accordingly.
>
> >From c0cbc1cb7d5bbb0942a76781c1ed29d1346e5644 Mon Sep 17 00:00:00 2001
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Sat, 27 Oct 2018 15:27:45 -0400
> Subject: [PATCH v1] * lisp/simple.el (filter-buffer-substring): Clarify doc
> (Bug#33179).
This patch is fine with me, thanks.
next prev parent reply other threads:[~2018-10-27 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<08b6c241-7972-48e3-b354-95b6cb50fe52@default>
[not found] ` <<83in1nmdae.fsf@gnu.org>
2018-10-27 19:10 ` bug#33179: 26; Doc string of `filter-buffer-substring' Drew Adams
2018-10-27 19:25 ` Eli Zaretskii
2018-10-27 19:32 ` Noam Postavsky
2018-10-27 19:38 ` Eli Zaretskii [this message]
2018-10-27 17:24 Drew Adams
2018-10-27 18:53 ` Eli Zaretskii
[not found] ` <<8c1ed257-be78-4355-84a1-572cfa1d3af6@default>
[not found] ` <<87h8h7jicd.fsf@gmail.com>
[not found] ` <<83d0rvmb7r.fsf@gnu.org>
2018-10-27 21:35 ` Drew Adams
2018-10-27 21:59 ` Noam Postavsky
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=83d0rvmb7r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33179@debbugs.gnu.org \
--cc=npostavs@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).