all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: use and doc of function symbol properties [was: bug#11381: 23.3; isearch-search-and-update issue?]
Date: Mon, 28 May 2012 20:53:16 +0300	[thread overview]
Message-ID: <83ehq419bn.fsf@gnu.org> (raw)
In-Reply-To: <09237F12532B42C381CDBC71FA09EA08@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <11381@debbugs.gnu.org>, <emacs-devel@gnu.org>
> Date: Mon, 28 May 2012 10:34:34 -0700
> 
> The question you (Eli) raise is not specific to isearch or to
> delsel.

It was relevant to proliferation of the technique discussed there.

> But the use of symbol properties, including for function symbols, is nothing
> special.  It is similar to using attributes or methods with objects in OOP.
> What's sometimes missing perhaps is better documentation/discoverability.

That's what I was trying to say.  "Discoverability" means that someone
who calls a function from Org mode (say) that invokes some magic via
delsel should be able to understand how that magic happened.  I don't
see how this can be done today without a lot of digging.  If you are
hard-pressed for time, this could be a maintenance nightmare.

> Can you be more specific about what is missing from the Commentary in delsel.el?

It basically doesn't explain anything apart of the fact that the
property can have several values.  The exact effect of each value is
left unclear to the degree of obfuscation.  And the names of the
values are similarly non-specific.

What is needed is a clear description what each value does, and it
should be part of the doc string.  Right now, this info is only
available by reading the code.



  reply	other threads:[~2012-05-28 17:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-29 22:31 bug#11381: 23.3; isearch-search-and-update issue? Andy Grover
2012-04-30  0:27 ` Juri Linkov
2012-05-01  9:03 ` Juri Linkov
2012-05-01 13:08   ` Stefan Monnier
2012-05-01 15:17     ` Juri Linkov
2012-05-15 21:35       ` Juri Linkov
2012-05-16  2:35         ` Stefan Monnier
2012-05-17  0:08           ` Juri Linkov
2012-05-20  0:15             ` Juri Linkov
2012-05-21  1:36               ` Stefan Monnier
2012-05-21  2:23                 ` Stefan Monnier
2012-05-27  9:43                   ` Juri Linkov
2012-05-28  4:48                     ` Stefan Monnier
2012-05-28  8:55                       ` Juri Linkov
2012-05-28 14:08                         ` Stefan Monnier
2012-05-29  9:49                           ` Juri Linkov
2012-05-29 13:34                             ` Stefan Monnier
2012-05-27  9:35                 ` Juri Linkov
2012-05-28  4:23                   ` Stefan Monnier
2012-05-28 15:44                     ` Eli Zaretskii
2012-05-28 17:34                       ` use and doc of function symbol properties [was: bug#11381: 23.3; isearch-search-and-update issue?] Drew Adams
2012-05-28 17:53                         ` Eli Zaretskii [this message]
2012-05-28 18:26                           ` Drew Adams
2012-05-28 20:43                             ` Eli Zaretskii
2012-05-30  0:10                               ` Drew Adams
2012-06-02 16:47                                 ` Eli Zaretskii
2012-06-02 16:57                                   ` Drew Adams
2012-06-02 17:52                                     ` Drew Adams
2012-05-28 17:34                       ` bug#11381: " Drew Adams
2012-05-28 19:34                       ` bug#11381: 23.3; isearch-search-and-update issue? Stefan Monnier
2012-05-29  0:27                         ` Juri Linkov
2012-05-29  1:26                           ` Stefan Monnier

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=83ehq419bn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.