From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: set-text-properties, remove-set-properties, add-text-properties: 1) doc string 2) return value
Date: Wed, 28 Dec 2005 20:15:02 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICMENPDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87oe307fuq.fsf-monnier+emacs@gnu.org>
> 1. The set-text-properties doc string should say what the
> function returns.
Why?
I should have said, "Does the value of set-text-properties change, or is it
always the same? If it changes, then the value is significant and it should
be documented."
> 2. Wouldn't it be more useful for set-text-properties,
> remove-set-properties, and add-text-properties to return the modified
> OBJECT (or nil if no modification occurred)? In case OBJECT
> is a buffer (or nil), the modified buffer substring could be returned.
Why would that be useful?
Why is it useful for `push' and `pop' to return values that correspond to
the updated list and the removed car?
It would be convenient to say
(setq foo (or (remove-text-properties start end props toto) ...))
Of course, you can always write
(setq foo (if (remove-text-properties start end props toto)
toto
...))
As for `push' and `pop' and many other "functions", returning a richer value
offers only a slight convenience, but why not?
next prev parent reply other threads:[~2005-12-29 4:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 21:59 set-text-properties, remove-set-properties, add-text-properties: 1) doc string 2) return value Drew Adams
2005-12-29 3:18 ` Stefan Monnier
2005-12-29 4:15 ` Drew Adams [this message]
2005-12-30 2:18 ` Richard M. Stallman
2005-12-30 3:47 ` Luc Teirlinck
2005-12-30 3:57 ` Luc Teirlinck
2005-12-30 11:24 ` David Kastrup
2005-12-29 11:10 ` Kim F. Storm
2005-12-29 16:03 ` Drew Adams
2005-12-29 19:41 ` Kevin Rodgers
2005-12-30 0:57 ` Juri Linkov
2006-02-18 19:37 ` Drew Adams
2006-02-19 15:14 ` Stefan Monnier
2005-12-29 22:41 ` Kim F. Storm
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=DNEMKBNJBGPAOPIJOOICMENPDAAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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).