From: Drew Adams <drew.adams@oracle.com>
To: 33179@debbugs.gnu.org
Subject: bug#33179: 26; Doc string of `filter-buffer-substring'
Date: Sat, 27 Oct 2018 10:24:32 -0700 (PDT) [thread overview]
Message-ID: <08b6c241-7972-48e3-b354-95b6cb50fe52@default> (raw)
IIUC, the meaning of "extract" in this sentence is to exclude the chars
from the result. If so, please consider using "exclude" or "remove"
(preferably the former, as nothing is removed from the buffer) instead.
"Extract" can give the impression that those chars are extracted as the
result, rather than being excluded from the result.
"For example, major or minor modes can use
'filter-buffer-substring-function' to extract characters that are
^^^^^^^
special to a buffer, and should not be copied into other buffers."
Yes, if read carefully one can guess what was really meant here, because
of the "and should not..." part. Still, the text can be misleading as
it is now.
In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
of 2018-05-30
Repository revision: 07f8f9bc5a51f5aa94eb099f3e15fbe0c20ea1ea
Windowing system distributor `Microsoft Corp.', version 10.0.16299
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2018-10-27 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 17:24 Drew Adams [this message]
2018-10-27 18:53 ` bug#33179: 26; Doc string of `filter-buffer-substring' 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
[not found] <<08b6c241-7972-48e3-b354-95b6cb50fe52@default>
[not found] ` <<83in1nmdae.fsf@gnu.org>
2018-10-27 19:10 ` Drew Adams
2018-10-27 19:25 ` Eli Zaretskii
2018-10-27 19:32 ` Noam Postavsky
2018-10-27 19:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08b6c241-7972-48e3-b354-95b6cb50fe52@default \
--to=drew.adams@oracle.com \
--cc=33179@debbugs.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 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.