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: guile-debugging and breakpoints
Date: Sun, 14 Jan 2007 10:21:49 +0000	[thread overview]
Message-ID: <87irf9hps2.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <20070114090341.GA1343@alamut> (Volkan YAZICI's message of "Sun, 14 Jan 2007 11:03:41 +0200")

Volkan YAZICI <yazicivo@ttnet.net.tr> writes:

> On Jan 14 01:30, Neil Jerram wrote:
>> Volkan YAZICI <yazicivo@ttnet.net.tr> writes:
>> > gds-scheme.el:
>> > --------------
>> > 406              (define-key map [mouse-1] 'gds-show-last-stack)
>> > 407	         (insert "[click here to show error stack]"
>> 
>> Good point, thanks.  How about adding two possibilities here?
>> 
>> 1. `RET' as a text-property binding within the "[click here to show
>>    error stack]" text - i.e. same scope as mouse-1.
>> 
>> 2. `C-h S' in scheme-mode-map.  This means that `C-h S' will work
>>    anywhere in both the *Guile Evaluation* buffer and the source code
>>    buffer.
>
> Both of these features would be nice. Umm... If it is possible, I'd
> give my vote to both!

Doing both is what I meant.  These bindings will be in CVS soon and
then the next guile-debugging release.

Regards,
     Neil



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


      reply	other threads:[~2007-01-14 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  1:48 guile-debugging and breakpoints Volkan YAZICI
2006-12-29  2:29 ` Neil Jerram
2007-01-10 15:33   ` Volkan YAZICI
2007-01-14  1:01     ` Neil Jerram
2007-01-14  9:38       ` Volkan YAZICI
2007-01-10 15:45   ` Volkan YAZICI
2007-01-14  1:30     ` Neil Jerram
2007-01-14  9:03       ` Volkan YAZICI
2007-01-14 10:21         ` Neil Jerram [this message]

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=87irf9hps2.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).