unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 33167@debbugs.gnu.org
Subject: bug#33167: 26; Doc string of `region-extract-function'
Date: Sat, 27 Oct 2018 12:30:31 -0700 (PDT)	[thread overview]
Message-ID: <d158d6af-25cc-443a-b0d8-52a0aaa061ac@default> (raw)
In-Reply-To: <<83h8h7mbxf.fsf@gnu.org>>

> > But if the spec of the variable imposes nothing on the BEG
> > and END values passed for filtering, then why does it impose
> > a requirement that `filter-buffer-substring' must be called?
> 
> So that applications could rely on that, and could provide their own
> filter functions, if they want.

I see.  That makes sense.  Thx.

Is it really the case that the value of `region-extract-function'
can pass any limits it wants to `filter-buffer-substring', even
limits that have no relation to the pieces of the noncontiguous
region?

So the only thing specified is that `filter-buffer-substring'
gets called once for each each piece?  I.e., all that's specified
is that if the nc region has N pieces then `filter-buffer-substring'
is called N times - nothing more?





       reply	other threads:[~2018-10-27 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<2e187b74-9999-4090-96b4-bb13d1f27544@default>
     [not found] ` <<<831s8bocu3.fsf@gnu.org>
     [not found]   ` <<db9097a6-7687-484c-9e32-1262e5825d92@default>
     [not found]     ` <<83o9bfmjte.fsf@gnu.org>
     [not found]       ` <<0a008152-d861-4b96-ad2a-b837bd412d98@default>
     [not found]         ` <<83h8h7mbxf.fsf@gnu.org>
2018-10-27 19:30           ` Drew Adams [this message]
2018-10-27 19:37             ` bug#33167: 26; Doc string of `region-extract-function' Eli Zaretskii
     [not found] <<2e187b74-9999-4090-96b4-bb13d1f27544@default>
     [not found] ` <<831s8bocu3.fsf@gnu.org>
2018-10-27 15:27   ` Drew Adams
2018-10-27 16:32     ` Eli Zaretskii
2018-10-27 19:02       ` Drew Adams
2018-10-27 19:23         ` Eli Zaretskii
2018-10-26 15:32 Drew Adams
2018-10-27 11:20 ` 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=d158d6af-25cc-443a-b0d8-52a0aaa061ac@default \
    --to=drew.adams@oracle.com \
    --cc=33167@debbugs.gnu.org \
    --cc=eliz@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).