unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: A widget-based version of find-cmd
Date: Tue, 04 Jun 2019 00:40:43 +0200	[thread overview]
Message-ID: <877ea2pa1g.fsf@web.de> (raw)
In-Reply-To: <jwvv9xmpkk0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 03 Jun 2019 15:07:41 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> I think I understand what you're after, but I'd like to clarify:
> find-cmd lets you build a command using an Elisp expression, so it's
> meant for use from Elisp code, rather than interactively.
> Whereas you seem to be considering an interactive use case, right?

Exactly.  The main overlap with find-cmd is the inherent knowledge about
"find".

I want that a user can compose the "find" call with widgets and hit C-c
C-c or so to execute it.

> 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`
> [ Of course, we don't want elisp-mode.el to know about find-cmd.el,
>   we'd instead want this to be modular; could be used for `rx` as well,
>   for example.  ]

Something like that would be good, yes.

> I'm sending you all my psychic power.  I hope it helps.

I think it does.

> I think you're looking for the `lazy` widget.

Bingo!  Thanks.

> The Widgets code was written pretty much specifically for Customs, so
> I'm not surprised if some parts are not cleanly separated.
> Please mark them with a FIXME or fix them when you bump into them ;-)

Ok, will do.


Thanks,

Michael.



      parent reply	other threads:[~2019-06-03 22:40 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
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   ` Michael Heerdegen [this message]

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=877ea2pa1g.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --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).