all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: default-text-properties
Date: Wed, 19 May 2004 22:12:27 -0500 (CDT)	[thread overview]
Message-ID: <200405200312.i4K3CRc18707@raven.dms.auburn.edu> (raw)
In-Reply-To: <200405200301.i4K31BR18694@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 19 May 2004 22:01:11 -0500 (CDT))

Maybe yet another problem with default-text-properties, illustrated
with the following ielm run:

*** Welcome to IELM ***  Type (describe-mode) for help.
ELISP> (set-buffer "*scratch*")
#<buffer *scratch*>
ELISP> (setq default-text-properties '(foo 69))
(foo 69)

ELISP> (setq char-property-alias-alist '((foo bar)))
((foo bar))

ELISP> (get-text-property (point-max) 'foo)
69
ELISP> 

This contradicts the last line of get-text-property's docstring:

    get-text-property is a built-in function in `C source code'.
    (get-text-property position prop &optional object)

    Return the value of position's property prop, in object.
    object is optional and defaults to the current buffer.
    If position is at the end of object, the value is nil.

I suspect again that this is a bug.  If it is intentional, the
documentation should be fixed.  I could take care of both bugs(?) I
reported, but I first want to make completely sure that they are
really bugs and not, for some strange reason, intentional.

Sincerely,

Luc.

  reply	other threads:[~2004-05-20  3:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20  1:33 default-text-properties Luc Teirlinck
2004-05-20  3:01 ` default-text-properties Luc Teirlinck
2004-05-20  3:12   ` Luc Teirlinck [this message]
2004-05-20  3:20     ` default-text-properties Luc Teirlinck
2004-05-20 13:17     ` default-text-properties Richard Stallman
2004-05-20 13:17   ` default-text-properties Richard Stallman
2004-05-20 17:40     ` default-text-properties Luc Teirlinck

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=200405200312.i4K3CRc18707@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@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.