From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: Customising Guile's prompt
Date: Wed, 11 Dec 2024 16:35:48 -0800 [thread overview]
Message-ID: <f5cd42f0-9ec0-4629-9bb4-f098f603b8d1@gmail.com> (raw)
In-Reply-To: <Z1mwsXDrGD-8RYrz@dragonfly.nameserver.nu>
On 12/11/24 7:33 AM, Ray Soto wrote:
> Hi! I've read the HTML manual and I have created a 'nice'
> prompt for my machines as follows:
>
> (use-modules ... (system repl common))
> ...
> (repl-default-option-set! 'prompt
> (string-append
> (getlogin) "@" (gethostname) " > "))
>
> What bothers me is that I have been unable to replicate
> the default prompt's feature of printing the current
> debug (level/frame? don't even know how to call it!)
>
> I've searched in my /usr/local/share/guile (I am on BSD)
> to no avail. Could you point me in the right direction here?
> BR, Ray.-
>
Maybe kludgy but check out this: (length (fluid-ref *repl-stack*))
prev parent reply other threads:[~2024-12-12 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 15:33 Customising Guile's prompt Ray Soto
2024-12-12 0:35 ` Matt Wette [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=f5cd42f0-9ec0-4629-9bb4-f098f603b8d1@gmail.com \
--to=matt.wette@gmail.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).