From: Andy Wingo <wingo@pobox.com>
To: guile-user@gnu.org
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Wed, 01 Mar 2017 18:36:20 +0100 [thread overview]
Message-ID: <87lgsodhm3.fsf@pobox.com> (raw)
In-Reply-To: <8760jtcfsc.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Wed, 01 Mar 2017 14:01:07 +0100")
On Wed 01 Mar 2017 14:01, Thien-Thi Nguyen <ttn@gnu.org> writes:
> () Andy Wingo <wingo@pobox.com>
> () Thu, 23 Feb 2017 22:06:30 +0100
>
> Yeah pk is nice!!!!
>
> Thumbs up for ‘pk’. Here's the pair of commands i use:
>
> ;;; pk-unpk.el --- Commands to instrument Scheme code
Neat :) I guess you are not a paredit person? For me in that
situation:
> ;; (let ((answer (compute-answer))) ...)
> ;; ^
> ;; point is here
> ;;
> ;; Try `M-x pk' then type
> ;;
> ;; 'answer 'is
> ;;
> ;; The code then looks like:
> ;;
> ;; (let ((answer (pk 'answer 'is (compute-answer)))) ...)
I would do
M-( pk 'answer is
and it "just works" (if you have a paredit-infected brain like me).
> ;;
> ;; `M-x unpk' searches backwards and upwards for a `pk' form and removes
> ;; it, or signals error if one cannot be found.
Here with point on the open paren in (compute-answer), in paredit M-<Up>
does a similar thing.
FWIW :)
Andy
next prev parent reply other threads:[~2017-03-01 17:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran
2017-02-23 21:06 ` Andy Wingo
2017-03-01 13:01 ` Thien-Thi Nguyen
2017-03-01 17:36 ` Andy Wingo [this message]
2017-03-02 5:50 ` Thien-Thi Nguyen
2017-02-24 0:52 ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02 ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46 ` Arne Babenhauserheide
2017-02-26 17:57 ` Andy Wingo
2017-02-27 19:32 ` Mike Gran
2017-02-27 20:30 ` Andy Wingo
2017-02-27 23:00 ` Thomas Morley
2017-02-28 8:31 ` Andy Wingo
2017-02-28 9:38 ` David Kastrup
2017-02-28 14:03 ` Andy Wingo
2017-03-05 16:54 ` Thomas Morley
2017-03-01 18:04 ` Arne Babenhauserheide
2017-02-28 0:04 ` David Pirotte
2017-02-28 1:49 ` Daniel Llorens
2017-03-02 20:54 ` David Pirotte
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=87lgsodhm3.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@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.
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).