On Wed, Sep 09, 2020 at 12:40:36AM +0200, Enrico Forestieri wrote: > On Tue, Sep 08, 2020 at 05:28:58PM -0400, Scott Kostyshak wrote: > > On Tue, Sep 08, 2020 at 11:04:39PM +0200, Enrico Forestieri wrote: > > > On Mon, Sep 07, 2020 at 11:34:50PM +0200, Enrico Forestieri wrote: > > > > On Mon, Sep 07, 2020 at 07:02:39PM +0200, Enrico Forestieri wrote: > > > > > On Mon, Sep 07, 2020 at 12:43:35PM +0200, Jean-Marc Lasgouttes wrote: > > > > > > > > > > And if this is OK, I should do the same for iint, iiint and iiiint, > > > > > > right? > > > > > > > > > > Yes, this fixes it, but also reveals another problem. If a macro > > > > > appears > > > > > in the expansion of a \def, its requirements are also taken into > > > > > account. > > > > > This is wrong, because the \def is only meant for on-screen > > > > > representation > > > > > and not for output. So, the correct patch would be fixing this glitch. > > > > > This time you incurred in it, but I bet it will bite again. > > > > > > > > The attached patch works for me. > > > > > > Scott, does it work for you? > > > > Yes, with the patch the esint package is not loaded. I only applied your > > patch and not the other patch in this thread. Let me know if I was > > supposed to test with both. > > No, you did it right. My point was that the other patch was only hiding > the problem.
In the absence of comments from JMarc, I committed the patch at fcd14df2. -- Enrico -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
