Hello,
does anyone know of a simple way to have the last line of a section with ragged
right, something like ragged-last=##t affecting not only the last line of a
score, but also the last line of a section?
Thanks,
Gilg
On 2024-01-07 11:14 pm, John Helly wrote:
Aloha.
In reading the documentation about \include
(https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files),
I find the following sentence but can't find any explanation anywhere
about what *#f and #t *are or do. Can anyone en
On Sun, 2024-01-07 at 21:14 -1000, John Helly wrote:
> Aloha.
>
> In reading the documentation about \include
> (https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files
> ), I find the following sentence but can't find any explanation
> anywhere about what #f and #t are or d
Good-oh, indeed.
It's true that special characters can cause inconsistent results in
almost anything but if you're searching Documentation for a command that
includes them, you expect the search to be 'complete'; i.e.,
encompassing all possibities.
This search capability does not seem to be
Mahalo. Appreciate the response.
J.
On 1/8/24 02:39, Graham King wrote:
On Sun, 2024-01-07 at 21:14 -1000, John Helly wrote:
Aloha.
In reading the documentation about \include
(https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files),
I find the following sentence but
Mahalo. Appreciate the input. I understand the \include stuff and am
familiar with the concepts with that added info.
My larger concern is with the ability to find these details with limited
knowledge about LP; as a relative novice. I wrote a longer reply to the
list about this but, in short
Hi John,
> My larger concern is with the ability to find these details with limited
> knowledge about LP; as a relative novice. I wrote a longer reply to the list
> about this but, in short, I wouldn't have likely found this bit about #t #f
> without referrals. Seems I should have been able t
> If you do a web search for
>
> lilypond "#f"
>
> is the very first hit not sufficiently helpful?
In defense of the OP, the first hit for me on Qwant is
http://lilypond.org/doc/v2.25/Documentation/usage/advanced-command_002dline-options-for-lilypond
which would not be exactly helpful if I we
Aloha.
Well, when I do that search I just get back the \include page
(https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files).
So, the answer is no. However, one has to consider the issues of
web-caching interfering with search results.
Within the LP docs I wouldn't
Hi all,
> A pity, since this is clearly explained on
> https://lilypond.org/doc/v2.24/Documentation/learning/types-of-properties.html
That’s the first hit when I search! :)
K
__
My work day may look different than your work day. Please do not feel obl
Exactly.
J.
On 1/8/24 10:49, Kieren MacMillan wrote:
Hi all,
A pity, since this is clearly explained on
https://urldefense.com/v3/__https://lilypond.org/doc/v2.24/Documentation/learning/types-of-properties.html__;!!Mih3wA!HBqo-HvW94DSKk2DDGkbgwtz9zOikB4lQukpZRtlEGWoWXMkUhDEX0T6AtXdwXwIzM-IPgdH
Hi John,
On the main webpage (https://lilypond.org/doc/v2.23/Documentation/web/index),
when you use the search box (in the top nav bar), and type #f (no quotes or
anything), do you not get the “Types of Properties” link within the first few
hits (it’s the third when I search)?
Thanks,
Kieren.
On 2024-01-08 21:49, Kieren MacMillan
wrote:
Hi all,
A pity, since this is clearly explained on
https://lilypond.org/doc/v2.24/Documentation/learning/types-of-properties.html
That’s the first hit when I search! :)
K
Le lundi 08 janvier 2024 à 12:04 -1000, John Helly a écrit :
> My default search engine is Google but I've also tried DuckDuckGo and Bing
> with similar, but different, results. So, this problem falls into a use-case
> that I usually call 'the completeness and consistency of a search'.
Is th
Aloha J-A.
Excellent. That's a good place but I don't see the #t,f. Am I missing it?
I'd like to suggest placing a link to the Index in the Manuals area
(https://lilypond.org/doc/v2.23/Documentation/web/manuals.html). This
seems to be the /de facto/ top of the Documentation tree even though
Dear Experts,
I am working on writing my own function which combines several notes into
one custom symbol (ligature).
(For the context, I now about Mensural_ligature_engraver, but I want to
create something that will allow for more flexibility, as I try to engrave
symbols as close to one of differ
Dear Lilypond-user,
I sent this mail to the wrong mail, I should have send it to
lilypond-user-requ...@gnu.org ! Sorry!
Best,
Artur Dobija
pon., 8 sty 2024 o 23:56 Artur Dobija napisał(a):
> Dear Experts,
>
> I am working on writing my own function which combines several notes into
> one custom
On Mon, Jan 8, 2024 at 3:29 PM John Helly wrote:
> Aloha K.
>
> I go to the LP home page, using that search box (upper right), type #f and
> this is what is returned. I can send a video if you'd find it helpful.:
>
>
John,
It looks like the reference Kieren found is the next one down on your
Artur Dobija writes:
> Dear Lilypond-user,
> I sent this mail to the wrong mail, I should have send it to
> lilypond-user-requ...@gnu.org ! Sorry!
No, you sent it to the right address. lilypond-user-request is the
address for sending list server commands. Send it an Email with "help"
in the bo
Aloha Carl.
Yes, I have read most of the manuals and have created ~12 scores over
the past few years but LP is so vast that there seems to be no end of
interesting things I don't understand or can't find. It's a truly
amazing piece of work and my ship is so small.
The point I am trying to c
Artur Dobija writes:
> Dear Experts,
>
> I am working on writing my own function which combines several notes into
> one custom symbol (ligature).
> (For the context, I now about Mensural_ligature_engraver, but I want to
> create something that will allow for more flexibility, as I try to engrave
> See for example http://lilypond.org/notation.html, which you reach
> by clicking on "details of Notation" at
> http://lilypond.org/manuals.html. Could anyone please come up with
> a better formulation than "details of ...", since it's far from
> intuitive what such a link might contain.
Perha
> It's true that special characters can cause inconsistent results in
> almost anything but if you're searching Documentation for a command
> that includes them, you expect the search to be 'complete'; i.e.,
> encompassing all possibities.
The thing is that `#f` and `#t` are nothing special; the
Aloha.
I kind of suspected that this was a Scheme-ism but didn't dig into it
(yet). I used to progam Lisp but know nothing about Scheme. Perhaps
it's so fundamental to the Core group that it's 'duh' but that's not the
case for the rest of us (me).
Of course, booleans would be fundamental bu
24 matches
Mail list logo
