From: Thien-Thi Nguyen <ttn@gnu.org>
To: Shane Celis <shane.celis@gmail.com>
Cc: Guile Mailing List <guile-user@gnu.org>
Subject: Re: Emacsy: Context Sensitive Commands Design Question
Date: Fri, 30 Aug 2013 09:32:24 +0200 [thread overview]
Message-ID: <87vc2nr5vb.fsf@zigzag.favinet> (raw)
In-Reply-To: <D49B4F36-FD32-45FD-9C56-9F699F70B511@gmail.com> (Shane Celis's message of "Thu, 29 Aug 2013 16:57:00 -0400")
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
() Shane Celis <shane.celis@gmail.com>
() Thu, 29 Aug 2013 16:57:00 -0400
6. Tag commands as special procedures [...] Implement "command?"
CON: Adding something to the procedure makes wrapping commands in
other lambdas awkward. Might necessitate a define-command,
lambda-command, method-command, which I'd prefer to avoid.
Why would you prefer to avoid this?
What would you do?
I'd explore option 6, starting w/:
(define command? (make-object-property))
I think object properties are better suited than procedure properties
after observing this in the (Emacs) *scratch* buffer:
(commandp [42])
t
It would be cool for Emacsy to have good "keyboard macros" support.
Many a non-programmer fall into consciousness via such, in Emacs.
[cc trimmed]
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2013-08-30 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 20:57 Emacsy: Context Sensitive Commands Design Question Shane Celis
2013-08-30 0:26 ` Noah Lavine
2013-08-30 2:02 ` Mark H Weaver
2013-08-30 11:32 ` Ludovic Courtès
2013-08-30 7:32 ` Thien-Thi Nguyen [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc2nr5vb.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=guile-user@gnu.org \
--cc=shane.celis@gmail.com \
/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.
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).