On Nov 23, 2020, at 18:01, Han-Wen Nienhuys wrote:
>
> We'd have to make unsmob return a Stencil const *. Maybe that is
> appropriate for more simple smobs?
>
or for a more explicit interface, delete unsmob so that unsmob is required.
—
Dan
On Mon, Nov 23, 2020 at 9:11 PM Jonas Hahnfeld wrote:
> Am Sonntag, den 22.11.2020, 22:49 +0100 schrieb David Kastrup:
> > Jonas Hahnfeld writes:
> >
> > > Nope, that was a red herring: The reason is that the footnote creation
> > > process in footnote-volta-spanner.ly messes with (point-stencil
Jonas Hahnfeld writes:
> Am Sonntag, den 22.11.2020, 22:49 +0100 schrieb David Kastrup:
>>
>> To me that seems crazy. Instead \footnote should not modify the
>> stencil generated from its argument in place. If it needs something
>> with different dimensions, it needs to create a new stencil, c
>> Similarly, I have to regenerate various `.map` files by calling
>> `updmap-user` to integrate my private fonts into TeX.
>
> Maybe my use-cases are restricted in that I don't switch away from
> some of the most-commonly used fonts, but having many local user
> fonts is on the other extreme of t
Am Sonntag, den 22.11.2020, 22:49 +0100 schrieb David Kastrup:
> Jonas Hahnfeld writes:
>
> > Nope, that was a red herring: The reason is that the footnote creation
> > process in footnote-volta-spanner.ly messes with (point-stencil), which
> > is used by skyline-point-extent.ly and also the Bend
Am Montag, den 23.11.2020, 11:17 +0100 schrieb Werner LEMBERG:
> > > > But please generate the files in the build directory by
> > > > specifying --destdir (and use them from there), putting things
> > > > in a cache directory located in the user's $HOME directory is
> > > > IMHO a very poor defaul
> On Nov 23, 2020, at 08:19, Werner LEMBERG wrote:
>
>
>>> I strongly disagree. It's definitely not LilyPond's job to decide
>>> where the TeX system stores its internal files. In other words,
>>> the build infracture has to adjust this, to be handled outside of
>>> LilyPond.
>>
>> Should
>>> Should this part of the font setup be baked into the Docker image?
>>
>> I don't know enough about Docker images to decide that. In case
>> the Docker's `$HOME` directory can be easily deleted on a clean-up,
>> nothing needs to be changed IMHO. Otherwise it is trivial to set
>> the `$TEXMFVA
>> I strongly disagree. It's definitely not LilyPond's job to decide
>> where the TeX system stores its internal files. In other words,
>> the build infracture has to adjust this, to be handled outside of
>> LilyPond.
>
> Should this part of the font setup be baked into the Docker image?
I do
On Nov 23, 2020, at 05:17, Werner LEMBERG wrote:
> I think you either don't use TeX a lot, or your use-cases are very
> restricted. As soon as I update TeXLive, I have to regenerate the
> format files by `fmtutil-user`, which are all stored in $HOME.
> Similarly, I have to regenerate various `.ma
>> Something like the attached (untested) patch should do.
>
> Please don't defeat all recent cleanups of the build system by
> putting the same code in there three times, that's bad for
> maintenance reasons. [...]
Done.
https://gitlab.com/lilypond/lilypond/-/merge_requests/520
Werne
>> > But please generate the files in the build directory by
>> > specifying --destdir (and use them from there), putting things in
>> > a cache directory located in the user's $HOME directory is IMHO a
>> > very poor default choice...
>>
>> Why? IMHO those two TFM files are to be handled *exact
12 matches
Mail list logo
