From: "Mathias Dahl" <mathias.dahl@gmail.com>
To: rms@gnu.org
Cc: yzhh <yezonghui@gmail.com>, emacs-devel@gnu.org
Subject: Re: recording-elisp.el - try recording commands as elisp code
Date: Tue, 6 Nov 2007 17:33:30 +0100 [thread overview]
Message-ID: <7dbe73ed0711060833p6a57778x2277035cb2966954@mail.gmail.com> (raw)
In-Reply-To: <E1IpDzO-0003jV-N0@fencepost.gnu.org>
> If you offer user choices, I think the only way to make that easy to use
> is to generate output in one way (the default), then let the user point at
> various places in the generated Lisp code and give commands that say
> "generate this function call using a different method".
Slightly off-topic, but this got me wondering if it would be useful
with a command similar to `checkdoc', something that would scan
through the code for various "mistakes", suggesting changes. For
example suggesting `replace-string' to be replaced by the loop
discussed earlier. Does something like this already exist? I would
imagine this would be useful to beginning elispers.
next prev parent reply other threads:[~2007-11-06 16:33 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
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 [this message]
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
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=7dbe73ed0711060833p6a57778x2277035cb2966954@mail.gmail.com \
--to=mathias.dahl@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=yezonghui@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.
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).