Re: Bug while cutting rows of a table

2024-05-19 Thread Jean-Marc Lasgouttes 

Le 19/05/2024 à 19:14, emile a écrit :
On several occasions I have encountered a LyX2.4R4 crash when trying to 
delete several consecutive rows from a table, either under Windows or 
Linux. I have reproduced this phenomenon on the empty table attached.




Hello Émile,

Can you describe precisely what you do to obtain a crash? I tried a bit, 
but I am probably not doing the right things.


JMarc

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug Report - 2.3.7

2023-07-12 Thread Julio Rojas 
Lyx 2.3.6.1 on Windows 11 here, no problem.
*Dr. Julio Rojas Mora*
Director del Dpto. de Ing. Informática
Universidad Católica de Temuco
Campus San Juan Pablo II
Rudecindo Ortega 02950
Edif. Biblioteca, 2do Piso, Oficina EB1-213
Temuco, Chile
Tlf: +56-45-2205229


El mar, 11 jul 2023 a la(s) 12:39, Richard Kimberly Heck (rikih...@gmail.com)
escribió:

> On 7/11/23 08:42, Xm Z wrote:
>
> Latex code \approx cannot be correctly displayed in lyx window, but can be
> compiled correctly. Like the plot in the following.
> Version: LyX 2.3.7.
> [image: image.png]
>
> This is the mailing list for discussing documentation. I'm transferring
> discussion to lyx-users.
>
> I use \approx sometimes and have not seen this error. What OS?
>
> Riki
>
>
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug Report - 2.3.7

2023-07-11 Thread Richard Kimberly Heck 

On 7/11/23 08:42, Xm Z wrote:
Latex code \approx cannot be correctly displayed in lyx window, but 
can be compiled correctly. Like the plot in the following.

Version: LyX 2.3.7.
image.png


This is the mailing list for discussing documentation. I'm transferring 
discussion to lyx-users.


I use \approx sometimes and have not seen this error. What OS?

Riki

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug tracker accounts

2022-07-20 Thread Steve Litt 
On Wed, 2022-07-20 at 14:49 +0200, Dr Eberhard Lisse wrote:
> 
> On 15/07/2022 23:16, Steve Litt wrote:
> [...]
> > Or, how's this for a novel idea: How about discussing bugs on the
> > mailing list so that many eyes can effortlessly and immediately peruse
> > it and many voices can effortlessly narrow it down.  This will weed
> > out the "defective user" caused bugs, and will produce a pinpoint
> > accurate symptom description for the overworked developer.
> [...]

> While deliberation on email lists are very helpful that just will not
> work for software development, not even in closed shops, but most
> certainly not in Open Source projects and large ones such as this.
> 
> el

N O T   T R U E !

SteveT
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug tracker accounts

2022-07-20 Thread Dr Eberhard Lisse 



While deliberation on email lists are very helpful that just will not
work for software development, not even in closed shops, but most
certainly not in Open Source projects and large ones such as this.

el

On 15/07/2022 23:16, Steve Litt wrote:
[...]

Or, how's this for a novel idea: How about discussing bugs on the
mailing list so that many eyes can effortlessly and immediately peruse
it and many voices can effortlessly narrow it down.  This will weed
out the "defective user" caused bugs, and will produce a pinpoint
accurate symptom description for the overworked developer.

[...]

--
To email me replace 'nospam' with 'el'

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug tracker accounts

2022-07-15 Thread Jean-Marc Lasgouttes 


Le 15/07/2022 à 23:16, Steve Litt a écrit :

Or, how's this for a novel idea: How about discussing bugs on the
mailing list so that many eyes can effortlessly and immediately peruse
it and many voices can effortlessly narrow it down. This will weed out
the "defective user" caused bugs, and will produce a pinpoint accurate
symptom description for the overworked developer.


There are many things that are possible with a bug tracker and not 
email. For example, a new developer can understand what choices were 
made 10 years before, and why.


But, yes, we do use the mailing list at times to pinpoint bugs. Actually 
some bugs or even new features just got fixed/implemented this way recently.


JMarc
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug tracker accounts

2022-07-15 Thread Steve Litt 
Pavel Sanda said on Thu, 14 Jul 2022 01:07:33 +0200

>Dear LyXers,
>
>we recently suffer massive spam abuse in our bug tracker. For the
>moment we disabled automatized account creation and removed approx.
>30k fake user accounts.

[snip]

>If new account needs to be (re)created, please send the request to
>mailling list and we'll do it for you until new solution is found
>(captcha/migration to different platform).

Or, how's this for a novel idea: How about discussing bugs on the
mailing list so that many eyes can effortlessly and immediately peruse
it and many voices can effortlessly narrow it down. This will weed out
the "defective user" caused bugs, and will produce a pinpoint accurate
symptom description for the overworked developer.

SteveT

Steve Litt 
Summer 2022 featured book: Making Mental Models: Advanced Edition
http://www.troubleshooters.com/mmm
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

2020-02-05 Thread Stephan Witt 
> Am 05.02.2020 um 23:33 schrieb emile lunardon :
> 
> I have installed LyX 2.3.4 on Windows10 and the same crash already seen on 
> LyX for Linux occurs when trying to enter the two Math Symbols : 
> $\textrm{Ø}\textrm{Å}$
> 
> Le mer. 5 févr. 2020 à 08:32, emile lunardon  a 
> écrit :
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols 
> shown in the attached file (written with LyX 1.3.3), there is a crash of LyX 
> 1.3.4 with the attached messages.
> 
> Can someone confirm this strange phenomena ?

I can confirm your bug with Qt5 on macOS with LyX 2.3.4. I think this is the 
version you’re talking about all the time.

One has to use the math toolbar and there choose the symbol Å from the 
miscellaneous pane.

The backtrace is:

(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS 
(code=1, address=0x18)
frame #0: 0x0001000699dc 
LyX`lyx::Buffer::params(this=0x) at Buffer.cpp:719:9
frame #1: 0x00010079fa18 LyX`lyx::(anonymous 
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf23e0, 
flags=128, mode=TEXT_MODE, numbered=false) at MathParser.cpp:2080:20
  * frame #2: 0x000100790987 LyX`lyx::(anonymous 
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x000113353690, 
flags=64, mode=TEXT_MODE) at MathParser.cpp:782:2
frame #3: 0x00010079f18c LyX`lyx::(anonymous 
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf5a30, 
flags=0, mode=MATH_MODE, numbered=false) at MathParser.cpp:2013:6
frame #4: 0x000100790987 LyX`lyx::(anonymous 
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x7ffeefbf6530, 
flags=0, mode=MATH_MODE) at MathParser.cpp:782:2
frame #5: 0x000100790874 
LyX`lyx::mathed_parse_cell(ar=0x7ffeefbf6530, str=L"\\textrm \\AA", 
f=NORMAL) at MathParser.cpp:2156:37
frame #6: 0x0001007c28d2 LyX`lyx::asArray(str=L"\\textrm \\AA", 
ar=0x7ffeefbf6530, pf=NORMAL) at MathSupport.cpp:990:38
frame #7: 0x0001006deba4 
LyX`lyx::InsetMathNest::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathNest.cpp:1237:4
frame #8: 0x00010065baa2 
LyX`lyx::InsetMathGrid::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathGrid.cpp:1733:18
frame #9: 0x00010067e615 
LyX`lyx::InsetMathHull::doDispatch(this=0x0001112cde10, 
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathHull.cpp:2024:18
frame #10: 0x000100811520 
LyX`lyx::Inset::dispatch(this=0x0001112cde10, cur=0x000106149098, 
cmd=0x7ffeefbf9068) at Inset.cpp:325:2
frame #11: 0x0001001e018b 
LyX`lyx::Cursor::dispatch(this=0x000106149098, cmd0=0x00011123dd68) at 
Cursor.cpp:337:11
frame #12: 0x000100d876b4 
LyX`lyx::frontend::GuiView::dispatchToBufferView(this=0x00011159b6f0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:3687:15
frame #13: 0x000100d80df6 
LyX`lyx::frontend::GuiView::dispatch(this=0x00011159b6f0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:4343:4
frame #14: 0x000100a96008 
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0, 
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiApplication.cpp:2076:19
frame #15: 0x000100a8ff88 
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0, 
cmd=0x00011123dd68) at GuiApplication.cpp:1405:3
frame #16: 0x00010037a4ea LyX`lyx::dispatch(action=0x00011123dd68) 
at LyX.cpp:1462:19
frame #17: 0x000100a41c4b 
LyX`lyx::frontend::Action::action(this=0x00011334a560) at Action.cpp:87:2
frame #18: 0x000100a41d51 
LyX`lyx::frontend::Action::qt_static_metacall(_o=0x00011334a560, 
_c=InvokeMetaMethod, _id=1, _a=0x7ffeefbfc970) at moc_Action.cpp:81:21
frame #19: 0x00010554d63a QtCore`QMetaObject::activate(QObject*, int, 
int, void**) + 2298
frame #20: 0x00010474e185 
QtWidgets`QAction::activate(QAction::ActionEvent) + 309
frame #21: 0x000104841be3 QtWidgets`QAbstractButtonPrivate::click() + 
147
frame #22: 0x000104842d6c 
QtWidgets`QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 268
frame #23: 0x000104939bbf 
QtWidgets`QToolButton::mouseReleaseEvent(QMouseEvent*) + 15
frame #24: 0x0001047931d2 QtWidgets`QWidget::event(QEvent*) + 450
frame #25: 0x00010493a14f QtWidgets`QToolButton::event(QEvent*) + 319
frame #26: 0x0001047576ff 
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 271
frame #27: 0x00010475a59d QtWidgets`QApplication::notify(QObject*, 
QEvent*) + 7373
frame #28: 0x000100a9d033 
LyX`lyx::frontend::GuiApplication::notify(this=0x000105d0a1d0, 
receiver=0x0001114debf0, event=0x7ffeefbfd060) at 
GuiApplication.cpp:2712:24
frame #29: 0x00010551c684 
QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) +

Re: Bug in Lyx 1.3.4 ?

2020-02-05 Thread emile lunardon 
I have installed LyX 2.3.4 on Windows10 and the same crash already seen on
LyX for Linux occurs when trying to enter the two Math Symbols :
$\textrm{Ø}\textrm{Å}$

Le mer. 5 févr. 2020 à 08:32, emile lunardon  a
écrit :

> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of
> LyX 1.3.4 with the attached messages.
>
> Can someone confirm this strange phenomena ?
>
> --
>
> (  1) ./lyx: ./lyx() [0x906d2a]
> (  2) ./lyx: ./lyx() [0x9062e6]
> (  3) ./lyx: ./lyx() [0x63e005]
> (  4) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]
> (  5) ./lyx: ./lyx() [0x5553f0]
> (  6) ./lyx: ./lyx() [0x7bcbcd]
> (  7) ./lyx: ./lyx() [0x7b6231]
> (  8) ./lyx: ./lyx() [0x7bcf6a]
> (  9) ./lyx: ./lyx() [0x7b6231]
> ( 10) ./lyx: ./lyx() [0x7b6381]
> ( 11) ./lyx: ./lyx() [0x7c4f15]
> ( 12) ./lyx: ./lyx() [0x791b67]
> ( 13) ./lyx: ./lyx() [0x7e87a8]
> ( 14) ./lyx: ./lyx() [0x77274b]
> ( 15) ./lyx: ./lyx() [0x812b46]
> ( 16) ./lyx: ./lyx() [0x5d41dd]
> ( 17) ./lyx: ./lyx() [0x9321bb]
> ( 18) ./lyx: ./lyx() [0x9429f6]
> ( 19) ./lyx: ./lyx() [0x911f0e]
> ( 20) ./lyx: ./lyx() [0x90c5e9]
> ( 21) ./lyx: ./lyx() [0x98abf1]
> ( 22) ./lyx: ./lyx() [0x98ac78]
> ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
> ( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
> ( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAction::activate(QAction::ActionEvent)
> ( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
> ( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAbstractButton::mouseReleaseEvent(QMouseEvent*)
> ( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QToolButton::mouseReleaseEvent(QMouseEvent*)
> ( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
> ( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::notify_helper(QObject*, QEvent*)
> ( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::notify(QObject*, QEvent*)
> ( 32) ./lyx: ./lyx() [0x916195]
> ( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QCoreApplication::notifyInternal(QObject*, QEvent*)
> ( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
> QWidget*, QWidget**, QPointer&, bool)
> ( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
> ( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::x11ProcessEvent(_XEvent*)
> ( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
> ( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7)
> [0x7fbd1b301417]
> ( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
> ( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)
> [0x7fbd1b3016dc]
> ( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventDispatcherGlib::processEvents(QFlags)
> ( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
> ( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::processEvents(QFlags)
> ( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::exec(QFlags)
> ( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
> ( 46) ./lyx: ./lyx() [0x643306]
> ( 47) ./lyx: ./lyx() [0x50827d]
> ( 48) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]
> ( 49) ./lyx: ./lyx() [0x512eba]
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

2020-02-05 Thread Pavel Sanda 
On Wed, Feb 05, 2020 at 08:32:21AM +0100, emile lunardon wrote:
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of
> LyX 1.3.4 with the attached messages.
> 
> Can someone confirm this strange phenomena ?

I can not (tried with Qt 4 as you do). (My entering was copy paste from your 
document.)
Your backtrace is not much useful, if you compile on your own we would need it 
with debug symbols...
Pavel
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

2020-02-05 Thread Paul A. Rubin 

On 2/5/20 2:32 AM, emile lunardon wrote:
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math 
symbols shown in the attached file (written with LyX 1.3.3), there is 
a crash of LyX 1.3.4 with the attached messages.


Can someone confirm this strange phenomena ?

--

(  1) ./lyx: ./lyx() [0x906d2a]
(  2) ./lyx: ./lyx() [0x9062e6]
(  3) ./lyx: ./lyx() [0x63e005]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]

(  5) ./lyx: ./lyx() [0x5553f0]
(  6) ./lyx: ./lyx() [0x7bcbcd]
(  7) ./lyx: ./lyx() [0x7b6231]
(  8) ./lyx: ./lyx() [0x7bcf6a]
(  9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QToolButton::mouseReleaseEvent(QMouseEvent*)

( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) 
[0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) 
[0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]

( 49) ./lyx: ./lyx() [0x512eba]

LyX 1.3.4 is rather old. Have you tried a more recent version? I cannot 
reproduce the crash, but I'm using LyX 2.3.3.


Paul

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in Lyx 1.3.4 ?

2020-02-04 Thread Daniel 
I seem to have no problem entering them on MacOS. Though if I use the 
keyboard to enter them I get


$\mathrm{\mathring{A}}$$\mathrm{\slashed{O}}$

instead of

$\textrm{Å}$$\textrm{Ø}$

However, if I copy and paste the symbols from the file, I get the latter 
and no crash either.


Daniel

On 2020-02-05 08:32, emile lunardon wrote:
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math 
symbols shown in the attached file (written with LyX 1.3.3), there is a 
crash of LyX 1.3.4 with the attached messages.


Can someone confirm this strange phenomena ?

--

(  1) ./lyx: ./lyx() [0x906d2a]
(  2) ./lyx: ./lyx() [0x9062e6]
(  3) ./lyx: ./lyx() [0x63e005]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]

(  5) ./lyx: ./lyx() [0x5553f0]
(  6) ./lyx: ./lyx() [0x7bcbcd]
(  7) ./lyx: ./lyx() [0x7b6231]
(  8) ./lyx: ./lyx() [0x7bcf6a]
(  9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QToolButton::mouseReleaseEvent(QMouseEvent*)

( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]

( 49) ./lyx: ./lyx() [0x512eba]




--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Bug in LyX regarding page format and hyperref

2019-08-06 Thread Jürgen Spitzmüller 
Am Montag, den 05.08.2019, 16:19 +0200 schrieb Jürgen Spitzmüller:
> But still, if A4 is selected in LyX and memoir outputs US
> letter, that's simply plain wrong. We can do better.

This will be fixed in LyX 2.3.4.

Jürgen


signature.asc
Description: This is a digitally signed message part

Re: Bug in LyX regarding page format and hyperref

2019-08-05 Thread Jürgen Spitzmüller 
Am Montag, den 05.08.2019, 08:22 -0500 schrieb Les:
> I doubt if accounting for Memoir's idiosyncracies is practical. The
> Memoir class allows fine tuning of numerous parameters that LyX
> doesn't
> even know about.

I know. But still, if A4 is selected in LyX and memoir outputs US
letter, that's simply plain wrong. We can do better.

Jürgen


signature.asc
Description: This is a digitally signed message part

Re: Bug in LyX regarding page format and hyperref

2019-08-05 Thread Les 
On Mon, 05 Aug 2019 10:40:53 +0200
Jürgen Spitzmüller  wrote:

> Yes, memoir overrides geometry (which is used for the custom margins).
> However, we could account for that in LyX. See
> https://www.lyx.org/trac/ticket/10970

I doubt if accounting for Memoir's idiosyncracies is practical. The
Memoir class allows fine tuning of numerous parameters that LyX doesn't
even know about. It's not just page format, its:
\setstocksize
\settrimmedsize
\settrims
\settypeblocksize
\setlrmargins
\setlength{\marginparwidth}
\pagestyle
\chapterstyle
and many other parameters I've never used.

If you're not prepared to read the 609 page Memoir manual (memman.pdf)
you really shouldn't try to use Memoir.

If you do read it, and understand it, you will view page layout in a
completely new way.

I have used memoir extensively for years, and I'm still learning how to
improve page layout. If you want good page layout that is nearly what
you need, use KOMA-script Book. If you want an exact page layout, use
Memoir, but be prepared to learn how to do it.

Les
-- 
Les Denham

Re: Bug in LyX regarding page format and hyperref

2019-08-05 Thread Jürgen Spitzmüller 
Am Samstag, den 27.07.2019, 11:06 -0400 schrieb Paul A. Rubin:
> I don't have any experience with book classes, so I do not know the 
> peculiarities of the Memoir class. I suspect this is problem with
> how 
> Memoir reacts to certain combinations of things, rather than a LyX
> bug. 

Yes, memoir overrides geometry (which is used for the custom margins).
However, we could account for that in LyX. See
https://www.lyx.org/trac/ticket/10970

Jürgen


signature.asc
Description: This is a digitally signed message part

Re: Bug in LyX regarding page format and hyperref

2019-07-29 Thread Baris Erkus 
On 27-Jul-19 9:32 AM, Marius Shekow wrote:
> Hi again,
>
> I forgot to mention that you also need to set custom page margins. An
> example file is attached.
>
> Best regards!
>
> Am 26.07.2019 um 20:14 schrieb Marius Shekow:
>> Hi,
>>
>> I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
>> is of "US Letter" size, even though I've explicitly set up A4 in the
>> document settings (Page Layout -> Format). This happens once I enable
>> Hyperref support in the document settings.
>>
>> As suggested in
>> https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size
>>  
>>
>> it seems that adding "a4paper" as custom option to the documentclass
>> seems to work. This is extreme expert knowledge that you should not
>> expect your users to have. When a normal/novice user sets up A4, then
>> the generated PDF should be A4 (and the same goes for any other page
>> format).
>>
>> Is this something that you could fix?
>>
>> Best regards!
>> Marius
>>
Hello Marius,

As you may be aware of that LyX serves as a front-end for the LaTeX 
system. When you select a paper size in LyX, LyX -probably- simply adds 
that paper size as an option to the document class in the generated tex 
file.

On the other hand, LaTeX is a sophisticated typesetting system, where 
many packages and classes are used. Sometimes, some of these packages 
and classes have conflicts and associated rules. When you try to use 
some specific packages for a given class, you may not be allowed to 
change some settings.

As far as I observe, LyX developers are trying to identify these 
conflicts and implement LyX-based solutions for some of them. However, 
it is not always possible to follow every single one of these 
conflicts/rules since there are so many of these packages and classes. 
Further, LaTeX packages are being updated constantly and may result a 
conflict after an update, which makes it very difficult to track them.

To put this in another way, if you are not using LyX, but using 
conventional text-based LaTeX typesetting, you will probably encounter 
these issues as well. If this issue is a well-known issue, LyX 
developers might have provided a solution in LyX. However, it is not 
always possible for LyX to have a solution. In this case, you are 
supposed to identify the issue and provide a solution by yourself, which 
we LyX-used do all the time.

Best Regards,

Baris

-- 
↓↓
Please bottom-post. Start your reply here:

Re: Bug in LyX regarding page format and hyperref

2019-07-27 Thread Marius Shekow 

Hi,

I was aware of https://wiki.lyx.org/LyX/UsingMemoirInLyX but at the same
time that page seems outdated, as it explicitly mentions Lyx 1.5, which
is dated. I saw that it also mentions section 6.3 of the "Additional
Features" LyX help document (valid for LyX 2.x), but did not see this
caveat (US Letter) being listed. It may still make sense for LyX to
handle this specific case, but that's up to you. I'm content with the
fix I found (which I mentioned in the original post).

I've been using memoir simply out of habit. I don't think I'm using
specific features that other book classes wouldn't offer. I'd say that I
just liked the look of the generated PDF that came out of the box, in
comparison to other book classes. I may look into scrbook for the next
project, though.

Best!
Marius

Am 27.07.2019 um 17:27 schrieb Axel Dessecker:

Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow:

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa
ge-change-the-paper-size it seems that adding "a4paper" as custom option
to the documentclass seems to work. This is extreme expert knowledge that
you should not expect your users to have. When a normal/novice user sets
up A4, then the generated PDF should be A4 (and the same goes for any
other page format).

Is this something that you could fix?

Best regards!
Marius

Marius,

I can reproduce this behaviour, which seems to be associated with the memoir
class. Very configurable but tricky, as announced at
https://wiki.lyx.org/LyX/UsingMemoirInLyX .

Is there a specific reason why you are not using scrbook?

Axel

Re: Bug in LyX regarding page format and hyperref

2019-07-27 Thread Axel Dessecker 
Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow:
> Hi again,
> 
> I forgot to mention that you also need to set custom page margins. An
> example file is attached.
> 
> Best regards!
> 
> Am 26.07.2019 um 20:14 schrieb Marius Shekow:
> > Hi,
> > 
> > I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
> > is of "US Letter" size, even though I've explicitly set up A4 in the
> > document settings (Page Layout -> Format). This happens once I enable
> > Hyperref support in the document settings.
> > 
> > As suggested in
> > https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa
> > ge-change-the-paper-size it seems that adding "a4paper" as custom option
> > to the documentclass seems to work. This is extreme expert knowledge that
> > you should not expect your users to have. When a normal/novice user sets
> > up A4, then the generated PDF should be A4 (and the same goes for any
> > other page format).
> > 
> > Is this something that you could fix?
> > 
> > Best regards!
> > Marius

Marius,

I can reproduce this behaviour, which seems to be associated with the memoir 
class. Very configurable but tricky, as announced at 
https://wiki.lyx.org/LyX/UsingMemoirInLyX .

Is there a specific reason why you are not using scrbook?

Axel

Re: Bug in LyX regarding page format and hyperref

2019-07-27 Thread Paul A. Rubin 

On 7/27/19 2:32 AM, Marius Shekow wrote:

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size 


it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius


Please bottom post in messages to the forum.

I can confirm your example compiles to US letter when it should compile 
to A4, but the trigger mechanism is more complex than hyperref + custom 
margins + A4 paper size. It only seems to happen with the Memoir class. 
I tried the basic book class, the AMS book class and also the basic 
article class, and they all compiled to A4.


I don't have any experience with book classes, so I do not know the 
peculiarities of the Memoir class. I suspect this is problem with how 
Memoir reacts to certain combinations of things, rather than a LyX bug. 
Perhaps an experience Memoir user can weigh in.


Paul

Re: Bug in LyX regarding page format and hyperref

2019-07-27 Thread Marius Shekow 

Hi again,

I forgot to mention that you also need to set custom page margins. An
example file is attached.

Best regards!

Am 26.07.2019 um 20:14 schrieb Marius Shekow:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that
is of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size
it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius



newfile2.lyx
Description: application/lyx

Re: Bug in LyX regarding page format and hyperref

2019-07-26 Thread Paul A. Rubin 

On 7/26/19 2:14 PM, Marius Shekow wrote:

Hi,

I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is
of "US Letter" size, even though I've explicitly set up A4 in the
document settings (Page Layout -> Format). This happens once I enable
Hyperref support in the document settings.

As suggested in
https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size 


it seems that adding "a4paper" as custom option to the documentclass
seems to work. This is extreme expert knowledge that you should not
expect your users to have. When a normal/novice user sets up A4, then
the generated PDF should be A4 (and the same goes for any other page
format).

Is this something that you could fix?

Best regards!
Marius

I'm unable to reproduce that here. I switched a document from US Letter 
to A4 in the page layout settings, turned on hyperref in the PDF 
settings, viewed the document (using pdflatex), and the resulting file 
was A4 (confirmed by checking File > Properties in the PDF viewer). I 
also tried A2, which produces a visibly different result (many fewer pages).


If you can reproduce the bug, please reply with a minimal working 
example of it.


Paul

Re: Bug Lyx 2.2.2 saving file

2017-01-24 Thread Kornel Benko 
Am Dienstag, 24. Januar 2017 um 13:08:49, schrieb Sven Diermann 

> Hi Kornel,
> 
> 
> 
> Please find my answers below.
> 
> These are the error messages:
> 
> [cid:image001.png@01D27696.86D82590]
> 
> 
> 
> [cid:image002.png@01D27696.CF60B840]
> 

I see. And yes, it is confusing.

> 
> And this appears every time, I want to save anything.
> 

Can it be you are editing the backup-file?

> 
> What can I do?
> 

Sorry, I cannot see this effect here. Maybe on windows only?

> 
> Wir koennen auch gern auf Deutsch schreiben.
> 

Das würde leider auch nicht helfen.

Kornel

signature.asc
Description: This is a digitally signed message part.

RE: Bug Lyx 2.2.2 saving file

2017-01-24 Thread Sven Diermann 
Hi Kornel,



Please find my answers below.

These are the error messages:

[cid:image001.png@01D27696.86D82590]



[cid:image002.png@01D27696.CF60B840]



And this appears every time, I want to save anything.



What can I do?



Wir koennen auch gern auf Deutsch schreiben.



Sven



-Original Message-
From: Kornel Benko [mailto:kor...@lyx.org]
Sent: Tuesday, 24 January 2017 10:44 PM
To: lyx-users@lists.lyx.org
Cc: Sven Diermann <s.dierm...@uq.edu.au>
Subject: Re: Bug Lyx 2.2.2 saving file



Am Dienstag, 24. Januar 2017 um 11:12:04, schrieb Sven Diermann 
<s.dierm...@uq.edu.au<mailto:s.dierm...@uq.edu.au>>

> Dear Mr. Benko,



Hi, first of all, please keep the conversation on the mailing list.



> I am a big fan of Lyx and I thought I upgrade to the latest version 2.2.2 
> after using 2.1.3.

> Now I have trouble saving the .lyx file. The error message says:

> LyX: Backup failure.

> Cannot create backup file "THE PATH WERE I WANT TO SAVE IT". Please check 
> whether the directory exists and is writable.



How did you specify the backup directory?

(I suppose 'Tools->Preferences...->Paths->BackUp directory')

Yes



> It certainly exists and is writable because I just created this file 1min ago 
> for test purposes.

> Instead it saves the file under a alternative name such as:

> Wanted: test.lyx

> Actual: test-qr6264.lyx



What is wrong with this file name? In the end it is backup only, not meant for 
normal workflow.

The issue is that it doesn’t save the original file.





> I tried to use the backup directory, however if I use it all the "\" are 
> converted to "!"

> which does not help the problem in identifying the correct path.



You mean, you are using '"' chars in file names?

Normally I'd expect the path-separators to be converted to '!'.



> Thanks for your help.

>

> Best regards,

> Sven Diermann



Kornel

Re: Bug Lyx 2.2.2 saving file

2017-01-24 Thread Kornel Benko 
Am Dienstag, 24. Januar 2017 um 11:12:04, schrieb Sven Diermann 

> Dear Mr. Benko,

Hi, first of all, please keep the conversation on the mailing list.

> I am a big fan of Lyx and I thought I upgrade to the latest version 2.2.2 
> after using 2.1.3.
> Now I have trouble saving the .lyx file. The error message says:
> LyX: Backup failure.
> Cannot create backup file "THE PATH WERE I WANT TO SAVE IT". Please check 
> whether the directory exists and is writable.

How did you specify the backup directory?
(I suppose 'Tools->Preferences...->Paths->BackUp directory')

> It certainly exists and is writable because I just created this file 1min ago 
> for test purposes.
> Instead it saves the file under a alternative name such as:
> Wanted: test.lyx
> Actual: test-qr6264.lyx

What is wrong with this file name? In the end it is backup only, not meant for 
normal workflow.

> I tried to use the backup directory, however if I use it all the "\" are 
> converted to "!"
> which does not help the problem in identifying the correct path.

You mean, you are using '"' chars in file names?
Normally I'd expect the path-separators to be converted to '!'.

> Thanks for your help.
> 
> Best regards,
> Sven Diermann

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Bug using BibTex and IEEEtran with author name containing And

2017-01-12 Thread Anders Ekberg 
> On 2017Jan12, at 10:48, Jürgen Spitzmüller  wrote:
> 
> 2017-01-12 9:28 GMT+01:00 Anders Ekberg >:
> I discovered a very strange bug:
> Using Lyx on Mac and inserting a reference file created by BibDesk using the 
> IEEEtran format. The reference file has two entries that have the same 
> authors. One author has a name containing And that I suspect can be related 
> to the problem. In the output the first reference is fine, but in the second 
> the author is missing. If I change the bibliography format to plain 
> everything works. I can also get it to work by tweaking with the authors’ 
> names (e.g. removing the second author). LyX, bib and pdf-files for a minimum 
> example are enclosed.
> 
> Don’t know if it is a bug in LyX, TeX, BibDesk, BibTeX or something else, but 
> it is definitely the strangest bug I have seen for a long time… 
> Any ideas of the cause?
> 
> It's not a bug but a feature of IEEEtran.bst:
> 
> % This function detects entries with names that are identical to that of
> % the previous entry and replaces the repeated names with dashes (if the
> % "is.dash.repeated.names" user control is nonzero).
> FUNCTION {name.or.dash}
> { 's :=
>oldname empty$
>  { s 'oldname := s }
>  { s oldname =
>  { is.dash.repeated.names
>   { repeated.name.dashes }
>   { s 'oldname := s }
> if$
>  }
>  { s 'oldname := s }
>if$
>  }
>if$
> }
> 
> You can switch it off by 
> 
> 1. adding the following entry to your bib file:
> 
> @IEEEtranBSTCTL{IEEEexample:BSTcontrol,
> CTLdash_repeated_names = "no",
> }
> 2. then adding the following to your preamble
> 
> \usepackage{IEEEtrantools}
> 3. and finally, this somewhere in your document:
> 
> \bstctlcite{IEEEexample:BSTcontrol} <>
> 
> HTH
> Jürgen
Thanks, that explained it perfectly!

Anders

Re: Bug using BibTex and IEEEtran with author name containing And

2017-01-12 Thread Jürgen Spitzmüller 
2017-01-12 9:28 GMT+01:00 Anders Ekberg :

> I discovered a very strange bug:
> Using Lyx on Mac and inserting a reference file created by BibDesk using
> the IEEEtran format. The reference file has two entries that have the same
> authors. One author has a name containing And that I suspect can be related
> to the problem. In the output the first reference is fine, but in the
> second the author is missing. If I change the bibliography format to plain
> everything works. I can also get it to work by tweaking with the authors’
> names (e.g. removing the second author). LyX, bib and pdf-files for a
> minimum example are enclosed.
>
> Don’t know if it is a bug in LyX, TeX, BibDesk, BibTeX or something else,
> but it is definitely the strangest bug I have seen for a long time…
> Any ideas of the cause?
>

It's not a bug but a feature of IEEEtran.bst:

% This function detects entries with names that are identical to that of
% the previous entry and replaces the repeated names with dashes (if the
% "is.dash.repeated.names" user control is nonzero).
FUNCTION {name.or.dash}
{ 's :=
   oldname empty$
 { s 'oldname := s }
 { s oldname =
 { is.dash.repeated.names
  { repeated.name.dashes }
  { s 'oldname := s }
if$
 }
 { s 'oldname := s }
   if$
 }
   if$
}

You can switch it off by

1. adding the following entry to your bib file:

@IEEEtranBSTCTL{IEEEexample:BSTcontrol,
CTLdash_repeated_names = "no",
}

2. then adding the following to your preamble

\usepackage{IEEEtrantools}

3. and finally, this somewhere in your document:

\bstctlcite{IEEEexample:BSTcontrol}


HTH

Jürgen




>
> All the best!
> Anders
>
>
>
>
>
>

Re: Bug with theorems in LyX 2.2?

2016-08-11 Thread Scott Kostyshak 
On Thu, Aug 11, 2016 at 03:01:01PM +0200, Kornel Benko wrote:
> Am Donnerstag, 11. August 2016 um 12:34:19, schrieb Bernt Lie 
> <bernt@hit.no>
> > Thanks, Jürgen!
> > -B
> > 
> > From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
> > Jürgen Lange
> > Sent: Thursday, August 11, 2016 14:20
> > To: lyx-users@lists.lyx.org
> > Subject: Re: Bug with theorems in LyX 2.2?
> > 
> > To seperate the two theorems, you have to go to the end of the first 
> > theorem and press 3 times "enter", a red line should occur. Then you can 
> > add your second theorem below.

I did not take a deep look, but perhaps Edit > Start New Environment is
relevant here. The main point is, how can LyX know that you want to
start a new environment and not continue the first one? You have to tell
it in some way. That said, this does seem to be a source of confusion
for many users.

Scott


signature.asc
Description: PGP signature

Re: Bug with theorems in LyX 2.2?

2016-08-11 Thread Kornel Benko 
Am Donnerstag, 11. August 2016 um 12:34:19, schrieb Bernt Lie <bernt@hit.no>
> Thanks, Jürgen!
> -B
> 
> From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
> Jürgen Lange
> Sent: Thursday, August 11, 2016 14:20
> To: lyx-users@lists.lyx.org
> Subject: Re: Bug with theorems in LyX 2.2?
> 
> To seperate the two theorems, you have to go to the end of the first theorem 
> and press 3 times "enter", a red line should occur. Then you can add your 
> second theorem below.
> 

That's better.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Bug with theorems in LyX 2.2?

2016-08-11 Thread Kornel Benko 
Am Donnerstag, 11. August 2016 um 12:01:10, schrieb Bernt Lie 
> I used new "theorem" in both cases. Here is what it looks like:

I see. The only option may be to insert empty text. 
As a separator use standard with ERT containing only {}

Kornel

signature.asc
Description: This is a digitally signed message part.

RE: Bug with theorems in LyX 2.2?

2016-08-11 Thread Bernt Lie 
Thanks, Jürgen!
-B

From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
Jürgen Lange
Sent: Thursday, August 11, 2016 14:20
To: lyx-users@lists.lyx.org
Subject: Re: Bug with theorems in LyX 2.2?

To seperate the two theorems, you have to go to the end of the first theorem 
and press 3 times "enter", a red line should occur. Then you can add your 
second theorem below.

Regards

Am 11.08.2016, 14:01 Uhr, schrieb Bernt Lie 
<bernt@hit.no<mailto:bernt@hit.no>>:


I used new "theorem" in both cases. Here is what it looks like:

[cid:image001.png@01D1F3DD.7275A690]



The second one does not get numbered.

--

However, if I insert a *standard paragraph* in between, then it works.



[cid:image002.png@01D1F3DD.7275A690]



But I think that it should be possible to have two theorems in sequence, 
without standard text in between???



-B

-Original Message-
From: lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org> 
[mailto:lyx-users@lists.lyx.org] On Behalf Of Kornel Benko
Sent: Thursday, August 11, 2016 13:56
To: lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org>
Subject: Re: Bug with theorems in LyX 2.2?



Am Donnerstag, 11. August 2016 um 11:34:53, schrieb Bernt Lie 
<bernt@hit.no<mailto:bernt@hit.no>>

> Preliminaries: Windows 10, LyX 2.2.1.

>

> Suppose I change a paragraph from standard to Theorem. The theorem then gets 
> numbered. Nice.

>

> However, If I have a *new* theorem in the subsequent paragraph, this one does 
> not get numbered!!! At least not in the LyX editor?

>

> This must be a bug??? It should be possible to have two theorems in sequence?

>

> Thanks.

> -Bernt L.



Use new 'theorem', not new 'theorem*'.



Kornel

Re: Bug with theorems in LyX 2.2?

2016-08-11 Thread Jürgen Lange 
To seperate the two theorems, you have to go to the end of the first  
theorem and press 3 times "enter", a red line should occur. Then you can  
add your second theorem below.


Regards

Am 11.08.2016, 14:01 Uhr, schrieb Bernt Lie <bernt@hit.no>:



I used new "theorem" in both cases. Here is what it looks like:




The second one does not get numbered.

--

However, if I insert a *standard paragraph* in between, then it works.





But I think that it should be possible to have two theorems in sequence,  
without standard text in between???



-B

-Original Message-
From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf  
Of Kornel Benko

Sent: Thursday, August 11, 2016 13:56
To: lyx-users@lists.lyx.org
Subject: Re: Bug with theorems in LyX 2.2?


Am Donnerstag, 11. August 2016 um 11:34:53, schrieb Bernt Lie  
<bernt@hit.no>



Preliminaries: Windows 10, LyX 2.2.1.






Suppose I change a paragraph from standard to Theorem. The theorem then  
gets numbered. Nice.






However, If I have a *new* theorem in the subsequent paragraph, this  
one does not get numbered!!! At least not in the LyX editor?






This must be a bug??? It should be possible to have two theorems in  
sequence?







Thanks.



-Bernt L.



Use new 'theorem', not new 'theorem*'.


   Kornel

RE: Bug with theorems in LyX 2.2?

2016-08-11 Thread Bernt Lie 
I used new "theorem" in both cases. Here is what it looks like:

[cid:image001.png@01D1F3D8.D138EF70]



The second one does not get numbered.

--

However, if I insert a *standard paragraph* in between, then it works.



[cid:image002.png@01D1F3D8.D138EF70]



But I think that it should be possible to have two theorems in sequence, 
without standard text in between???



-B

-Original Message-
From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
Kornel Benko
Sent: Thursday, August 11, 2016 13:56
To: lyx-users@lists.lyx.org
Subject: Re: Bug with theorems in LyX 2.2?



Am Donnerstag, 11. August 2016 um 11:34:53, schrieb Bernt Lie 
<bernt@hit.no<mailto:bernt@hit.no>>

> Preliminaries: Windows 10, LyX 2.2.1.

>

> Suppose I change a paragraph from standard to Theorem. The theorem then gets 
> numbered. Nice.

>

> However, If I have a *new* theorem in the subsequent paragraph, this one does 
> not get numbered!!! At least not in the LyX editor?

>

> This must be a bug??? It should be possible to have two theorems in sequence?

>

> Thanks.

> -Bernt L.



Use new 'theorem', not new 'theorem*'.



Kornel

Re: Bug with theorems in LyX 2.2?

2016-08-11 Thread Kornel Benko 
Am Donnerstag, 11. August 2016 um 11:34:53, schrieb Bernt Lie 
> Preliminaries: Windows 10, LyX 2.2.1.
> 
> Suppose I change a paragraph from standard to Theorem. The theorem then gets 
> numbered. Nice.
> 
> However, If I have a *new* theorem in the subsequent paragraph, this one does 
> not get numbered!!! At least not in the LyX editor?
> 
> This must be a bug??? It should be possible to have two theorems in sequence?
> 
> Thanks.
> -Bernt L.

Use new 'theorem', not new 'theorem*'.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Bug in LyX 2.2.0?

2016-07-14 Thread Uwe Stöhr 

Am 14.07.2016 um 09:52 schrieb Bernt Lie:


On my *job laptop*, I get the following error message when I try to preview the 
document I work on: [cid:image002.jpg@01D1DDB5.6D9DC410]


So on this PC the LaTeX package "units" is not installed. LaTeX packages 
are handled by the program MiKTeX. MiKTeX is by default configured to 
install missing packages automatically. It seems that this failed. I 
suggest to

- open an Internet connection
- log in to Windows as Admin
- check in the MiKTeX settings (available via Windows' start menu) that 
the option "Install missing packages on the fly" is set to "Yes".

- reconfigure LyX using the menu Tools -> Reconfigure

Does it now work?

regards Uwe

Re: Bug

2014-05-14 Thread Patrick Dupre 


 - Original Message -
 From: Richard Heck
 Sent: 05/13/14 08:45 PM
 To: Patrick Dupre
 Subject: Re: Bug
 
 On 05/13/2014 12:10 PM, Patrick Dupre wrote:
  Hello,
 
  I could propably report as a bug, but let me do it that way.
  In versin 2.1.0 on
  Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 
  x86_64 x86_64 GNU/Linux
  Every time that I have an opne document and that I want to open a new
  one (open recent). I get an error:
  SIGSEGV signal caught!
  Sorry, you have found a bug in LyX, hope you have not lost any data.
 
 If you run LyX from a terminal, do you get any more information?


 unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O 
mathalpha]] [char 2 mathalpha]]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha][char = mathalpha][frac [char 1 mathalpha] [char 2 
mathalpha]][char c mathalpha][sub [symbol epsilon] [char 0 mathalpha]][sup 
[char E mathalpha] [char 2 mathalpha]][char ( mathalpha][char t mathalpha][char 
) mathalpha]]
unusual contents found: [Unknown [sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]][symbol leq][char L mathalpha]]
unusual contents found: [Unknown [symbol omega]]
unusual contents found: [Unknown [char t mathalpha][symbol ll][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [char t mathalpha][symbol gg][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [sub [symbol tau] [char r mathalpha][char d 
mathalpha]][symbol rightarrow][sub [symbol tau] [char e mathalpha]]]

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.

[4]+  Aborted                 (core dumped) lyx NO2_threshold.lyx


===
 Patrick DUPRÉ                                 | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===

Re: Bug

2014-05-14 Thread Scott Kostyshak 
On Wed, May 14, 2014 at 5:10 PM, Patrick Dupre pdu...@gmx.com wrote:

   Every time that I have an opne document and that I want to open a new
  one (open recent). I get an error:
  SIGSEGV signal caught!
  Sorry, you have found a bug in LyX, hope you have not lost any data.

Does this only happen if you use Open recent? If so, does it happen if
you use open recent on a very simple (hello world) document?

Can you try renaming your ~/.lyx (or ~.lyx2.1 or whatever) and then
restarting LyX? Note that this will temporarily remove all preferences
(e.g. keybindings) you've set. You can always move the folder back.
After you do that can you reproduce the problem?

I'm on Linux also. Actually in this type of situation (and most
related to LyX), the Linux kernel probably is irrelevant. More
relevant is which distribution, which version of LyX, and how did you
install LyX (compile yourself, download a package, or use a package
manager).

Best,

Scott

Re: Bug in the Math UI

2014-05-14 Thread Julio Rojas 
Thanks David, I agree with you, middle alignment should be set by default.

Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 5:02 PM, David L. Johnson d...@lehigh.edu wrote:

  On 05/13/2014 04:48 PM, Julio Rojas wrote:


 As you can see, there is [t] in the array that is generating the
 problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up
 by default on top alignment instead of middle aligment? I don't really
 remember changing this aligment.

 The popup window does seem to come up with top-alignment as the default.
 Middle would be better, I think.



 On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

  I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
 coefficient for a binomial distribution, so I did as I alway did, i.e.,
 insert the parenthesis in my equation and a size 2 column vector in the
 parenthesis.


 I was going to respond to this part anyway.  For binomial coefficients,
 use (gee) \binom  instead.  The parentheses are tighter around the numbers,
 and it looks more like a binomial coefficient. Easier as well.


 --

 David L. Johnson
 Department of Mathematics
 Lehigh University

Re: Bug

2014-05-14 Thread Georg Baum 
Patrick Dupre wrote:

  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg

Re: Bug

2014-05-14 Thread Patrick Dupre 


 - Original Message -
 From: Richard Heck
 Sent: 05/13/14 08:45 PM
 To: Patrick Dupre
 Subject: Re: Bug
 
 On 05/13/2014 12:10 PM, Patrick Dupre wrote:
  Hello,
 
  I could propably report as a bug, but let me do it that way.
  In versin 2.1.0 on
  Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 
  x86_64 x86_64 GNU/Linux
  Every time that I have an opne document and that I want to open a new
  one (open recent). I get an error:
  SIGSEGV signal caught!
  Sorry, you have found a bug in LyX, hope you have not lost any data.
 
 If you run LyX from a terminal, do you get any more information?


 unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O 
mathalpha]] [char 2 mathalpha]]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha][char = mathalpha][frac [char 1 mathalpha] [char 2 
mathalpha]][char c mathalpha][sub [symbol epsilon] [char 0 mathalpha]][sup 
[char E mathalpha] [char 2 mathalpha]][char ( mathalpha][char t mathalpha][char 
) mathalpha]]
unusual contents found: [Unknown [sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]][symbol leq][char L mathalpha]]
unusual contents found: [Unknown [symbol omega]]
unusual contents found: [Unknown [char t mathalpha][symbol ll][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [char t mathalpha][symbol gg][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [sub [symbol tau] [char r mathalpha][char d 
mathalpha]][symbol rightarrow][sub [symbol tau] [char e mathalpha]]]

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.

[4]+  Aborted                 (core dumped) lyx NO2_threshold.lyx


===
 Patrick DUPRÉ                                 | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===

Re: Bug

2014-05-14 Thread Scott Kostyshak 
On Wed, May 14, 2014 at 5:10 PM, Patrick Dupre pdu...@gmx.com wrote:

   Every time that I have an opne document and that I want to open a new
  one (open recent). I get an error:
  SIGSEGV signal caught!
  Sorry, you have found a bug in LyX, hope you have not lost any data.

Does this only happen if you use Open recent? If so, does it happen if
you use open recent on a very simple (hello world) document?

Can you try renaming your ~/.lyx (or ~.lyx2.1 or whatever) and then
restarting LyX? Note that this will temporarily remove all preferences
(e.g. keybindings) you've set. You can always move the folder back.
After you do that can you reproduce the problem?

I'm on Linux also. Actually in this type of situation (and most
related to LyX), the Linux kernel probably is irrelevant. More
relevant is which distribution, which version of LyX, and how did you
install LyX (compile yourself, download a package, or use a package
manager).

Best,

Scott

Re: Bug in the Math UI

2014-05-14 Thread Julio Rojas 
Thanks David, I agree with you, middle alignment should be set by default.

Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 5:02 PM, David L. Johnson d...@lehigh.edu wrote:

  On 05/13/2014 04:48 PM, Julio Rojas wrote:


 As you can see, there is [t] in the array that is generating the
 problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up
 by default on top alignment instead of middle aligment? I don't really
 remember changing this aligment.

 The popup window does seem to come up with top-alignment as the default.
 Middle would be better, I think.



 On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

  I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
 coefficient for a binomial distribution, so I did as I alway did, i.e.,
 insert the parenthesis in my equation and a size 2 column vector in the
 parenthesis.


 I was going to respond to this part anyway.  For binomial coefficients,
 use (gee) \binom  instead.  The parentheses are tighter around the numbers,
 and it looks more like a binomial coefficient. Easier as well.


 --

 David L. Johnson
 Department of Mathematics
 Lehigh University

Re: Bug

2014-05-14 Thread Georg Baum 
Patrick Dupre wrote:

  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg

Re: Bug

2014-05-14 Thread Patrick Dupre 


> - Original Message -
> From: Richard Heck
> Sent: 05/13/14 08:45 PM
> To: Patrick Dupre
> Subject: Re: Bug
> 
> On 05/13/2014 12:10 PM, Patrick Dupre wrote:
> > Hello,
> >
> > I could propably report as a bug, but let me do it that way.
> > In versin 2.1.0 on
> > Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 
> > x86_64 x86_64 GNU/Linux
> > Every time that I have an opne document and that I want to open a new
> > one (open recent). I get an error:
> > SIGSEGV signal caught!
> > Sorry, you have found a bug in LyX, hope you have not lost any data.
> 
> If you run LyX from a terminal, do you get any more information?


 unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O 
mathalpha]] [char 2 mathalpha]]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha]]
unusual contents found: [Unknown [char I mathalpha][char ( mathalpha][char t 
mathalpha][char ) mathalpha][char = mathalpha][frac [char 1 mathalpha] [char 2 
mathalpha]][char c mathalpha][sub [symbol epsilon] [char 0 mathalpha]][sup 
[char E mathalpha] [char 2 mathalpha]][char ( mathalpha][char t mathalpha][char 
) mathalpha]]
unusual contents found: [Unknown [sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]]]
unusual contents found: [Unknown [sub [char l mathalpha] [char a 
mathalpha][char b mathalpha][char s mathalpha]][symbol leq][char L mathalpha]]
unusual contents found: [Unknown [symbol omega]]
unusual contents found: [Unknown [char t mathalpha][symbol ll][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [char t mathalpha][symbol gg][sub [char t 
mathalpha] [char r mathalpha][char t mathalpha]][char / mathalpha][delim ( ) 
[char 2 mathalpha][sub [symbol alpha] [char 0 mathalpha]][char ( 
mathalpha][symbol omega][char ) mathalpha][space 4] [sub [char l mathalpha] 
[char a mathalpha][char b mathalpha][char s mathalpha
unusual contents found: [Unknown [sub [symbol tau] [char r mathalpha][char d 
mathalpha]][symbol rightarrow][sub [symbol tau] [char e mathalpha]]]

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.

[4]+  Aborted                 (core dumped) lyx NO2_threshold.lyx


===
 Patrick DUPRÉ                                 | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===

Re: Bug

2014-05-14 Thread Scott Kostyshak 
On Wed, May 14, 2014 at 5:10 PM, Patrick Dupre  wrote:

 >> > Every time that I have an opne document and that I want to open a new
>> > one (open recent). I get an error:
>> > SIGSEGV signal caught!
>> > Sorry, you have found a bug in LyX, hope you have not lost any data.

Does this only happen if you use Open recent? If so, does it happen if
you use open recent on a very simple ("hello world") document?

Can you try renaming your ~/.lyx (or ~.lyx2.1 or whatever) and then
restarting LyX? Note that this will temporarily remove all preferences
(e.g. keybindings) you've set. You can always move the folder back.
After you do that can you reproduce the problem?

I'm on Linux also. Actually in this type of situation (and most
related to LyX), the Linux kernel probably is irrelevant. More
relevant is which distribution, which version of LyX, and how did you
install LyX (compile yourself, download a package, or use a package
manager).

Best,

Scott

Re: Bug in the Math UI

2014-05-14 Thread Julio Rojas 
Thanks David, I agree with you, middle alignment should be set by default.

Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 5:02 PM, David L. Johnson  wrote:

>  On 05/13/2014 04:48 PM, Julio Rojas wrote:
>
>
> As you can see, there is "[t]" in the array that is generating the
> problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up
> by default on top alignment instead of middle aligment? I don't really
> remember changing this aligment.
>
> The popup window does seem to come up with top-alignment as the default.
> Middle would be better, I think.
>
>
>
> On Tue, May 13, 2014 at 4:41 PM, Julio Rojas  wrote:
>
>> Dear all,
>>
>>  I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
>> coefficient for a binomial distribution, so I did as I alway did, i.e.,
>> insert the parenthesis in my equation and a size 2 column vector in the
>> parenthesis.
>>
>
> I was going to respond to this part anyway.  For binomial coefficients,
> use (gee) \binom  instead.  The parentheses are tighter around the numbers,
> and it looks more like a binomial coefficient. Easier as well.
>
>
> --
>
> David L. Johnson
> Department of Mathematics
> Lehigh University
>
>

Re: Bug

2014-05-14 Thread Georg Baum 
Patrick Dupre wrote:

>  unusual contents found: [Unknown [sub [mathrm [char N mathalpha][char O
>  mathalpha]] [char 2 mathalpha]]]

This means that LyX does not understand a math formula of that document. My 
first geuss would be that it has nothing to do with the OS our how you 
compiled LyX. This looks like a serious issue to me, which we need to 
investigate.

Could you please file a bug report at 
http://www.lyx.org/trac/wiki/BugTrackerHome and attach the document? If you 
can't publish it, you could also send it to me privately and I'll have a 
look, but without having the original document its is nearly impossible to 
investigate these kinds of bugs. If the document is really secret please do 
a bisection in with LyX 2.0.x and try to reduce it (removing first half of 
the document, seer if that fixes the problem, if yes continue with second 
half etc) until you find the formula which causes the problem.


Georg

Re: Bug

2014-05-13 Thread David L. Johnson 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.

Odd, I can't reproduce that here.  My linux version is a bit different:

Linux  3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux

but when I have a document open in LyX 2.1.0 and then open a new one 
from recent documents, it works correctly.  I wonder whether it is a bug 
in LyX, or elsewhere.  Are these particularly large or complicated 
documents?  Do you have the same problem no matter which documents you 
have open and opening?


--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug

2014-05-13 Thread Richard Heck 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.


If you run LyX from a terminal, do you get any more information?

Richard

Re: Bug in the Math UI

2014-05-13 Thread Julio Rojas 
I have checked the source for my snippet compared to one of the old
fashioned that I had:

\begin{align*}

P(X\leq150)  =\left(\begin{array}{c}

n\\

k

\end{array}\right)\\

P(X\leq150)  =\left(\begin{array}[t]{c}

n\\

k

\end{array}\right)
\end{align*}

As you can see, there is [t] in the array that is generating the problem,
i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up by
default on top alignment instead of middle aligment? I don't really
remember changing this aligment.

Sorry for the false report. Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

 I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
 coefficient for a binomial distribution, so I did as I alway did, i.e.,
 insert the parenthesis in my equation and a size 2 column vector in the
 parenthesis. To my surprise the vector is not centered on the parenthesis,
 but on the top element. Is doesn't mater if the vector is of even or odd
 size; the vector is being setup from the top element to the bottom one.
 This way the parenthesis are bigger than usual and the top part of their
 space is empty.

 I don't know if I was completely clear, so I have attached a couple of
 PNG's of the UI and a PDF showing this behavior. Again, I stress that this
 exactly the same way I have doing it for years, so this issue is related to
 the UI. Is there some new way of doing it on Lyx which I am not aware of?

 Thanks for your help.
 -
 Julio Rojas
 jcredbe...@gmail.com

Re: Bug in the Math UI

2014-05-13 Thread David L. Johnson 

On 05/13/2014 04:48 PM, Julio Rojas wrote:


As you can see, there is [t] in the array that is generating the 
problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 
set up by default on top alignment instead of middle aligment? I don't 
really remember changing this aligment.
The popup window does seem to come up with top-alignment as the 
default.  Middle would be better, I think.



On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com 
mailto:jcredbe...@gmail.com wrote:


Dear all,

I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the
binomial coefficient for a binomial distribution, so I did as I
alway did, i.e., insert the parenthesis in my equation and a size
2 column vector in the parenthesis.



I was going to respond to this part anyway.  For binomial coefficients, 
use (gee) \binom  instead.  The parentheses are tighter around the 
numbers, and it looks more like a binomial coefficient. Easier as well.



--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug

2014-05-13 Thread David L. Johnson 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.

Odd, I can't reproduce that here.  My linux version is a bit different:

Linux  3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux

but when I have a document open in LyX 2.1.0 and then open a new one 
from recent documents, it works correctly.  I wonder whether it is a bug 
in LyX, or elsewhere.  Are these particularly large or complicated 
documents?  Do you have the same problem no matter which documents you 
have open and opening?


--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug

2014-05-13 Thread Richard Heck 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.


If you run LyX from a terminal, do you get any more information?

Richard

Re: Bug in the Math UI

2014-05-13 Thread Julio Rojas 
I have checked the source for my snippet compared to one of the old
fashioned that I had:

\begin{align*}

P(X\leq150)  =\left(\begin{array}{c}

n\\

k

\end{array}\right)\\

P(X\leq150)  =\left(\begin{array}[t]{c}

n\\

k

\end{array}\right)
\end{align*}

As you can see, there is [t] in the array that is generating the problem,
i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up by
default on top alignment instead of middle aligment? I don't really
remember changing this aligment.

Sorry for the false report. Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com wrote:

 Dear all,

 I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
 coefficient for a binomial distribution, so I did as I alway did, i.e.,
 insert the parenthesis in my equation and a size 2 column vector in the
 parenthesis. To my surprise the vector is not centered on the parenthesis,
 but on the top element. Is doesn't mater if the vector is of even or odd
 size; the vector is being setup from the top element to the bottom one.
 This way the parenthesis are bigger than usual and the top part of their
 space is empty.

 I don't know if I was completely clear, so I have attached a couple of
 PNG's of the UI and a PDF showing this behavior. Again, I stress that this
 exactly the same way I have doing it for years, so this issue is related to
 the UI. Is there some new way of doing it on Lyx which I am not aware of?

 Thanks for your help.
 -
 Julio Rojas
 jcredbe...@gmail.com

Re: Bug in the Math UI

2014-05-13 Thread David L. Johnson 

On 05/13/2014 04:48 PM, Julio Rojas wrote:


As you can see, there is [t] in the array that is generating the 
problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 
set up by default on top alignment instead of middle aligment? I don't 
really remember changing this aligment.
The popup window does seem to come up with top-alignment as the 
default.  Middle would be better, I think.



On Tue, May 13, 2014 at 4:41 PM, Julio Rojas jcredbe...@gmail.com 
mailto:jcredbe...@gmail.com wrote:


Dear all,

I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the
binomial coefficient for a binomial distribution, so I did as I
alway did, i.e., insert the parenthesis in my equation and a size
2 column vector in the parenthesis.



I was going to respond to this part anyway.  For binomial coefficients, 
use (gee) \binom  instead.  The parentheses are tighter around the 
numbers, and it looks more like a binomial coefficient. Easier as well.



--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug

2014-05-13 Thread David L. Johnson 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.

Odd, I can't reproduce that here.  My linux version is a bit different:

Linux  3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux

but when I have a document open in LyX 2.1.0 and then open a new one 
from recent documents, it works correctly.  I wonder whether it is a bug 
in LyX, or elsewhere.  Are these particularly large or complicated 
documents?  Do you have the same problem no matter which documents you 
have open and opening?


--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug

2014-05-13 Thread Richard Heck 

On 05/13/2014 12:10 PM, Patrick Dupre wrote:

Hello,

I could propably report as a bug, but let me do it that way.
In versin 2.1.0 on
Linux 3.14.3-200.fc20.x86_64 #1 SMP Tue May 6 19:00:18 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux
Every time that I have an opne document and that I want to open a new
one (open recent). I get an error:
SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.


If you run LyX from a terminal, do you get any more information?

Richard

Re: Bug in the Math UI

2014-05-13 Thread Julio Rojas 
I have checked the source for my snippet compared to one of the "old
fashioned" that I had:

\begin{align*}

P(X\leq150) & =\left(\begin{array}{c}

n\\

k

\end{array}\right)\\

P(X\leq150) & =\left(\begin{array}[t]{c}

n\\

k

\end{array}\right)
\end{align*}

As you can see, there is "[t]" in the array that is generating the problem,
i.e., the array was top aligned. Are matrices in Lyx 2.1.0 set up by
default on top alignment instead of middle aligment? I don't really
remember changing this aligment.

Sorry for the false report. Regards.

-
Julio Rojas
jcredbe...@gmail.com


On Tue, May 13, 2014 at 4:41 PM, Julio Rojas  wrote:

> Dear all,
>
> I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the binomial
> coefficient for a binomial distribution, so I did as I alway did, i.e.,
> insert the parenthesis in my equation and a size 2 column vector in the
> parenthesis. To my surprise the vector is not centered on the parenthesis,
> but on the top element. Is doesn't mater if the vector is of even or odd
> size; the vector is being setup from the top element to the bottom one.
> This way the parenthesis are bigger than usual and the top part of their
> space is empty.
>
> I don't know if I was completely clear, so I have attached a couple of
> PNG's of the UI and a PDF showing this behavior. Again, I stress that this
> exactly the same way I have doing it for years, so this issue is related to
> the UI. Is there some new way of doing it on Lyx which I am not aware of?
>
> Thanks for your help.
> -
> Julio Rojas
> jcredbe...@gmail.com
>

Re: Bug in the Math UI

2014-05-13 Thread David L. Johnson 

On 05/13/2014 04:48 PM, Julio Rojas wrote:


As you can see, there is "[t]" in the array that is generating the 
problem, i.e., the array was top aligned. Are matrices in Lyx 2.1.0 
set up by default on top alignment instead of middle aligment? I don't 
really remember changing this aligment.
The popup window does seem to come up with top-alignment as the 
default.  Middle would be better, I think.



On Tue, May 13, 2014 at 4:41 PM, Julio Rojas > wrote:


Dear all,

I am on Ubuntu 12.02 with Lyx 2.1.0. I wanted to make set the
binomial coefficient for a binomial distribution, so I did as I
alway did, i.e., insert the parenthesis in my equation and a size
2 column vector in the parenthesis.



I was going to respond to this part anyway.  For binomial coefficients, 
use (gee) \binom  instead.  The parentheses are tighter around the 
numbers, and it looks more like a binomial coefficient. Easier as well.



--
 
David L. Johnson

Department of Mathematics
Lehigh University

Re: Bug with .dia figure Preview in Lyx 2.1.0(Trusty Tahr)

2014-04-23 Thread Liviu Andronic 
Dear Chan,
Please direct such inquiries to lyx-users (cc'ed), as you're much
likelier to get a useful answer. I'm not sure what could be wrong with
the preview of teh .dia figures, but if you believe that this could be
a bug feel free to submit a report at our bugtracker (
http://www.lyx.org/trac/wiki/BugTrackerHome ).

Regards,
Liviu


On Wed, Apr 23, 2014 at 7:53 PM, zyzhen88 zyzhe...@gmail.com wrote:
 Hi Liviu,

 I have installed Lyx 2.1 on my Trusty Tahr recently. Everything works
 properly until one day I inserted a .dia figure directly. The text in
 the float preview window is not displayed in the correct position. All
 the text in the same line will always be displayed at the same position
 which means one character is over another character. However, the figure
 in the generated pdflatex file is shown correctly again.

 I guess it might be the problem of the DIA-EPS converter but not 100%
 sure. Contact me if u need more information related to the bug such as
 the screen capture or anything else. It will be my great honor to
 contribute to the project.

 best regards, Chan
 --
 This message was sent from Launchpad by
 zyzhen88 (https://launchpad.net/~zyzhen88)
 using the Contact this user link on your profile page
 (https://launchpad.net/~landronimirc).
 For more information see
 https://help.launchpad.net/YourAccount/ContactingPeople



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Bug with .dia figure Preview in Lyx 2.1.0(Trusty Tahr)

2014-04-23 Thread Liviu Andronic 
Dear Chan,
Please direct such inquiries to lyx-users (cc'ed), as you're much
likelier to get a useful answer. I'm not sure what could be wrong with
the preview of teh .dia figures, but if you believe that this could be
a bug feel free to submit a report at our bugtracker (
http://www.lyx.org/trac/wiki/BugTrackerHome ).

Regards,
Liviu


On Wed, Apr 23, 2014 at 7:53 PM, zyzhen88 zyzhe...@gmail.com wrote:
 Hi Liviu,

 I have installed Lyx 2.1 on my Trusty Tahr recently. Everything works
 properly until one day I inserted a .dia figure directly. The text in
 the float preview window is not displayed in the correct position. All
 the text in the same line will always be displayed at the same position
 which means one character is over another character. However, the figure
 in the generated pdflatex file is shown correctly again.

 I guess it might be the problem of the DIA-EPS converter but not 100%
 sure. Contact me if u need more information related to the bug such as
 the screen capture or anything else. It will be my great honor to
 contribute to the project.

 best regards, Chan
 --
 This message was sent from Launchpad by
 zyzhen88 (https://launchpad.net/~zyzhen88)
 using the Contact this user link on your profile page
 (https://launchpad.net/~landronimirc).
 For more information see
 https://help.launchpad.net/YourAccount/ContactingPeople



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: Bug with .dia figure Preview in Lyx 2.1.0(Trusty Tahr)

2014-04-23 Thread Liviu Andronic 
Dear Chan,
Please direct such inquiries to lyx-users (cc'ed), as you're much
likelier to get a useful answer. I'm not sure what could be wrong with
the preview of teh .dia figures, but if you believe that this could be
a bug feel free to submit a report at our bugtracker (
http://www.lyx.org/trac/wiki/BugTrackerHome ).

Regards,
Liviu


On Wed, Apr 23, 2014 at 7:53 PM, zyzhen88  wrote:
> Hi Liviu,
>
> I have installed Lyx 2.1 on my Trusty Tahr recently. Everything works
> properly until one day I inserted a .dia figure directly. The text in
> the float preview window is not displayed in the correct position. All
> the text in the same line will always be displayed at the same position
> which means one character is over another character. However, the figure
> in the generated pdflatex file is shown correctly again.
>
> I guess it might be the problem of the DIA->EPS converter but not 100%
> sure. Contact me if u need more information related to the bug such as
> the screen capture or anything else. It will be my great honor to
> contribute to the project.
>
> best regards, Chan
> --
> This message was sent from Launchpad by
> zyzhen88 (https://launchpad.net/~zyzhen88)
> using the "Contact this user" link on your profile page
> (https://launchpad.net/~landronimirc).
> For more information see
> https://help.launchpad.net/YourAccount/ContactingPeople



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck rgh...@lyx.org:
 OK, so I have finally found the bug. The problem is that we are outputting
 this code:

 Itemize, Enumeration, and Description lists may have an optional arguments.
 If the optional argument contains special characters (e.g. the backslash),
 put it in an ERT box.
 \begin{enumerate}[\selectlanguage{british}%
 labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
 \selectlanguage{english}%
 ]
 \item  An enumeration
 \item with left-aligned roman
 \item numbering
 \item 1of items.
 \end{enumerate}

 Note the language change. This would appear to be because the two files use
 different languages. We obviously should not be outputting that in this
 case.

 Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.

Jürgen

 Richard

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Richard Heck 

On 03/19/2013 12:14 PM, Jürgen Spitzmüller wrote:

2013/3/19 Richard Heck rgh...@lyx.org:

OK, so I have finally found the bug. The problem is that we are outputting
this code:

Itemize, Enumeration, and Description lists may have an optional arguments.
If the optional argument contains special characters (e.g. the backslash),
put it in an ERT box.
\begin{enumerate}[\selectlanguage{british}%
labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
\selectlanguage{english}%
]
\item  An enumeration
\item with left-aligned roman
\item numbering
\item 1of items.
\end{enumerate}

Note the language change. This would appear to be because the two files use
different languages. We obviously should not be outputting that in this
case.

Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.
If this one is fixed in trunk, we could leave it there. It's a pretty 
obscure bug.


rh

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck rgh...@lyx.org:
 If this one is fixed in trunk, we could leave it there. It's a pretty
 obscure bug.

We need to check. If someone has a recipe for the bug, please test.

Jürgen

 rh

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck rgh...@lyx.org:
 OK, so I have finally found the bug. The problem is that we are outputting
 this code:

 Itemize, Enumeration, and Description lists may have an optional arguments.
 If the optional argument contains special characters (e.g. the backslash),
 put it in an ERT box.
 \begin{enumerate}[\selectlanguage{british}%
 labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
 \selectlanguage{english}%
 ]
 \item  An enumeration
 \item with left-aligned roman
 \item numbering
 \item 1of items.
 \end{enumerate}

 Note the language change. This would appear to be because the two files use
 different languages. We obviously should not be outputting that in this
 case.

 Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.

Jürgen

 Richard

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Richard Heck 

On 03/19/2013 12:14 PM, Jürgen Spitzmüller wrote:

2013/3/19 Richard Heck rgh...@lyx.org:

OK, so I have finally found the bug. The problem is that we are outputting
this code:

Itemize, Enumeration, and Description lists may have an optional arguments.
If the optional argument contains special characters (e.g. the backslash),
put it in an ERT box.
\begin{enumerate}[\selectlanguage{british}%
labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
\selectlanguage{english}%
]
\item  An enumeration
\item with left-aligned roman
\item numbering
\item 1of items.
\end{enumerate}

Note the language change. This would appear to be because the two files use
different languages. We obviously should not be outputting that in this
case.

Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.
If this one is fixed in trunk, we could leave it there. It's a pretty 
obscure bug.


rh

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck rgh...@lyx.org:
 If this one is fixed in trunk, we could leave it there. It's a pretty
 obscure bug.

We need to check. If someone has a recipe for the bug, please test.

Jürgen

 rh

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck :
> OK, so I have finally found the bug. The problem is that we are outputting
> this code:
>
> Itemize, Enumeration, and Description lists may have an optional arguments.
> If the optional argument contains special characters (e.g. the backslash),
> put it in an ERT box.
> \begin{enumerate}[\selectlanguage{british}%
> labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
> \selectlanguage{english}%
> ]
> \item  An enumeration
> \item with left-aligned roman
> \item numbering
> \item 1of items.
> \end{enumerate}
>
> Note the language change. This would appear to be because the two files use
> different languages. We obviously should not be outputting that in this
> case.
>
> Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.

Jürgen

> Richard
>

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Richard Heck 

On 03/19/2013 12:14 PM, Jürgen Spitzmüller wrote:

2013/3/19 Richard Heck :

OK, so I have finally found the bug. The problem is that we are outputting
this code:

Itemize, Enumeration, and Description lists may have an optional arguments.
If the optional argument contains special characters (e.g. the backslash),
put it in an ERT box.
\begin{enumerate}[\selectlanguage{british}%
labelindent=\parindent,leftmargin=*,label=\Roman*.,widest=IV,align=left
\selectlanguage{english}%
]
\item  An enumeration
\item with left-aligned roman
\item numbering
\item 1of items.
\end{enumerate}

Note the language change. This would appear to be because the two files use
different languages. We obviously should not be outputting that in this
case.

Can you file a bug about this?

FWIW I have fixed some problems along this line in trunk.
If this one is fixed in trunk, we could leave it there. It's a pretty 
obscure bug.


rh

Re: [BUG] Langauge Change When Outputting Optional Argument

2013-03-19 Thread Jürgen Spitzmüller 
2013/3/19 Richard Heck :
> If this one is fixed in trunk, we could leave it there. It's a pretty
> obscure bug.

We need to check. If someone has a recipe for the bug, please test.

Jürgen

> rh
>

Re: Bug mhchem-Czech

2013-03-13 Thread Uwe Stöhr 

Am 13.03.2013 03:11, schrieb Jürgen Lange:


have you seen the attached lyx and pdf file?
The bug is, that mhchem in lyx does not format the symbolic arrow - to a 
chemical reaction arrow.
The latex code in lyx is \ce{-} as shown in lyx file.
In attachment an example of a correct formatted arrow in a pure English 
document (without Czech).
Please compare both pdf outputs. Do you see the difference?


Now I see. I tested now all languages and the problem only occurs for Czech and Slovak. Could you 
please inform the package author of mhchem about this bug? (if you like CC me)


thanks and regards
Uwe

Re: Bug mhchem-Czech

2013-03-13 Thread Uwe Stöhr 

Am 13.03.2013 03:11, schrieb Jürgen Lange:


have you seen the attached lyx and pdf file?
The bug is, that mhchem in lyx does not format the symbolic arrow - to a 
chemical reaction arrow.
The latex code in lyx is \ce{-} as shown in lyx file.
In attachment an example of a correct formatted arrow in a pure English 
document (without Czech).
Please compare both pdf outputs. Do you see the difference?


Now I see. I tested now all languages and the problem only occurs for Czech and Slovak. Could you 
please inform the package author of mhchem about this bug? (if you like CC me)


thanks and regards
Uwe

Re: Bug mhchem-Czech

2013-03-13 Thread Uwe Stöhr 

Am 13.03.2013 03:11, schrieb Jürgen Lange:


have you seen the attached lyx and pdf file?
The bug is, that mhchem in lyx does not format the symbolic arrow -> to a 
chemical reaction arrow.
The latex code in lyx is \ce{->} as shown in lyx file.
In attachment an example of a correct formatted arrow in a pure English 
document (without Czech).
Please compare both pdf outputs. Do you see the difference?


Now I see. I tested now all languages and the problem only occurs for Czech and Slovak. Could you 
please inform the package author of mhchem about this bug? (if you like CC me)


thanks and regards
Uwe

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 02.12.2011 um 15:22 schrieb Nate:

 Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
 After I
 installed it, I double clicked on the App to run it, but nothing happened, the
 Lyx did not show up at all. On my Mac, it is the same problem for both
 LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Jinghua Feng 
Hi Stephan, thanks for your help. I have done what you suggest, and below are 
the report:

For the LyX-2.0.2+qt4-tiger.dmg:

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
  Referenced from: 
/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
  Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

Trace/BPT trap


As for the LyX-2.0.2+qt4-cocoa.dmg:

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Library not loaded: /usr/lib/libiconv.2.dylib
  Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
  Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
but libiconv.2.dylib provides version 5.0.0
Trace/BPT trap






 From: Stephan Witt st.w...@gmx.net
To: Nate jinghua.f...@yahoo.com 
Cc: lyx-users@lists.lyx.org 
Sent: Saturday, December 3, 2011 5:04 AM
Subject: Re: Bug of installing the 2.0.2 binaries version on Mac OS X?
 
Am 02.12.2011 um 15:22 schrieb Nate:

 Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
 After I
 installed it, I double clicked on the App to run it, but nothing happened, the
 Lyx did not show up at all. On my Mac, it is the same problem for both
 LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 03.12.2011 um 00:10 schrieb Jinghua Feng:

 Hi Stephan, thanks for your help. I have done what you suggest, and below are 
 the report:
 
 For the LyX-2.0.2+qt4-tiger.dmg:
 
 $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
 dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
   Referenced from: 
 /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
   Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
 
 Trace/BPT trap

Sorry, I've used the wrong version of the QtGui framework for packaging.
I have to create the corrected version as soon as possible. But I cannot
do this before tomorrow evening.

 
 
 As for the LyX-2.0.2+qt4-cocoa.dmg:
 
 $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
 dyld: Library not loaded: /usr/lib/libiconv.2.dylib
   Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
   Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
 but libiconv.2.dylib provides version 5.0.0
 Trace/BPT trap

This is to be expected - this package is for Leopard and newer Mac OS versions.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 02.12.2011 um 15:22 schrieb Nate:

 Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
 After I
 installed it, I double clicked on the App to run it, but nothing happened, the
 Lyx did not show up at all. On my Mac, it is the same problem for both
 LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Jinghua Feng 
Hi Stephan, thanks for your help. I have done what you suggest, and below are 
the report:

For the LyX-2.0.2+qt4-tiger.dmg:

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
  Referenced from: 
/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
  Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

Trace/BPT trap


As for the LyX-2.0.2+qt4-cocoa.dmg:

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Library not loaded: /usr/lib/libiconv.2.dylib
  Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
  Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
but libiconv.2.dylib provides version 5.0.0
Trace/BPT trap






 From: Stephan Witt st.w...@gmx.net
To: Nate jinghua.f...@yahoo.com 
Cc: lyx-users@lists.lyx.org 
Sent: Saturday, December 3, 2011 5:04 AM
Subject: Re: Bug of installing the 2.0.2 binaries version on Mac OS X?
 
Am 02.12.2011 um 15:22 schrieb Nate:

 Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
 After I
 installed it, I double clicked on the App to run it, but nothing happened, the
 Lyx did not show up at all. On my Mac, it is the same problem for both
 LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 03.12.2011 um 00:10 schrieb Jinghua Feng:

 Hi Stephan, thanks for your help. I have done what you suggest, and below are 
 the report:
 
 For the LyX-2.0.2+qt4-tiger.dmg:
 
 $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
 dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
   Referenced from: 
 /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
   Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
 
 Trace/BPT trap

Sorry, I've used the wrong version of the QtGui framework for packaging.
I have to create the corrected version as soon as possible. But I cannot
do this before tomorrow evening.

 
 
 As for the LyX-2.0.2+qt4-cocoa.dmg:
 
 $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
 dyld: Library not loaded: /usr/lib/libiconv.2.dylib
   Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
   Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
 but libiconv.2.dylib provides version 5.0.0
 Trace/BPT trap

This is to be expected - this package is for Leopard and newer Mac OS versions.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 02.12.2011 um 15:22 schrieb Nate:

> Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
> After I
> installed it, I double clicked on the App to run it, but nothing happened, the
> Lyx did not show up at all. On my Mac, it is the same problem for both
> LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Jinghua Feng 
Hi Stephan, thanks for your help. I have done what you suggest, and below are 
the report:

For the "LyX-2.0.2+qt4-tiger.dmg":

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
  Referenced from: 
/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
  Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

Trace/BPT trap


As for the "LyX-2.0.2+qt4-cocoa.dmg":

$/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
dyld: Library not loaded: /usr/lib/libiconv.2.dylib
  Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
  Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
but libiconv.2.dylib provides version 5.0.0
Trace/BPT trap






 From: Stephan Witt <st.w...@gmx.net>
To: Nate <jinghua.f...@yahoo.com> 
Cc: lyx-users@lists.lyx.org 
Sent: Saturday, December 3, 2011 5:04 AM
Subject: Re: Bug of installing the 2.0.2 binaries version on Mac OS X?
 
Am 02.12.2011 um 15:22 schrieb Nate:

> Hi, I have just failed installing the 2.0.2 binaries on my OS X 10.4.11. 
> After I
> installed it, I double clicked on the App to run it, but nothing happened, the
> Lyx did not show up at all. On my Mac, it is the same problem for both
> LyX-2.0.2+qt4-cocoa.dmg and LyX-2.0.2+qt4-tiger.dmg. 

Really *nothing* happens? That's strange. I'd expect a crash report at least.
Sorry, I don't have a Mac OS with Tiger.

Please, try to the following:
1. Mount the disk image
2. Open the Terminal.app
3. Start LyX with
% /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx

... and report what happens.

Regards,
Stephan

Re: Bug of installing the 2.0.2 binaries version on Mac OS X?

2011-12-02 Thread Stephan Witt 
Am 03.12.2011 um 00:10 schrieb Jinghua Feng:

> Hi Stephan, thanks for your help. I have done what you suggest, and below are 
> the report:
> 
> For the "LyX-2.0.2+qt4-tiger.dmg":
> 
> $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
> dyld: Symbol not found: _kTISPropertyUnicodeKeyLayoutData
>   Referenced from: 
> /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
>   Expected in: /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
> 
> Trace/BPT trap

Sorry, I've used the wrong version of the QtGui framework for packaging.
I have to create the corrected version as soon as possible. But I cannot
do this before tomorrow evening.

> 
> 
> As for the "LyX-2.0.2+qt4-cocoa.dmg":
> 
> $/Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
> dyld: Library not loaded: /usr/lib/libiconv.2.dylib
>   Referenced from: /Volumes/LyX-2.0.2/LyX.app/Contents/MacOS/lyx
>   Reason: Incompatible library version: lyx requires version 7.0.0 or later, 
> but libiconv.2.dylib provides version 5.0.0
> Trace/BPT trap

This is to be expected - this package is for Leopard and newer Mac OS versions.

Regards,
Stephan

Re: Bug with Comments or Greyed out in section headings?

2011-09-18 Thread Julien Rioux 

On 19/09/2011 12:28 AM, Lisa Andrews wrote:

Apologies if I have missed something in the documentation:

With 2.0.1 on OSX or  2.0.0 on Win7-64, I am unable to insert a Comment or
Greyed out inset in a section heading (through the menu or right-clicking),
but if I create one in the standard environment and then change the
environment to a section such as Part or Subsection the comment inset is
allowed or kept.
Right clicking or the menu now allows the comment to be changed to a note,
but its a one-way affair; once done, one cannot change it back again.

Is the reason for this covered somewhere?
Thanks, Lisa



This will most likely give you compilation errors from LaTeX and that 
would be why LyX tries to prevent you from doing it. But if you are very 
insistent you can get around it, s yo saw! If it works for you then why 
not use it, but expect the unexpected.


Cheers,
Julien

Re: Bug with Comments or Greyed out in section headings?

2011-09-18 Thread Julien Rioux 

On 19/09/2011 12:28 AM, Lisa Andrews wrote:

Apologies if I have missed something in the documentation:

With 2.0.1 on OSX or  2.0.0 on Win7-64, I am unable to insert a Comment or
Greyed out inset in a section heading (through the menu or right-clicking),
but if I create one in the standard environment and then change the
environment to a section such as Part or Subsection the comment inset is
allowed or kept.
Right clicking or the menu now allows the comment to be changed to a note,
but its a one-way affair; once done, one cannot change it back again.

Is the reason for this covered somewhere?
Thanks, Lisa



This will most likely give you compilation errors from LaTeX and that 
would be why LyX tries to prevent you from doing it. But if you are very 
insistent you can get around it, s yo saw! If it works for you then why 
not use it, but expect the unexpected.


Cheers,
Julien

Re: Bug with Comments or Greyed out in section headings?

2011-09-18 Thread Julien Rioux 

On 19/09/2011 12:28 AM, Lisa Andrews wrote:

Apologies if I have missed something in the documentation:

With 2.0.1 on OSX or  2.0.0 on Win7-64, I am unable to insert a Comment or
Greyed out inset in a section heading (through the menu or right-clicking),
but if I create one in the standard environment and then change the
environment to a section such as "Part" or "Subsection" the comment inset is
allowed or kept.
Right clicking or the menu now allows the comment to be changed to a note,
but its a one-way affair; once done, one cannot change it back again.

Is the reason for this covered somewhere?
Thanks, Lisa



This will most likely give you compilation errors from LaTeX and that 
would be why LyX tries to prevent you from doing it. But if you are very 
insistent you can get around it, s yo saw! If it works for you then why 
not use it, but expect the unexpected.


Cheers,
Julien

Re: Bug ?

2011-09-04 Thread Pavel Sanda 
Richard Heck wrote:
 But nonetheless, someone on gentoo who did not previously have xetex
 support, but who has compiled 2.0.0 already, can add it by acquiring the
 xetex binary

thats right for xetex/luatex and few others USE flags. they are there merely
for pulling running depencies, not that they are needed for compilation.
so no need to recompile lyx if you know which packages should be emerged
to the system.

pavel

Re: Bug ?

2011-09-04 Thread Pavel Sanda 
Richard Heck wrote:
 But nonetheless, someone on gentoo who did not previously have xetex
 support, but who has compiled 2.0.0 already, can add it by acquiring the
 xetex binary

thats right for xetex/luatex and few others USE flags. they are there merely
for pulling running depencies, not that they are needed for compilation.
so no need to recompile lyx if you know which packages should be emerged
to the system.

pavel

Re: Bug ?

2011-09-04 Thread Pavel Sanda 
Richard Heck wrote:
> But nonetheless, someone on gentoo who did not previously have xetex
> support, but who has compiled 2.0.0 already, can add it by acquiring the
> xetex binary

thats right for xetex/luatex and few others USE flags. they are there merely
for pulling running depencies, not that they are needed for compilation.
so no need to recompile lyx if you know which packages should be emerged
to the system.

pavel

Re: Bug ?

2011-09-03 Thread Richard Heck 
On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
 I recompiled lyx  yesterday (on a gentoo system), adding support to luatex 
 and xetex. 

Recompilation should not be required, unless you were upgrading to 2.0.0
or something of the sort.

 Now, none of the book class documents compile (they use to compile without 
 any problem). Every once in a while, compile fails with a message like:
 Chapitre 2.

 LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
 27 
 undefined on input line 1385.


 LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
 27 
 undefined on input line 1385.

 ! Missing \endcsname inserted.
 to be read again 
:
 l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
pour plus de d�tails).
 The control sequence marked to be read again should
 not appear between \csname and \endcsname.

 ! Extra \endcsname.
 argument ...s-d=E9di=E9es-aux\endcsname 
   \space 
 l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}

 Is this a known bug ? Any workaround ?

This looks odd, with the \endcsname\space. Can you try to produce a
minimal test document that exhibits the problem? I.e., keep deleting
stuff until the problem goes away.

Richard

Re: Bug ?

2011-09-03 Thread Alain Didierjean 


- Mail original -
 De: Richard Heck rgh...@comcast.net
 À: alain didierjean alain.didierj...@free.fr
 Cc: lyx-users@lists.lyx.org
 Envoyé: Samedi 3 Septembre 2011 16:13:36
 Objet: Re: Bug ?

 On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
  I recompiled lyx  yesterday (on a gentoo system), adding support to
  luatex and xetex.
 
 Recompilation should not be required, unless you were upgrading to
 2.0.0
 or something of the sort.

using gentoo linux, packages are compiled localy. Adding luatex and xetex
support means recompiling lyx.


  Now, none of the book class documents compile (they use to compile
  without any problem). Every once in a while, compile fails with a
  message like:
  Chapitre 2.
 
  LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
  on page 27
  undefined on input line 1385.
 
 
  LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
  on page 27
  undefined on input line 1385.
 
  ! Missing \endcsname inserted.
  to be read again
 :
  l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
 pour plus de
 d�tails).
  The control sequence marked to be read again should
  not appear between \csname and \endcsname.
 
  ! Extra \endcsname.
  argument ...s-d=E9di=E9es-aux\endcsname
\space
  l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
 
  Is this a known bug ? Any workaround ?
 
 This looks odd, with the \endcsname\space. Can you try to produce a
 minimal test document that exhibits the problem? I.e., keep deleting
 stuff until the problem goes away.

more than weird. This seems linked to the use of any book class. articles, 
letter, lettre, exam compile ok while a book class document of one line (title)
returns:

This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
2011.9.3)  3 SEP 2011 18:10
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**nouveau1.tex
(./nouveau1.tex
LaTeX2e 2009/09/24
Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi
nyin, ukenglish, usenglishmax, basque, french, loaded.

(/usr/share/texmf-dist/tex/latex/base/book.cls
Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/bk11.clo
File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@chapter=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
\symupright=\mathgroup4
) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/share/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2008/03/30 v1.1d Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/share/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2008/03/30 v1.1d Input encoding file
)) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
Package: `setspace' 6.7 2000/12/01
)
! Undefined control sequence.
l.30 \LoadLetterOption
  {DIN}%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H return  for immediate help.
 ...

l.30 \LoadLetterOption{D
IN}%
You're in trouble here.  Try typing  return  to proceed.
If that doesn't work, type  X return  to quit.

! Undefined control sequence.
l.34 \KOMAoptions
 {%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H return  for immediate help.
 ...

l.39 f
  romalign=right%alignment of the address
You're in trouble here.  Try typing  return  to proceed.
If that doesn't work, type  X return  to quit.


Overfull \hbox (176.49751pt too wide) in paragraph at lines 39--55
[]\T1/cmr/m/n/10.95 fromalign=right

Re: Bug ?

2011-09-03 Thread Pavel Sanda 
Alain Didierjean wrote:
 more than weird. This seems linked to the use of any book class. articles, 
 letter, lettre, exam compile ok while a book class document of one line 
 (title)
 returns:

these logs are not much of help. you should report lyx version, texlive version,
and show some problematic file. i can't reproduce your troubles here.

pavel

 
 This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
 2011.9.3)  3 SEP 2011 18:10
 entering extended mode
  restricted \write18 enabled.
  %-line parsing enabled.
 **nouveau1.tex
 (./nouveau1.tex
 LaTeX2e 2009/09/24
 Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, 
 pi
 nyin, ukenglish, usenglishmax, basque, french, loaded.
 
 (/usr/share/texmf-dist/tex/latex/base/book.cls
 Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
 (/usr/share/texmf-dist/tex/latex/base/bk11.clo
 File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
 )
 \c@part=\count79
 \c@chapter=\count80
 \c@section=\count81
 \c@subsection=\count82
 \c@subsubsection=\count83
 \c@paragraph=\count84
 \c@subparagraph=\count85
 \c@figure=\count86
 \c@table=\count87
 \abovecaptionskip=\skip41
 \belowcaptionskip=\skip42
 \bibindent=\dimen102
 ) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
 Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
 \symupright=\mathgroup4
 ) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
 Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
 (/usr/share/texmf-dist/tex/latex/base/t1enc.def
 File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
 LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
 )) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
 Package: inputenc 2008/03/30 v1.1d Input encoding file
 \inpenc@prehook=\toks14
 \inpenc@posthook=\toks15
 (/usr/share/texmf-dist/tex/latex/base/latin9.def
 File: latin9.def 2008/03/30 v1.1d Input encoding file
 )) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
 Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
 Package: `setspace' 6.7 2000/12/01
 )
 ! Undefined control sequence.
 l.30 \LoadLetterOption
   {DIN}%
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.30 \LoadLetterOption{D
 IN}%
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 ! Undefined control sequence.
 l.34 \KOMAoptions
  {%
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.39 f
   romalign=right%alignment of the address
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 
 Overfull \hbox (176.49751pt too wide) in paragraph at lines 39--55
 []\T1/cmr/m/n/10.95 
 fromalign=right,fromrule=aftername,fromphone=true,fromemail
 =true,foldmarks=false,enlargefirstpage=true
  []
 
 ! Undefined control sequence.
 l.58 \setkomavar
 {backaddressseparator}{ $\cdot$ }
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.58 \setkomavar{b
   ackaddressseparator}{ $\cdot$ }
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 LaTeX Font Info:Try loading font information for OT1+ppl on input line 58.
 (/usr/share/texmf-dist/tex/latex/psnfss/ot1ppl.fd
 File: ot1ppl.fd 2001/06/04 font definitions for OT1/ppl.
 )
 LaTeX Font Info:Try loading font information for OML+zplm on input line 
 58.
 
 (/usr/share/texmf-dist/tex/latex/psnfss/omlzplm.fd
 File: omlzplm.fd 2002/09/08 Fontinst v1.914 font definitions for OML/zplm.
 )
 LaTeX Font Info:Try loading font information for OMS+zplm on input line 
 58.
 
 (/usr/share/texmf-dist/tex/latex/psnfss/omszplm.fd
 File: omszplm.fd 2002/09/08 Fontinst v1.914 font definitions for OMS/zplm.
 )
 LaTeX Font Info:Try loading

Re: Bug ?

2011-09-03 Thread Richard Heck 
On 09/03/2011 12:11 PM, Alain Didierjean wrote:

 - Mail original -
 De: Richard Heck rgh...@comcast.net
 À: alain didierjean alain.didierj...@free.fr
 Cc: lyx-users@lists.lyx.org
 Envoyé: Samedi 3 Septembre 2011 16:13:36
 Objet: Re: Bug ?

 On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
 I recompiled lyx  yesterday (on a gentoo system), adding support to
 luatex and xetex.

 Recompilation should not be required, unless you were upgrading to
 2.0.0 or something of the sort.
 using gentoo linux, packages are compiled localy. Adding luatex and xetex 
 support means recompiling lyx.

Last I knew, Pavel was using gentoo, so perhaps he can help.

But nonetheless, someone on gentoo who did not previously have xetex
support, but who has compiled 2.0.0 already, can add it by acquiring the
xetex binary (however they might do that) and doing ToolsReconfigure in
LyX. There's no compilation setting in LyX for this, as there is, e.g.,
for libx264 support in ffmpeg. LyX has no sort of compilation dependency
upon xetex (there are no headers that it needs, e.g.), but only uses it
as a completely external tool.

Indeed, you could create a script /usr/bin/xe(?:la)?tex whose entire
code was:
#!/bin/bash
exit 0;
and LyX would happily let you use XeTeX. (Not that it would work very
well) All LyX cares is that there is some program called
xe(?:la)?tex in the path, and that is checked during LyX's
configuration process, not during the autotools configuration.

Richard

PS Security issues anyone?

Re: Bug ?

2011-09-03 Thread Richard Heck 
On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
 I recompiled lyx  yesterday (on a gentoo system), adding support to luatex 
 and xetex. 

Recompilation should not be required, unless you were upgrading to 2.0.0
or something of the sort.

 Now, none of the book class documents compile (they use to compile without 
 any problem). Every once in a while, compile fails with a message like:
 Chapitre 2.

 LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
 27 
 undefined on input line 1385.


 LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
 27 
 undefined on input line 1385.

 ! Missing \endcsname inserted.
 to be read again 
:
 l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
pour plus de d�tails).
 The control sequence marked to be read again should
 not appear between \csname and \endcsname.

 ! Extra \endcsname.
 argument ...s-d=E9di=E9es-aux\endcsname 
   \space 
 l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}

 Is this a known bug ? Any workaround ?

This looks odd, with the \endcsname\space. Can you try to produce a
minimal test document that exhibits the problem? I.e., keep deleting
stuff until the problem goes away.

Richard

Re: Bug ?

2011-09-03 Thread Alain Didierjean 


- Mail original -
 De: Richard Heck rgh...@comcast.net
 À: alain didierjean alain.didierj...@free.fr
 Cc: lyx-users@lists.lyx.org
 Envoyé: Samedi 3 Septembre 2011 16:13:36
 Objet: Re: Bug ?

 On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
  I recompiled lyx  yesterday (on a gentoo system), adding support to
  luatex and xetex.
 
 Recompilation should not be required, unless you were upgrading to
 2.0.0
 or something of the sort.

using gentoo linux, packages are compiled localy. Adding luatex and xetex
support means recompiling lyx.


  Now, none of the book class documents compile (they use to compile
  without any problem). Every once in a while, compile fails with a
  message like:
  Chapitre 2.
 
  LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
  on page 27
  undefined on input line 1385.
 
 
  LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
  on page 27
  undefined on input line 1385.
 
  ! Missing \endcsname inserted.
  to be read again
 :
  l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
 pour plus de
 d�tails).
  The control sequence marked to be read again should
  not appear between \csname and \endcsname.
 
  ! Extra \endcsname.
  argument ...s-d=E9di=E9es-aux\endcsname
\space
  l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
 
  Is this a known bug ? Any workaround ?
 
 This looks odd, with the \endcsname\space. Can you try to produce a
 minimal test document that exhibits the problem? I.e., keep deleting
 stuff until the problem goes away.

more than weird. This seems linked to the use of any book class. articles, 
letter, lettre, exam compile ok while a book class document of one line (title)
returns:

This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
2011.9.3)  3 SEP 2011 18:10
entering extended mode
 restricted \write18 enabled.
 %-line parsing enabled.
**nouveau1.tex
(./nouveau1.tex
LaTeX2e 2009/09/24
Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, pi
nyin, ukenglish, usenglishmax, basque, french, loaded.

(/usr/share/texmf-dist/tex/latex/base/book.cls
Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/bk11.clo
File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@chapter=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
\symupright=\mathgroup4
) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/share/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2008/03/30 v1.1d Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/share/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2008/03/30 v1.1d Input encoding file
)) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
Package: `setspace' 6.7 2000/12/01
)
! Undefined control sequence.
l.30 \LoadLetterOption
  {DIN}%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H return  for immediate help.
 ...

l.30 \LoadLetterOption{D
IN}%
You're in trouble here.  Try typing  return  to proceed.
If that doesn't work, type  X return  to quit.

! Undefined control sequence.
l.34 \KOMAoptions
 {%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H return  for immediate help.
 ...

l.39 f
  romalign=right%alignment of the address
You're in trouble here.  Try typing  return  to proceed.
If that doesn't work, type  X return  to quit.


Overfull \hbox (176.49751pt too wide) in paragraph at lines 39--55
[]\T1/cmr/m/n/10.95 fromalign=right

Re: Bug ?

2011-09-03 Thread Pavel Sanda 
Alain Didierjean wrote:
 more than weird. This seems linked to the use of any book class. articles, 
 letter, lettre, exam compile ok while a book class document of one line 
 (title)
 returns:

these logs are not much of help. you should report lyx version, texlive version,
and show some problematic file. i can't reproduce your troubles here.

pavel

 
 This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
 2011.9.3)  3 SEP 2011 18:10
 entering extended mode
  restricted \write18 enabled.
  %-line parsing enabled.
 **nouveau1.tex
 (./nouveau1.tex
 LaTeX2e 2009/09/24
 Babel v3.8l and hyphenation patterns for english, dumylang, nohyphenation, 
 pi
 nyin, ukenglish, usenglishmax, basque, french, loaded.
 
 (/usr/share/texmf-dist/tex/latex/base/book.cls
 Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
 (/usr/share/texmf-dist/tex/latex/base/bk11.clo
 File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
 )
 \c@part=\count79
 \c@chapter=\count80
 \c@section=\count81
 \c@subsection=\count82
 \c@subsubsection=\count83
 \c@paragraph=\count84
 \c@subparagraph=\count85
 \c@figure=\count86
 \c@table=\count87
 \abovecaptionskip=\skip41
 \belowcaptionskip=\skip42
 \bibindent=\dimen102
 ) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
 Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
 \symupright=\mathgroup4
 ) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
 Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
 (/usr/share/texmf-dist/tex/latex/base/t1enc.def
 File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
 LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
 )) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
 Package: inputenc 2008/03/30 v1.1d Input encoding file
 \inpenc@prehook=\toks14
 \inpenc@posthook=\toks15
 (/usr/share/texmf-dist/tex/latex/base/latin9.def
 File: latin9.def 2008/03/30 v1.1d Input encoding file
 )) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
 Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
 Package: `setspace' 6.7 2000/12/01
 )
 ! Undefined control sequence.
 l.30 \LoadLetterOption
   {DIN}%
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.30 \LoadLetterOption{D
 IN}%
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 ! Undefined control sequence.
 l.34 \KOMAoptions
  {%
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.39 f
   romalign=right%alignment of the address
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 
 Overfull \hbox (176.49751pt too wide) in paragraph at lines 39--55
 []\T1/cmr/m/n/10.95 
 fromalign=right,fromrule=aftername,fromphone=true,fromemail
 =true,foldmarks=false,enlargefirstpage=true
  []
 
 ! Undefined control sequence.
 l.58 \setkomavar
 {backaddressseparator}{ $\cdot$ }
 The control sequence at the end of the top line
 of your error message was never \def'ed. If you have
 misspelled it (e.g., `\hobx'), type `I' and the correct
 spelling (e.g., `I\hbox'). Otherwise just continue,
 and I'll forget about whatever was undefined.
 
 
 ! LaTeX Error: Missing \begin{document}.
 
 See the LaTeX manual or LaTeX Companion for explanation.
 Type  H return  for immediate help.
  ...
 
 l.58 \setkomavar{b
   ackaddressseparator}{ $\cdot$ }
 You're in trouble here.  Try typing  return  to proceed.
 If that doesn't work, type  X return  to quit.
 
 LaTeX Font Info:Try loading font information for OT1+ppl on input line 58.
 (/usr/share/texmf-dist/tex/latex/psnfss/ot1ppl.fd
 File: ot1ppl.fd 2001/06/04 font definitions for OT1/ppl.
 )
 LaTeX Font Info:Try loading font information for OML+zplm on input line 
 58.
 
 (/usr/share/texmf-dist/tex/latex/psnfss/omlzplm.fd
 File: omlzplm.fd 2002/09/08 Fontinst v1.914 font definitions for OML/zplm.
 )
 LaTeX Font Info:Try loading font information for OMS+zplm on input line 
 58.
 
 (/usr/share/texmf-dist/tex/latex/psnfss/omszplm.fd
 File: omszplm.fd 2002/09/08 Fontinst v1.914 font definitions for OMS/zplm.
 )
 LaTeX Font Info:Try loading

Re: Bug ?

2011-09-03 Thread Richard Heck 
On 09/03/2011 12:11 PM, Alain Didierjean wrote:

 - Mail original -
 De: Richard Heck rgh...@comcast.net
 À: alain didierjean alain.didierj...@free.fr
 Cc: lyx-users@lists.lyx.org
 Envoyé: Samedi 3 Septembre 2011 16:13:36
 Objet: Re: Bug ?

 On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
 I recompiled lyx  yesterday (on a gentoo system), adding support to
 luatex and xetex.

 Recompilation should not be required, unless you were upgrading to
 2.0.0 or something of the sort.
 using gentoo linux, packages are compiled localy. Adding luatex and xetex 
 support means recompiling lyx.

Last I knew, Pavel was using gentoo, so perhaps he can help.

But nonetheless, someone on gentoo who did not previously have xetex
support, but who has compiled 2.0.0 already, can add it by acquiring the
xetex binary (however they might do that) and doing ToolsReconfigure in
LyX. There's no compilation setting in LyX for this, as there is, e.g.,
for libx264 support in ffmpeg. LyX has no sort of compilation dependency
upon xetex (there are no headers that it needs, e.g.), but only uses it
as a completely external tool.

Indeed, you could create a script /usr/bin/xe(?:la)?tex whose entire
code was:
#!/bin/bash
exit 0;
and LyX would happily let you use XeTeX. (Not that it would work very
well) All LyX cares is that there is some program called
xe(?:la)?tex in the path, and that is checked during LyX's
configuration process, not during the autotools configuration.

Richard

PS Security issues anyone?

Re: Bug ?

2011-09-03 Thread Richard Heck 
On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
> I recompiled lyx  yesterday (on a gentoo system), adding support to luatex 
> and xetex. 
>
Recompilation should not be required, unless you were upgrading to 2.0.0
or something of the sort.

> Now, none of the book class documents compile (they use to compile without 
> any problem). Every once in a while, compile fails with a message like:
> Chapitre 2.
>
> LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
> 27 
> undefined on input line 1385.
>
>
> LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux' on page 
> 27 
> undefined on input line 1385.
>
> ! Missing \endcsname inserted.
>  
>:
> l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
>pour plus de d�tails).
> The control sequence marked  should
> not appear between \csname and \endcsname.
>
> ! Extra \endcsname.
>  ...s-d=E9di=E9es-aux\endcsname 
>   \space 
> l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
>
> Is this a known bug ? Any workaround ?
>
This looks odd, with the \endcsname\space. Can you try to produce a
minimal test document that exhibits the problem? I.e., keep deleting
stuff until the problem goes away.

Richard

Re: Bug ?

2011-09-03 Thread Alain Didierjean 


- Mail original -
> De: "Richard Heck" <rgh...@comcast.net>
> À: "alain didierjean" <alain.didierj...@free.fr>
> Cc: lyx-users@lists.lyx.org
> Envoyé: Samedi 3 Septembre 2011 16:13:36
> Objet: Re: Bug ?
>
> On 09/03/2011 03:27 AM, alain.didierj...@free.fr wrote:
> > I recompiled lyx  yesterday (on a gentoo system), adding support to
> > luatex and xetex.
> >
> Recompilation should not be required, unless you were upgrading to
> 2.0.0
> or something of the sort.

using gentoo linux, packages are compiled localy. Adding luatex and xetex
support means recompiling lyx.

>
> > Now, none of the book class documents compile (they use to compile
> > without any problem). Every once in a while, compile fails with a
> > message like:
> > Chapitre 2.
> >
> > LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
> > on page 27
> > undefined on input line 1385.
> >
> >
> > LaTeX Warning: Reference `sec:T=E2ches-d=E9di=E9es-aux'
> > on page 27
> > undefined on input line 1385.
> >
> > ! Missing \endcsname inserted.
> > 
> >:
> > l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
> >pour plus de
> >d�tails).
> > The control sequence marked  should
> > not appear between \csname and \endcsname.
> >
> > ! Extra \endcsname.
> >  ...s-d=E9di=E9es-aux\endcsname
> >   \space
> > l.1385 ...ec:T=E2ches-d=E9di=E9es-aux}
> >
> > Is this a known bug ? Any workaround ?
> >
> This looks odd, with the \endcsname\space. Can you try to produce a
> minimal test document that exhibits the problem? I.e., keep deleting
> stuff until the problem goes away.

more than weird. This seems linked to the use of any book class. articles, 
letter, lettre, exam compile ok while a book class document of one line (title)
returns:

This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
2011.9.3)  3 SEP 2011 18:10
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**nouveau1.tex
(./nouveau1.tex
LaTeX2e <2009/09/24>
Babel  and hyphenation patterns for english, dumylang, nohyphenation, pi
nyin, ukenglish, usenglishmax, basque, french, loaded.

(/usr/share/texmf-dist/tex/latex/base/book.cls
Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/bk11.clo
File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@chapter=\count80
\c@section=\count81
\c@subsection=\count82
\c@subsubsection=\count83
\c@paragraph=\count84
\c@subparagraph=\count85
\c@figure=\count86
\c@table=\count87
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
\symupright=\mathgroup4
) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
(/usr/share/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
)) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2008/03/30 v1.1d Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/share/texmf-dist/tex/latex/base/latin9.def
File: latin9.def 2008/03/30 v1.1d Input encoding file
)) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
Package: `setspace' 6.7 <2000/12/01>
)
! Undefined control sequence.
l.30 \LoadLetterOption
  {DIN}%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.30 \LoadLetterOption{D
IN}%
You're in trouble here.  Try typingto proceed.
If that doesn't work, type  X   to quit.

! Undefined control sequence.
l.34 \KOMAoptions
 {%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for ex

Re: Bug ?

2011-09-03 Thread Pavel Sanda 
Alain Didierjean wrote:
> more than weird. This seems linked to the use of any book class. articles, 
> letter, lettre, exam compile ok while a book class document of one line 
> (title)
> returns:

these logs are not much of help. you should report lyx version, texlive version,
and show some problematic file. i can't reproduce your troubles here.

pavel

> 
> This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 
> 2011.9.3)  3 SEP 2011 18:10
> entering extended mode
>  restricted \write18 enabled.
>  %&-line parsing enabled.
> **nouveau1.tex
> (./nouveau1.tex
> LaTeX2e <2009/09/24>
> Babel  and hyphenation patterns for english, dumylang, nohyphenation, 
> pi
> nyin, ukenglish, usenglishmax, basque, french, loaded.
> 
> (/usr/share/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2007/10/19 v1.4h Standard LaTeX document class
> (/usr/share/texmf-dist/tex/latex/base/bk11.clo
> File: bk11.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
> )
> \c@part=\count79
> \c@chapter=\count80
> \c@section=\count81
> \c@subsection=\count82
> \c@subsubsection=\count83
> \c@paragraph=\count84
> \c@subparagraph=\count85
> \c@figure=\count86
> \c@table=\count87
> \abovecaptionskip=\skip41
> \belowcaptionskip=\skip42
> \bibindent=\dimen102
> ) (/usr/share/texmf-dist/tex/latex/psnfss/mathpazo.sty
> Package: mathpazo 2005/04/12 PSNFSS-v9.2a Palatino w/ Pazo Math (D.Puga, WaS)
> \symupright=\mathgroup4
> ) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
> Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
> (/usr/share/texmf-dist/tex/latex/base/t1enc.def
> File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
> LaTeX Font Info:Redeclaring font encoding T1 on input line 43.
> )) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
> Package: inputenc 2008/03/30 v1.1d Input encoding file
> \inpenc@prehook=\toks14
> \inpenc@posthook=\toks15
> (/usr/share/texmf-dist/tex/latex/base/latin9.def
> File: latin9.def 2008/03/30 v1.1d Input encoding file
> )) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
> Package: setspace 2000/12/01 6.7 Contributed and Supported LaTeX2e package
> Package: `setspace' 6.7 <2000/12/01>
> )
> ! Undefined control sequence.
> l.30 \LoadLetterOption
>   {DIN}%
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
> 
> 
> ! LaTeX Error: Missing \begin{document}.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...
> 
> l.30 \LoadLetterOption{D
> IN}%
> You're in trouble here.  Try typingto proceed.
> If that doesn't work, type  X   to quit.
> 
> ! Undefined control sequence.
> l.34 \KOMAoptions
>  {%
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
> 
> 
> ! LaTeX Error: Missing \begin{document}.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...
> 
> l.39 f
>   romalign=right%alignment of the address
> You're in trouble here.  Try typingto proceed.
> If that doesn't work, type  X   to quit.
> 
> 
> Overfull \hbox (176.49751pt too wide) in paragraph at lines 39--55
> []\T1/cmr/m/n/10.95 
> fromalign=right,fromrule=aftername,fromphone=true,fromemail
> =true,foldmarks=false,enlargefirstpage=true
>  []
> 
> ! Undefined control sequence.
> l.58 \setkomavar
> {backaddressseparator}{ $\cdot$ }
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
> 
> 
> ! LaTeX Error: Missing \begin{document}.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...
> 
> l.58 \setkomavar{b
>   ackaddressseparator}{ $\cdot$ }
> You're in trouble here.  Try typingto proceed.
> If that doesn't work, type  X   to quit.
> 
> LaTeX Font Info:Try loading font information for OT1+ppl on input line 58.
> (/usr/share/texmf-dist/tex/latex/psnfss/ot1ppl.fd
> File: ot1ppl.fd 2001/06/04 font definitions for OT1/ppl.
> )
> LaTeX Font Info:Try loading font information for OML+zplm on input line 
> 58.
> 
> (/usr/share/texmf-dist/tex/latex/psnfss/omlzplm.fd
> File: omlzplm.fd 2002/09/08 Fontinst v1.914 font definitions for OML/zplm.
> )
> LaTeX Font Info:Try loading font information for OMS+zplm on input line 
> 58.
> 
> (/usr/share/texmf-dist/tex/latex/psnfss/omszplm.fd
> File: omszplm.fd 2002/09/08

  1   2   3   4   5   6   7   8   9   10   >