unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: text_property_stickiness
Date: Tue, 27 Jun 2006 11:03:24 +0900	[thread overview]
Message-ID: <buoac7ztkwj.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <87d5cvx0vd.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 26 Jun 2006 13:50:14 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:
>> 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)

I just checked the code and since `get_pos_property' is only called with
the initial position being passed by the original caller, I think you're
right, it does make sense to signal an error if it's out of range.

-Miles
-- 
`Suppose Korea goes to the World Cup final against Japan and wins,' Moon said.
`All the past could be forgiven.'   [NYT]

  reply	other threads:[~2006-06-27  2:03 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       ` text_property_stickiness Chong Yidong
2006-06-27  2:03         ` Miles Bader [this message]
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

  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=buoac7ztkwj.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 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).