unofficial mirror of emacs-devel@gnu.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 23:43:43 +0300	[thread overview]
Message-ID: <83d35o11fk.fsf@gnu.org> (raw)
In-Reply-To: <AAE7775371CE4A2C9FD967B7D803BCBF@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <monnier@iro.umontreal.ca>, <emacs-devel@gnu.org>
> Date: Mon, 28 May 2012 11:26:35 -0700
> 
> > And the names of the values are similarly non-specific.
> 
> The names do not stand alone without their descriptions.

I'm saying that the names don't help to understand the descriptions,
that's all.  If the descriptions were clear, I would care much less
for the names.  As things are, I'm grasping at every straw in sight.

>  Even so, I think that `yank' and `kill' are pretty clear even
> without reading their descriptions.

Not to me.  "For commands that do a yank" is not a description, it's
tautology at best.  "Ensures that the region about to be deleted is
not yanked"? why would it be yanked otherwise? and why the value is
'yank' if it "ensures the region will NOT be yanked"?  That just
doesn't make any sense!

'kill'? let's see... "`kill-region' is used on the selection, rather
than `delete-region'".  So? why would that matter, and when would I
want the former rather than the latter?  And what is "Text selected
with the mouse is typically yankable anyway" about? why "anyway"?

Etc., etc.  These are riddles, or maybe notes for someone who once
knew everything about this but forgot.  This is not documentation
suitable for first-time reading.  It leaves too much to previous
knowledge.

> I'm not saying the existing descriptions should not be changed.  I'm asking you
> what changes you have in mind.

How can I explain what I don't understand?  I _really_ have no clear
idea about what each value does, can you believe that?  If I'd study
the code long enough, I'd eventually understand, but I didn't.

> > What is needed is a clear description what each value does,
> 
> For instance?  What is missing, in your opinion?

I don't know.  How about if you try explaining each value in full,
from scratch?  Assume that only primitives like kill-region,
delete-region, 'yank', etc. are known, all the rest is not.  Explain
the effect of each value, both on the text that was selected and on
any other text that's involved.  Give at least one example for a use
case where each value will be useful.  That kind of stuff.



  reply	other threads:[~2012-05-28 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F9DC154.2000605@groveronline.com>
     [not found] ` <87ipgggtmw.fsf@mail.jurta.org>
     [not found]   ` <jwvbom8837m.fsf-monnier+emacs@gnu.org>
     [not found]     ` <878vhcc4nl.fsf@mail.jurta.org>
     [not found]       ` <87vcjxdt5p.fsf@mail.jurta.org>
     [not found]         ` <jwvlikszweb.fsf-monnier+emacs@gnu.org>
     [not found]           ` <87vcjvwtxa.fsf@mail.jurta.org>
     [not found]             ` <87r4ufhfmi.fsf@mail.jurta.org>
     [not found]               ` <jwvsjeuxqrs.fsf-monnier+emacs@gnu.org>
     [not found]                 ` <878vge3ri7.fsf@mail.jurta.org>
     [not found]                   ` <jwvbol9ue9d.fsf-monnier+emacs@gnu.org>
     [not found]                     ` <83pq9o1f9s.fsf@gnu.org>
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
2012-05-28 18:26                           ` Drew Adams
2012-05-28 20:43                             ` Eli Zaretskii [this message]
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

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=83d35o11fk.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 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).