lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Add an expert font tree interface (issue 108700043 by address@hidden


From: perpeduumimmobile
Subject: Re: Add an expert font tree interface (issue 108700043 by address@hidden)
Date: Thu, 17 Jul 2014 08:55:09 +0000

On 2014/07/17 08:28:36, dak wrote:
mailto:address@hidden writes:

> Two follow-up questions:
> 1.) Is there a way to list all Lily scheme functions and/or all
their
> docstrings?  If you know what function or variable you are looking
for,
> the docstrings are obviously great.  But if I look for something
which
> matches your favourite buzzword, I currently grep in some way
through
> the entire scheme code.

(module-for-each
   (lambda (s v)
     (let ((r (variable-ref v)))
        (if (and (procedure? r) (procedure-documentation r))
            (format #t "~a: ~a\n\n" s (procedure-documentation r)))))
   (resolve-module '(lily)))

But actually

   git grep something scm

*is* pretty great.

I agree; I was asking more from a user perspective who does not have a
clone of the repo, but still might want to use one or the other of those
define-public thingies in user-level scheme.

> 2.) If I run `guile`, `(help)` gives me all sorts of info on how to
use,
> well, the help.  But if I run `lilypond scheme-sandbox`, `(help)`
will
> only show me a complaint "ERROR: Unbound variable: help".  Do I have
to
> use a special trick to access these docs in a guile REPL?

(use-modules (ice-9 session))

Thanks.

That leaves me with only one more question: Is there any reason to use
Texinfo markup in those docstrings, given that all more-or-less obvious
ways of accessing it do not seem to use it? Or should I rather give a
well-formatted uncluttered raw text description for unprocessed human
consumption?


Best,
Alexander

https://codereview.appspot.com/108700043/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]