From: Martin Castillo <castilma@uni-bremen.de>
To: Gottfried <gottfried@posteo.de>,
"Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: help-guix@gnu.org
Subject: Re: Musescore and other music notation packages like Lilypond, Frescobaldi, Denemo, Rosegarden
Date: Tue, 21 Mar 2023 12:06:36 +0100 [thread overview]
Message-ID: <cf123cd9-1a00-9190-76f1-6ebcf59df977@uni-bremen.de> (raw)
In-Reply-To: <95c96181-caf1-9bdc-f0eb-5d256db95c79@posteo.de>
Hi,
I'm just leaving a simle note here.
Am 21.03.23 um 10:02 schrieb Gottfried:
> I can’t create a document with:
> lilypond THE_FILENAME.ly
And you are not supposed to. lilypond is not a program to create or edit
.ly files. It is only there to read those files and produce pdfs and
midi files.
The command
lilypond THE_FILENAME.ly
is used to create a pdf using an existing file named THE_FILENAME.ly
as input!
Here is a simple figure. Programs are inside bars (|program|) and take
input from the left and output to the right.
With frescobaldi the data flow looked something like this
|frescobaldi| -> THE_FILENAME.ly -> |lilypond| -> THE_FILENAME.pdf
where the middle parts were invisible to you, because frescobaldi was
made that way, to hide that part. You just interacted with frescobaldi
and used the pdf at the end.
If you change away from frescobaldi, the middle part becomes visible
(i.e. you have to "do more"):
|nano | -> THE_FILENAME.ly -> |lilypond| -> THE_FILENAME.pdf
Now you have to create the file THE_FILENAME.ly explicitly yourself with
some program, possibly nano, and then call lilypond THE_FILENAME.ly so
that lilypond creates the pdf file from THE_FILENAME.ly.
Now you can replace nano by your favourite (working) editor, so once the
gtk stuff is fixed, you may even use gedit in the future.
Hope that helps.
> with which command can I copy the songbook from this guix shell into
my home folder?
Do you mean the pdf?
I'd guess it already is in your home folder: If you just started your
terminal before executing
guix shell lilypond nano mercurial timidity++ and the other commands,
THE_FILENAME.ly should be in your home folder (/home/gfp I guess). And
executing
lilypond THE_FILENAME.ly creates the pdf file in the same folder.
Here is how to copy a file:
cp source.file dest.file
Example:
cp THE_FILENAME.pdf ~/Dokumente/
This will copy THE_FILENAME.pdf to the Dokumente directory.
This assumes THE_FILENAME.pdf is in your current working directory of
your shell.
(That just means you're in that directory with the shell. The command
`pwd` prints the current working directory. With cd you can change
between working directories:
$ cd # this changes to your home directory
$ cd Dokumente # go into ~/Dokumente, which is Dokumente inside your
home directory
# you can swith down multiple directories at once
$ cd Musik/Noten # go into ~/Dokument/Musik/Noten
$ cd .. # go one level up, back into ~/Dokument/Musik
$ cd ~/Desktop/Projekt/Musical # jump to Projekt Musical inside Desktop
$ cd ../.. # go two levels up to Desktop
Note, these examples assume that those directories even exist. If one of
those doesn't, cd will print an Error:
bash: cd: Musik/Noten: Datei oder Verzeichnis nicht gefunden
)
Example 2: If THE_FILENAME.pdf was for example on your desktop, you could do
cp ~/Desktop/THE_FILENAME.pdf ~/Dokumente/songbook-v0.1.pdf
to copy it to Dokumente and give it a different name at once.
Martin
next prev parent reply other threads:[~2023-03-21 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 16:52 Musescore and other music notation packages like Lilypond, Frescobaldi, Denemo, Rosegarden Gottfried
2023-03-19 17:34 ` Dr. Arne Babenhauserheide
2023-03-20 12:45 ` Gottfried
2023-03-20 14:43 ` Dr. Arne Babenhauserheide
2023-03-21 6:08 ` Gottfried
2023-03-21 7:24 ` Dr. Arne Babenhauserheide
2023-03-21 9:02 ` Gottfried
2023-03-21 11:06 ` Martin Castillo [this message]
2023-03-21 17:21 ` Gottfried
2023-03-21 17:37 ` Dr. Arne Babenhauserheide
2023-03-19 17:50 ` Spencer Skylar Chan
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf123cd9-1a00-9190-76f1-6ebcf59df977@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=arne_bab@web.de \
--cc=gottfried@posteo.de \
--cc=help-guix@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).