On 04/08/2023 11:07, Scott Kostyshak wrote:
On Fri, Aug 04, 2023 at 10:27:28AM +0300, Folsk Pratima wrote:
Then there is still a question as to why the declared module does not do
what it is supposed to do? Or do you think I should create a different
thread for this question?
Could you please
On Fri, Aug 04, 2023 at 10:27:28AM +0300, Folsk Pratima wrote:
> Then there is still a question as to why the declared module does not do
> what it is supposed to do? Or do you think I should create a different
> thread for this question?
Could you please attach a simple example .lyx file?
/On Thu Aug 3 13:42:06 UTC 2023///, *Pavel Sanda* wrote:
>I am afraid you will need to use the hackish solution.
>https://www.lyx.org/trac/ticket/5366
Then there is still a question as to why the declared module does not do
what it is supposed to do? Or do you think I should create a
Am Thu, 3 Aug 2023 15:42:06 +0200
schrieb Pavel Sanda :
> On Wed, Aug 02, 2023 at 08:39:14PM +0300, Folsk Pratima wrote:
> > One solution to this problem is loading *hyperref* manually, however, I
> > think of this as of a hack. Is it possible to somehow make *titlesec* to be
> > loaded before
On Wed, Aug 02, 2023 at 08:39:14PM +0300, Folsk Pratima wrote:
> One solution to this problem is loading *hyperref* manually, however, I
> think of this as of a hack. Is it possible to somehow make *titlesec* to be
> loaded before *hyperref*?
I am afraid you will need to use the hackish solution.
LyX generated preamble package loading order.
Greetings.
Debian 11. LyX 2.3.6 (2020-11-27).
I want to use *titlesec* package in my document. However, if it is
loaded /after/ *hyperref* package, it causes inconsistent behavior. For
example, ToC entries might point to wrong places.
One
