This is absolutely not our bug.
I did not say this is lyx' fault. I said that lyx is vulnerable to an
existing mail system caveat, and lyx is likely to be the scapegoat. To
the best interest of lyx, I suggest that lyx do something with it.
You and other developers have all the reasons to say
This is absolutely not our bug.
I did not say this is lyx' fault. I said that lyx is vulnerable to an
existing mail system caveat, and lyx is likely to be the scapegoat. To
the best interest of lyx, I suggest that lyx do something with it.
You and other developers have all the reasons to say
> This is absolutely not our bug.
I did not say this is lyx' fault. I said that lyx is vulnerable to an
existing mail system caveat, and lyx is likely to be the scapegoat. To
the best interest of lyx, I suggest that lyx do something with it.
You and other developers have all the reasons to say
Dear list,
I have not been able to track down the source of this problem. Some of
my colleagues use different versions of lyx (such as 1.3.5) on
different platforms (linux/windows). If I send my lyx file
(linux/1.3.6-1) to them and let them modify it, the revised version
will have additional dot
Dear list,
I have not been able to track down the source of this problem. Some of
my colleagues use different versions of lyx (such as 1.3.5) on
different platforms (linux/windows). If I send my lyx file
(linux/1.3.6-1) to them and let them modify it, the revised version
will have additional dot
Dear list,
I have not been able to track down the source of this problem. Some of
my colleagues use different versions of lyx (such as 1.3.5) on
different platforms (linux/windows). If I send my lyx file
(linux/1.3.6-1) to them and let them modify it, the revised version
will have additional dot
