From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
"'Johan Bockgård' " <bojohan@gnu.org>
Cc: 'Chong Yidong' <cyd@stupidchicken.com>,
'Stephen Berman' <stephen.berman@gmx.net>,
6493@debbugs.gnu.org, 'Deniz Dogan' <deniz.a.m.dogan@gmail.com>
Subject: bug#6493:
Date: Sun, 1 Aug 2010 14:17:35 -0700 [thread overview]
Message-ID: <C4823D9D6C674A348CBD0AEFCC27C4A2@us.oracle.com> (raw)
In-Reply-To: <AANLkTik0iJTWYmchbHEYfZimcTmYn4yFiKBqCzUETOSg@mail.gmail.com>
> > Something that should be mentioned in the doc strings is
> > the following:
> >
> > The next two functions signal an error if the mark does not point
> > anywhere. If Transient Mark mode is enabled and
> > `mark-even-if-inactive' is `nil', they also signal an
> > error if the mark is inactive.
Why should that be mentioned?
What important problem or use case would we be pointing out?
> Can we simplify that to just say that they signal an error if the
> region is not active? (The region-* commands are somewhat specific, so
> it's reasonable to suppose that the programmer knows what he's doing
> or can lookup the docs.)
I have no real objection to a clear statement of the error handling.
In general it is a good idea to mention important error cases.
But I do not think it is necessary to mention error handling at all for these
doc strings. In this case, saying more is saying less, and likely to just add
confusion.
It's pretty obvious that a numerical comparison needs to be done to determine
the smaller/larger of point and mark, and it's similarly obvious that if the
numerical value of one of them (mark) cannot be determined then an error would
be raised.
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. I see no reason to add
info about the error handling.
next prev parent reply other threads:[~2010-08-01 21:17 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 ` Drew Adams [this message]
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=C4823D9D6C674A348CBD0AEFCC27C4A2@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6493@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=lekktu@gmail.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 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.