all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: problem with text properties whose names aren't symbols
Date: Mon, 12 Dec 2005 12:04:12 +0100	[thread overview]
Message-ID: <jehd9e8tlf.fsf@sykes.suse.de> (raw)
In-Reply-To: <20051212024921.DBF2881A3@planetmath.cc.vt.edu> (Joe Corneli's message of "Sun, 11 Dec 2005 21:49:21 -0500 (EST)")

Joe Corneli <jcorneli@planetmath.org> writes:

>>From the elisp manual (node: Text Properties):
>
>    Each property has a name and a value.  Both of these
>    can be any Lisp object, but the name is normally a symbol.
>
> Well, it seems that when the Lisp object is not a symbol,
> there is a problem.  This is illustrated by evaluating
> the following form interactively:
>
> (progn
>   (put-text-property (point) (1+ (point)) 
>                      '(example name)
>                       t)
>   (put-text-property (point) (1+ (point)) 
>                      '(example name)
>                       nil)
>   (text-properties-at (point)))

This is not a bug, because '(example name) and '(example name) are
distinct objects:

ELISP> (eq '(example name) '(example name))
nil

Try this instead:

(let ((name '(example name)))
  (put-text-property (point) (1+ (point)) name t)
  (put-text-property (point) (1+ (point)) name nil)
  (text-properties-at (point)))

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2005-12-12 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12  2:49 problem with text properties whose names aren't symbols Joe Corneli
2005-12-12 11:04 ` Andreas Schwab [this message]
2005-12-12 16:48   ` Joe Corneli

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=jehd9e8tlf.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=bug-gnu-emacs@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.