From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Chong Yidong" <cyd@stupidchicken.com>,
"Stephen Berman" <stephen.berman@gmx.net>,
6493@debbugs.gnu.org, "Johan Bockgård" <bojohan@gnu.org>,
"Deniz Dogan" <deniz.a.m.dogan@gmail.com>
Subject: bug#6493:
Date: Mon, 2 Aug 2010 05:30:31 +0200 [thread overview]
Message-ID: <AANLkTim1ELvbfdyotyRAzDiJuNdpOCCXT5w_KcWQL8zg@mail.gmail.com> (raw)
In-Reply-To: <C4823D9D6C674A348CBD0AEFCC27C4A2@us.oracle.com>
2010/8/1 Drew Adams <drew.adams@oracle.com>:
> That does not follow _logically_ - we could return the other value (point is
> numeric) or some special value to indicate this condition, but raising an error
> seems like common sense and what users would expect.
That's highly subjective IMHO.
Do you oppose to the following (minimal) version?
Juanma
=== modified file 'src/editfns.c'
--- src/editfns.c 2010-07-29 15:50:04 +0000
+++ src/editfns.c 2010-08-02 03:27:32 +0000
@@ -337,5 +337,6 @@
DEFUN ("region-beginning", Fregion_beginning, Sregion_beginning, 0, 0, 0,
- doc: /* Return position of beginning of region, as an integer. */)
+ doc: /* Return the integer value of point or mark, whichever is smaller.
+Signal an error if the region is not active. */)
(void)
{
@@ -344,5 +345,6 @@
DEFUN ("region-end", Fregion_end, Sregion_end, 0, 0, 0,
- doc: /* Return position of end of region, as an integer. */)
+ doc: /* Return the integer value of point or mark, whichever is larger.
+Signal an error if the region is not active. */)
(void)
{
next prev parent reply other threads:[~2010-08-02 3:30 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 ` bug#6493: Deniz Dogan
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 ` Juanma Barranquero [this message]
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
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=AANLkTim1ELvbfdyotyRAzDiJuNdpOCCXT5w_KcWQL8zg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=6493@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=drew.adams@oracle.com \
--cc=stephen.berman@gmx.net \
/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).