From: Martin Castillo <castilma@uni-bremen.de>
To: Gottfried <gottfried@posteo.de>,
help-guix@gnu.org, Wojtek Kosior <koszko@koszko.org>
Subject: Re: 2 Profiles with 2 different version of Musescore
Date: Sat, 29 Apr 2023 15:48:48 +0200 [thread overview]
Message-ID: <2c6b7e86-dcd8-8dc3-9a1f-c33a1ae7bd9c@uni-bremen.de> (raw)
In-Reply-To: <330242cc-fef4-a852-fb52-c60f8fbec7bc@posteo.de>
Am 28.04.23 um 17:07 schrieb Gottfried:
> Hi,
>
> I have 2 profiles, one with Musescore 3.6.2, the other with Musescore
> 4.02 (the last version, ongoing).
> When I enter "mscore" in the terminal it opens the version 3.6.2, which
> I want.
>
> But what do I have to enter in the terminal to get the new version of
> Musescore?
>
You need to write down the absolute path to the musescore 4 executable.
Something like
/home/gfp/Projekte/pfad/zum/profil/mit/musescore4/bin/mscore
should work.
As a shorthand you could add an alias like this
alias mscore4="/home/gfp/Projekte/pfad/zum/profil/mit/musescore4/bin/mscore"
to .bash_aliases (if it is being 'source'd by bashrc) or.bashrc otherwise.
(Put everything in one line. My mailclient automatically wraps long
lines even if it should not do so in this case.)
when you restart your shell (or type `source ~/.bashrc`) then
mscore4
should execute musescore 4.
next prev parent reply other threads:[~2023-04-29 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:07 2 Profiles with 2 different version of Musescore Gottfried
2023-04-29 13:48 ` Martin Castillo [this message]
2023-04-29 16:18 ` Skyler
2023-04-29 21:25 ` Martin Castillo
2023-05-01 10:16 ` Gottfried
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=2c6b7e86-dcd8-8dc3-9a1f-c33a1ae7bd9c@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=koszko@koszko.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).