as_ly_scm_list

[Jean Abou Samra]

lily-lexer.cc contains

   for (SCM scope : as_ly_scm_list (scopes_))
 ly_use_module (module, scope);

When I read this code again after modifying it some
time ago, my reaction was "what, scopes_ will be SCM_EOL
at the end of this iteration, didn't I introduce a big
bad bug??", but inserting debug message () statements
shows that this is not true.

I understand that ly_scm_list takes an rvalue and disallows
lvalues for clarity, while as_ly_scm_list takes an lvalue,
and will fail on an rvalue by design, with the failure being
a compilation failure since e67154f7e330b61c5d9a973fbb89bd56866a148e.

But I don't understand the real difference that distinguishes
them. Before that commit, what would have been the difference
between as_ly_scm_list (lvalue) and ly_scm_list (lvalue)?

Thanks,
Jean

Re: LilyPond 2.23.11

[Jean Abou Samra]

Le 25/07/2022 à 00:36, Jean Abou Samra a écrit :

Le 25/07/2022 à 00:32, Knute Snortum a écrit :

Okay, it's even stranger than I thought. It's this URL:

https://lilypond.org/doc/v2.23/Documentation/web/unix

...but the only way I can get to it is:

https://lilypond.org/doc/v2.23/Documentation -> web -> download -> unix.

It must be a Google thing -- even though I just tried to get to that
page through a Google search and couldn't.  Weird.  Well, it's
probably not something people are going to run into frequently.



You mean this?

https://lilypond.org/doc/v2.23/Documentation/web/unix



Sorry. I'm tired.

Re: LilyPond 2.23.11

[Jean Abou Samra]

Le 25/07/2022 à 00:32, Knute Snortum a écrit :

Okay, it's even stranger than I thought.  It's this URL:

https://lilypond.org/doc/v2.23/Documentation/web/unix

...but the only way I can get to it is:

https://lilypond.org/doc/v2.23/Documentation -> web -> download -> unix.

It must be a Google thing -- even though I just tried to get to that
page through a Google search and couldn't.  Weird.  Well, it's
probably not something people are going to run into frequently.



You mean this?

https://lilypond.org/doc/v2.23/Documentation/web/unix

The URL has "2.23", but this page contains 2.22 downloads. The
website is maintained like a manual, so you can browse it offline
from the documentation archive. This is the latest version of
the website (2.23), the same version that is served when
you arrive on lilypond.org, and since the version recommended
for most people, the download page of this 2.23 website points
to 2.22.

Best,
Jean

Re: LilyPond 2.23.11

[Knute Snortum]

--
Knute Snortum


On Sun, Jul 24, 2022 at 2:08 PM Jean Abou Samra  wrote:
>
>
>
> Le 24/07/2022 à 22:33, Knute Snortum a écrit :
> > On Sun, Jul 24, 2022 at 1:25 PM Knute Snortum  wrote:
> >> On Sun, Jul 24, 2022 at 10:44 AM Jonas Hahnfeld via LilyPond user
> >> discussion  wrote:
> >>> We are happy to announce the release of LilyPond 2.23.11. This is
> >>> termed a development release, but these are usually reliable. However,
> >>> if you require stability, we recommend using version 2.22.2, the
> >>> current stable release. Please refer to the Installing section in the
> >>> Learning Manual for instructions how to set up the provided binaries:
> >>> https://lilypond.org/doc/v2.23/Documentation/learning/installing
> >> It looks like we went back to shell installation, is that correct?
> > Oh, I see what happened.  The 2.22.2 version is on the 2.23
> > development download page.
>
>
> Where do you see this? On
> https://lilypond.org/development.html
> the bit of text
> "If you are unsure about how to install these binaries, please read the
> start of the Learning
>  manual."
> redirects to
> https://lilypond.org/doc/v2.23/Documentation/learning/index.html

Okay, it's even stranger than I thought.  It's this URL:

https://lilypond.org/doc/v2.23/Documentation/web/unix

...but the only way I can get to it is:

https://lilypond.org/doc/v2.23/Documentation -> web -> download -> unix.

It must be a Google thing -- even though I just tried to get to that
page through a Google search and couldn't.  Weird.  Well, it's
probably not something people are going to run into frequently.

---
Knute Snortum

Re: LilyPond 2.23.11

[Jean Abou Samra]

Le 24/07/2022 à 22:33, Knute Snortum a écrit :

On Sun, Jul 24, 2022 at 1:25 PM Knute Snortum  wrote:

On Sun, Jul 24, 2022 at 10:44 AM Jonas Hahnfeld via LilyPond user
discussion  wrote:

We are happy to announce the release of LilyPond 2.23.11. This is
termed a development release, but these are usually reliable. However,
if you require stability, we recommend using version 2.22.2, the
current stable release. Please refer to the Installing section in the
Learning Manual for instructions how to set up the provided binaries:
https://lilypond.org/doc/v2.23/Documentation/learning/installing

It looks like we went back to shell installation, is that correct?

Oh, I see what happened.  The 2.22.2 version is on the 2.23
development download page.



Where do you see this? On
https://lilypond.org/development.html
the bit of text
"If you are unsure about how to install these binaries, please read the 
start of the Learning 
 manual."

redirects to
https://lilypond.org/doc/v2.23/Documentation/learning/index.html

Re: LilyPond 2.23.11

[Knute Snortum]

On Sun, Jul 24, 2022 at 1:25 PM Knute Snortum  wrote:
>
> On Sun, Jul 24, 2022 at 10:44 AM Jonas Hahnfeld via LilyPond user
> discussion  wrote:
> >
> > We are happy to announce the release of LilyPond 2.23.11. This is
> > termed a development release, but these are usually reliable. However,
> > if you require stability, we recommend using version 2.22.2, the
> > current stable release. Please refer to the Installing section in the
> > Learning Manual for instructions how to set up the provided binaries:
> > https://lilypond.org/doc/v2.23/Documentation/learning/installing
>
> It looks like we went back to shell installation, is that correct?

Oh, I see what happened.  The 2.22.2 version is on the 2.23
development download page.

--
Knute Snortum

Re: LilyPond 2.23.11

[Knute Snortum]

On Sun, Jul 24, 2022 at 10:44 AM Jonas Hahnfeld via LilyPond user
discussion  wrote:
>
> We are happy to announce the release of LilyPond 2.23.11. This is
> termed a development release, but these are usually reliable. However,
> if you require stability, we recommend using version 2.22.2, the
> current stable release. Please refer to the Installing section in the
> Learning Manual for instructions how to set up the provided binaries:
> https://lilypond.org/doc/v2.23/Documentation/learning/installing

It looks like we went back to shell installation, is that correct?

--
Knute Snortum

LilyPond 2.23.11

[Jonas Hahnfeld via Discussions on LilyPond development]

We are happy to announce the release of LilyPond 2.23.11. This is
termed a development release, but these are usually reliable. However,
if you require stability, we recommend using version 2.22.2, the
current stable release. Please refer to the Installing section in the
Learning Manual for instructions how to set up the provided binaries:
https://lilypond.org/doc/v2.23/Documentation/learning/installing


signature.asc
Description: This is a digitally signed message part

Re: Fixing regressions and serious issues

[Jean Abou Samra]

Le 24/07/2022 à 17:20, Jonas Hahnfeld a écrit :

I didn't want to imply this problem isn't important, but it's also
difficult to address (at least from my attempts).


https://gitlab.com/lilypond/lilypond/-/merge_requests/1510

Re: Fixing regressions and serious issues

[Jonas Hahnfeld via Discussions on LilyPond development]

On Wed, 2022-07-20 at 13:56 +0200, Thomas Morley wrote:
> Am Mi., 20. Juli 2022 um 11:40 Uhr schrieb Jonas Hahnfeld via
> Discussions on LilyPond development :
> > 
> > On Thu, 2022-07-14 at 17:38 +0200, Jean Abou Samra wrote:
> > > * “GUILE 2.2 doesn't provide source locations”
> > > 
> > >https://gitlab.com/lilypond/lilypond/-/issues/5992
> > > 
> > >Needs figuring out if executing Scheme code with
> > >`compile` is OK performance-wise and how to get
> > >it to display source location info.
> > 
> > I agree this is annoying, and it would be great to improve the
> > situation. I'm not sure if this should block the release though.
> 
> I beg to differ.
> For me it's the most pressing and annoying issue. A stable release
> without good error messages is unusable for huge custom scheme
> codings.
> Granted, recently some workarounds were discussed on -user. Alas, I
> can't imagine a stable version needing those workarounds right from
> it's release date.
> Even it does not crash lilypond, I'd label it Critical as well.

I didn't want to imply this problem isn't important, but it's also
difficult to address (at least from my attempts). So the real question
is: If this is the only remaining issue, would we rather still have a
release or no stable release at all until it can be fixed. That's what
~Critical means in the end.

Jonas


signature.asc
Description: This is a digitally signed message part