Frescobaldi: missing menu bar FIXED
I'd like to record a fix, of sorts, for a missing menu bar in Frescobaldi under a rather specific combination of circumstances. It might help someone. Possibly future-me! I run Frescobaldi on an Ubuntu 22.04 system, with an Apple-Mac-OS-X- like KDE theme that puts the menus of the currently-focussed application at the top of the screen. Following a recent upgrade to KDE Plasma 6, the menus in Frescobaldi completely disappeared. You can force the menu bar to appear at the top of the application window for all apps. To do this, go to System Settings -> Session -> Background services and uncheck "Application menus daemon" It might be necessary to restart your session for this to take effect. It might be possible to create a specific exception for Frescobaldi, using the KWin rule editor, accessed by right-clicking on the title bar of the Frescobaldi window and selecting More Actions. Unfortunately I've been unable to find a specific combination of settings that work.
Re: Frescobaldi?
I can confirm the same problem. Just installed macports and frescobaldi port and it launches only via terminal. Double clicking on the .app (inside the apps/macports folder) returns a general launch error with py2app. Once launched via terminal, frescobaldi works great, though. > El 10 maig 2024, a les 17:48, Xavier Mayeur va escriure: > > yes, I am sure. This is the frescobaldi.app under the /Applications/MacPorts > folder. I've cleaned all older versions before installing with Mac Port > > Xavier > > Le 10/05/24 à 17:37, Jean Abou Samra a écrit : >>> I've freshly installed Frescobaldi using mac port. When lauching the >>> frescobaldi.app, >> Are you sure that this is the Frescobaldi that was installed by MacPorts? >> It rather sounds like the (buggy) .app distributed in the Frescobaldi >> releases. I think the MacPorts-installed Frescobaldi should be launched >> by executing the `frescobaldi` command in a terminal — which was apparently >> successful for you. > -- > Cordialement, > > Xavier MAYEUR > 14 rue Thiernesse > 1070 Bruxelles
Re: Frescobaldi?
yes, I am sure. This is the frescobaldi.app under the /Applications/MacPorts folder. I've cleaned all older versions before installing with Mac Port Xavier Le 10/05/24 à 17:37, Jean Abou Samra a écrit : I've freshly installed Frescobaldi using mac port. When lauching the frescobaldi.app, Are you sure that this is the Frescobaldi that was installed by MacPorts? It rather sounds like the (buggy) .app distributed in the Frescobaldi releases. I think the MacPorts-installed Frescobaldi should be launched by executing the `frescobaldi` command in a terminal — which was apparently successful for you. -- Cordialement, Xavier MAYEUR 14 rue Thiernesse 1070 Bruxelles
Re: Frescobaldi?
> I've freshly installed Frescobaldi using mac port. When lauching the > frescobaldi.app, Are you sure that this is the Frescobaldi that was installed by MacPorts? It rather sounds like the (buggy) .app distributed in the Frescobaldi releases. I think the MacPorts-installed Frescobaldi should be launched by executing the `frescobaldi` command in a terminal — which was apparently successful for you. signature.asc Description: This is a digitally signed message part
Re[6]: Frescobaldi?
No no, I understand what you're saying. I'm new to the codebase and it's silly to take on an entire rewrite before even fixing basic stuff. However, I believe that in programming it's important to dream big and reel back those expectations, because the fact remains that we can do some pretty neat stuff with computers. So I figure there's always opportunity for revision and growth. That being said, I'll look over it and try to implement a patch for Qt6 to start. I still encourage people reading this to continue getting in touch with me tho, I'm happy to be a contact point for Frescobaldi-stuff. Especially if you have background in Python! ~Steph
Re: Frescobaldi?
> Regarding MacOs porting, a valid alternative would be to run > the linux version of Frescobaldi from a Docker container Perhaps, but from the perspective of building .app bundles, that replaces a headache (shipping Qt, PyQt, Poppler and python-poppler-qt5) with what sounds like an even larger headache, and there's a myriad of ways it won't integrate well with the macOS system around it (file dialogs, global menu, and so on). If the goal is to just have something that works, the Homebrew and MacPorts packages already work better. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
Regarding MacOs porting, a valid alternative would be to run the linux version of Frescobaldi from a Docker container A Dockerfile like this one FROM ubuntu RUN apt update-yq&& apt install-y frescobaldi pulseaudio&& apt clean-y RUN mkdir -p/Users//Scores WORKDIR /Users//Scores ENV XDG_RUNTIME_DIR=/tmp ENV PULSE_SERVER=docker.for.mac.localhost CMD frescobaldi should made the trick. Then create the image docker build . -t fresco_image Lastly, invoke the container #! /bin/sh # Pre-requisites: # brew install pulseaudio # brew services start pulseaudio xhost + docker run --rm -v /tmp/.X11-unix:/tmp/.X11-unix \ -v /Users//Scores/:/Users//Scores/ \ -e PULSE_SERVER=docker.for.mac.localhost \ -v ~/.config/pulse:/home/pulseaudio/.config/pulse \ -e DISPLAY=docker.for.mac.host.internal:0 \ fresco_image I have to fine tune this (midi playback not working yet) , but it is fully working from an editing and compilation perspective, including point-and-click Xavier Mayeur Le 28/04/24 à 19:06, Jean Abou Samra a écrit : Just had a quick look. It seems to me we need to create a python-poppler-qt6, port qpageview to Qt6 and of course frescobaldi itself. I would hope that qpageview and frescobaldi both basically mean moving from PyQt5 to PyQt6 which I expect to be mostly busy work. The poppler bindings seem to require understanding of what poppler does though. All of the above is based on a brief look and thus not a reliable assessment. Honestly, I have zero idea how hard porting to Qt 6 actually is. I think we won't know until someone tries and finds out what exactly Frescobaldi uses that is modified or removed in Qt 6 compared to Qt 5 as well as poppler-qt6 compared to poppler-qt5. In any case, I do rely on Frescobaldi and am willing to help keep it alive. If you want to attempt the port, of course feel free. -- Cordialement, Xavier MAYEUR 14 rue Thiernesse 1070 Bruxelles
Re: Re[4]: Frescobaldi?
> I'm an intermediate-level python programmer but I might be able to help with > busy work like typing and documenting functions, with some feedback. Anything > to give back to a project that I use all the time! Thanks. However, without wanting to stop you from contributing, I'll reiterate that from my point of view, what the project needs right now is focus on macOS distribution, and Qt 6. Other work is welcome but it will not really help the project to get out of the current impasse. signature.asc Description: This is a digitally signed message part
Re: Re[4]: Frescobaldi?
I think that all sounds good, but that kind of rework is probably going to involve a lot of regression risk (what are the tests like right now?), but also a ton of opportunities for improvements to the extent that it might be a good time to make a break from backward functional compatibility, maybe brand it as something else, and market it as the next gen or something like that. It sounds like the code as it is is in kind of a bad state, we've got people here on this list that care about that code but don't have time to do much more than review your changes, but then you are showing a lot of initiative to contribute and have the skills and interest to take this kind of project on. We could all just take a step back and see what you do? On Mon, May 6, 2024 at 10:06 AM Steph Phillips wrote: > > Well, I'm glad you asked about feedback because I'm curious what other > folks who contribute to Frescobaldi might think. > > After digging around in the codebase, I'm wondering if the application > might benefit from a more object-oriented design. It's definitely in > Python, but with more of C-style approach. You've worked on it, you know > what I'm talking about. Was wondering what your thoughts are. > > Additionally, I was wondering if it might benefit from typehinting > throughout the codebase to allow for easier maintenance and plugin > development. > > Thoughts? ♥ > > -- Original Message -- > From "Jean Abou Samra" > To "Steph Phillips" ; "Graham King" > ; "N. Andrew Walsh" > Cc "Lilypond-User Mailing List" > Date 5/6/2024 7:00:17 AM > Subject Re: Re[2]: Frescobaldi? > > > > >> Hey all, I've been looking over the Frescobaldi codebase for the last > >> few days, and it seems to be within the realm of something I could pick > >> up maintenance for. > >> > >> There would definitely be a learning curve, so hopefully it doesn't > >> reach it's EOL too soon... But, I don't know, I feel pretty confident. > >> > >> Not really sure what more info I can contribute to the public discourse > >> at this point, but I welcome anyone else interested with the upkeep of > >> Frescobaldi to get in touch with me so we can coordinate~ > > > > > > > >I'd encourage you to start by fixing some small issues to get acquainted > >with the code. Then if you want to do the Qt 6 port, work on a branch > >and make it public so I (for example) can have a look (don't wait for > >having finished the port before seeking feedback). > > > >Thanks, > >Jean > > > > >
Re: Re[4]: Frescobaldi?
Le lundi 06 mai 2024 à 14:05 +, Steph Phillips a écrit : > Well, I'm glad you asked about feedback because I'm curious what other > folks who contribute to Frescobaldi might think. > > After digging around in the codebase, I'm wondering if the application > might benefit from a more object-oriented design. It's definitely in > Python, but with more of C-style approach. You've worked on it, you know > what I'm talking about. Was wondering what your thoughts are. I wouldn't focus on large-scale refactorings that will only pay off on the long term without first (1) doing smaller things to get used to the code and (2) doing what needs to get done on the short term to be able to do releases and keep up to date with the rest of the world. signature.asc Description: This is a digitally signed message part
Re: Re[4]: Frescobaldi?
On Mon, May 6, 2024 at 7:06 AM Steph Phillips wrote: > Well, I'm glad you asked about feedback because I'm curious what other > folks who contribute to Frescobaldi might think. > > After digging around in the codebase, I'm wondering if the application > might benefit from a more object-oriented design. It's definitely in > Python, but with more of C-style approach. You've worked on it, you know > what I'm talking about. Was wondering what your thoughts are. > > Additionally, I was wondering if it might benefit from typehinting > throughout the codebase to allow for easier maintenance and plugin > development. > > Thoughts? ♥ > I'm an intermediate-level python programmer but I might be able to help with busy work like typing and documenting functions, with some feedback. Anything to give back to a project that I use all the time! -- Knute Snortum
Re[4]: Frescobaldi?
Well, I'm glad you asked about feedback because I'm curious what other folks who contribute to Frescobaldi might think. After digging around in the codebase, I'm wondering if the application might benefit from a more object-oriented design. It's definitely in Python, but with more of C-style approach. You've worked on it, you know what I'm talking about. Was wondering what your thoughts are. Additionally, I was wondering if it might benefit from typehinting throughout the codebase to allow for easier maintenance and plugin development. Thoughts? ♥ -- Original Message -- From "Jean Abou Samra" To "Steph Phillips" ; "Graham King" ; "N. Andrew Walsh" Cc "Lilypond-User Mailing List" Date 5/6/2024 7:00:17 AM Subject Re: Re[2]: Frescobaldi? Hey all, I've been looking over the Frescobaldi codebase for the last few days, and it seems to be within the realm of something I could pick up maintenance for. There would definitely be a learning curve, so hopefully it doesn't reach it's EOL too soon... But, I don't know, I feel pretty confident. Not really sure what more info I can contribute to the public discourse at this point, but I welcome anyone else interested with the upkeep of Frescobaldi to get in touch with me so we can coordinate~ I'd encourage you to start by fixing some small issues to get acquainted with the code. Then if you want to do the Qt 6 port, work on a branch and make it public so I (for example) can have a look (don't wait for having finished the port before seeking feedback). Thanks, Jean
Re: Re[2]: Frescobaldi?
> Hey all, I've been looking over the Frescobaldi codebase for the last > few days, and it seems to be within the realm of something I could pick > up maintenance for. > > There would definitely be a learning curve, so hopefully it doesn't > reach it's EOL too soon... But, I don't know, I feel pretty confident. > > Not really sure what more info I can contribute to the public discourse > at this point, but I welcome anyone else interested with the upkeep of > Frescobaldi to get in touch with me so we can coordinate~ I'd encourage you to start by fixing some small issues to get acquainted with the code. Then if you want to do the Qt 6 port, work on a branch and make it public so I (for example) can have a look (don't wait for having finished the port before seeking feedback). Thanks, Jean signature.asc Description: This is a digitally signed message part
RE: Re[2]: Frescobaldi?
Steph, Thank you. Mark -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org On Behalf Of Steph Phillips Sent: Sunday, May 5, 2024 11:46 PM To: Jean Abou Samra ; Graham King ; N. Andrew Walsh Cc: Lilypond-User Mailing List Subject: Re[2]: Frescobaldi? Hey all, I've been looking over the Frescobaldi codebase for the last few days, and it seems to be within the realm of something I could pick up maintenance for. There would definitely be a learning curve, so hopefully it doesn't reach it's EOL too soon... But, I don't know, I feel pretty confident. Not really sure what more info I can contribute to the public discourse at this point, but I welcome anyone else interested with the upkeep of Frescobaldi to get in touch with me so we can coordinate~ -- Original Message -- >From "Jean Abou Samra" To "Graham King" >; "N. Andrew Walsh" Cc "Lilypond-User Mailing List" Date 5/5/2024 1:37:35 PM Subject Re: Frescobaldi? >> The technical stuff is way over my head, but this reads like the >> top- level description of a GSOC project (in case the mentioned >> friend doesn't take the bait)... > > > >GSoC projects are nice for doing focused work on some specific part of >the code base. For overhauling just about everything, I'd be a lot more >skeptical, especially since there will unavoidably be fallout to deal >with afterwards in terms of bugs, and that's less nice to do if the >person who did the port isn't available after the summer to do that >part of the work.
Re: Frescobaldi?
> I’m wondering if the Frescobaldi approach is actually working out. Keep in > mind that originally Frescobaldi was just a project for adding support for > Lilypond to KATE, then it became a KDE parts solution, then it started to do > everything itself for more control. And this means you’ll need to maintain and > develop many components for a niche community. Frescobaldi is essentially a > full text editor, solely for Lilypond. And I do not think the Lilypond > community is the best place for maintaining a whole text editor. > > This also means you get a weird dependency situation which is hard to > maintain. Frescobaldi has a lot of qt-independent functionality, including a > reduced Lilypond parser and transformation tools and stuff. And it has a lot > of > interface stuff. This is the part that depends on qt5, and only one component > depends on the poppler integration. > > So maybe instead of trying to maintain this collosus of tools it could make > sense to split it up into different parts: > > → An LSP server > → A transformative toolset > → An editor using these features > > This way no matter what might happen to Frescobaldi, much of the functionality > would be still usable. With an LSP server any modern text editor with an LSP > client could benefit from understanding Lilypond syntax. And being able to a > toolset would make extending editors much more fun. > > And this way the maintainance effort could be split. Maybe the LSP could even > become part of Lilypond itself (no need to implement a new parser if you > already have one), keeping it always up to date (rather than the always > outdated approch we have with Frescobaldi). Well, what you call the "transformative toolset" is already separated, in the form of the python-ly package. An LSP server might be nice, but it wouldn't really take off that much functionality from Frescobaldi. I'd have to check how advanced the LSP protocol exactly is now, but you definitely can't do things like the MIDI player, the fonts dialog, or the manuscript viewer through LSP. And of course, if we already have trouble maintaining the software as it is, finding people to work on that kind of split is not going to be easier :( Also, you cannot really use the LilyPond parser because it won't parse LilyPond code without also interpreting it at the same time (e.g., music functions can be defined dynamically). You don't want to pay the price of parsing the full file every time a character changes, and you don't want to lose syntax highlighting as soon as there is a syntax error. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
An LSP server for lilypond would be awesome! I'm using it all the time for coding in neovim, and it's a total game changer. Best, Kenneth Valentin Petzel, May 06, 2024 at 15:23: > I’m wondering if the Frescobaldi approach is actually working out. Keep in > mind that originally Frescobaldi was just a project for adding support for > Lilypond to KATE, then it became a KDE parts solution, then it started to do > everything itself for more control. And this means you’ll need to maintain > and > develop many components for a niche community. Frescobaldi is essentially a > full text editor, solely for Lilypond. And I do not think the Lilypond > community is the best place for maintaining a whole text editor. > > This also means you get a weird dependency situation which is hard to > maintain. Frescobaldi has a lot of qt-independent functionality, including a > reduced Lilypond parser and transformation tools and stuff. And it has a lot > of > interface stuff. This is the part that depends on qt5, and only one component > depends on the poppler integration. > > So maybe instead of trying to maintain this collosus of tools it could make > sense to split it up into different parts: > > → An LSP server > → A transformative toolset > → An editor using these features > > This way no matter what might happen to Frescobaldi, much of the > functionality > would be still usable. With an LSP server any modern text editor with an LSP > client could benefit from understanding Lilypond syntax. And being able to a > toolset would make extending editors much more fun. > > And this way the maintainance effort could be split. Maybe the LSP could even > become part of Lilypond itself (no need to implement a new parser if you > already have one), keeping it always up to date (rather than the always > outdated approch we have with Frescobaldi). > > Cheers, > Valentin > > Am Sonntag, 5. Mai 2024, 22:37:35 MESZ schrieb Jean Abou Samra: > > > The technical stuff is way over my head, but this reads like the top- > > > level description of a GSOC project (in case the mentioned friend > > > doesn't take the bait)... > > > > GSoC projects are nice for doing focused work on some specific part > > of the code base. For overhauling just about everything, I'd be a lot > > more skeptical, especially since there will unavoidably be fallout > > to deal with afterwards in terms of bugs, and that's less nice to do > > if the person who did the port isn't available after the summer to > > do that part of the work.
Re: Frescobaldi?
I’m wondering if the Frescobaldi approach is actually working out. Keep in mind that originally Frescobaldi was just a project for adding support for Lilypond to KATE, then it became a KDE parts solution, then it started to do everything itself for more control. And this means you’ll need to maintain and develop many components for a niche community. Frescobaldi is essentially a full text editor, solely for Lilypond. And I do not think the Lilypond community is the best place for maintaining a whole text editor. This also means you get a weird dependency situation which is hard to maintain. Frescobaldi has a lot of qt-independent functionality, including a reduced Lilypond parser and transformation tools and stuff. And it has a lot of interface stuff. This is the part that depends on qt5, and only one component depends on the poppler integration. So maybe instead of trying to maintain this collosus of tools it could make sense to split it up into different parts: → An LSP server → A transformative toolset → An editor using these features This way no matter what might happen to Frescobaldi, much of the functionality would be still usable. With an LSP server any modern text editor with an LSP client could benefit from understanding Lilypond syntax. And being able to a toolset would make extending editors much more fun. And this way the maintainance effort could be split. Maybe the LSP could even become part of Lilypond itself (no need to implement a new parser if you already have one), keeping it always up to date (rather than the always outdated approch we have with Frescobaldi). Cheers, Valentin Am Sonntag, 5. Mai 2024, 22:37:35 MESZ schrieb Jean Abou Samra: > > The technical stuff is way over my head, but this reads like the top- > > level description of a GSOC project (in case the mentioned friend > > doesn't take the bait)... > > GSoC projects are nice for doing focused work on some specific part > of the code base. For overhauling just about everything, I'd be a lot > more skeptical, especially since there will unavoidably be fallout > to deal with afterwards in terms of bugs, and that's less nice to do > if the person who did the port isn't available after the summer to > do that part of the work. signature.asc Description: This is a digitally signed message part.
Re[2]: Frescobaldi?
Hey all, I've been looking over the Frescobaldi codebase for the last few days, and it seems to be within the realm of something I could pick up maintenance for. There would definitely be a learning curve, so hopefully it doesn't reach it's EOL too soon... But, I don't know, I feel pretty confident. Not really sure what more info I can contribute to the public discourse at this point, but I welcome anyone else interested with the upkeep of Frescobaldi to get in touch with me so we can coordinate~ -- Original Message -- From "Jean Abou Samra" To "Graham King" ; "N. Andrew Walsh" Cc "Lilypond-User Mailing List" Date 5/5/2024 1:37:35 PM Subject Re: Frescobaldi? The technical stuff is way over my head, but this reads like the top- level description of a GSOC project (in case the mentioned friend doesn't take the bait)... GSoC projects are nice for doing focused work on some specific part of the code base. For overhauling just about everything, I'd be a lot more skeptical, especially since there will unavoidably be fallout to deal with afterwards in terms of bugs, and that's less nice to do if the person who did the port isn't available after the summer to do that part of the work.
Re: Frescobaldi?
> The technical stuff is way over my head, but this reads like the top- > level description of a GSOC project (in case the mentioned friend > doesn't take the bait)... GSoC projects are nice for doing focused work on some specific part of the code base. For overhauling just about everything, I'd be a lot more skeptical, especially since there will unavoidably be fallout to deal with afterwards in terms of bugs, and that's less nice to do if the person who did the port isn't available after the summer to do that part of the work. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
The technical stuff is way over my head, but this reads like the top- level description of a GSOC project (in case the mentioned friend doesn't take the bait)... In other threads spawned by this one, there have been some helpful suggestions for alternative lilypond IDE's, but there is some cost to lilypond in fragmenting its user experience. At the moment, we can just say to new users "choose Frescobaldi; it's the best and most popular IDE, and it's really easy to install" confident that any questions that arise will likely be understood and answered readily. On Sun, 2024-04-28 at 21:36 +0200, Jean Abou Samra wrote: > > unfortunately, as I noted above, the problem seems to be that > > frescobaldi > > depends on a now-deprecated version of qtwebengine, and without > > updating > > it we'll eventually reach a point where it no longer runs. I looked > > into > > this because qtwebengine-5.15 failed to compile on my machine this > > morning, > > so I'm worried we're already approaching EOL on it. > > Note that we're talking about Qt as a whole, not just QtWebEngine > which > is just a small part of it (well, for some definition of "small" > since it > embeds Chromium's Web rendering engine…) that Frescobaldi only uses > in a > few places (IIRC, the SVG viewer and the documentation browser). > > Qt 5 *is* already EOL upstream, since May 2023. > > > > Jean: I have a colleague who does UI work and is "fairly" capable > > of dealing > > with python and Qt dependencies. Can you give me a brief (but as > > technical > > as it needs to be for a specialist to understand the issue) summary > > of where > > the sticking points are? > > Frescobaldi uses the Poppler library in order to display PDF files. > (It cannot > use Qt's native PDF viewer based on Chromium, because that one is not > powerful > enough to support point-and-click.) Since Frescobaldi is written in > Python and > Poppler is a C++ library, it needs an FFI wrapper, which is called > python- > poppler-qt5 and written with a tool called sip that is developed by > the > creator and maintainer of PyQt itself and also used for PyQt. > > Thus there is a diamond dependency: > > Qt5 --> Poppler (C++) > | | > | | > | | > v v > PyQt5 -> python-poppler-qt5 (Python extension modules) > > > python-poppler-qt5 is a little fiddly to build: it's multiple layers > with sip generating C++ code and QMake project files, then QMake > generating a Makefile and sip finally executing make on that > Makefile. > > On macOS, the platform favors distributing applications as .app > bundles, > which are optimized for being created by the native app development > tools (Swift+XCode). These have a peculiar structure organized into > "frameworks", with data files separated from code files, shared > library > lookup paths modified and that sort of thing (the specifics I do not > know > or remember). Of course, that doesn't play well with Python packages > relying on a different structure, and Qt + PyQt also needing their > file structure. In fact there are whole tools written just to deploy > PyQt in a .app bundle, see pyqtdeploy. > > Now throw python-poppler-qt5 into the mix, which needs to be loaded > by > Python and find its linked Poppler and Qt and PyQt, and you should > start > to understand the problem. > > Basically, it's the Apple flavor of "things will work well but only > if you do it my way with the non-cross-platform tools from my walled > garden" in its full glory. > > Add that macOS displays scary warnings to users if the app bundle > hasn't been signed with a certificate that costs real money. > Details are on > https://github.com/frescobaldi/frescobaldi/issues/1584 > > Also add that the tool Frescobaldi has used so far to create app > bundles, py2app, relies heavily on setuptools, which prevents > Frescobaldi from moving to a more modern and less complicated > build backend like hatchling. > > Apart from these packaging issues, there's also an issue with > the global menu (the one at the top of the screen on macOS, it > doesn't appear on other platforms) which isn't really up-to-date > and has been a source of crashes. > > There are also miscellaneous bugs that only reproduce on macOS > (they have the macOS label on GitHub) and it's not always easy > to understand why. > > Well, the explanation wasn't that brief. Sorry that I didn't have > time to write a shorter one, as they say. >
Re: Frescobaldi... panic alternatives?
My very first contribution :-) Nice! Colin Campbell, May 04, 2024 at 02:51: > Thanks again for the text, Ken! I've put it up for review along with a > bunch of housekeeping bits, and it could get merged into the > documentation mid-week. You'll be able to point to your contribution to > LilyPond! > > Cheers, > > Colin > > On 2024-05-01 22:33, Kenneth Flak wrote: > > OK, giving it a shot... Feel free to edit as needed! > > > > Kenneth > > > > > > Neovim > > > > https://neovim.io > > > > Neovim is a minimal text editor and fork of vim. It is highly extensible > > and configurable through the vimscript and lua programming languages. > > Lilypond support is provided by the nvim-lilypond-suite plugin > > (https://github.com/martineausimon/nvim-lilypond-suite). The plugin > > supports playback of midi files through external programs; point-and-click > > when using a supported PDF viewer; snippets and code completion when > > combined with other plugins; in addition to the full range of tools > > available in the neovim ecosystem. For more details on how to set it up > > consult the plugin's github page. You will also want to spend some time > > with some of the numerous online tutorials for learning vim/neovim to get > > the most out of your editing experience. > > > > > > Werner LEMBERG, May 02, 2024 at 05:49: > Maybe one of you two can provide some text for > > https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > >>> It happens that my first contribution to the Lilypond documentation > >>> was a rewrite of the Easier Editing section, some 14 years ago or > >>> so. > >> Aaah :-) > >> > >>> If either or both care to send me their thoughts and comments, I'll > >>> be glad to turn it into a patch. > >> This would be great! Thanks for the offer. > >> > >> > >> Werner > > > > > >
Re: Frescobaldi... panic alternatives?
Thanks again for the text, Ken! I've put it up for review along with a bunch of housekeeping bits, and it could get merged into the documentation mid-week. You'll be able to point to your contribution to LilyPond! Cheers, Colin On 2024-05-01 22:33, Kenneth Flak wrote: OK, giving it a shot... Feel free to edit as needed! Kenneth Neovim https://neovim.io Neovim is a minimal text editor and fork of vim. It is highly extensible and configurable through the vimscript and lua programming languages. Lilypond support is provided by the nvim-lilypond-suite plugin (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports playback of midi files through external programs; point-and-click when using a supported PDF viewer; snippets and code completion when combined with other plugins; in addition to the full range of tools available in the neovim ecosystem. For more details on how to set it up consult the plugin's github page. You will also want to spend some time with some of the numerous online tutorials for learning vim/neovim to get the most out of your editing experience. Werner LEMBERG, May 02, 2024 at 05:49: Maybe one of you two can provide some text for https://lilypond.org/doc/v2.24/Documentation/web/easier-editing It happens that my first contribution to the Lilypond documentation was a rewrite of the Easier Editing section, some 14 years ago or so. Aaah :-) If either or both care to send me their thoughts and comments, I'll be glad to turn it into a patch. This would be great! Thanks for the offer. Werner
Re: Re: Frescobaldi... panic alternatives?
Cool! TBH I've not used point-and-click much, but according to the documentation it should work both ways: https://github.com/martineausimon/nvim-lilypond-suite/wiki/2.-Configuration#point-and-click Roosna & Flak Contemporary Dance & Music https://roosnaflak.com Original Message On 5/2/24 22:59, Colin Campbell wrote: > This looks really good, Ken. I'm going to do a general tidy up on the > Easier Editing page, but I hope to have something up for review in a day > or two. I've installed neovim, but to save a bit of time: is the > point-and-click two-way, like Frescobaldi, or from PDF to code only? > > > Cheers, > > Colin > > On 2024-05-01 22:33, Kenneth Flak wrote: > > OK, giving it a shot... Feel free to edit as needed! > > > > Kenneth > > > > > > Neovim > > > > https://neovim.io > > > > Neovim is a minimal text editor and fork of vim. It is highly extensible > and configurable through the vimscript and lua programming languages. > Lilypond support is provided by the nvim-lilypond-suite plugin > (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports > playback of midi files through external programs; point-and-click when using > a supported PDF viewer; snippets and code completion when combined with other > plugins; in addition to the full range of tools available in the neovim > ecosystem. For more details on how to set it up consult the plugin's github > page. You will also want to spend some time with some of the numerous online > tutorials for learning vim/neovim to get the most out of your editing > experience. > > > > > > Werner LEMBERG, May 02, 2024 at 05:49: > >>>> Maybe one of you two can provide some text for > >>>> > >>>> https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > >>> It happens that my first contribution to the Lilypond documentation > >>> was a rewrite of the Easier Editing section, some 14 years ago or > >>> so. > >> Aaah :-) > >> > >>> If either or both care to send me their thoughts and comments, I'll > >>> be glad to turn it into a patch. > >> This would be great! Thanks for the offer. > >> > >> > >> Werner > > > > > > >
Re: Frescobaldi... panic alternatives? (Kenneth Flak)
Sounds like just the VSLilyPond-PDF-Preview extension is not being maintained. I'll take a look at that tonight...thanks, Federico! On Thu, May 2, 2024 at 4:41 PM Federico Sarudiansky wrote: > Hi Jeff. > > I've been using VSLilypond for VSCode for a while now and I found a > solution for the annoying lack of refresh of the PDF output. It is here: > https://github.com/lhl2617/VSLilyPond-PDF-preview/pull/118 > Basically you have to edit a file of the Lilypond PDF preview extension > (~/.vscode/extensions/lhl2617.lilypond-pdf-preview-0.2.8/out/extension/pdf-preview.js) > and, look for "watcher.onDidChange" and add a similar construction for > using "watcher.onDidCreate". And it works flawlessly. > I think the owner of VSLilypond is not maintaining this project anymore. > So this is not merged in the extension you can download and should be done > by hand. > > Regards, > > F. > -- *Jeff Kopmanis* Medium: https://kopmanis.medium.com GLAAC: https://www.glaac.org/ University Lowbrow Astronomers: http://umich.edu/~lowbrows Orange Can Astronomy: https://www.facebook.com/orangecanastronomy/ ** Go Green and leave this email on the Screen! **
Re: Frescobaldi... panic alternatives? (Colin Campbell)
No it's only a one way point-and-click from the pdf and not as smooth
and fast as Fresco.
It's not as complete as Fresco but when you're a vim-centric guy on
different project your're looking for interaction with your linux system
and this plugin becomes really helpful for that.
And his maintenance will evolve, for sure.
Here is some more about Simon.
https://github.com/martineausimon/lilypond-lib
Jeff
On 02/05/2024 22:16, lilypond-user-requ...@gnu.org wrote:
Send lilypond-user mailing list submissions to
lilypond-user@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
lilypond-user-requ...@gnu.org
You can reach the person managing the list at
lilypond-user-ow...@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."
Today's Topics:
1. Re: Frescobaldi... panic alternatives? (Colin Campbell)
2. Re: Frescobaldi... panic alternatives? (Kenneth Flak)
(Jeff Kopmanis)
3. Re: \after … \beforeLast? (Pierre-Luc Gauthier)
4. Re: Frescobaldi... panic alternatives? (Hajo Baess)
--
Message: 1
Date: Thu, 2 May 2024 13:59:12 -0600
From: Colin Campbell
To: Kenneth Flak , Werner LEMBERG
Cc: lilypond-user@gnu.org
Subject: Re: Frescobaldi... panic alternatives?
Message-ID:
Content-Type: text/plain; charset=UTF-8; format=flowed
This looks really good, Ken. I'm going to do a general tidy up on the
Easier Editing page, but I hope to have something up for review in a day
or two. I've installed neovim, but to save a bit of time: is the
point-and-click two-way, like Frescobaldi, or from PDF to code only?
Cheers,
Colin
On 2024-05-01 22:33, Kenneth Flak wrote:
OK, giving it a shot... Feel free to edit as needed!
Kenneth
Neovim
https://neovim.io
Neovim is a minimal text editor and fork of vim. It is highly extensible and
configurable through the vimscript and lua programming languages. Lilypond
support is provided by the nvim-lilypond-suite plugin
(https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports
playback of midi files through external programs; point-and-click when using a
supported PDF viewer; snippets and code completion when combined with other
plugins; in addition to the full range of tools available in the neovim
ecosystem. For more details on how to set it up consult the plugin's github
page. You will also want to spend some time with some of the numerous online
tutorials for learning vim/neovim to get the most out of your editing
experience.
Werner LEMBERG, May 02, 2024 at 05:49:
Maybe one of you two can provide some text for
https://lilypond.org/doc/v2.24/Documentation/web/easier-editing
It happens that my first contribution to the Lilypond documentation
was a rewrite of the Easier Editing section, some 14 years ago or
so.
Aaah :-)
If either or both care to send me their thoughts and comments, I'll
be glad to turn it into a patch.
This would be great! Thanks for the offer.
Werner
--
Message: 2
Date: Thu, 2 May 2024 16:04:17 -0400
From: Jeff Kopmanis
To: jeff
Cc: lilypond-user@gnu.org
Subject: Re: Frescobaldi... panic alternatives? (Kenneth Flak)
Message-ID:
Content-Type: text/plain; charset="utf-8"
I kicked the tires with VScode and the VSLilypond extension set, and it
worked pretty well. I'm not sure I figured out how to *automagically* update
the PDF display, all I had to do was to close and reopen the file and it
was there. Clicking on a note in the PDF viewer took me right to the text
and clicking on text and asking for it to find it in the PDF worked as
well. Syntax highlighting and completion worked nicely as well as the
formatting. Compiling worked nicely, although in some cases, my files
generate some warnings that Frescobaldi did not. I suspect different
compile options that could be worked out over time.
Overall, a reasonable replacement if Frescobaldi goes awayuntil then,
Frescobaldi is still easier.
-Jeff. :)
On Thu, May 2, 2024 at 3:57 PM jeff wrote:
Well done Kenneth! I don't have anything better to say. Maybe asking
Simon Martineau is thoughts about that. And thanks to Werner for the
proposal. It feels a little bit like I'm a part of the game, haha. I have
more than 20 scores to transpose on lilypond so I'm here to stay a little
longer and read and learn from you.
Jeff
On 02/05/2024 19:29, lilypond-user-requ...@gnu.org wrote:
Send lilypond-user mailing list submissions to
lilypond-user@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
lilypond-user-requ...@gn
Re: Frescobaldi... panic alternatives? (Kenneth Flak)
Hi Jeff. I've been using VSLilypond for VSCode for a while now and I found a solution for the annoying lack of refresh of the PDF output. It is here: https://github.com/lhl2617/VSLilyPond-PDF-preview/pull/118 Basically you have to edit a file of the Lilypond PDF preview extension (~/.vscode/extensions/lhl2617.lilypond-pdf-preview-0.2.8/out/extension/pdf-preview.js) and, look for "watcher.onDidChange" and add a similar construction for using "watcher.onDidCreate". And it works flawlessly. I think the owner of VSLilypond is not maintaining this project anymore. So this is not merged in the extension you can download and should be done by hand. Regards, F.
Re: Frescobaldi... panic alternatives?
And while you are about to extend the 'Easier Editing' section: maybe for the Mac users in particular one might want to add the combination of TeXShop/LaTeX and Skim/Preview. I had a Mac until about 12 years ago when I started to use LilyPond. That was on Mac OS 10.4, before I left the Apple universe for good in favor of Linux. But this combo worked very well for me, and both programs are still around, so that one can safely assume that it still is an option today. It is just good to know there are alternatives to Frescobaldi, and it would be convenient to have them mentioned in one place, so everyone can check them out. Am Donnerstag, dem 02.05.2024 um 04:33 + schrieb Kenneth Flak: > OK, giving it a shot... Feel free to edit as needed! > > Kenneth > > > Neovim > > https://neovim.io > > Neovim is a minimal text editor and fork of vim. It is highly > extensible and configurable through the vimscript and lua programming > languages. Lilypond support is provided by the nvim-lilypond-suite > plugin (https://github.com/martineausimon/nvim-lilypond-suite). The > plugin supports playback of midi files through external programs; > point-and-click when using a supported PDF viewer; snippets and code > completion when combined with other plugins; in addition to the full > range of tools available in the neovim ecosystem. For more details on > how to set it up consult the plugin's github page. You will also want > to spend some time with some of the numerous online tutorials for > learning vim/neovim to get the most out of your editing experience. > > > Werner LEMBERG, May 02, 2024 at 05:49: > > > > > > Maybe one of you two can provide some text for > > > > > > > > > > > > https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > > > > > It happens that my first contribution to the Lilypond > > > documentation > > > was a rewrite of the Easier Editing section, some 14 years ago or > > > so. > > > > Aaah :-) > > > > > If either or both care to send me their thoughts and comments, > > > I'll > > > be glad to turn it into a patch. > > > > This would be great! Thanks for the offer. > > > > > > Werner > > > >
Re: Frescobaldi... panic alternatives? (Kenneth Flak)
I kicked the tires with VScode and the VSLilypond extension set, and it worked pretty well. I'm not sure I figured out how to *automagically* update the PDF display, all I had to do was to close and reopen the file and it was there. Clicking on a note in the PDF viewer took me right to the text and clicking on text and asking for it to find it in the PDF worked as well. Syntax highlighting and completion worked nicely as well as the formatting. Compiling worked nicely, although in some cases, my files generate some warnings that Frescobaldi did not. I suspect different compile options that could be worked out over time. Overall, a reasonable replacement if Frescobaldi goes awayuntil then, Frescobaldi is still easier. -Jeff. :) On Thu, May 2, 2024 at 3:57 PM jeff wrote: > Well done Kenneth! I don't have anything better to say. Maybe asking > Simon Martineau is thoughts about that. And thanks to Werner for the > proposal. It feels a little bit like I'm a part of the game, haha. I have > more than 20 scores to transpose on lilypond so I'm here to stay a little > longer and read and learn from you. > Jeff > > On 02/05/2024 19:29, lilypond-user-requ...@gnu.org wrote: > > Send lilypond-user mailing list submissions to > lilypond-user@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/lilypond-user > or, via email, send a message with subject or body 'help' to > lilypond-user-requ...@gnu.org > > You can reach the person managing the list at > lilypond-user-ow...@gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lilypond-user digest..." > > > Today's Topics: > >1. Re: Frescobaldi... panic alternatives? (Raphael Mankin) >2. Re: \after … \beforeLast? (Knute Snortum) >3. Re: Frescobaldi... panic alternatives? (Kenneth Flak) >4. Re: \after … \beforeLast? (Hans Aikema) >5. Re: \after … \beforeLast? (Lukas-Fabian Moser) > > > -- > > Message: 1 > Date: Thu, 2 May 2024 18:07:33 +0100 > From: Raphael Mankin > To: lilypond-user@gnu.org > Subject: Re: Frescobaldi... panic alternatives? > Message-ID: <474001f7-e9c0-4759-8106-174a0bb41...@mankin.org.uk> > <474001f7-e9c0-4759-8106-174a0bb41...@mankin.org.uk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > This is a much better description of Neovim than exists on any of the > Neovim web-sites. They all jump straight into detail without telling one > what the whole thing is about. I struggled to work out what Neovim is, > or why I should want to use it. > > On 02/05/2024 05:33, Kenneth Flak wrote: > > OK, giving it a shot... Feel free to edit as needed! > > Kenneth > > > Neovim > https://neovim.io > > Neovim is a minimal text editor and fork of vim. It is highly extensible and > configurable through the vimscript and lua programming languages. Lilypond > support is provided by the nvim-lilypond-suite plugin > (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports > playback of midi files through external programs; point-and-click when using > a supported PDF viewer; snippets and code completion when combined with other > plugins; in addition to the full range of tools available in the neovim > ecosystem. For more details on how to set it up consult the plugin's github > page. You will also want to spend some time with some of the numerous online > tutorials for learning vim/neovim to get the most out of your editing > experience. > > > Werner LEMBERG, May 02, 2024 at 05:49: > > Maybe one of you two can provide some text for > > https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > It happens that my first contribution to the Lilypond documentation > was a rewrite of the Easier Editing section, some 14 years ago or > so. > > Aaah :-) > > > If either or both care to send me their thoughts and comments, I'll > be glad to turn it into a patch. > > This would be great! Thanks for the offer. > > > Werner > > > -- https://jefflagoutte.com/ > > -- *Jeff Kopmanis* Medium: https://kopmanis.medium.com GLAAC: https://www.glaac.org/ University Lowbrow Astronomers: http://umich.edu/~lowbrows Orange Can Astronomy: https://www.facebook.com/orangecanastronomy/ ** Go Green and leave this email on the Screen! **
Re: Frescobaldi... panic alternatives?
This looks really good, Ken. I'm going to do a general tidy up on the Easier Editing page, but I hope to have something up for review in a day or two. I've installed neovim, but to save a bit of time: is the point-and-click two-way, like Frescobaldi, or from PDF to code only? Cheers, Colin On 2024-05-01 22:33, Kenneth Flak wrote: OK, giving it a shot... Feel free to edit as needed! Kenneth Neovim https://neovim.io Neovim is a minimal text editor and fork of vim. It is highly extensible and configurable through the vimscript and lua programming languages. Lilypond support is provided by the nvim-lilypond-suite plugin (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports playback of midi files through external programs; point-and-click when using a supported PDF viewer; snippets and code completion when combined with other plugins; in addition to the full range of tools available in the neovim ecosystem. For more details on how to set it up consult the plugin's github page. You will also want to spend some time with some of the numerous online tutorials for learning vim/neovim to get the most out of your editing experience. Werner LEMBERG, May 02, 2024 at 05:49: Maybe one of you two can provide some text for https://lilypond.org/doc/v2.24/Documentation/web/easier-editing It happens that my first contribution to the Lilypond documentation was a rewrite of the Easier Editing section, some 14 years ago or so. Aaah :-) If either or both care to send me their thoughts and comments, I'll be glad to turn it into a patch. This would be great! Thanks for the offer. Werner
Re: Frescobaldi... panic alternatives? (Kenneth Flak)
Well done Kenneth! I don't have anything better to say.Maybe asking
Simon Martineau is thoughts about that.And thanks to Werner for the
proposal.It feels a little bit like I'm a part of the game, haha. I have
more than 20 scores to transpose on lilypond so I'm here to stay a
little longer and read and learn from you.
Jeff
On 02/05/2024 19:29, lilypond-user-requ...@gnu.org wrote:
Send lilypond-user mailing list submissions to
lilypond-user@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
lilypond-user-requ...@gnu.org
You can reach the person managing the list at
lilypond-user-ow...@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."
Today's Topics:
1. Re: Frescobaldi... panic alternatives? (Raphael Mankin)
2. Re: \after … \beforeLast? (Knute Snortum)
3. Re: Frescobaldi... panic alternatives? (Kenneth Flak)
4. Re: \after … \beforeLast? (Hans Aikema)
5. Re: \after … \beforeLast? (Lukas-Fabian Moser)
--
Message: 1
Date: Thu, 2 May 2024 18:07:33 +0100
From: Raphael Mankin
To:lilypond-user@gnu.org
Subject: Re: Frescobaldi... panic alternatives?
Message-ID:<474001f7-e9c0-4759-8106-174a0bb41...@mankin.org.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
This is a much better description of Neovim than exists on any of the
Neovim web-sites. They all jump straight into detail without telling one
what the whole thing is about. I struggled to work out what Neovim is,
or why I should want to use it.
On 02/05/2024 05:33, Kenneth Flak wrote:
OK, giving it a shot... Feel free to edit as needed!
Kenneth
Neovim
https://neovim.io
Neovim is a minimal text editor and fork of vim. It is highly extensible and
configurable through the vimscript and lua programming languages. Lilypond
support is provided by the nvim-lilypond-suite plugin
(https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports
playback of midi files through external programs; point-and-click when using a
supported PDF viewer; snippets and code completion when combined with other
plugins; in addition to the full range of tools available in the neovim
ecosystem. For more details on how to set it up consult the plugin's github
page. You will also want to spend some time with some of the numerous online
tutorials for learning vim/neovim to get the most out of your editing
experience.
Werner LEMBERG, May 02, 2024 at 05:49:
Maybe one of you two can provide some text for
https://lilypond.org/doc/v2.24/Documentation/web/easier-editing
It happens that my first contribution to the Lilypond documentation
was a rewrite of the Easier Editing section, some 14 years ago or
so.
Aaah :-)
If either or both care to send me their thoughts and comments, I'll
be glad to turn it into a patch.
This would be great! Thanks for the offer.
Werner
--
https://jefflagoutte.com/
Re: Frescobaldi... panic alternatives?
Glad to hear that the description is useful for you! I agree, the website is not great at onboarding new users... Best, Kenneth Raphael Mankin, May 02, 2024 at 20:07: > This is a much better description of Neovim than exists on any of the > Neovim web-sites. They all jump straight into detail without telling one > what the whole thing is about. I struggled to work out what Neovim is, > or why I should want to use it. > > On 02/05/2024 05:33, Kenneth Flak wrote: > > OK, giving it a shot... Feel free to edit as needed! > > > > Kenneth > > > > > > Neovim > > > > https://neovim.io > > > > Neovim is a minimal text editor and fork of vim. It is highly extensible > > and configurable through the vimscript and lua programming languages. > > Lilypond support is provided by the nvim-lilypond-suite plugin > > (https://github.com/martineausimon/nvim-lilypond-suite). The plugin > > supports playback of midi files through external programs; point-and-click > > when using a supported PDF viewer; snippets and code completion when > > combined with other plugins; in addition to the full range of tools > > available in the neovim ecosystem. For more details on how to set it up > > consult the plugin's github page. You will also want to spend some time > > with some of the numerous online tutorials for learning vim/neovim to get > > the most out of your editing experience. > > > > > > Werner LEMBERG, May 02, 2024 at 05:49: > >> > Maybe one of you two can provide some text for > > https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > >>> > >>> It happens that my first contribution to the Lilypond documentation > >>> was a rewrite of the Easier Editing section, some 14 years ago or > >>> so. > >> > >> Aaah :-) > >> > >>> If either or both care to send me their thoughts and comments, I'll > >>> be glad to turn it into a patch. > >> > >> This would be great! Thanks for the offer. > >> > >> > >> Werner > > > > > > > > > > > > -- > https://saturday-october-seven.com/
Re: Frescobaldi... panic alternatives?
This is a much better description of Neovim than exists on any of the Neovim web-sites. They all jump straight into detail without telling one what the whole thing is about. I struggled to work out what Neovim is, or why I should want to use it. On 02/05/2024 05:33, Kenneth Flak wrote: OK, giving it a shot... Feel free to edit as needed! Kenneth Neovim https://neovim.io Neovim is a minimal text editor and fork of vim. It is highly extensible and configurable through the vimscript and lua programming languages. Lilypond support is provided by the nvim-lilypond-suite plugin (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports playback of midi files through external programs; point-and-click when using a supported PDF viewer; snippets and code completion when combined with other plugins; in addition to the full range of tools available in the neovim ecosystem. For more details on how to set it up consult the plugin's github page. You will also want to spend some time with some of the numerous online tutorials for learning vim/neovim to get the most out of your editing experience. Werner LEMBERG, May 02, 2024 at 05:49: Maybe one of you two can provide some text for https://lilypond.org/doc/v2.24/Documentation/web/easier-editing It happens that my first contribution to the Lilypond documentation was a rewrite of the Easier Editing section, some 14 years ago or so. Aaah :-) If either or both care to send me their thoughts and comments, I'll be glad to turn it into a patch. This would be great! Thanks for the offer. Werner -- https://saturday-october-seven.com/
Re: Frescobaldi... panic alternatives?
OK, giving it a shot... Feel free to edit as needed! Kenneth Neovim https://neovim.io Neovim is a minimal text editor and fork of vim. It is highly extensible and configurable through the vimscript and lua programming languages. Lilypond support is provided by the nvim-lilypond-suite plugin (https://github.com/martineausimon/nvim-lilypond-suite). The plugin supports playback of midi files through external programs; point-and-click when using a supported PDF viewer; snippets and code completion when combined with other plugins; in addition to the full range of tools available in the neovim ecosystem. For more details on how to set it up consult the plugin's github page. You will also want to spend some time with some of the numerous online tutorials for learning vim/neovim to get the most out of your editing experience. Werner LEMBERG, May 02, 2024 at 05:49: > > >> Maybe one of you two can provide some text for > >> > >>https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > > > It happens that my first contribution to the Lilypond documentation > > was a rewrite of the Easier Editing section, some 14 years ago or > > so. > > Aaah :-) > > > If either or both care to send me their thoughts and comments, I'll > > be glad to turn it into a patch. > > This would be great! Thanks for the offer. > > > Werner
Re: Frescobaldi... panic alternatives?
>> Maybe one of you two can provide some text for >> >>https://lilypond.org/doc/v2.24/Documentation/web/easier-editing > > It happens that my first contribution to the Lilypond documentation > was a rewrite of the Easier Editing section, some 14 years ago or > so. Aaah :-) > If either or both care to send me their thoughts and comments, I'll > be glad to turn it into a patch. This would be great! Thanks for the offer. Werner
Re: Frescobaldi... panic alternatives?
On 2024-05-01 12:38, Werner LEMBERG wrote: Maybe one of you two can provide some text for https://lilypond.org/doc/v2.24/Documentation/web/easier-editing It happens that my first contribution to the Lilypond documentation was a rewrite of the Easier Editing section, some 14 years ago or so. If either or both care to send me their thoughts and comments, I'll be glad to turn it into a patch. Cheers, Colin
Re: Frescobaldi... panic alternatives?
> Yes, I also use that combo. It's fantastic, but you'd have to be > willing to invest some time to climb the admittedly steep learning > curve of (neo)vim. However, it's a time investment that pays off > massively, so I recommend it heartily! Maybe one of you two can provide some text for https://lilypond.org/doc/v2.24/Documentation/web/easier-editing ? Werner
Re: Frescobaldi... panic alternatives?
Yes, I also use that combo. It's fantastic, but you'd have to be willing to invest some time to climb the admittedly steep learning curve of (neo)vim. However, it's a time investment that pays off massively, so I recommend it heartily! Kenneth Roosna & Flak Contemporary Dance & Music https://roosnaflak.com Sent from Proton Mail Android Original Message On 5/1/24 20:26, jeff wrote: > Hi,I live in Paris. I'm a composer. This discussion is really > interesting. I came back to lilypond a few month ago because there is no > language better than Lilypond dealing with code. I'm not interested in > those WYSIWYG. But I also came back because I have a really good tool > for Lilypond you didn't mention : neovim + nvim-lilypond-suite by > Martineau Simon. > > https://github.com/martineausimon/nvim-lilypond-suite > > This plugin blow my mind ! > > Is there someone who experienced it and feel the same enjoyment ? > > Happy to be a part of your community again, cheers. > > Jeff Lagoutte > > > On 30/04/2024 22:33, lilypond-user-requ...@gnu.org wrote: > > Send lilypond-user mailing list submissions to > >lilypond-user@gnu.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > >https://lists.gnu.org/mailman/listinfo/lilypond-user > > or, via email, send a message with subject or body 'help' to > >lilypond-user-requ...@gnu.org > > > > You can reach the person managing the list at > >lilypond-user-ow...@gnu.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of lilypond-user digest..." > > > > > > Today's Topics: > > > > 1. Re: Fw: Frescobaldi ... panic alternatives? (Paolo Prete) > > 2. RE: Fw: Frescobaldi ... panic alternatives? (Mark Stephen Mrotek) > > > > > > ------ > > > > Message: 1 > > Date: Tue, 30 Apr 2024 22:08:29 +0200 > > From: Paolo Prete > > To: Mark Stephen Mrotek , lilypond-user > > > > Subject: Re: Fw: Frescobaldi ... panic alternatives? > > Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > > > You'll find all you need at the main page: > > > > https://github.com/paopre/Spontini > > > > Cheers > > > > On Tue, Apr 30, 2024 at 10:04 PM Mark Stephen Mrotek > > wrote: > > > >> Paolo, > >> > >> > >> > >> Installation instructions? > >> Learning/notation manual? > >> > >> I want to try it. > >> > >> > >> > >> Mark > >> > >> > >> > >> *From:* lilypond-user-bounces+carsonmark=ca.rr@gnu.org > >> *On Behalf Of *Paolo > >> Prete > >> *Sent:* Tuesday, April 30, 2024 12:58 PM > >> *To:* Dirck Nagy ; lilypond-user > >> *Subject:* Re: Fw: Frescobaldi ... panic alternatives? > >> > >> > >> > >> FYI I just made a new release of Spontini editor, with the most recent > >> changes (most notably: support for recent Lilypond versions) > >> > >> As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD > >> should avoid bad surprises. When I say "huge", I mean it. > >> > >> I always hope that someone decides to host the application, so that it > >> provides the same service that LilyBin previously offered. > >> > >> Please note that you don't have to install anything. Nor the editor, nor > >> LilyPond, and you can switch between multiple LilyPond versions. > >> > >> Anyway, I'm currently the only developer and maintainer of the software, > >> and I need collaboration (most notably for testing). Without it, I'm > forced > >> to mark my releases as "alfa" (but it should work...) > >> > >> > >> > >> https://github.com/paopre/Spontini/releases/tag/1.23_alfa > >> > >> > >> > >> > >> > >> On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete wrote: > >> > >> > >> > >> > >> > >> On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote: > >> > >> Hi all > >> > >> > >> > >> Reading that last thread about Frescobaldi and its possible disappearance > >> from Mac is causing me to panic. Jean, I
Frescobaldi... panic alternatives?
Hi,I live in Paris. I'm a composer. This discussion is really
interesting. I came back to lilypond a few month ago because there is no
language better than Lilypond dealing with code. I'm not interested in
those WYSIWYG. But I also came back because I have a really good tool
for Lilypond you didn't mention : neovim + nvim-lilypond-suite by
Martineau Simon.
https://github.com/martineausimon/nvim-lilypond-suite
This plugin blow my mind !
Is there someone who experienced it and feel the same enjoyment ?
Happy to be a part of your community again, cheers.
Jeff Lagoutte
On 30/04/2024 22:33, lilypond-user-requ...@gnu.org wrote:
Send lilypond-user mailing list submissions to
lilypond-user@gnu.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
lilypond-user-requ...@gnu.org
You can reach the person managing the list at
lilypond-user-ow...@gnu.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."
Today's Topics:
1. Re: Fw: Frescobaldi ... panic alternatives? (Paolo Prete)
2. RE: Fw: Frescobaldi ... panic alternatives? (Mark Stephen Mrotek)
--
Message: 1
Date: Tue, 30 Apr 2024 22:08:29 +0200
From: Paolo Prete
To: Mark Stephen Mrotek , lilypond-user
Subject: Re: Fw: Frescobaldi ... panic alternatives?
Message-ID:
Content-Type: text/plain; charset="utf-8"
You'll find all you need at the main page:
https://github.com/paopre/Spontini
Cheers
On Tue, Apr 30, 2024 at 10:04 PM Mark Stephen Mrotek
wrote:
Paolo,
Installation instructions?
Learning/notation manual?
I want to try it.
Mark
*From:* lilypond-user-bounces+carsonmark=ca.rr@gnu.org
*On Behalf Of *Paolo
Prete
*Sent:* Tuesday, April 30, 2024 12:58 PM
*To:* Dirck Nagy ; lilypond-user
*Subject:* Re: Fw: Frescobaldi ... panic alternatives?
FYI I just made a new release of Spontini editor, with the most recent
changes (most notably: support for recent Lilypond versions)
As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD
should avoid bad surprises. When I say "huge", I mean it.
I always hope that someone decides to host the application, so that it
provides the same service that LilyBin previously offered.
Please note that you don't have to install anything. Nor the editor, nor
LilyPond, and you can switch between multiple LilyPond versions.
Anyway, I'm currently the only developer and maintainer of the software,
and I need collaboration (most notably for testing). Without it, I'm forced
to mark my releases as "alfa" (but it should work...)
https://github.com/paopre/Spontini/releases/tag/1.23_alfa
On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete wrote:
On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote:
Hi all
Reading that last thread about Frescobaldi and its possible disappearance
from Mac is causing me to panic. Jean, I did not realize that you were the
last person to seriously work on Frescobaldi / Mac.
I use Mac exclusively, and Frescobaldi / Lilypond is very important to me.
FYI, what I like the most about Frescobaldi are:
- Templates and wizards
- Snippets
- Point and Click selection
- Syntax highlighting
If Frescobaldi for Mac does indeed vanish, what are my alternatives for a
Lilypond editor?
Hi,
Although https://github.com/paopre/Spontini is focused on _very
different_ tasks than Frescobaldi, it has the features you just mentioned
(they are exposed in a somewhat different way, but they should work),
including code completion
I could not extensively test it in the past months, nor I own a Mac, but
thanks to CI/CD it should work on newer versions.
I'm planning to make a new release in the next few weeks.
Also, at the moment there are no active contributors for it. Therefore,
any help is really appreciated...
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.gnu.org/archive/html/lilypond-user/attachments/20240430/e8e0ad62/attachment.htm>
--
Message: 2
Date: Tue, 30 Apr 2024 13:33:28 -0700
From: "Mark Stephen Mrotek"
To: "'Paolo Prete'" , "'lilypond-user'"
Subject: RE: Fw: Frescobaldi ... panic alternatives?
Message-ID: <009301da9b3d$a935da00$fba18e00$@ca.rr.com>
Content-Type: text/plain; charset="utf-8"
Paolo,
Thank you.
Mark
From: Paolo Prete
Sent: Tuesday, April 30, 2024 1:08 PM
To: Mark Stephen Mrotek ; lilypond-user
Subject: Re: Fw: Frescobaldi ... panic alternatives?
You'll find all you need at the main page:
https://github.com/paopre/Spontini
Cheers
On Tue, Apr 30, 2024 at 10:04 PM Mark Stephen Mr
RE: Fw: Frescobaldi ... panic alternatives?
Paolo, Thank you. Mark From: Paolo Prete Sent: Tuesday, April 30, 2024 1:08 PM To: Mark Stephen Mrotek ; lilypond-user Subject: Re: Fw: Frescobaldi ... panic alternatives? You'll find all you need at the main page: https://github.com/paopre/Spontini Cheers On Tue, Apr 30, 2024 at 10:04 PM Mark Stephen Mrotek mailto:carsonm...@ca.rr.com> > wrote: Paolo, Installation instructions? Learning/notation manual? I want to try it. Mark From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org <mailto:ca.rr@gnu.org> mailto:ca.rr@gnu.org> > On Behalf Of Paolo Prete Sent: Tuesday, April 30, 2024 12:58 PM To: Dirck Nagy mailto:dn...@uwlax.edu> >; lilypond-user mailto:lilypond-user@gnu.org> > Subject: Re: Fw: Frescobaldi ... panic alternatives? FYI I just made a new release of Spontini editor, with the most recent changes (most notably: support for recent Lilypond versions) As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD should avoid bad surprises. When I say "huge", I mean it. I always hope that someone decides to host the application, so that it provides the same service that LilyBin previously offered. Please note that you don't have to install anything. Nor the editor, nor LilyPond, and you can switch between multiple LilyPond versions. Anyway, I'm currently the only developer and maintainer of the software, and I need collaboration (most notably for testing). Without it, I'm forced to mark my releases as "alfa" (but it should work...) https://github.com/paopre/Spontini/releases/tag/1.23_alfa On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete mailto:paolopr...@gmail.com> > wrote: On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy mailto:dn...@uwlax.edu> > wrote: Hi all Reading that last thread about Frescobaldi and its possible disappearance from Mac is causing me to panic. Jean, I did not realize that you were the last person to seriously work on Frescobaldi / Mac. I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. FYI, what I like the most about Frescobaldi are: * Templates and wizards * Snippets * Point and Click selection * Syntax highlighting If Frescobaldi for Mac does indeed vanish, what are my alternatives for a Lilypond editor? Hi, Although https://github.com/paopre/Spontini is focused on _very different_ tasks than Frescobaldi, it has the features you just mentioned (they are exposed in a somewhat different way, but they should work), including code completion I could not extensively test it in the past months, nor I own a Mac, but thanks to CI/CD it should work on newer versions. I'm planning to make a new release in the next few weeks. Also, at the moment there are no active contributors for it. Therefore, any help is really appreciated...
Re: Fw: Frescobaldi ... panic alternatives?
You'll find all you need at the main page: https://github.com/paopre/Spontini Cheers On Tue, Apr 30, 2024 at 10:04 PM Mark Stephen Mrotek wrote: > Paolo, > > > > Installation instructions? > Learning/notation manual? > > I want to try it. > > > > Mark > > > > *From:* lilypond-user-bounces+carsonmark=ca.rr@gnu.org > *On Behalf Of *Paolo > Prete > *Sent:* Tuesday, April 30, 2024 12:58 PM > *To:* Dirck Nagy ; lilypond-user > *Subject:* Re: Fw: Frescobaldi ... panic alternatives? > > > > FYI I just made a new release of Spontini editor, with the most recent > changes (most notably: support for recent Lilypond versions) > > As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD > should avoid bad surprises. When I say "huge", I mean it. > > I always hope that someone decides to host the application, so that it > provides the same service that LilyBin previously offered. > > Please note that you don't have to install anything. Nor the editor, nor > LilyPond, and you can switch between multiple LilyPond versions. > > Anyway, I'm currently the only developer and maintainer of the software, > and I need collaboration (most notably for testing). Without it, I'm forced > to mark my releases as "alfa" (but it should work...) > > > > https://github.com/paopre/Spontini/releases/tag/1.23_alfa > > > > > > On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete wrote: > > > > > > On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote: > > Hi all > > > > Reading that last thread about Frescobaldi and its possible disappearance > from Mac is causing me to panic. Jean, I did not realize that you were the > last person to seriously work on Frescobaldi / Mac. > > > > I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. > > > > FYI, what I like the most about Frescobaldi are: > > > >- Templates and wizards >- Snippets >- Point and Click selection >- Syntax highlighting > > > > If Frescobaldi for Mac does indeed vanish, what are my alternatives for a > Lilypond editor? > > > > > > Hi, > > > > Although https://github.com/paopre/Spontini is focused on _very > different_ tasks than Frescobaldi, it has the features you just mentioned > (they are exposed in a somewhat different way, but they should work), > including code completion > > I could not extensively test it in the past months, nor I own a Mac, but > thanks to CI/CD it should work on newer versions. > > I'm planning to make a new release in the next few weeks. > > Also, at the moment there are no active contributors for it. Therefore, > any help is really appreciated... > > > > > >
RE: Fw: Frescobaldi ... panic alternatives?
Paolo, Installation instructions? Learning/notation manual? I want to try it. Mark From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org On Behalf Of Paolo Prete Sent: Tuesday, April 30, 2024 12:58 PM To: Dirck Nagy ; lilypond-user Subject: Re: Fw: Frescobaldi ... panic alternatives? FYI I just made a new release of Spontini editor, with the most recent changes (most notably: support for recent Lilypond versions) As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD should avoid bad surprises. When I say "huge", I mean it. I always hope that someone decides to host the application, so that it provides the same service that LilyBin previously offered. Please note that you don't have to install anything. Nor the editor, nor LilyPond, and you can switch between multiple LilyPond versions. Anyway, I'm currently the only developer and maintainer of the software, and I need collaboration (most notably for testing). Without it, I'm forced to mark my releases as "alfa" (but it should work...) https://github.com/paopre/Spontini/releases/tag/1.23_alfa On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete mailto:paolopr...@gmail.com> > wrote: On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy mailto:dn...@uwlax.edu> > wrote: Hi all Reading that last thread about Frescobaldi and its possible disappearance from Mac is causing me to panic. Jean, I did not realize that you were the last person to seriously work on Frescobaldi / Mac. I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. FYI, what I like the most about Frescobaldi are: * Templates and wizards * Snippets * Point and Click selection * Syntax highlighting If Frescobaldi for Mac does indeed vanish, what are my alternatives for a Lilypond editor? Hi, Although https://github.com/paopre/Spontini is focused on _very different_ tasks than Frescobaldi, it has the features you just mentioned (they are exposed in a somewhat different way, but they should work), including code completion I could not extensively test it in the past months, nor I own a Mac, but thanks to CI/CD it should work on newer versions. I'm planning to make a new release in the next few weeks. Also, at the moment there are no active contributors for it. Therefore, any help is really appreciated...
Re: Fw: Frescobaldi ... panic alternatives?
FYI I just made a new release of Spontini editor, with the most recent changes (most notably: support for recent Lilypond versions) As mentioned before, I don't own a MacOS, but the HUGE implemented CI/CD should avoid bad surprises. When I say "huge", I mean it. I always hope that someone decides to host the application, so that it provides the same service that LilyBin previously offered. Please note that you don't have to install anything. Nor the editor, nor LilyPond, and you can switch between multiple LilyPond versions. Anyway, I'm currently the only developer and maintainer of the software, and I need collaboration (most notably for testing). Without it, I'm forced to mark my releases as "alfa" (but it should work...) https://github.com/paopre/Spontini/releases/tag/1.23_alfa On Tue, Apr 30, 2024 at 12:56 PM Paolo Prete wrote: > > > On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote: > >> Hi all >> >> Reading that last thread about Frescobaldi and its possible disappearance >> from Mac is causing me to panic. Jean, I did not realize that you were the >> last person to seriously work on Frescobaldi / Mac. >> >> >> I use Mac exclusively, and Frescobaldi / Lilypond is very important to >> me. >> >> >> FYI, what I like the most about Frescobaldi are: >> >> >> >>- >> >>Templates and wizards >>- >> >>Snippets >>- >> >>Point and Click selection >>- >> >>Syntax highlighting >> >> >> If Frescobaldi for Mac does indeed vanish, what are my alternatives for a >> Lilypond editor? >> >> >> > Hi, > > Although https://github.com/paopre/Spontini is focused on _very > different_ tasks than Frescobaldi, it has the features you just mentioned > (they are exposed in a somewhat different way, but they should work), > including code completion > I could not extensively test it in the past months, nor I own a Mac, but > thanks to CI/CD it should work on newer versions. > I'm planning to make a new release in the next few weeks. > Also, at the moment there are no active contributors for it. Therefore, > any help is really appreciated... > > >
Re: Fw: Frescobaldi ... panic alternatives?
On 2024-04-30 10:05 am, Karlin High wrote: On 4/30/2024 10:25 AM, Jennifer Doering wrote: What happened to the Frescobaldi dev? Just doesn't have time to maintain it anymore? Link to past discussion: <https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00131.html> His software development activity appears reduced after a health crisis in 2021. Can relate to that. Had open heart surgery myself last year and still recovering, in and out of hospital. Wishing all the best to him and his family. -- Aaron Hill
Re: Fw: Frescobaldi ... panic alternatives?
On 4/30/2024 10:25 AM, Jennifer Doering wrote: What happened to the Frescobaldi dev? Just doesn't have time to maintain it anymore? Link to past discussion: <https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00131.html> His software development activity appears reduced after a health crisis in 2021. -- Karlin High Missouri, USA
Re: Fw: Frescobaldi ... panic alternatives?
What happened to the Frescobaldi dev? Just doesn't have time to maintain it anymore?
Re: Fw: Frescobaldi ... panic alternatives?
Hi all, There are various alternatives around at least for Linux users, but there will certainly be different ones available for the Mac users as well. And who knows: maybe Frescobaldi will survive after all. And if it may stop working one day, it is good to know that at least you are not completely left in the wild. I have checked out the following ones for Linux: 1. Spontini (not so known maybe, but definitely worth a try) 2. Kate/Okular as a "team" with one-way point-and-click from Okular to Kate 3. Visual Studio Code with its LilyPond plugins/extensions All three are not exactly like Frescobaldi, but can certainly amply be adapted to individual needs into a good workspace. And then, of course, there is also lilypond-book, which I personally find a bit complicated - at least when you come from Frescobaldi. Steeper learning curve, but not impossible if you are determined and open to something new. So: don't panic (do not forget the towel either) and let us keep using Frescobaldi and enjoy as long as it will exist... Am Dienstag, dem 30.04.2024 um 12:56 +0200 schrieb Paolo Prete: > On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote: > > > Hi all > > > > Reading that last thread about Frescobaldi and its possible > > disappearance > > from Mac is causing me to panic. Jean, I did not realize that you > > were the > > last person to seriously work on Frescobaldi / Mac. > > > > > > I use Mac exclusively, and Frescobaldi / Lilypond is very important > > to me. > > > > > > FYI, what I like the most about Frescobaldi are: > > > > > > > > - > > > > Templates and wizards > > - > > > > Snippets > > - > > > > Point and Click selection > > - > > > > Syntax highlighting > > > > > > If Frescobaldi for Mac does indeed vanish, what are my alternatives > > for a > > Lilypond editor? > > > > > > > Hi, > > Although https://github.com/paopre/Spontini is focused on _very > different_ > tasks than Frescobaldi, it has the features you just mentioned (they > are > exposed in a somewhat different way, but they should work), including > code > completion > I could not extensively test it in the past months, nor I own a Mac, > but > thanks to CI/CD it should work on newer versions. > I'm planning to make a new release in the next few weeks. > Also, at the moment there are no active contributors for it. > Therefore, any > help is really appreciated...
Re: Fw: Frescobaldi ... panic alternatives?
On Tue, Apr 30, 2024 at 6:45 AM Dirck Nagy wrote: > Hi all > > Reading that last thread about Frescobaldi and its possible disappearance > from Mac is causing me to panic. Jean, I did not realize that you were the > last person to seriously work on Frescobaldi / Mac. > > > I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. > > > FYI, what I like the most about Frescobaldi are: > > > >- > >Templates and wizards >- > >Snippets >- > >Point and Click selection >- > >Syntax highlighting > > > If Frescobaldi for Mac does indeed vanish, what are my alternatives for a > Lilypond editor? > > > Hi, Although https://github.com/paopre/Spontini is focused on _very different_ tasks than Frescobaldi, it has the features you just mentioned (they are exposed in a somewhat different way, but they should work), including code completion I could not extensively test it in the past months, nor I own a Mac, but thanks to CI/CD it should work on newer versions. I'm planning to make a new release in the next few weeks. Also, at the moment there are no active contributors for it. Therefore, any help is really appreciated...
Re: Fw: Frescobaldi ... panic alternatives?
VS Code also provide point and click. Snippets and wizards are tipical features for any other programming language in VS Code. It should not be too difficult to write them for lilypond. I understand that it can be difficult to find the developers and mantainers to keep Frescobaldi runnig, but not so difficult to implement such features in VS Code, I believe. That would be my case, for instamve, and provably other it could be the same fornother people: I develope with VS Code and participate in other communities and I might help on developing the lilypond plugins, but I don't have enough knowledge to develope Frescobaldi. Robert On 30 d’abr. de 2024, 8:11, at 8:11, Jean Abou Samra wrote: > >> FYI, what I like the most about Frescobaldi are: >> >> * Templates and wizards >> * Snippets >> * Point and Click selection >> * Syntax highlighting >> >> If Frescobaldi for Mac does indeed vanish, what are my alternatives >for a >> Lilypond editor? > >Syntax highlighting should be doable in Emacs, VS Code or such. Point >and click >can be arranged with various PDF viewers (see the LilyPond Usage >manual). >The other two only exist in Frescobaldi AFAIK. > >> Also, how can I help? (I'm not a programmer at all...) > > >Thanks, but you cannot really help in a way meaningful for the current >issues without programming knowledge. > >Also, for the record, Frescobaldi needs developers, but perhaps >even more importantly, it needs maintainers, i.e., people who will >not just work on a technical problem because they were told >it's important, but also proactively and autonomously respond >to GitHub issues and support questions, update the website, >figure out what parts of the code need regular maintenance like >lists of LilyPond commands and maintain them, monitor the >frescobaldi package in major Linux distros, and so on. >Unfortunately, it can be really hard to find maintainers (even for >projects that the entire world infrastructure relies on, cf. xz…). > >Best, >Jean
Re: Fw: Frescobaldi ... panic alternatives?
> FYI, what I like the most about Frescobaldi are: > > * Templates and wizards > * Snippets > * Point and Click selection > * Syntax highlighting > > If Frescobaldi for Mac does indeed vanish, what are my alternatives for a > Lilypond editor? Syntax highlighting should be doable in Emacs, VS Code or such. Point and click can be arranged with various PDF viewers (see the LilyPond Usage manual). The other two only exist in Frescobaldi AFAIK. > Also, how can I help? (I'm not a programmer at all...) Thanks, but you cannot really help in a way meaningful for the current issues without programming knowledge. Also, for the record, Frescobaldi needs developers, but perhaps even more importantly, it needs maintainers, i.e., people who will not just work on a technical problem because they were told it's important, but also proactively and autonomously respond to GitHub issues and support questions, update the website, figure out what parts of the code need regular maintenance like lists of LilyPond commands and maintain them, monitor the frescobaldi package in major Linux distros, and so on. Unfortunately, it can be really hard to find maintainers (even for projects that the entire world infrastructure relies on, cf. xz…). Best, Jean signature.asc Description: This is a digitally signed message part
Re: Frescobaldi ... panic alternatives?
> With not too much work, you could get emacs to do all of that I > think. Well, it would be great if someone could convert the LilyPond mode of Emacs so that it uses the new 'tree-sitter' interface: https://tree-sitter.github.io/tree-sitter/ (look at the 'Playground' link to get a feeling what this tool is good for). This would allow seamless support of both Scheme and LilyPond syntax simultaneously... While there already is tree-sitter syntax support for Scheme (https://github.com/6cdh/tree-sitter-scheme, including some Guile extensions), no such thing exists yet for LilyPond syntax, which makes the conversion a larger undertaking, unfortunately. Werner
Re: Fw: Frescobaldi ... panic alternatives?
With not too much work, you could get emacs to do all of that I think. But my guess is that there's no reason to panic yet. I don't see frescobaldi magically disappearing. On Mon, Apr 29, 2024, 10:45 PM Dirck Nagy wrote: > Hi all > > Reading that last thread about Frescobaldi and its possible disappearance > from Mac is causing me to panic. Jean, I did not realize that you were the > last person to seriously work on Frescobaldi / Mac. > > > I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. > > > FYI, what I like the most about Frescobaldi are: > > > >- > >Templates and wizards >- > >Snippets >- > >Point and Click selection >- > >Syntax highlighting > > > If Frescobaldi for Mac does indeed vanish, what are my alternatives for a > Lilypond editor? > > > Also, how can I help? (I'm not a programmer at all...) > > > Peace! and thank you for all your work! > > > Dirck >
Fw: Frescobaldi ... panic alternatives?
Hi all Reading that last thread about Frescobaldi and its possible disappearance from Mac is causing me to panic. Jean, I did not realize that you were the last person to seriously work on Frescobaldi / Mac. I use Mac exclusively, and Frescobaldi / Lilypond is very important to me. FYI, what I like the most about Frescobaldi are: * Templates and wizards * Snippets * Point and Click selection * Syntax highlighting If Frescobaldi for Mac does indeed vanish, what are my alternatives for a Lilypond editor? Also, how can I help? (I'm not a programmer at all...) Peace! and thank you for all your work! Dirck
Re: Frescobaldi?
Hi Kieren, On Mon, Apr 29, 2024 at 3:12 PM Kieren MacMillan < kie...@kierenmacmillan.info> wrote: > > 1. Any thoughts about what the optimal package is? > I use TexStudio for all my TeX work, and it's excellent. Here: https://texstudio.sourceforge.net (shoutout to extremely old-skool sourceforge hosting) > > 2. Is there any benefit/interest in trying to duplicate the most > important/useful functionality of Frescobaldi (e.g. two-way point-and-click > navigation) into a LaTeX-based IDE? > TexStudio let's you right-click the pdf output and select "go to source", so presumably the functionality is there. The only issue is that the lilypond code isn't interpreted by LaTeX directly, but called through lyluatex. I worked with Urs a few years back to produce an architecture for editing multi-volume Lily file trees, with excellent output, all called through LaTeX. I'm not sure if the project is still hosted anywhere (it was residing on Urs' private github/gitlab server), but it worked well. I don't use any tools in frescobaldi besides the point-and-click functionality that wouldn't already be available in any modern TeX IDE. But it seems my issues with frescobaldi are due to some problems with my qtwebengine installation, so I might be able to get them resolved relatively easily. Updating it to use PyQt6 would be an important long-term sustainability goal, but at least it's not a complete blocker for me (for now). Cheers, A
Re: Frescobaldi?
Hi all, > Fortunately for me, I'm using lualatex already, so that worked. I do indeed > lose point-and-click, but it's good to know that if frescobaldi stops working > I at least have a backup. I’ve been considering moving fully to *lula*tex ever since Urs demonstrated his lyluatexmp (https://github.com/uliska/lyluatexmp) at the Salzburg conference. 1. Any thoughts about what the optimal package is? 2. Is there any benefit/interest in trying to duplicate the most important/useful functionality of Frescobaldi (e.g. two-way point-and-click navigation) into a LaTeX-based IDE? Cheers, Kieren. __ My work day may look different than your work day. Please do not feel obligated to read or respond to this email outside of your normal working hours.
Re: Frescobaldi?
Hi Jean,
On Mon, Apr 29, 2024 at 1:17 PM Jean Abou Samra wrote:
>
> lilypond-book isn't called by LaTeX, it's a preprocessor that you first
> have
> to run on a .lytex file to get a .tex file, then you compile that .tex file
> with TeX.
>
> Consider lyLuaTeX, which is an alternative that runs inside the TeX process
> directly, but requires LuaTeX. You can specify the path to the LilyPond
> executable with \usepackage[program=/path/to/bin/lilypond]{lyluatex}.
> See https://ctan.org/pkg/lyluatex
>
>
> Fortunately for me, I'm using lualatex already, so that worked. I do
indeed lose point-and-click, but it's good to know that if frescobaldi
stops working I at least have a backup. Thanks for the help!
N. Andrew Walsh
er/ihn/ihm/sein | he/him/his
Berlin
Re: Frescobaldi?
> yeah, I just had the package-manager in gentoo downgrade to the previous
> version of snappy, and then filed a bug with gentoo. It's a workaround for
> now.
>
> As another workaround, I'm trying to get my latex editor to use lilypond-book,
> but since it's on a nonstandard path, I don't seem able to use it. How do you
> integrate lilypond-book into a LaTeX toolchain?
lilypond-book isn't called by LaTeX, it's a preprocessor that you first have
to run on a .lytex file to get a .tex file, then you compile that .tex file
with TeX.
Consider lyLuaTeX, which is an alternative that runs inside the TeX process
directly, but requires LuaTeX. You can specify the path to the LilyPond
executable with \usepackage[program=/path/to/bin/lilypond]{lyluatex}.
See https://ctan.org/pkg/lyluatex
With both methods, you will lose point-and-click, though.
signature.asc
Description: This is a digitally signed message part
Re: Frescobaldi?
Hi Jean, yeah, I just had the package-manager in gentoo downgrade to the previous version of snappy, and then filed a bug with gentoo. It's a workaround for now. As another workaround, I'm trying to get my latex editor to use lilypond-book, but since it's on a nonstandard path, I don't seem able to use it. How do you integrate lilypond-book into a LaTeX toolchain? Cheers, N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin On Mon, Apr 29, 2024 at 12:35 PM Jean Abou Samra wrote: > > > It gets a bit more complicated now. See this bug: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 > > > > That bug is for freeBSD, but I expect it applies to other > > distros as well (it certainly applies to gentoo, as I'm > > getting the exact same error). In short, snappy (an archiver) > > was updated to version 1.2.0 a few days ago, and it contains > > symbols that aren't defined in earlier versions. > > > Well, new symbols shouldn't be a problem (removed symbols would be, > if other packages expect them). Based on > https://github.com/conda-forge/snappy-feedstock/issues/35 > what apparently happened is that the snappy developers released > 1.2.0 but forgot to update the library soname even though they > changed function signatures. The lookup of that symbol > > _ZN6snappy11RawCompressEPKcmPcPm > > which is the mangled version of > > snappy::RawCompress(char const*, unsigned long, char*, unsigned long*) > > fails because the new version only has a (mangled) symbol for > > snappy::RawCompress(char const*, unsigned long, char*, unsigned long*, > snappy::CompressionOptions) > > That's a bug in snappy, and it will affect things other than qtwebengine > too… > You should probably ask the Gentoo developers to revert to the previous > version > or patch it. There's probably a way to ask the Gentoo package manager > to downgrade the package, too. > >
Re: Frescobaldi?
> It gets a bit more complicated now. See this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 > > That bug is for freeBSD, but I expect it applies to other > distros as well (it certainly applies to gentoo, as I'm > getting the exact same error). In short, snappy (an archiver) > was updated to version 1.2.0 a few days ago, and it contains > symbols that aren't defined in earlier versions. Well, new symbols shouldn't be a problem (removed symbols would be, if other packages expect them). Based on https://github.com/conda-forge/snappy-feedstock/issues/35 what apparently happened is that the snappy developers released 1.2.0 but forgot to update the library soname even though they changed function signatures. The lookup of that symbol _ZN6snappy11RawCompressEPKcmPcPm which is the mangled version of snappy::RawCompress(char const*, unsigned long, char*, unsigned long*) fails because the new version only has a (mangled) symbol for snappy::RawCompress(char const*, unsigned long, char*, unsigned long*, snappy::CompressionOptions) That's a bug in snappy, and it will affect things other than qtwebengine too… You should probably ask the Gentoo developers to revert to the previous version or patch it. There's probably a way to ask the Gentoo package manager to downgrade the package, too. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
OK, so maybe I should just move lilypond work into my LaTeX IDE for the time being. Since my lilypond installation isn't on the system PATH, how do I include it as part of a .tex document to get access to the lilypond-book commands? Cheers, N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin On Mon, Apr 29, 2024 at 12:16 PM Mats-Olof Liljegren wrote: > I use it on Sonoma without issues. > > Med vänlig hälsning / Kind regards > *Mats-Olof Liljegren* > > *e-pro* > Oskarsvägen 11B > 702 14 Örebro > Tel 070 360 19 19 > e-post m...@e-pro.se > web: http://e-pro.se > > 29 apr. 2024 kl. 11:40 skrev Robert Garrigos : > > I cannot use Frescobaldi on Mac Sonoma (not working), so I went for Visual > Studio Code, with some lilypond plugins, and I have to say that it offers > everything I need > > Robert > > El 28 abr. 2024, a les 13:57, Jean Abou Samra va > escriure: > > Is Frescobaldi the most common tool on Linux, or what do the majority of > Lilypond users use? > > > Frescobaldi is the most common LilyPond editor, on all OSes. > > > > >
Re: Frescobaldi?
> Would it maybe make things a bit easier to leave the whole MacOS > business aside and take care of the Linux-specific stuff first? Linux is not really causing us any specific problems. Packaging is a lot easier, thanks to Linux distributions and Flatpak. The only wrinkle is the oddities on Wayland that are related to Qt 5. > And what actually about Windows - out of curiosity. Windows is… a can of worms of its own. The Windows installers for the past few releases were built by a user (@19joho66 on GitHub) who apparently manages to them work by moving shared libraries around manually :-( > I myself am a Linux user (Mint), and so far Frescobaldi is still running > flawlessly. > And - another question out of curiosity: Could it be a workaround (if > Qt5 would be officially retired and no longer be available in the repos > of the "big" distros like Mint, Ubuntu and the like) if one used a > distro for older computers which might stick to Qt5 much longer? I may be wrong, but I don't really foresee distros retiring Qt 5 soon since Frescobaldi should not be the only piece of software still requiring it (as Qt is so widely used). In any case, the Flatpak package can still ship it. What's more likely to happen is that changes in the desktop environments (like Xorg → Wayland) make Qt 5 work less and less well. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
I use it on Sonoma without issues. Med vänlig hälsning / Kind regards Mats-Olof Liljegren e-pro Oskarsvägen 11B 702 14 Örebro Tel 070 360 19 19 e-post m...@e-pro.se web: http://e-pro.se > 29 apr. 2024 kl. 11:40 skrev Robert Garrigos : > > I cannot use Frescobaldi on Mac Sonoma (not working), so I went for Visual > Studio Code, with some lilypond plugins, and I have to say that it offers > everything I need > > Robert > >> El 28 abr. 2024, a les 13:57, Jean Abou Samra va >> escriure: >> >>> Is Frescobaldi the most common tool on Linux, or what do the majority of >>> Lilypond users use? >> >> Frescobaldi is the most common LilyPond editor, on all OSes. >> >> >
Re: Frescobaldi?
I cannot use Frescobaldi on Mac Sonoma (not working), so I went for Visual Studio Code, with some lilypond plugins, and I have to say that it offers everything I need Robert > El 28 abr. 2024, a les 13:57, Jean Abou Samra va > escriure: > >> Is Frescobaldi the most common tool on Linux, or what do the majority of >> Lilypond users use? > > Frescobaldi is the most common LilyPond editor, on all OSes. > >
Re: Frescobaldi?
It gets a bit more complicated now. See this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 That bug is for freeBSD, but I expect it applies to other distros as well (it certainly applies to gentoo, as I'm getting the exact same error). In short, snappy (an archiver) was updated to version 1.2.0 a few days ago, and it contains symbols that aren't defined in earlier versions. So qtwebengine-5* will fail on systems with older versions of qtwebengine but newer versions of snappy. My error message is this: -- $ frescobaldi Traceback (most recent call last): File "/usr/lib/python-exec/python3.11/frescobaldi", line 42, in import main File "/usr/lib/python3.11/site-packages/frescobaldi_app/main.py", line 34, in import app # Instantiate global signals etc ^^ File "/usr/lib/python3.11/site-packages/frescobaldi_app/app.py", line 38, in import PyQt5.QtWebEngineWidgets ImportError: /usr/lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm ---- So now frescobaldi won't run on my system at all. I sure hope we can fix this soon. I've talked to a colleague of mine who does python and UI development, and they're going to have a look at the code and see what needs updating to work with Qt6. Cheers, N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin On Mon, Apr 29, 2024 at 10:49 AM Hajo Baess wrote: > Would it maybe make things a bit easier to leave the whole MacOS > business aside and take care of the Linux-specific stuff first? And > what actually about Windows - out of curiosity. I myself am a Linux > user (Mint), and so far Frescobaldi is still running flawlessly. > > And - another question out of curiosity: Could it be a workaround (if > Qt5 would be officially retired and no longer be available in the repos > of the "big" distros like Mint, Ubuntu and the like) if one used a > distro for older computers which might stick to Qt5 much longer? > > At any rate the present state of affairs is really sad, since > Frescobaldi just is a masterpiece of software for its purpose. I have > looked at a couple of alternatives, but I was less convinced of them. > > Maybe in case Frescobaldi one day will not run any more, I need to > return to a combination of a good text editor and a PDF viewer like I > had many years ago when I was still a Mac user. I had TeXShop and Skim, > and that worked well enough. And then I also sometimes used > LilyPondTool which in the meantime is defunct as well, but was a > similar approach to editing LilyPond files as Frescobaldi. > > This is the moment when I wish I'd be a programmer, but I am afraid the > learning curve for helping out with Frescobaldi would be way to steep > for me... > > Am Sonntag, dem 28.04.2024 um 22:14 +0200 schrieb Jean Abou Samra: > > > […] > > > Well, the explanation wasn't that brief. Sorry that I didn't have > > > time to write a shorter one, as they say. > > > > > > PS: Maybe I should mention that at the time I went down the rabbit > > hole of Python packaging in general because of Frescobaldi, I wrote > > two articles on the LinuxFR site, which may be of interest here if > > one reads French: > > > > > https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-1-4 > > > https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-2-4 > > > > (Yes, these are ~8 and ~14 pages long. Yes, they're only the two > > first articles in a series of four. I haven't given up on publishing > > the two others, but it's not my priority at the moment.) > > > >
Re: Frescobaldi?
Would it maybe make things a bit easier to leave the whole MacOS business aside and take care of the Linux-specific stuff first? And what actually about Windows - out of curiosity. I myself am a Linux user (Mint), and so far Frescobaldi is still running flawlessly. And - another question out of curiosity: Could it be a workaround (if Qt5 would be officially retired and no longer be available in the repos of the "big" distros like Mint, Ubuntu and the like) if one used a distro for older computers which might stick to Qt5 much longer? At any rate the present state of affairs is really sad, since Frescobaldi just is a masterpiece of software for its purpose. I have looked at a couple of alternatives, but I was less convinced of them. Maybe in case Frescobaldi one day will not run any more, I need to return to a combination of a good text editor and a PDF viewer like I had many years ago when I was still a Mac user. I had TeXShop and Skim, and that worked well enough. And then I also sometimes used LilyPondTool which in the meantime is defunct as well, but was a similar approach to editing LilyPond files as Frescobaldi. This is the moment when I wish I'd be a programmer, but I am afraid the learning curve for helping out with Frescobaldi would be way to steep for me... Am Sonntag, dem 28.04.2024 um 22:14 +0200 schrieb Jean Abou Samra: > > […] > > Well, the explanation wasn't that brief. Sorry that I didn't have > > time to write a shorter one, as they say. > > > PS: Maybe I should mention that at the time I went down the rabbit > hole of Python packaging in general because of Frescobaldi, I wrote > two articles on the LinuxFR site, which may be of interest here if > one reads French: > > https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-1-4 > https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-2-4 > > (Yes, these are ~8 and ~14 pages long. Yes, they're only the two > first articles in a series of four. I haven't given up on publishing > the two others, but it's not my priority at the moment.) >
Re: Frescobaldi?
> […] > Well, the explanation wasn't that brief. Sorry that I didn't have > time to write a shorter one, as they say. PS: Maybe I should mention that at the time I went down the rabbit hole of Python packaging in general because of Frescobaldi, I wrote two articles on the LinuxFR site, which may be of interest here if one reads French: https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-1-4 https://linuxfr.org/news/l-installation-et-la-distribution-de-paquets-python-2-4 (Yes, these are ~8 and ~14 pages long. Yes, they're only the two first articles in a series of four. I haven't given up on publishing the two others, but it's not my priority at the moment.) signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
> unfortunately, as I noted above, the problem seems to be that frescobaldi > depends on a now-deprecated version of qtwebengine, and without updating > it we'll eventually reach a point where it no longer runs. I looked into > this because qtwebengine-5.15 failed to compile on my machine this morning, > so I'm worried we're already approaching EOL on it. Note that we're talking about Qt as a whole, not just QtWebEngine which is just a small part of it (well, for some definition of "small" since it embeds Chromium's Web rendering engine…) that Frescobaldi only uses in a few places (IIRC, the SVG viewer and the documentation browser). Qt 5 *is* already EOL upstream, since May 2023. > Jean: I have a colleague who does UI work and is "fairly" capable of dealing > with python and Qt dependencies. Can you give me a brief (but as technical > as it needs to be for a specialist to understand the issue) summary of where > the sticking points are? Frescobaldi uses the Poppler library in order to display PDF files. (It cannot use Qt's native PDF viewer based on Chromium, because that one is not powerful enough to support point-and-click.) Since Frescobaldi is written in Python and Poppler is a C++ library, it needs an FFI wrapper, which is called python- poppler-qt5 and written with a tool called sip that is developed by the creator and maintainer of PyQt itself and also used for PyQt. Thus there is a diamond dependency: Qt5 --> Poppler (C++) || || || vv PyQt5 -> python-poppler-qt5 (Python extension modules) python-poppler-qt5 is a little fiddly to build: it's multiple layers with sip generating C++ code and QMake project files, then QMake generating a Makefile and sip finally executing make on that Makefile. On macOS, the platform favors distributing applications as .app bundles, which are optimized for being created by the native app development tools (Swift+XCode). These have a peculiar structure organized into "frameworks", with data files separated from code files, shared library lookup paths modified and that sort of thing (the specifics I do not know or remember). Of course, that doesn't play well with Python packages relying on a different structure, and Qt + PyQt also needing their file structure. In fact there are whole tools written just to deploy PyQt in a .app bundle, see pyqtdeploy. Now throw python-poppler-qt5 into the mix, which needs to be loaded by Python and find its linked Poppler and Qt and PyQt, and you should start to understand the problem. Basically, it's the Apple flavor of "things will work well but only if you do it my way with the non-cross-platform tools from my walled garden" in its full glory. Add that macOS displays scary warnings to users if the app bundle hasn't been signed with a certificate that costs real money. Details are on https://github.com/frescobaldi/frescobaldi/issues/1584 Also add that the tool Frescobaldi has used so far to create app bundles, py2app, relies heavily on setuptools, which prevents Frescobaldi from moving to a more modern and less complicated build backend like hatchling. Apart from these packaging issues, there's also an issue with the global menu (the one at the top of the screen on macOS, it doesn't appear on other platforms) which isn't really up-to-date and has been a source of crashes. There are also miscellaneous bugs that only reproduce on macOS (they have the macOS label on GitHub) and it's not always easy to understand why. Well, the explanation wasn't that brief. Sorry that I didn't have time to write a shorter one, as they say. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
> I own a bunch of Macs. In fact, right here in my studio I have two late-2014
> Mac Minis with fresh Monterey installs which are completely unused. I also
> have a *really* excellent [fibre] internet connection — it usually hovers near
> 900Mbps up and down (though right now it’s only at 200Mbps for some reason?!)
> — and I’m happy to put a machine on a DMZ for external access.
>
> Is there anything, non-programming-wise, I can do to help the cause?
Currently, I don't have the time or honestly the stamina to work on
Frescobaldi again, but if anyone does tackle macOS issues then I'm
sure that they would much appreciate access to these machines.
Perhaps one thing you can do right now is subscribe to notifications on
the Frescobaldi repository on GitHub ("Watch" button on the top right of
https://github.com/frescobaldi/frescobaldi when you're logged in)
so you get informed of any activity.
signature.asc
Description: This is a digitally signed message part
Re: Frescobaldi?
> Just had a quick look. It seems to me we need to create a python-poppler-qt6, > port qpageview to Qt6 and of course frescobaldi itself. I would hope that > qpageview and frescobaldi both basically mean moving from PyQt5 to PyQt6 which > I expect to be mostly busy work. The poppler bindings seem to require > understanding of what poppler does though. > > All of the above is based on a brief look and thus not a reliable assessment. Honestly, I have zero idea how hard porting to Qt 6 actually is. I think we won't know until someone tries and finds out what exactly Frescobaldi uses that is modified or removed in Qt 6 compared to Qt 5 as well as poppler-qt6 compared to poppler-qt5. > In any case, I do rely on Frescobaldi and am willing to help keep it alive. If you want to attempt the port, of course feel free. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
> Thanks, but unfortunately the kind of work needed is deeply technical, not > busy work. > Just had a quick look. It seems to me we need to create a python-poppler-qt6, port qpageview to Qt6 and of course frescobaldi itself. I would hope that qpageview and frescobaldi both basically mean moving from PyQt5 to PyQt6 which I expect to be mostly busy work. The poppler bindings seem to require understanding of what poppler does though. All of the above is based on a brief look and thus not a reliable assessment. In any case, I do rely on Frescobaldi and am willing to help keep it alive. Kind regards, Michael
Re: Frescobaldi?
> I understood that. I was responding in particular to Jean’s comment > > > NB: I don't own a macOS machine, which of course makes all testing very > difficult > > but also offering the hardware for use in whatever way it might be helpful > (e.g., compilation, not just testing). > > Cheers, > Kieren. > __ > ah, whoops, my mistake. I missed the context. Sorry about that. N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin
Re: Frescobaldi?
Hi, > unfortunately, as I noted above, the problem seems to be that frescobaldi > depends on a now-deprecated version of qtwebengine, and without updating it > we'll eventually reach a point where it no longer runs. I understood that. I was responding in particular to Jean’s comment > NB: I don't own a macOS machine, which of course makes all testing very > difficult but also offering the hardware for use in whatever way it might be helpful (e.g., compilation, not just testing). Cheers, Kieren. __ My work day may look different than your work day. Please do not feel obligated to read or respond to this email outside of your normal working hours.
Re: Frescobaldi?
Hi All, The Qt5 dependency seems a much more serious and important issue than the packaging for macOS. Although an app bundle installer is most desirable for ordinary macOS users, there are alternatives such as MacPorts and Homebrew. I’m currently running Frescobaldi from the latest source pulled from GitHub repo with Python310 and Qt5-related libraries installed by MacPorts, and it works just fine. I’m sorry that I’m not a programmer and cannot help with the deeply technical work. I sincerely hope that we can find new volunteers to tackle the Qt5 issue. Frescobaldi is quite important for many of us. Jun Tamura he/him/his Tokyo > 2024/04/28 23:22、N. Andrew Walsh のメール: > > Hi Kieren, > > unfortunately, as I noted above, the problem seems to be that frescobaldi > depends on a now-deprecated version of qtwebengine, and without updating it > we'll eventually reach a point where it no longer runs. I looked into this > because qtwebengine-5.15 failed to compile on my machine this morning, so I'm > worried we're already approaching EOL on it. > > Jean: I have a colleague who does UI work and is "fairly" capable of dealing > with python and Qt dependencies. Can you give me a brief (but as technical as > it needs to be for a specialist to understand the issue) summary of where the > sticking points are? > > Cheers, > > N. Andrew Walsh > er/ihn/ihm/sein | he/him/his > Berlin > > > On Sun, Apr 28, 2024 at 4:08 PM Kieren MacMillan <mailto:kie...@kierenmacmillan.info>> wrote: >> Hi all, >> >> >> If there is busy work that needs to be done on the project, I can do >> >> that, but I also don't own a Mac. >> >> I own a bunch of Macs. In fact, right here in my studio I have two late-2014 >> Mac Minis with fresh Monterey installs which are completely unused. I also >> have a *really* excellent [fibre] internet connection — it usually hovers >> near 900Mbps up and down (though right now it’s only at 200Mbps for some >> reason?!) — and I’m happy to put a machine on a DMZ for external access. >> >> Is there anything, non-programming-wise, I can do to help the cause? >> >> Cheers, >> Kieren. >> __ >> >> My work day may look different than your work day. Please do not feel >> obligated to read or respond to this email outside of your normal working >> hours. >>
Re: Frescobaldi?
Hi Kieren, unfortunately, as I noted above, the problem seems to be that frescobaldi depends on a now-deprecated version of qtwebengine, and without updating it we'll eventually reach a point where it no longer runs. I looked into this because qtwebengine-5.15 failed to compile on my machine this morning, so I'm worried we're already approaching EOL on it. Jean: I have a colleague who does UI work and is "fairly" capable of dealing with python and Qt dependencies. Can you give me a brief (but as technical as it needs to be for a specialist to understand the issue) summary of where the sticking points are? Cheers, N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin On Sun, Apr 28, 2024 at 4:08 PM Kieren MacMillan < kie...@kierenmacmillan.info> wrote: > Hi all, > > >> If there is busy work that needs to be done on the project, I can do > that, but I also don't own a Mac. > > I own a bunch of Macs. In fact, right here in my studio I have two > late-2014 Mac Minis with fresh Monterey installs which are completely > unused. I also have a *really* excellent [fibre] internet connection — it > usually hovers near 900Mbps up and down (though right now it’s only at > 200Mbps for some reason?!) — and I’m happy to put a machine on a DMZ for > external access. > > Is there anything, non-programming-wise, I can do to help the cause? > > Cheers, > Kieren. > __ > > My work day may look different than your work day. Please do not feel > obligated to read or respond to this email outside of your normal working > hours. > >
Re: Frescobaldi?
Hi all, >> If there is busy work that needs to be done on the project, I can do that, >> but I also don't own a Mac. I own a bunch of Macs. In fact, right here in my studio I have two late-2014 Mac Minis with fresh Monterey installs which are completely unused. I also have a *really* excellent [fibre] internet connection — it usually hovers near 900Mbps up and down (though right now it’s only at 200Mbps for some reason?!) — and I’m happy to put a machine on a DMZ for external access. Is there anything, non-programming-wise, I can do to help the cause? Cheers, Kieren. __ My work day may look different than your work day. Please do not feel obligated to read or respond to this email outside of your normal working hours.
Re: Frescobaldi?
> If there is busy work that needs to be done on the project, I can do that, but > I also don't own a Mac. Thanks, but unfortunately the kind of work needed is deeply technical, not busy work. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
On Sun, Apr 28, 2024 at 4:15 AM Jean Abou Samra wrote: > Doing some system updates today, I see that frescobaldi is the only > program that requires PyQtWebEngine:5, which in turn requires > qtwebengine:5. Looking at the frescobaldi page, I see a somewhat concerning > note that the project is on the verge of being unmaintained, due to this > dependency on a deprecated version of qtwebengine. > > Is there any further information on this? I don't see any other IDE that > works as well as frescobaldi for editing lilypond files, and I'm a bit > worried that there hasn't been an update to the program in over a year. Any > news would be appreciated. > > > > You've basically nailed the problem. I was the last person to work on > making Frescobaldi actually work on macOS, and I gave up by lack of time > (NB: I don't own a macOS machine, which of course makes all testing very > difficult). Currently, there is close to no activity on the project. > > I doubt Linux distributions are going to remove Qt 5 really soon, and the > Flatpak package can always provide it, but like every toolkit that's > end-of-life, it's only going to be a source of trouble going forward. For > example, Frescobaldi has some problems on Wayland (which is increasingly > becoming the default on the Linux desktop, for good reason) that are caused > by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the > Qt 6 migration. > > Yes, if the current state continues, Frescobaldi will ultimately die a > natural death. Sorry that I cannot exactly bring an optimistic message > here. > If there is busy work that needs to be done on the project, I can do that, but I also don't own a Mac. -- Knute Snortum
Re: Frescobaldi?
> Is Frescobaldi the most common tool on Linux, or what do the majority of > Lilypond users use? Frescobaldi is the most common LilyPond editor, on all OSes. signature.asc Description: This is a digitally signed message part
Re: Frescobaldi?
I use Frescobaldi on all of my Macs with slightly different operating systems. It works well, but I'm concerned about the future. Unfortunately, I'm not a programmer, so I can't contribute with coding. This is exciting, perhaps a bit too exciting, considering how we'll be able to continue with Lilypond. Is Frescobaldi the most common tool on Linux, or what do the majority of Lilypond users use? Regards /MO > 28 apr. 2024 kl. 13:15 skrev Jean Abou Samra : > > >> >> Doing some system updates today, I see that frescobaldi is the only program >> that requires PyQtWebEngine:5, which in turn requires qtwebengine:5. Looking >> at the frescobaldi page, I see a somewhat concerning note that the project >> is on the verge of being unmaintained, due to this dependency on a >> deprecated version of qtwebengine. >> >> Is there any further information on this? I don't see any other IDE that >> works as well as frescobaldi for editing lilypond files, and I'm a bit >> worried that there hasn't been an update to the program in over a year. Any >> news would be appreciated. > > > You've basically nailed the problem. I was the last person to work on making > Frescobaldi actually work on macOS, and I gave up by lack of time (NB: I > don't own a macOS machine, which of course makes all testing very difficult). > Currently, there is close to no activity on the project. > > I doubt Linux distributions are going to remove Qt 5 really soon, and the > Flatpak package can always provide it, but like every toolkit that's > end-of-life, it's only going to be a source of trouble going forward. For > example, Frescobaldi has some problems on Wayland (which is increasingly > becoming the default on the Linux desktop, for good reason) that are caused > by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the Qt > 6 migration. > > Yes, if the current state continues, Frescobaldi will ultimately die a > natural death. Sorry that I cannot exactly bring an optimistic message here. > > Best, > Jean > >
Re: Frescobaldi?
> Doing some system updates today, I see that frescobaldi is the only program > that requires PyQtWebEngine:5, which in turn requires qtwebengine:5. Looking > at the frescobaldi page, I see a somewhat concerning note that the project is > on the verge of being unmaintained, due to this dependency on a deprecated > version of qtwebengine. > > Is there any further information on this? I don't see any other IDE that works > as well as frescobaldi for editing lilypond files, and I'm a bit worried that > there hasn't been an update to the program in over a year. Any news would be > appreciated. You've basically nailed the problem. I was the last person to work on making Frescobaldi actually work on macOS, and I gave up by lack of time (NB: I don't own a macOS machine, which of course makes all testing very difficult). Currently, there is close to no activity on the project. I doubt Linux distributions are going to remove Qt 5 really soon, and the Flatpak package can always provide it, but like every toolkit that's end-of- life, it's only going to be a source of trouble going forward. For example, Frescobaldi has some problems on Wayland (which is increasingly becoming the default on the Linux desktop, for good reason) that are caused by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the Qt 6 migration. Yes, if the current state continues, Frescobaldi will ultimately die a natural death. Sorry that I cannot exactly bring an optimistic message here. Best, Jean signature.asc Description: This is a digitally signed message part
Frescobaldi?
Hi List, Doing some system updates today, I see that frescobaldi is the only program that requires PyQtWebEngine:5, which in turn requires qtwebengine:5. Looking at the frescobaldi page, I see a somewhat concerning note that the project is on the verge of being unmaintained, due to this dependency on a deprecated version of qtwebengine. Is there any further information on this? I don't see any other IDE that works as well as frescobaldi for editing lilypond files, and I'm a bit worried that there hasn't been an update to the program in over a year. Any news would be appreciated. Cheers, N. Andrew Walsh er/ihn/ihm/sein | he/him/his Berlin
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
On Wed, Feb 14, 2024 at 7:59 AM Hajo Baess wrote: > I have (just completely accidentally, with a little help from the > Breeze theme color scheme) discovered a keyboard shortcut for switching > back and forth between the editor and the Music View. I think that it > is undocumented, and strange it is, too. Here it is: > > * from editor to Music View: press CTRL+TAB 5 times or until the Music >View scroll bar is not greyed out any more. In Breeze for example, >it turns light blue. The editor scroll bar turns grey at the same >time. > * from Music View to editor: press CTRL+Shift+TAB 5 times or until the >editor's scroll bar is no longer greyed out, but Music View's is. > > This is a crazy thing, but it seems to work... > > No mouse needed. > It doesn't work for me on Ubuntu Linux. I do see different widgets getting focus but it never seems to go to the Music View. Still, it's an interesting find! -- Knute Snortum
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
That makes sense to me. The Frescobaldo keyboard shortcuts are all, for my Linux version, Meta-Ctrl-?. If TAB moves around fields in dialog windows, then it makes sense that Ctrl-Tab might shift between those dialogs, or in this case the various Tool palettes, etc. Your persistence is admirable. Guy -- “Happiness is the meaning and the purpose of life, the whole aim and end of human existence.” ― Aristotle On Wed, Feb 14, 2024, 9:59 AM Hajo Baess wrote: > I have (just completely accidentally, with a little help from the > Breeze theme color scheme) discovered a keyboard shortcut for switching > back and forth between the editor and the Music View. I think that it > is undocumented, and strange it is, too. Here it is: > > * from editor to Music View: press CTRL+TAB 5 times or until the Music >View scroll bar is not greyed out any more. In Breeze for example, >it turns light blue. The editor scroll bar turns grey at the same >time. > * from Music View to editor: press CTRL+Shift+TAB 5 times or until the >editor's scroll bar is no longer greyed out, but Music View's is. > > This is a crazy thing, but it seems to work... > > No mouse needed. > > > > Am Dienstag, dem 13.02.2024 um 13:24 -0600 schrieb Guy Stalnaker: > > I do not see such a toggle or any system call in the Key Shortcuts > > preferences that seems relevant. And perhaps that is not surprising - > > Frescobaldi is after all a code editor; that it assumes (!) one would > > always want the code visible makes sense to me. > > > > Regards > > > > On 2/12/24 15:36, Hajo Baess wrote: > > > Hello all, > > > > > > Maybe I am missing it alltogether or it does not exist or it is to > > > hard > > > to find for me: > > > I am looking for a keyboard shortcut in Frescobaldi enabling me to > > > toggle between editor and music view, so I do not have to click > > > with > > > the mouse. > > > > > > I just can't find it. I have tried all kinds of possible candidates > > > to > > > no avail. Is someone here who happens to know? > > > > > > Thank you for pointing this out to me... > > > > >
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
I have (just completely accidentally, with a little help from the Breeze theme color scheme) discovered a keyboard shortcut for switching back and forth between the editor and the Music View. I think that it is undocumented, and strange it is, too. Here it is: * from editor to Music View: press CTRL+TAB 5 times or until the Music View scroll bar is not greyed out any more. In Breeze for example, it turns light blue. The editor scroll bar turns grey at the same time. * from Music View to editor: press CTRL+Shift+TAB 5 times or until the editor's scroll bar is no longer greyed out, but Music View's is. This is a crazy thing, but it seems to work... No mouse needed. Am Dienstag, dem 13.02.2024 um 13:24 -0600 schrieb Guy Stalnaker: > I do not see such a toggle or any system call in the Key Shortcuts > preferences that seems relevant. And perhaps that is not surprising - > Frescobaldi is after all a code editor; that it assumes (!) one would > always want the code visible makes sense to me. > > Regards > > On 2/12/24 15:36, Hajo Baess wrote: > > Hello all, > > > > Maybe I am missing it alltogether or it does not exist or it is to > > hard > > to find for me: > > I am looking for a keyboard shortcut in Frescobaldi enabling me to > > toggle between editor and music view, so I do not have to click > > with > > the mouse. > > > > I just can't find it. I have tried all kinds of possible candidates > > to > > no avail. Is someone here who happens to know? > > > > Thank you for pointing this out to me... > >
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
Maybe I was not clear enough in what I said: Of course the code should be visible all the time. What I mean is the following: When you have Frescobaldi open with its split window, there is always one of the two halves active and reacts to input. Say, you are in the editor, but want to go to a different page of your doc in the music view, you always have to click into the Music View half of Frescobaldi's window in order to activate it, so you can use a keyboard shortcut there. And when you have done this and want to go back to the editor, you have to click again into the editor pane to activate that one for more input. I am looking for a keyboard shortcut for activating whatever pane I want to be in for input instead of having to click all the time, because LilyPond is mostly keyboard work. The mouse (at least with me) is hardly in use... Am Dienstag, dem 13.02.2024 um 13:24 -0600 schrieb Guy Stalnaker: > I do not see such a toggle or any system call in the Key Shortcuts > preferences that seems relevant. And perhaps that is not surprising - > Frescobaldi is after all a code editor; that it assumes (!) one would > always want the code visible makes sense to me. > > Regards > > On 2/12/24 15:36, Hajo Baess wrote: > > Hello all, > > > > Maybe I am missing it alltogether or it does not exist or it is to > > hard > > to find for me: > > I am looking for a keyboard shortcut in Frescobaldi enabling me to > > toggle between editor and music view, so I do not have to click > > with > > the mouse. > > > > I just can't find it. I have tried all kinds of possible candidates > > to > > no avail. Is someone here who happens to know? > > > > Thank you for pointing this out to me... > >
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
I do not see such a toggle or any system call in the Key Shortcuts preferences that seems relevant. And perhaps that is not surprising - Frescobaldi is after all a code editor; that it assumes (!) one would always want the code visible makes sense to me. Regards On 2/12/24 15:36, Hajo Baess wrote: Hello all, Maybe I am missing it alltogether or it does not exist or it is to hard to find for me: I am looking for a keyboard shortcut in Frescobaldi enabling me to toggle between editor and music view, so I do not have to click with the mouse. I just can't find it. I have tried all kinds of possible candidates to no avail. Is someone here who happens to know? Thank you for pointing this out to me... -- “Happiness is the meaning and the purpose of life, the whole aim and end of human existence.” ― Aristotle
Re: Frescobaldi: Keyboard shortcut for toggling between editor and music view?
On Mon, Feb 12, 2024 at 1:37 PM Hajo Baess wrote: > Hello all, > > Maybe I am missing it alltogether or it does not exist or it is to hard > to find for me: > I am looking for a keyboard shortcut in Frescobaldi enabling me to > toggle between editor and music view, so I do not have to click with > the mouse. > > I just can't find it. I have tried all kinds of possible candidates to > no avail. Is someone here who happens to know? > > Thank you for pointing this out to me... > If it doesn't exist, it might be a nice addition! -- Knute Snortum
Frescobaldi: Keyboard shortcut for toggling between editor and music view?
Hello all, Maybe I am missing it alltogether or it does not exist or it is to hard to find for me: I am looking for a keyboard shortcut in Frescobaldi enabling me to toggle between editor and music view, so I do not have to click with the mouse. I just can't find it. I have tried all kinds of possible candidates to no avail. Is someone here who happens to know? Thank you for pointing this out to me...
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
On Mon, Jan 15, 2024 at 10:57 AM Hans Aikema wrote: > > I've created an issue for Frescobaldi and I should be able to start work > on it today. > > https://github.com/frescobaldi/frescobaldi/issues/172 > > > Knute, you've missed a digit while copying the link and without doubt > intended to refer to > https://github.com/frescobaldi/frescobaldi/issues/1728 > Thanks! The Issue is now fixed in the repository.
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
On 15 Jan 2024, at 19:40, Knute Snortum wrote:On Mon, Jan 15, 2024 at 7:47 AM David Kastrup <d...@gnu.org> wrote: Calling git grep "override[^=]*#'[a-z]" in the current Frescobaldi source tree delivers _way_ too many hits. I don't consider it sane that the current Frescobaldi will pump out pre-2.18 syntax in droves in its templates. And I suspect that it also splits overrides into multiple lines, making it harder to recognize them.I've created an issue for Frescobaldi and I should be able to start work on it today.https://github.com/frescobaldi/frescobaldi/issues/172Knute, you've missed a digit while copying the link and without doubt intended to refer tohttps://github.com/frescobaldi/frescobaldi/issues/1728--Knute Snortum
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
On Mon, Jan 15, 2024 at 7:47 AM David Kastrup wrote: > > Calling > > git grep "override[^=]*#'[a-z]" > > in the current Frescobaldi source tree delivers _way_ too many hits. I > don't consider it sane that the current Frescobaldi will pump out > pre-2.18 syntax in droves in its templates. > > And I suspect that it also splits overrides into multiple lines, making > it harder to recognize them. > I've created an issue for Frescobaldi and I should be able to start work on it today. https://github.com/frescobaldi/frescobaldi/issues/172 -- Knute Snortum
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Knute Snortum writes:
> On Mon, Jan 15, 2024 at 5:28 AM David Kastrup wrote:
>
>> Bernhard Kleine writes:
>>
>> > Dear David,
>> >
>> > the file was created this morning from frescobaldi with the
>> > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7.
>> > Nothing was done be myself apart from wrinting notes and lyrics.
>>
>> If the "Partitur-Assistent" creates those overrides, it needs to get fixed.
>>
>
> It has been:
>
> https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588
Well, it's a start. See my note about
git grep "override[^=]*#'[a-z]"
I get
TODO: * drag an object to e.g. create an \override #'extra-offset command
frescobaldi_app/fonts/templates/musicfont-glyphs.ly:\override
DynamicLineSpanner #'staff-padding = #2.0
frescobaldi_app/fonts/templates/musicfont-glyphs.ly: \override
BreathingSign #'text = \markup { \musicglyph #"scripts.rvarcomma" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly: \override
TrillSpanner #'direction = #DOWN
frescobaldi_app/fonts/templates/musicfont-glyphs.ly: \override
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.curved" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly: \override
BreathingSign #'text = \markup { \musicglyph #"scripts.caesura.straight" }
frescobaldi_app/fonts/templates/musicfont-glyphs.ly: \override
BreathingSign #'text = \markup { \musicglyph #"scripts.tickmark" }
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override Score.Clef
#'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override
Score.KeySignature #'break-visibility = #'#(#f #f #f)
frescobaldi_app/fonts/templates/musicfont-realbook.ly:\override
Score.SystemStartBar #'collapse-height = #1
frescobaldi_app/scorewiz/scoreproperties.py:
ly.dom.Line(r"\override Staff.TimeSignature #'style = #'()", node)
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol
#'transparent = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override StaffSymbol #'width
= #4
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead
#'no-ledgers = ##t
frescobaldi_app/symbols/arpeggio_defaults.ily:\override NoteHead #'stencil
= #empty-stencil
frescobaldi_app/symbols/arpeggio_defaults.ily:\override Stem #'stencil
=#empty-stencil
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'width = #'4
frescobaldi_app/symbols/bar_defaults.ily:\override StaffSymbol #'thickness
= #1.2
frescobaldi_app/symbols/bar_kievan.ly:\override StaffSymbol #'width = #1.44
frescobaldi_app/symbols/bar_repeat_angled_double.ly:\override StaffSymbol
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_end.ly:\override StaffSymbol
#'width = #5.5
frescobaldi_app/symbols/bar_repeat_angled_start.ly:\override StaffSymbol
#'width = #5.5
frescobaldi_app/symbols/bar_segno.ly:\override StaffSymbol #'width = #7
frescobaldi_app/symbols/bar_tick.ly:\override StaffSymbol #'staff-space =
#(/ 7 8)
frescobaldi_app/symbols/clef_defaults.ily:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'width = #4
frescobaldi_app/symbols/clef_tab.ly:\override StaffSymbol #'staff-space = #1
frescobaldi_app/symbols/clef_tab.ly:\override Clef #'font-size = #-3.5
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol
#'transparent = ##t
frescobaldi_app/symbols/glissando_defaults.ily:\override StaffSymbol
#'width = #4
frescobaldi_app/symbols/glissando_defaults.ily:\override NoteHead #'stencil
= #empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'stencil =
#empty-stencil
frescobaldi_app/symbols/glissando_defaults.ily:\override Stem #'length = #0
frescobaldi_app/symbols/glissando_defaults.ily:\override Glissando
#'bound-details = #
frescobaldi_app/symbols/glissando_defaults.ily: \override Glissando
#'style = $style
frescobaldi_app/symbols/glissando_dotted.ly:\override Glissando #'thickness
= #1.5
frescobaldi_app/symbols/spanner_beam16.ly: \override NoteHead
#'extra-spacing-width = #'(0 . 1.3)
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol #'width
= #4.4
frescobaldi_app/symbols/spanner_defaults.ily:\override StaffSymbol
#'transparent = ##t
frescobaldi_app/symbols/spanner_melisma.ly: \override Stem #'length = #3
frescobaldi_app/symbols/spanner_melisma.ly: \override VerticalAxisGroup
#'nonstaff-relatedstaff-spacing =
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'length = #0
frescobaldi_app/symbols/spanner_phrasingslur.ly:\override Stem #'direction
= #DOWN
frescobaldi_app/symbols/spanner_phrasin
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Bernhard Kleine writes: > Am 15.01.2024 um 14:28 schrieb David Kastrup: >> Bernhard Kleine writes: >> >>> Dear David, >>> >>> the file was created this morning from frescobaldi with the >>> Partitur-Assistent and the pre-set version of Lilypond was 2.25.7. >>> Nothing was done be myself apart from wrinting notes and lyrics. >> If the "Partitur-Assistent" creates those overrides, it needs to get fixed. > > It does create them. Any idea how to get is fixed in this particular case? Calling git grep "override[^=]*#'[a-z]" in the current Frescobaldi source tree delivers _way_ too many hits. I don't consider it sane that the current Frescobaldi will pump out pre-2.18 syntax in droves in its templates. And I suspect that it also splits overrides into multiple lines, making it harder to recognize them. -- David Kastrup
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
On Mon, Jan 15, 2024 at 5:28 AM David Kastrup wrote: > Bernhard Kleine writes: > > > Dear David, > > > > the file was created this morning from frescobaldi with the > > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7. > > Nothing was done be myself apart from wrinting notes and lyrics. > > If the "Partitur-Assistent" creates those overrides, it needs to get fixed. > It has been: https://github.com/frescobaldi/frescobaldi/commit/fb79df399056ddd8ce2fa2b48ac36fc37bdc0588 -- Knute Snortum
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Am 15.01.2024 um 14:28 schrieb David Kastrup: Bernhard Kleine writes: Dear David, the file was created this morning from frescobaldi with the Partitur-Assistent and the pre-set version of Lilypond was 2.25.7. Nothing was done be myself apart from wrinting notes and lyrics. If the "Partitur-Assistent" creates those overrides, it needs to get fixed. It does create them. Any idea how to get is fixed in this particular case?
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Bernhard Kleine writes: > Dear David, > > the file was created this morning from frescobaldi with the > Partitur-Assistent and the pre-set version of Lilypond was 2.25.7. > Nothing was done be myself apart from wrinting notes and lyrics. If the "Partitur-Assistent" creates those overrides, it needs to get fixed. -- David Kastrup
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Dear David, the file was created this morning from frescobaldi with the Partitur-Assistent and the pre-set version of Lilypond was 2.25.7. Nothing was done be myself apart from wrinting notes and lyrics. Am 15.01.2024 um 13:06 schrieb David Kastrup: Bernhard Kleine writes: The following MWE gave a warning C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25: Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space I think maybe the frescobaldi is not aware of changes to this lilypond version. What do I have change to make the score compile without this warning? Kind regards Bernhard \version "2.25.7" Do _NOT_ update the version header by hand. That is the job of convert-ly when it also updates the syntax of your file to a newer version.
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
Bernhard Kleine writes: > The following MWE gave a warning > > C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25: > Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space > > I think maybe the frescobaldi is not aware of changes to this lilypond > version. What do I have change to make the score compile without this > warning? > > Kind regards > > Bernhard > > \version "2.25.7" Do _NOT_ update the version header by hand. That is the job of convert-ly when it also updates the syntax of your file to a newer version. -- David Kastrup
Re: Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
On Mon, Jan 15, 2024 at 6:26 AM Bernhard Kleine wrote: > The following MWE gave a warning > > C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25: > Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space > > I think maybe the frescobaldi is not aware of changes to this lilypond > version. What do I have change to make the score compile without this warning? I'm FAR from an expert, but the few times I've encountered errors like that, the error message basically seems to tell me what I should do, albeit not in the clearest way. Does changing StaffSymbol #'staff-space to StaffSymbol.staff-space fix the problem? (Or am I misunderstanding your question?) I note, as I often do, too many older versions of documentation -- apparently, from 2.13 to 2.24, with the documentation for 2.25 not there yet. But this page for 2.24 suggests to me, the change that the error message suggested... https://lilypond.org/doc/v2.24/Documentation/snippets/spacing
Error/warning when creating a piano reduction with lilypond 2.25.7 and frescobaldi 3.3.0
The following MWE gave a warning
C:/Users/bk/AppData/Local/Temp/frescobaldi-n7fp9iem/tmp_isr57mt/document.ly:52:25:
Warnung: deprecated: missing `.' in property path StaffSymbol.staff-space
I think maybe the frescobaldi is not aware of changes to this lilypond
version. What do I have change to make the score compile without this
warning?
Kind regards
Bernhard
\override StaffSymbol
#'staff-space = #(magstep -1)
\version "2.25.7"
\language "deutsch"
global = {
\key b \major
\time 2/2
}
soprano = \relative c' {
\global
f1
}
alto = \relative c' {
\global
b1|
}
tenor = \relative c' {
\global
b1
}
bass = \relative c' {
\global
% Die Noten folgen hier.
b1
}
sopranoVerse = \lyricmode {
% Liedtext folgt hier.
O mag -- num
}
altoVerse = \lyricmode {
% Liedtext folgt hier.
O mag -- num
}
tenorVerse = \lyricmode {
% Liedtext folgt hier.
O mag -- num
}
bassVerse = \lyricmode {
% Liedtext folgt hier.
O mag -- num
}
pianoReduction = \new PianoStaff \with {
fontSize = #-1
\override StaffSymbol #'staff-space = #(magstep -1)
} <<
\new Staff \with {
\consists "Mark_engraver"
\consists "Metronome_mark_engraver"
\remove "Staff_performer"
} {
#(set-accidental-style 'piano)
<<
\soprano \\
\alto
>>
}
\new Staff \with {
\remove "Staff_performer"
} {
\clef bass
#(set-accidental-style 'piano)
<<
\tenor \\
\bass
>>
}
>>
\score {
<<
\new ChoirStaff <<
\new Staff \with {
midiInstrument = "choir aahs"
} { \soprano }
\addlyrics { \sopranoVerse }
\new Staff \with {
midiInstrument = "choir aahs"
} { \alto }
\addlyrics { \altoVerse }
\new Staff \with {
midiInstrument = "choir aahs"
} { \clef "treble_8" \tenor }
\addlyrics { \tenorVerse }
\new Staff \with {
midiInstrument = "choir aahs"
} { \clef bass \bass }
\addlyrics { \bassVerse }
>>
\pianoReduction
>>
\layout { }
\midi {
\tempo 4=100
}
}
Re: Obscure message in Frescobaldi
I found the answer. See the Frescobaldi issue. signature.asc Description: This is a digitally signed message part
