From: "Daniel Llorens del Río" <daniel.llorensdelrio@epfl.ch>
Subject: Re: find s-expr in the REPL?
Date: Mon, 25 Sep 2006 20:03:33 +0200 [thread overview]
Message-ID: <8F739E8D-5B27-4B06-A3BA-4E271AE89047@epfl.ch> (raw)
In-Reply-To: <0J6500HKIOS4MF@imap0.epfl.ch>
On 25 Sep, 2006, at 18:07, guile-user-request@gnu.org wrote:
> Just to check what you mean here: in many cases a line is a single
> sexp, so there is no difference - so I presume you're talking about
> the case where a sexp is split across lines, e.g.
>
> guile> (define (foo)
> guile> (bar))
>
> and saying that when you do up-arrow after this you'd like to see
>
> guile> (define (foo) (bar))
>
> Is that right?
Absolutely, that's what I mean. Actually, maybe I'd prefer up-arrow
to show
guile> (define (foo)
... (bar))
just as I would have typed it. But that's a minor detail.
> I think this is just a corollary of the above, isn't it? In other
> words, if you do "^R foo" you'd also like to see the combined line, as
> shown just above.
That's right.
> It seems to me that these could most easily be achieved by modifying
> what readline thinks its history is. I'm sure this is doable, but
> someone needs to look into the details.
The idea is, I guess, to have readline split its history not by
newlines but by matching parentheses at the top level, at least when
they cross line boundaries. I'll look into that, thanks.
> I'm not familiar with readline macros. Can they do this kind of line
> combination?
I'm not familiar with them either. They seem to provide good search
capabilities, so that's why I proposed them.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next parent reply other threads:[~2006-09-25 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0J6500HKIOS4MF@imap0.epfl.ch>
2006-09-25 18:03 ` Daniel Llorens del Río [this message]
2006-10-04 23:11 ` find s-expr in the REPL? Kevin Ryde
2006-09-25 1:47 Daniel Llorens del Río
2006-09-25 7:29 ` Neil Jerram
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=8F739E8D-5B27-4B06-A3BA-4E271AE89047@epfl.ch \
--to=daniel.llorensdelrio@epfl.ch \
/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).