From: Volkan YAZICI <yazicivo@ttnet.net.tr>
Cc: guile-user@gnu.org
Subject: Re: guile-debugging and breakpoints
Date: Wed, 10 Jan 2007 17:45:10 +0200 [thread overview]
Message-ID: <20070110154510.GC1376@alamut> (raw)
In-Reply-To: <87mz57qvs3.fsf@ossau.uklinux.net>
Hi,
I think we should support emacs console users too. AFAIK, below lines
just work with emacs under X.
gds-scheme.el:
--------------
406 (define-key map [mouse-1] 'gds-show-last-stack)
407 (insert "[click here to show error stack]"
As an emacs user who prefers to use emacs under GNU screen, it'd be
better to bind that action to a key too. (It's not very easy to type
M-x gds-show-last-stack everytime.)
Regards.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-01-10 15:45 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 [this message]
2007-01-14 1:30 ` Neil Jerram
2007-01-14 9:03 ` Volkan YAZICI
2007-01-14 10:21 ` 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=20070110154510.GC1376@alamut \
--to=yazicivo@ttnet.net.tr \
--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).