Hello,
After today's pull of auctex, I'm getting a
"font-latex-match-warning-make" void function error and auctex will not
load.
Best wishes,
Colin Baxter.
Hi Colin,
>>>>> Colin Baxter writes:
> After today's pull of auctex, I'm getting a
> "font-latex-match-warning-make" void function error and auctex will not
> load.
Thank you, fixed in the git repo. Recent reorder in font-latex.el broke
the dependen
>>>>> Ikumi Keita writes:
> Hi Colin,
>>>>> Colin Baxter writes:
>> After today's pull of auctex, I'm getting a
>> "font-latex-match-warning-make" void function error and auctex
>> will not load.
>>>>> Ikumi Keita writes:
> Hi Colin,
>>>>> Colin Baxter writes:
>> After today's pull of auctex, I'm getting a
>> "font-latex-match-warning-make" void function error and auctex will not
>> load.
> Thank you, fixed
Dear Ikumi,
> Ikumi Keita writes:
> Ah, no. The fontification doesn't happen when I open another latex
> file. I have to figure out why...
> Regards, Ikumi Keita
Yes, I can confirm that. I was too quick off the mark in my previous
email. I should have checked more thoroughly.
B
> Colin Baxter writes:
> Ikumi Keita writes:
>> Ah, no. The fontification doesn't happen when I open another latex
>> file. I have to figure out why...
>> Regards, Ikumi Keita
> Yes, I can confirm that. I was too quick off the mark in my previous
> email. I should have checked more thor
> At last I managed to figure out the origin and seem to recover the
> normal behavior. Sorry for your inconvinience.
Clearly I'm to blame, so thanks for the fix.
Stefan Monnier writes:
>> At last I managed to figure out the origin and seem to recover the
>> normal behavior. Sorry for your inconvinience.
>
> Clearly I'm to blame, so thanks for the fix.
Get your shits together, Stefan, and thanks a lot! ;-)
I've just merged master into externals/auctex.
> Tassilo Horn writes:
> Stefan Monnier writes:
>>> At last I managed to figure out the origin and seem to recover
>>> the normal behavior. Sorry for your inconvinience.
>>
>> Clearly I'm to blame, so thanks for the fix.
> Get your shits together, Stefan, and thanks
> Stefan Monnier writes:
>> At last I managed to figure out the origin and seem to recover the
>> normal behavior. Sorry for your inconvinience.
> Clearly I'm to blame, so thanks for the fix.
Sorry, I should have actually tested before merge. Actually, I think
that the relevant code should b
> Get your shits together, Stefan,
I'll try to mess up in a more challenging way next time, I promise.
> I've just merged master into externals/auctex. Could you please check
> if everything's right there, i.e., foremost that changes in *.el.in
> files on master are in the corresponding *.el fil
Stefan Monnier writes:
>> Get your shits together, Stefan,
>
> I'll try to mess up in a more challenging way next time, I promise.
Challenge accepted. :-)
>> I've just merged master into externals/auctex. Could you please
>> check if everything's right there, i.e., foremost that changes in
>>
> Stefan Monnier writes:
> Also, I had changes in the `README` which I had to throw out because
> I couldn't find anything corresponding to it in the auctex.git code.
The README file is generated from intro.texi and preview-readme.texi in
auctex.git, so README itself isn't under control of gi
>> Also, I had changes in the `README` which I had to throw out because
>> I couldn't find anything corresponding to it in the auctex.git code.
> The README file is generated from intro.texi and preview-readme.texi in
> auctex.git, so README itself isn't under control of git and is listed in
> .git
> Tassilo Horn writes:
> Stefan Monnier writes:
>>> Get your shits together, Stefan,
>>
>> I'll try to mess up in a more challenging way next time, I promise.
> Challenge accepted. :-)
Well, it seems that we already have a challenge. :-)
I'm now fixing regression tests, and found that pre
>>> I'll try to mess up in a more challenging way next time, I promise.
>> Challenge accepted. :-)
> Well, it seems that we already have a challenge. :-)
> I'm now fixing regression tests, and found that preview.el(.in) still
> needs adaptation because it uses ad-{enable,disable}-advice explicitly.
> Stefan Monnier writes:
>> Attached is a possible solution. Stefan, is it safe to repeat the same
>> `advice-add' or `advice-remove'? That is,
> Yes, they're idempotent.
>> Experiments seem to suggest that it's safe. But if not, I have to add
>> `advice-member-p' test.
> Not needed.
Thank
> Well, this is a piece of regresstion test suits and the variable in
> question is used only within this particular `ert-deftest'. So I
> presumed it's OK. Is this presumtion wrong?
Do you *need* the variable to be called "var"? If not, then renaming it
will save you the trouble of wondering und
> Stefan Monnier writes:
> Do you *need* the variable to be called "var"? If not, then renaming it
> will save you the trouble of wondering under which circumstances it's OK
> to use just "var".
I see, thanks for explanation.
Regards,
Ikumi Keita
19 matches
Mail list logo
