From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 6493@debbugs.gnu.org
Subject: bug#6493:
Date: Sun, 27 Jun 2010 16:29:13 +0200 [thread overview]
Message-ID: <AANLkTikKS9sm628o4hrkeSk74iCXSPq0Q0yrAl8fj3ME@mail.gmail.com> (raw)
In-Reply-To: <6B20ABD762564DE2AEBA810B54EB46FD@us.oracle.com>
2010/6/27 Drew Adams <drew.adams@oracle.com>:
>> > "Returns point or mark, whichever is larger."
>>
>> How about this (for region-end):
>>
>> "Returns point or mark, whichever is larger.
>> The returned value is the position of the end of the region
>> as an integer."
>
> The end of the region is always a position, so no need to speak of the position
> of the end of the region.
>
> We don't really need to say that a number is returned, as opposed to a marker.
> "Point" is a position, which is a number (natnump). "Mark" is more ambiguous -
> it is sometimes referred to as a marker and sometimes as the position of that
> marker. So it's probably good to mention that a number is returned, even if not
> really necessary. (We also need not specify what kind of number, since it is a
> position, but that doesn't hurt either.)
>
> "Returns the larger of point or mark, as a nonnegative integer."
>
> We can add that the function "raises an error if the mark is not set".
>
>
I'm all for your suggestion. So now we have:
"Returns the larger of point or mark, as a nonnegative integer.
Raises an error if the mark is not set."
Agreed?
--
Deniz Dogan
next prev parent reply other threads:[~2010-06-27 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 16:13 bug#6493: 24.0.50; doc strings of region-beginning, region-end Drew Adams
2010-06-27 12:26 ` bug#6493: Deniz Dogan
2010-06-27 13:52 ` bug#6493: Drew Adams
2010-06-27 14:02 ` bug#6493: Deniz Dogan
2010-06-27 14:18 ` bug#6493: Drew Adams
2010-06-27 14:29 ` Deniz Dogan [this message]
2010-06-27 14:33 ` bug#6493: Drew Adams
2010-07-10 23:41 ` bug#6493: Deniz Dogan
2010-07-11 4:20 ` bug#6493: Drew Adams
2010-07-23 0:12 ` bug#6493: Juanma Barranquero
2010-07-23 9:10 ` bug#6493: Deniz Dogan
2010-07-23 9:30 ` bug#6493: Juanma Barranquero
2010-07-23 15:45 ` bug#6493: Chong Yidong
2010-07-23 16:16 ` bug#6493: Drew Adams
2010-07-23 17:02 ` bug#6493: Stephen Berman
2010-07-23 17:26 ` bug#6493: Drew Adams
2010-07-23 17:32 ` bug#6493: Juanma Barranquero
2010-07-29 11:44 ` bug#6493: Juanma Barranquero
2010-07-29 15:16 ` bug#6493: Johan Bockgård
2010-08-01 19:01 ` bug#6493: Juanma Barranquero
2010-08-01 21:17 ` bug#6493: Drew Adams
2010-08-02 3:30 ` bug#6493: Juanma Barranquero
2010-08-02 5:09 ` bug#6493: Drew Adams
2010-08-02 5:34 ` bug#6493: Drew Adams
2010-08-02 6:43 ` bug#6493: Juanma Barranquero
2010-07-29 15:58 ` bug#6493: Chong Yidong
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=AANLkTikKS9sm628o4hrkeSk74iCXSPq0Q0yrAl8fj3ME@mail.gmail.com \
--to=deniz.a.m.dogan@gmail.com \
--cc=6493@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.