unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: find s-expr in the REPL?
Date: Mon, 25 Sep 2006 08:29:35 +0100	[thread overview]
Message-ID: <87irjch09s.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <AEA8CA04-AA61-4FF2-AB50-5744CBD15162@epfl.ch> ( Daniel Llorens del Río's message of "Mon, 25 Sep 2006 03:47:43 +0200")

Daniel Llorens del Río <daniel.llorensdelrio@epfl.ch> writes:

> Hi,
>
> I'd like to have the following key bindings in the REPL:
>
> - like up-arrow, but shows previous s-expr instead of last line

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?

> - like ^R, but searches s-exprs instead of lines

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.

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.

> Has somebody written readline macros to do these things? Any other way?

I'm not familiar with readline macros.  Can they do this kind of line
combination?

Regards,
     Neil



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2006-09-25  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25  1:47 find s-expr in the REPL? Daniel Llorens del Río
2006-09-25  7:29 ` Neil Jerram [this message]
     [not found] <0J6500HKIOS4MF@imap0.epfl.ch>
2006-09-25 18:03 ` Daniel Llorens del Río
2006-10-04 23:11   ` Kevin Ryde

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=87irjch09s.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).