From: Eli Zaretskii <eliz@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r113909: Refine the documentation of `insert-buffer-substring'.
Date: Sun, 18 Aug 2013 22:30:22 +0300 [thread overview]
Message-ID: <83k3jilru9.fsf@gnu.org> (raw)
In-Reply-To: <CAAF+z6HDmSniyLvsduGhpKrCGVVmZkWERCQi4ocD000FOCW8OQ@mail.gmail.com>
> Date: Sun, 18 Aug 2013 06:27:25 +0800
> From: Xue Fuqiao <xfq.free@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel <emacs-devel@gnu.org>
>
> This rule applies to all functions that use the region. More generally,
> it applies all functions that use BEG and END if they are buffer positions.
>
> Since there are too many functions, IMO a better approach is remove them
> ("inclusive" and "exclusive") from their own documentation and add a
> blurb like Stefan said in a node like (info "(elisp) The Region").
Like I said, I don't see anything wrong with "inclusive" and
"exclusive". But if you want a good place to add such a blurb, do
that in the preamble in the node "Text", which already tries to say
something along these lines. By contrast, "The Region" is only about
the region between mark and point, which is not entirely relevant to
the functions that accept BEG and END as arguments, because these
arguments don't have to come from the region limits.
Btw, this rule applies to string positions as well, I think.
prev parent reply other threads:[~2013-08-18 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VAAWJ-0007pJ-65@vcs.savannah.gnu.org>
2013-08-16 3:53 ` [Emacs-diffs] trunk r113909: Refine the documentation of `insert-buffer-substring' Stefan Monnier
2013-08-16 6:19 ` Eli Zaretskii
2013-08-16 16:20 ` Stefan Monnier
2013-08-16 18:43 ` Eli Zaretskii
2013-08-17 22:27 ` Xue Fuqiao
2013-08-18 19:30 ` Eli Zaretskii [this message]
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=83k3jilru9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=xfq.free@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).