Spellchecker not active, command disable
I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo
Re: Spellchecker not active, command disable
На 11.11.2010 10:18, Waluyo Adi Siswanto написа: I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo I confirm that the spellchecker is not activated by default. OS: Linux Mint 9 Best regards, Emil
Re: Spellchecker not active, command disable
Am 12.11.2010 um 00:33 schrieb Emil Pavlov: На 11.11.2010 10:18, Waluyo Adi Siswanto написа: I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo I confirm that the spellchecker is not activated by default. You are building LyX yourself and are using autotools (configure and make)? Did you read my answers to Waluyos message? What's the content of the file config.log? (grep for aspell and/or hunspell) Do you have the developer package for your spell checker software installed? It's not explicitly mentioned in INSTALL instructions... but you have to add the development packages for the spell checker tools to compile LyX with spell checker support. It's optional but enabled per default if found. Stephan OS: Linux Mint 9 Best regards, Emil
Spellchecker not active, command disable
I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo
Re: Spellchecker not active, command disable
На 11.11.2010 10:18, Waluyo Adi Siswanto написа: I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo I confirm that the spellchecker is not activated by default. OS: Linux Mint 9 Best regards, Emil
Re: Spellchecker not active, command disable
Am 12.11.2010 um 00:33 schrieb Emil Pavlov: На 11.11.2010 10:18, Waluyo Adi Siswanto написа: I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo I confirm that the spellchecker is not activated by default. You are building LyX yourself and are using autotools (configure and make)? Did you read my answers to Waluyos message? What's the content of the file config.log? (grep for aspell and/or hunspell) Do you have the developer package for your spell checker software installed? It's not explicitly mentioned in INSTALL instructions... but you have to add the development packages for the spell checker tools to compile LyX with spell checker support. It's optional but enabled per default if found. Stephan OS: Linux Mint 9 Best regards, Emil
Spellchecker not active, command disable
I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo
Re: Spellchecker not active, command disable
На 11.11.2010 10:18, Waluyo Adi Siswanto написа: I just compile lyx-2.0.0beta1 using the following commands: ./configure --with-version-suffix=-2.0.0beta1 make sudo make install everything ok no errors, but when I run lyx-2.0.0beta1, the spellchecker is not active. If I see the from the preference, it is grey (see the attachment) My lyx-1.6.7 works ok with the spellchecker. What was wrong my compilation? or how to make the spellchecker active? PS: I am in Ubuntu 10.04 Regards waluyo I confirm that the spellchecker is not activated by default. OS: Linux Mint 9 Best regards, Emil
Re: Spellchecker not active, command disable
Am 12.11.2010 um 00:33 schrieb Emil Pavlov: > На 11.11.2010 10:18, Waluyo Adi Siswanto написа: >> I just compile lyx-2.0.0beta1 >> using the following commands: >> >> ./configure --with-version-suffix=-2.0.0beta1 >> make >> sudo make install >> >> everything ok no errors, but when I run lyx-2.0.0beta1, the >> spellchecker is not active. >> If I see the from the preference, it is grey (see the attachment) >> >> My lyx-1.6.7 works ok with the spellchecker. >> >> What was wrong my compilation? or how to make the spellchecker active? >> >> PS: I am in Ubuntu 10.04 >> Regards >> waluyo >> >> > I confirm that the spellchecker is not activated by default. You are building LyX yourself and are using autotools (configure and make)? Did you read my answers to Waluyos message? What's the content of the file config.log? (grep for aspell and/or hunspell) Do you have the developer package for your spell checker software installed? It's not explicitly mentioned in INSTALL instructions... but you have to add the development packages for the spell checker tools to compile LyX with spell checker support. It's optional but enabled per default if found. Stephan > OS: Linux Mint 9 > > Best regards, > Emil
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás [EMAIL PROTECTED] writes: I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind C-Tab cell-split So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? Right. I did not think it might be re-bound in other files. I have changed the binding of cell-split, which I do not use much, and now C-Tab works for switching among documents. Great! Thanks very much for your help. Nicolás
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás [EMAIL PROTECTED] writes: I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind C-Tab cell-split So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? Right. I did not think it might be re-bound in other files. I have changed the binding of cell-split, which I do not use much, and now C-Tab works for switching among documents. Great! Thanks very much for your help. Nicolás
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás <[EMAIL PROTECTED]> writes: I get a "command disabled" message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind "C-Tab" "cell-split" So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? Right. I did not think it might be re-bound in other files. I have changed the binding of "cell-split", which I do not use much, and now C-Tab works for switching among documents. Great! Thanks very much for your help. Nicolás
Re: Command disable
Nicolás [EMAIL PROTECTED] writes: I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind C-Tab cell-split So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? JMarc
Re: Command disable
Nicolás [EMAIL PROTECTED] writes: I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind C-Tab cell-split So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? JMarc
Re: Command disable
Nicolás <[EMAIL PROTECTED]> writes: > I get a "command disabled" message when I press Crtl-TAB, which is > bound to buffer-next in the cua.bind file. However, If I press > Ctrl-PgUp or execute the command directly from the mini-buffer, I > obtain the desired result. Thie means that it is not the buffer-next > command taht is disbaled, but its invocation via Ctrl-TAB. Any clue > about this? Actually, C-Tab is not really bound to buffer-next, because in math.bind there is \bind "C-Tab" "cell-split" So it is the cell-split function that is disabled, not buffer-next. I do not know whether this cell-split function is useful though. Andre'? JMarc
Command disable
Hi! When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! Nicolás
Re: Command disable
Nicolás [EMAIL PROTECTED] writes: When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. JMarc
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás [EMAIL PROTECTED] writes: When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this?
Command disable
Hi! When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! Nicolás
Re: Command disable
Nicolás [EMAIL PROTECTED] writes: When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. JMarc
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás [EMAIL PROTECTED] writes: When I press certain combinations of keys I can see the message command disable in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. I get a command disabled message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this?
Command disable
Hi! When I press certain combinations of keys I can see the message "command disable" in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! Nicolás
Re: Command disable
Nicolás <[EMAIL PROTECTED]> writes: > When I press certain combinations of keys I can see the message > "command disable" in the lower bar. Could someone explain me what can > cause this message to appear? In other words, how/why is a command > disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. JMarc
Re: Command disable
Jean-Marc Lasgouttes wrote: Nicolás <[EMAIL PROTECTED]> writes: When I press certain combinations of keys I can see the message "command disable" in the lower bar. Could someone explain me what can cause this message to appear? In other words, how/why is a command disabled, and how can be enabled? Thanks! A command is disabled when it does not make sense at a given position (for example try to collapse an inset when there is no inset around cursor position). There is not much that needs to be done about it. I get a "command disabled" message when I press Crtl-TAB, which is bound to buffer-next in the cua.bind file. However, If I press Ctrl-PgUp or execute the command directly from the mini-buffer, I obtain the desired result. Thie means that it is not the buffer-next command taht is disbaled, but its invocation via Ctrl-TAB. Any clue about this?
