From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: A widget-based version of find-cmd
Date: Mon, 3 Jun 2019 13:41:33 -0700 (PDT) [thread overview]
Message-ID: <aa8312ee-8707-44f4-a32c-fac7abef35df@default> (raw)
In-Reply-To: <jwvv9xmpkk0.fsf-monnier+emacs@gnu.org>
> Yes, of course. Another direction (complementary rather than opposed to
> what you're suggesting) would be to extend Elisp's completion so it
> understands `find-cmd` and hence gives you the valid completion after
> you type `(find-cmd '(pru TAB`
Yes, both would be useful additions. Completion is
handy and quick. On the other hand, it would be
good to be able to fill out a "dialog box" (widgets)
once, and have the same filled-out settings available
for subsequent reuse (until you change some of those
settings).
You can perhaps get somewhat the same advantage from
completion by using `M-p' to retrieve the last input
for each completion type (assuming they are on separate
minibuffer histories), but that's not quite as handy.
One of the advantages of a dialog box in such contexts
is setting it and reusing it for multiple search actions
(interspersed with other, non-search actions). In fact,
that's about the only advantage I find for such a dialog
box.
In sum, when there are possibly a bunch of settings you
might fill out, Emacs should save them and offer them
to you again. You should not need to fill out the same
choices multiple times consecutively.
> I'm sending you all my psychic power. I hope it helps.
Ditto, FWIW.
> > What I basically need is to define a
> > widget type that let's you choose from a list of options. Among them
> > are combiners like "or" that, when chosen, should provide a widget of
> > the same type. My problem is that I run into an infinite recursion. I
> > thought I can avoid that by constructing the widget deferred via
> > :convert-widget but that doesn't help. Maybe :convert-widget is not for
> > that purpose (actually, then I don't get the purpose of :convert-widget
> > from the widget manual).
>
> I think you're looking for the `lazy` widget.
Or maybe just split it up, having part of it use `repeat'?
Thanks for working on this, Michael.
next prev parent reply other threads:[~2019-06-03 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 2:15 A widget-based version of find-cmd Michael Heerdegen
2019-06-03 19:07 ` Stefan Monnier
2019-06-03 20:41 ` Drew Adams [this message]
2019-06-03 22:53 ` Michael Heerdegen
2019-06-03 23:28 ` Drew Adams
2019-06-13 23:35 ` Michael Heerdegen
2019-09-05 15:04 ` Michael Heerdegen
2019-09-05 17:10 ` Drew Adams
2019-09-05 21:26 ` Michael Heerdegen
2019-09-06 12:39 ` local binding ineffective inside widget Stefan Monnier
2019-09-06 14:10 ` Michael Heerdegen
2019-09-24 9:28 ` Michael Heerdegen
2019-06-03 22:40 ` A widget-based version of find-cmd Michael Heerdegen
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=aa8312ee-8707-44f4-a32c-fac7abef35df@default \
--to=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).