Re: lyx 1.60cr2 issues

2008-09-09 Thread Abdelrazak Younes
Hello Matthew, Matthew wrote: I've been trying to use the candidate release for 1.6. While there are some nice new features, like the ability to cut and paste graphics there are some changes and perhaps bugs which negatively impact lyx. My first pet peeve is that the export document command

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 8.09.08, Matthew wrote: ... the export document command doesn't appear to generate any output, ... In particular I'm trying to convert a lyx 1.6 file back into a 1.5.3 file so that I can run a more 'stable' version. Besides the bug mentionend in another reply: The default settings will

Re: lyx 1.60cr2 issues

2008-09-09 Thread Konrad Hofbauer
G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files. /Konrad

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6

Re: lyx 1.60cr2 issues

2008-09-09 Thread Daniel Lohmann
On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
James Sutherland wrote: My next peeve that I've found is that tab no longer navigates through the cells in an eqnarray. I haven't tried it with tables yet, but if it has the same behavior there, that would also be bad. I agree with this. The tab key has been taken over by the (VERY NICE)

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Daniel Lohmann wrote: On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as

Re: lyx 1.60cr2 issues

2008-09-09 Thread Matthew Bromberg
I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. As for the export files bug, so far I have discovered that the export function sends

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Matthew Bromberg wrote: I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. There seems motivation to do this. But we have to figure out

Re: lyx 1.60cr2 issues

2008-09-09 Thread Abdelrazak Younes
Hello Matthew, Matthew wrote: I've been trying to use the candidate release for 1.6. While there are some nice new features, like the ability to cut and paste graphics there are some changes and perhaps bugs which negatively impact lyx. My first pet peeve is that the export document command

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 8.09.08, Matthew wrote: ... the export document command doesn't appear to generate any output, ... In particular I'm trying to convert a lyx 1.6 file back into a 1.5.3 file so that I can run a more 'stable' version. Besides the bug mentionend in another reply: The default settings will

Re: lyx 1.60cr2 issues

2008-09-09 Thread Konrad Hofbauer
G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files. /Konrad

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx extension. At least here on the Mac LyX-1.5.6

Re: lyx 1.60cr2 issues

2008-09-09 Thread Daniel Lohmann
On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a .lyx

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
James Sutherland wrote: My next peeve that I've found is that tab no longer navigates through the cells in an eqnarray. I haven't tried it with tables yet, but if it has the same behavior there, that would also be bad. I agree with this. The tab key has been taken over by the (VERY NICE)

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Daniel Lohmann wrote: On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension .lyx15 for the exported file and the file-open dialogue in LyX-1.5 will not show it, as

Re: lyx 1.60cr2 issues

2008-09-09 Thread Matthew Bromberg
I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. As for the export files bug, so far I have discovered that the export function sends

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Matthew Bromberg wrote: I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. There seems motivation to do this. But we have to figure out

Re: lyx 1.60cr2 issues

2008-09-09 Thread Abdelrazak Younes
Hello Matthew, Matthew wrote: I've been trying to use the candidate release for 1.6. While there are some nice new features, like the ability to cut and paste graphics there are some changes and perhaps bugs which negatively impact lyx. My first pet peeve is that the export document command

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 8.09.08, Matthew wrote: > ... the export document command doesn't appear to generate any output, > ... In particular I'm trying to convert a lyx 1.6 file back into a > 1.5.3 file so that I can run a more 'stable' version. Besides the bug mentionend in another reply: The default settings will

Re: lyx 1.60cr2 issues

2008-09-09 Thread Konrad Hofbauer
G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension ".lyx15" for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a ".lyx" extension. At least here on the Mac LyX-1.5.6 DOES show the .lyx15-files.

Re: lyx 1.60cr2 issues

2008-09-09 Thread G. Milde
On 9.09.08, Konrad Hofbauer wrote: > G. Milde wrote: >> Besides the bug mentionend in another reply: The default settings will >> use the extension ".lyx15" for the exported file and the file-open >> dialogue in LyX-1.5 will not show it, as it expects a ".lyx" extension. > At least here on the

Re: lyx 1.60cr2 issues

2008-09-09 Thread Daniel Lohmann
On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension ".lyx15" for the exported file and the file-open dialogue in LyX-1.5 will not show it, as it expects a

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
James Sutherland wrote: My next peeve that I've found is that tab no longer navigates through the cells in an eqnarray. I haven't tried it with tables yet, but if it has the same behavior there, that would also be bad. I agree with this. The tab key has been taken over by the (VERY NICE)

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Daniel Lohmann wrote: On 09.09.2008, at 11:25, G. Milde wrote: On 9.09.08, Konrad Hofbauer wrote: G. Milde wrote: Besides the bug mentionend in another reply: The default settings will use the extension ".lyx15" for the exported file and the file-open dialogue in LyX-1.5 will not show it,

Re: lyx 1.60cr2 issues

2008-09-09 Thread Matthew Bromberg
I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. As for the export files bug, so far I have discovered that the export function sends

Re: lyx 1.60cr2 issues

2008-09-09 Thread rgheck
Matthew Bromberg wrote: I do like the new features and would love to continue working with 1.60cr2 if there are some workarounds. If there is a way to map ctrl-B back to \mathbf{} instead of \boldsymbol{} it would do it for me. There seems motivation to do this. But we have to figure out

lyx 1.60cr2 issues

2008-09-08 Thread Matthew
there, that would also be bad. After these problems I will stop testing 1.6 because I need to actually get some work done. Now if I could just convert my document back.. -- View this message in context: http://n2.nabble.com/lyx-1.60cr2-issues-tp1076619p1076619.html Sent from the LyX - Users mailing list

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My first pet peeve is that the export document command doesn't appear to generate any output, unless it's doing so in an unknown directory different from the directory of the .lyx source. In particular I'm trying to convert a lyx 1.6 file back into a 1.5.3 file so that I can run a more

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My next problem is the bold font toggling in math mode. ctrl-B generates a default \mathsymbol{} command which is wrong wrong wrong! A bold math character should almost always be non-italicized. The one exception may be Greek characters, but only because Latex has issues with that anyway.

lyx 1.60cr2 issues

2008-09-08 Thread Matthew
there, that would also be bad. After these problems I will stop testing 1.6 because I need to actually get some work done. Now if I could just convert my document back.. -- View this message in context: http://n2.nabble.com/lyx-1.60cr2-issues-tp1076619p1076619.html Sent from the LyX - Users mailing list

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My first pet peeve is that the export document command doesn't appear to generate any output, unless it's doing so in an unknown directory different from the directory of the .lyx source. In particular I'm trying to convert a lyx 1.6 file back into a 1.5.3 file so that I can run a more

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My next problem is the bold font toggling in math mode. ctrl-B generates a default \mathsymbol{} command which is wrong wrong wrong! A bold math character should almost always be non-italicized. The one exception may be Greek characters, but only because Latex has issues with that anyway.

lyx 1.60cr2 issues

2008-09-08 Thread Matthew
there, that would also be bad. After these problems I will stop testing 1.6 because I need to actually get some work done. Now if I could just convert my document back.. -- View this message in context: http://n2.nabble.com/lyx-1.60cr2-issues-tp1076619p1076619.html Sent from the LyX - Users mailing list

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My first pet peeve is that the export document command doesn't appear to generate any output, unless it's doing so in an unknown directory different from the directory of the .lyx source. In particular I'm trying to convert a lyx 1.6 file back into a 1.5.3 file so that I can run a more

Re: lyx 1.60cr2 issues

2008-09-08 Thread James Sutherland
My next problem is the bold font toggling in math mode. ctrl-B generates a default \mathsymbol{} command which is wrong wrong wrong! A bold math character should almost always be non-italicized. The one exception may be Greek characters, but only because Latex has issues with that anyway.