From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: :format strings in Custom ending in %h
Date: Tue, 21 Oct 2003 14:03:23 +0200 [thread overview]
Message-ID: <rju162ol10.fsf@sheridan.dina.kvl.dk> (raw)
In-Reply-To: 200310201805.h9KI5Pm09318@raven.dms.auburn.edu
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Did you change your mind about the next to last paragraph?
No, I'm just waiting for a go-ahead.
RMS: Should I apply the patch?
And should I try to make the follow-up changes to obsolete
widget-children-value-delete and document the new behavior?
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> I am about ready to submit a file for inclusion in Emacs. It contains
> a complex defcustom which does not function properly without the
> following patch. I have applied this patch to my own Emacs CVS and
> have used it ever since the end of August without problems. The patch
> is needed to fix an annoying problem in Custom which we discussed at
> the end of August. I had the impression that you were going to commit
> something along these lines:
>
> 2003-08-24 Per Abrahamsen <abraham@dina.kvl.dk>
>
> * wid-edit.el (widget-default-delete): Always delete child
> widgets.
>
> *** wid-edit.el.~1.120.~ Thu Aug 21 14:17:37 2003
> --- wid-edit.el Sun Aug 24 17:37:04 2003
> ***************
> *** 1465,1470 ****
> --- 1465,1471 ----
> (inhibit-modification-hooks t)
> (inhibit-read-only t))
> (widget-apply widget :value-delete)
> + (widget-children-value-delete widget)
> (when inactive-overlay
> (delete-overlay inactive-overlay))
> (when button-overlay
>
> Old follow-up message (from Per Abrahamsen):
>
> Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>
> > I guess that after applying this patch
> > `widget-children-value-delete'
> > will become a pretty redundant value for :value-delete, essentially
> > equivalent with `ignore'.
>
> Yes, if we apply this patch we probably also should change all these
> values, mark widget-children-value-delete as obsolete (and inline the
> code in widget-default-delete), and document this property of :buttons
> and :children somewhere.
>
> But I don't know if there is some code that depend on :buttons and
> :children *not* being deleted recursively. Maybe applying the patch
> will be the easiest way to find out.
>
> Oh, and we probably should find other places where :buttons and
> :children are deleted (now) reduntantly, and adjust those.
>
> Did you change your mind about the next to last paragraph?
>
>>From diffing with the current CVS, I noticed that the actual complete
> patch I have been using since August (and hence has been tested for a
> while) is the diff below. I believe your patch above (included in the
> one below) makes the second (earlier) change redundant however. I
> just forgot to remove it after applying your patch above.
>
> d ~/
> diff -c /home/teirllm/emacscvsdir/emacs/lisp/wid-edit.el ;; (current CVS)
> /home/teirllm/wid-edit.el ;; personal, used since end August.
> *** /home/teirllm/emacscvsdir/emacs/lisp/wid-edit.el Mon Oct 20
> 11:00:20 2003
> --- /home/teirllm/wid-edit.el Tue Sep 2 07:38:18 2003
> ***************
> *** 1465,1470 ****
> --- 1465,1471 ----
> (inhibit-modification-hooks t)
> (inhibit-read-only t))
> (widget-apply widget :value-delete)
> + (widget-children-value-delete widget)
> (when inactive-overlay
> (delete-overlay inactive-overlay))
> (when button-overlay
> ***************
> *** 1556,1562 ****
> "Constant items for inclusion in other widgets."
> :convert-widget 'widget-value-convert-widget
> :value-create 'widget-item-value-create
> ! :value-delete 'ignore
> :value-get 'widget-value-value-get
> :match 'widget-item-match
> :match-inline 'widget-item-match-inline
> --- 1557,1563 ----
> "Constant items for inclusion in other widgets."
> :convert-widget 'widget-value-convert-widget
> :value-create 'widget-item-value-create
> ! :value-delete 'widget-children-value-delete
> :value-get 'widget-value-value-get
> :match 'widget-item-match
> :match-inline 'widget-item-match-inline
>
> Diff finished at Mon Oct 20 11:05:58
next prev parent reply other threads:[~2003-10-21 12:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 1:54 :format strings in Custom ending in %h Luc Teirlinck
2003-08-21 12:22 ` Per Abrahamsen
2003-08-21 20:50 ` Luc Teirlinck
2003-08-21 21:00 ` Luc Teirlinck
2003-08-22 11:22 ` Per Abrahamsen
2003-08-22 14:41 ` Luc Teirlinck
2003-08-24 15:38 ` Per Abrahamsen
2003-08-24 17:17 ` Luc Teirlinck
2003-08-24 18:30 ` Per Abrahamsen
2003-10-20 18:05 ` Luc Teirlinck
2003-10-20 21:10 ` Luc Teirlinck
2003-10-22 9:24 ` Richard Stallman
2003-10-22 9:41 ` Per Abrahamsen
2003-10-23 18:37 ` Richard Stallman
2003-10-24 16:00 ` Per Abrahamsen
2003-10-25 22:26 ` Richard Stallman
2003-10-21 12:03 ` Per Abrahamsen [this message]
2003-08-23 2:44 ` Luc Teirlinck
2003-08-23 15:32 ` Luc Teirlinck
2003-08-23 3:25 ` Luc Teirlinck
2003-08-23 18:09 ` Luc Teirlinck
2003-08-23 18:32 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 1:42 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
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=rju162ol10.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).