all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: yzhh <yezonghui@gmail.com>
To: emacs-devel@gnu.org
Subject: RE: recording-elisp.el - try recording commands as elisp code
Date: Mon, 05 Nov 2007 13:40:46 +0800	[thread overview]
Message-ID: <fgmacu$ajq$1@ger.gmane.org> (raw)
In-Reply-To: BNELLINCGFJLDJIKDGACCEHLCEAA.drew.adams@oracle.com

Drew Adams wrote:

> IOW, consider promoting some of the design discussion you are having now
> to interactive user choices. Just a suggestion to keep in mind. I have no
> idea how feasible this is.

I agree with you on offering choices to users, both custom options and
recording time interactions. So we are supposed to discuss what choices to
offer.

Allow me repeat them here (to make it clearer):
1. three choices for recording one isearch session:
    a. Record the last isearch item as a constant string search
    b. Record all successful isearch item as constant string searches
    c. Record all interactions, (especially) including yanking into the
search string.
2. two choices for recording minibuffer interactions:
    a. Totally ignore them, recording only the final command (this is for
M-x interactions, I haven't thought clearly about others)
    b. Record all interactions so that we replay everything including
yanking into the minibuffer.
3. two choices for recording case-fold-search value:
    a. Totally ignore.
    b. Record (and replay) case-fold value in-use at start of recording, and
every toggle-case-fold command during that.

Please note that I have also expressed the "maybe" infeasibility of choices
1.c and 2.b (given currently available commands). I would deeply appreciate
if anyone suggest solutions.

-- 
   regards,
yzhh

  reply	other threads:[~2007-11-05  5:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 21:27 recording-elisp.el - try recording commands as elisp code yzhh
2007-11-01 23:01 ` Juri Linkov
2007-11-02  5:39   ` yzhh
2007-11-02 20:46     ` Juri Linkov
2007-11-03  3:35       ` yzhh
2007-11-03 10:21         ` Reiner Steib
2007-11-04  5:02           ` yzhh
2007-11-02  2:06 ` Richard Stallman
2007-11-02  5:44   ` yzhh
2007-11-03  3:58     ` Richard Stallman
2007-11-03  7:14       ` yzhh
2007-11-02  6:14 ` yzhh
2007-11-02 20:45   ` Juri Linkov
2007-11-03  3:57     ` yzhh
2007-11-03 20:48       ` Richard Stallman
2007-11-04  8:51         ` yzhh
2007-11-04 16:48           ` Drew Adams
2007-11-05  5:40             ` yzhh [this message]
2007-11-06  2:16               ` Richard Stallman
2007-11-06  6:29                 ` yzhh
2007-11-07  0:15                   ` Richard Stallman
2007-11-06 16:33                 ` Mathias Dahl
2007-11-06 22:28                   ` Juri Linkov
2007-11-07  7:55                   ` Richard Stallman
2007-11-05  6:20           ` Richard Stallman
2007-11-05 14:27             ` yzhh
2007-11-05 14:43               ` Stefan Monnier
2007-11-05 15:03                 ` yzhh
2007-11-06  2:16                 ` Richard Stallman
2007-11-06  8:28                   ` Stefan Monnier
2007-11-05  6:20           ` Richard Stallman
2007-11-06  0:45           ` Juri Linkov
2007-11-06  6:12             ` yzhh
2007-11-07  0:15               ` Richard Stallman
2007-11-06  8:37             ` Richard Stallman
2007-11-06 22:28               ` Juri Linkov
2007-11-07  7:56                 ` Richard Stallman
2007-11-02 21:28   ` Stefan Monnier
2007-11-03  4:23     ` yzhh
2007-11-03  3:58   ` Richard Stallman
2007-11-03  7:12     ` yzhh

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='fgmacu$ajq$1@ger.gmane.org' \
    --to=yezonghui@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.