Re: problems in mac's LyX 1.6.5

2010-02-11 Thread Jean-Marc Lasgouttes
BH writes: > The keybindings you're using refer to obsolete command names. For > example, instead of "word-forward" you should use "word-right". And clearly, we should have a machanism in place for 'upgrading' users' file (like we do for layout files and, of course, lyx file). It may happen in ne

Re: problems in mac's LyX 1.6.5

2010-02-11 Thread BH
On Thu, Feb 11, 2010 at 10:52 AM, Ivan Werning wrote: > > On Feb 11, 2010, at 9:47 AM, Ivan Werning wrote: > >> >> On Feb 11, 2010, at 9:09 AM, BH wrote: >> >>> On Thu, Feb 11, 2010 at 9:04 AM, Ivan Werning >>> wrote: I have noticed the following problems with my Mac's LyX 1.6.5: -

Re: problems in mac's LyX 1.6.5

2010-02-11 Thread Ivan Werning
On Feb 11, 2010, at 9:47 AM, Ivan Werning wrote: > > On Feb 11, 2010, at 9:09 AM, BH wrote: > >> On Thu, Feb 11, 2010 at 9:04 AM, Ivan Werning >> wrote: >>> I have noticed the following problems with my Mac's LyX 1.6.5: >>> >>> - I cannot select text pressing SHIFT and the cursor >>> - I can

Re: problems in mac's LyX 1.6.5

2010-02-11 Thread Ivan Werning
On Feb 11, 2010, at 9:09 AM, BH wrote: > On Thu, Feb 11, 2010 at 9:04 AM, Ivan Werning > wrote: >> I have noticed the following problems with my Mac's LyX 1.6.5: >> >> - I cannot select text pressing SHIFT and the cursor >> - I can no longer create a new row in a formula by pressing CMD enter >

Re: problems in mac's LyX 1.6.5

2010-02-11 Thread BH
On Thu, Feb 11, 2010 at 9:04 AM, Ivan Werning wrote: > I have noticed the following problems with my Mac's LyX 1.6.5: > > - I cannot select text pressing SHIFT and the cursor > - I can no longer create a new row in a formula by pressing CMD enter > > I recently upgraded to 1.6.5, I don't know if t

problems in mac's LyX 1.6.5

2010-02-11 Thread Ivan Werning
I have noticed the following problems with my Mac's LyX 1.6.5: - I cannot select text pressing SHIFT and the cursor - I can no longer create a new row in a formula by pressing CMD enter I recently upgraded to 1.6.5, I don't know if this problem occurred a result of this installation. I never kn