On 2023-02-02 17:29, Richard Kimberly Heck wrote:
On 2/2/23 08:49, Daniel wrote:
Some modules exclude other modules. I took this to be a symmetric
relationship. However, for example, compare
AMS Theorems:
"Modules excluded: Standard Theorems and Standard Theorems (Unnumbered)."
and
AMS Theorems (Numbered by Type):
"Modules excluded: Standard Theorems, Standard Theorems (Unnumbered),
*AMS Theorems*, and Standard Theorems (Numbered by Type)."
Yes, it should be symmetric.
Also, has the feasibility of automatic inclusion/exclusion been
considered? I mean: when a module A is added and another module B is
incompatible/a dependency, then the user is asked whether B should be
removed/added in order to add A.
At present, you can't add incompatible modules, or ones that have
unsatisfied dependencies. It would be helpful to do it the way you
suggest, but this could get very messy (too messy) in some cases. E.g.,
someone wants to add a module that has unsatisfied dependencies, and
those dependencies exclude some module already installed, which itself
was a dependency for some other module. I don't think we want to do that
automatically, or even suggest it.
Riki
I am not fully sure whether the problem is in the implementation or the
usefulness? Your last sentence sounds a bit like the latter is the case.
I think, in your example case it would be particularly useful to have an
automatic removal because it would be so hard to figure the dependencies
out by oneself.
If I understood it correctly, the case is:
- Want to add: A
- Already added: C, D
- A depends on B
- B excludes C
- C depends on D
LyX suggests: Add B and remove C? [Yes] [No]
But probably it is the implementation that would be the issue.
Daniel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
