From: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: text_property_stickiness
Date: Mon, 26 Jun 2006 13:50:14 -0400 [thread overview]
Message-ID: <87d5cvx0vd.fsf@stupidchicken.com> (raw)
In-Reply-To: <buo1wtcv8m8.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Mon, 26 Jun 2006 13:33:35 +0900")
Miles Bader <miles.bader@necel.com> writes:
> Chong Yidong <cyd@stupidchicken.com> writes:
>> So the only thing we have to worry about are a bunch of lisp-visible
>> functions, Fdelete_field and so forth. I think it is acceptable for
>> us to handle this situation by the signalling of an args_out_of_range
>> error, which, as you pointed out, already happens with the call to
>> Fget_text_property in text_property_stickiness.
>
> Why do you think an error is the correct thing here?
>
> My feeling (when Richard brought this up earlier) was that perhaps the
> out-of-range value should be constrained to be within BEGV-ZV.
I don't think it's the wrong thing to do. It's also similar to the
current behavior for other Lisp-visible functions, for example:
C-u 10 a
M-: (narrow-to-region 3 4)
M-: (text-properties-at 1)
This signals an args-out-of-range error.
next prev parent reply other threads:[~2006-06-26 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 20:27 text_property_stickiness Chong Yidong
2006-06-25 15:33 ` text_property_stickiness Richard Stallman
2006-06-25 20:59 ` text_property_stickiness Chong Yidong
2006-06-26 4:33 ` text_property_stickiness Miles Bader
2006-06-26 17:50 ` Chong Yidong [this message]
2006-06-27 2:03 ` text_property_stickiness Miles Bader
2006-06-27 16:16 ` text_property_stickiness Richard Stallman
2006-06-28 0:04 ` text_property_stickiness Chong Yidong
2006-06-29 12:59 ` text_property_stickiness Richard Stallman
2006-06-27 10:34 ` text_property_stickiness Richard Stallman
2006-06-26 11:33 ` text_property_stickiness Richard Stallman
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=87d5cvx0vd.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.