[opensuse] Help with crontab
Hello, I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add @restart /usr/bin/festival --server Tha is straightforward, but then I don't know how to proceed from there. I read the man page for crontab and it says that once the commands are specified, you have to exit the editor that is specified (I guess in my system) and then the crontab file becomes active. I have no idea where to proceed after I past the command into the window. I tried typing exit, q and control q, but nothing happens. The menu of the window says to save the output, but when I try that it gives a blank box to type a name to save it to. What is the correct way to finish the task Any help would be appreciated. Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2019 03.40, Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
Tha is straightforward, but then I don't know how to proceed from there. I read the man page for crontab and it says that once the commands are specified, you have to exit the editor that is specified (I guess in my system) and then the crontab file becomes active. I have no idea where to proceed after I past the command into the window. I tried typing exit, q and control q, but nothing happens. The menu of the window says to save the output, but when I try that it gives a blank box to type a name to save it to. What is the correct way to finish the task Any help would be appreciated. Gustav
You are in "vi". Many people have been trapped by "vi" not knowing how to exit. Me too. I had to reboot the machine to exit, then I searched in "man" to find how. It is ESCape key, then ":wq" without the quotes. OR, better change the editor to one of your choice. Edit or create file ".bashrc": export EDITOR=/usr/bin/jstar Just add that line, pointing to the editor you prefer. Better one that works in text mode: vi, emacs, joe, mcedit. You can also use a graphic one, but then it will not work in emergencies. Once done, exit the terminal and try the crontab thing again :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 9/29/19 10:53 PM, Carlos E.R. wrote:
On 30/09/2019 03.40, Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console  " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
Tha is straightforward, but then I don't know how to proceed from there. I read the man page for crontab and it says that once the commands are specified, you have to exit the editor that is specified (I guess in my system) and then the crontab file becomes active. I have no idea where to proceed after I past the command into the window. I tried typing exit,  q and control q, but nothing happens. The menu of the window says to save the output, but when I try that it gives a blank box to type a name to save it to. What is the correct way to finish the task Any help would be appreciated. Gustav You are in "vi". Many people have been trapped by "vi" not knowing how to exit. Me too. I had to reboot the machine to exit, then I searched in "man" to find how.
It is ESCape key, then ":wq" without the quotes.
OR, better change the editor to one of your choice.
Edit or create file ".bashrc":
export EDITOR=/usr/bin/jstar
Just add that line, pointing to the editor you prefer. Better one that works in text mode: vi, emacs, joe, mcedit. You can also use a graphic one, but then it will not work in emergencies.
Once done, exit the terminal and try the crontab thing again :-)
Thank you!!! Yes, Esc :wq enter, did the trick. Now to reboot and see if TTS is working with festival. And I specified reboot instead of restart. It's been several years (on and off, not steady) trying to get the TTS voice to change. I'll post later, Gustav
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/30/2019 07:08 AM, Gustav Degreef wrote:
Thank you!!! Yes, Esc :wq enter, did the trick. Now to reboot and see if TTS is working with festival. And I specified reboot instead of restart. It's been several years (on and off, not steady) trying to get the TTS voice to change. I'll post later, Gustav
Take the 20-30 minutes to do a basic vim tutorial -- it will save you untold amounts of grief for years to come and make working from the command-line on almost any Unix/Linux machine you sit down to a breeze. Well worth the time spent. I used to just keep a cheatsheet handy. Any decent one will do. This one isn't bad: https://www.cs.cmu.edu/~15131/f17/topics/vim/vim-cheatsheet.pdf Just remember vim _has 2 modes_ (1) command mode and (2) insert mode. In command mode you can yank (copy) cut (del) paste search, etc. and interact with vim's command line. E.g. ':command` (type `:` followed by command) You type text into the document in insert mode. 'i' enters insert mode, ('R' enters it in replace mode). You hit [Esc] to exit insert mode and return to command mode. **so just remember to bang the [Esc] key twice** after entering text (one to exit, once more just to make you feel better) and you will be returned to the friendly command mode. vim is incredibly powerful, you can do just about anything you need by learning a few basic commands. Spend a bit more time with it and you will find it is more like the Swiss-Army knife of editors and there really isn't much you can't do with it. (now emacs is just a capable and a fine editor too, I use both, I've just spent more time vim than emacs, so this is no editor flame war) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2019 14:42, David C. Rankin wrote:
Take the 20-30 minutes to do a basic vim tutorial -- it will save you untold amounts of grief for years to come and make working from the command-line on almost any Unix/Linux machine you sit down to a breeze.
Well worth the time spent. I used to just keep a cheatsheet handy. Any decent one will do. This one isn't bad:
https://www.cs.cmu.edu/~15131/f17/topics/vim/vim-cheatsheet.pdf
There are many applications that can or do make use of the VI commands or fingerings. Among then is the BASH shell. READLINE This is the library that handles reading input when using an interactive shell, unless the --noediting option is given at shell invocation. Line editing is also used when using the -e option to the read builtin. By default, the line editing commands are similar to those of Emacs. A vi-style line editing interface is also available. Line editing can be enabled at any time using the -o emacs or -o vi options to the set builtin (see SHELL BUILTIN COMMANDS below). To turn off line editing after the shell is running, use the +o emacs or +o vi options to the set builtin. So you really need to learn to use VI or EMACS. or both. I learnt VI over 40 years ago on a PDP-11 that didn't have the memory to be able to run EMACS. (As in "Eight Megabytes and Constantly Swapping". Eventually we got a VAX-780 and with virtual memory it became EMACP - that's p-for-paging. In due course we got micro-EMACS and EMACS go redesigned so that it wasn't so hungry. And VI became VIM that was more hungry but also free of some of design deficiencies and bugs and idiosyncrasies of the original VI. But still used the same fingering. You really do need to learn one or the other. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2019 21.16, Anton Aylward wrote:
On 01/10/2019 14:42, David C. Rankin wrote:
Take the 20-30 minutes to do a basic vim tutorial -- it will save you untold amounts of grief for years to come and make working from the command-line on almost any Unix/Linux machine you sit down to a breeze.
Well worth the time spent. I used to just keep a cheatsheet handy. Any decent one will do. This one isn't bad:
https://www.cs.cmu.edu/~15131/f17/topics/vim/vim-cheatsheet.pdf
There are many applications that can or do make use of the VI commands or fingerings. Among then is the BASH shell.
READLINE This is the library that handles reading input when using an interactive shell, unless the --noediting option is given at shell invocation. Line editing is also used when using the -e option to the read builtin. By default, the line editing commands are similar to those of Emacs. A vi-style line editing interface is also available. Line editing can be enabled at any time using the -o emacs or -o vi options to the set builtin (see SHELL BUILTIN COMMANDS below). To turn off line editing after the shell is running, use the +o emacs or +o vi options to the set builtin.
So you really need to learn to use VI or EMACS. or both.
I never did, and I use the command line fine :-) It is the first time I see those options, thanks. Yeah, I know readline exists, that's about it.
I learnt VI over 40 years ago on a PDP-11 that didn't have the memory to be able to run EMACS. (As in "Eight Megabytes and Constantly Swapping". Eventually we got a VAX-780 and with virtual memory it became EMACP - that's p-for-paging. In due course we got micro-EMACS and EMACS go redesigned so that it wasn't so hungry. And VI became VIM that was more hungry but also free of some of design deficiencies and bugs and idiosyncrasies of the original VI. But still used the same fingering.
You really do need to learn one or the other.
Not really :-P You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-) And you need the basics of vi because every Linux (and unix) system has it. Even rescue/emergency modes - but in openSUSE, joe is installed by default. Then you can also learn a bit of emacs. Then if you like, learn one or both in depth: both are very very powerful. I never did. I prefer other editors, as I come from the DOS/WIN world, where the design of interfaces is, I have to recognize, better than in Linux. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 01/10/2019 19:00, Carlos E. R. wrote:
I never did, and I use the command line fine :-)
It is the first time I see those options, thanks. Yeah, I know readline exists, that's about it.
Yes. I grew up CLI with the original Bourne shell, as I said, 40 years ago. But I love the extended capabilities of BASH, both as a scripting too and as a interactive too. Command recall and editing using readline is brilliant. its like having a library at your fingertips. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2019 19:00, Carlos E. R. wrote:
Then if you like, learn one or both in depth: both are very very powerful. I never did. I prefer other editors, as I come from the DOS/WIN world, where the design of interfaces is, I have to recognize, better than in Linux.
You think it is better because it is what you grew up, what you first encountered. For me, the DOW/WIN editors are ... well, awkward and unnatural. VIM is so much better! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2019 01.26, Anton Aylward wrote:
On 01/10/2019 19:00, Carlos E. R. wrote:
Then if you like, learn one or both in depth: both are very very powerful. I never did. I prefer other editors, as I come from the DOS/WIN world, where the design of interfaces is, I have to recognize, better than in Linux.
You think it is better because it is what you grew up, what you first encountered. For me, the DOW/WIN editors are ... well, awkward and unnatural. VIM is so much better!
Not because of that. IBM designed a very thoughtful standard way for interfaces, called CUA, I think. <https://en.wikipedia.org/wiki/IBM_Common_User_Access> Why does Alt-F4 close a program? Or F1 call help? Well, it is CUA. Vi was designed for programmers. Word Star was designed for touch typists. None is CUA. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA.
indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-10-02 08:39 AM, Anton Aylward wrote:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA. indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure.
Way back in the dark ages, I used WordStar 2000 at work and was familiar with many of the key sequences. The big complaint with Word back then was that doing many things required moving a hand from the keyboard to the mouse and back. This would really slow down experienced typists. Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/2/19 3:50 PM, James Knott wrote:
Back in those days, I was using PC-Write on my home computer
- aha :) & * - at that epoch :Jim Knopf*, nicknamed*Jim Button : his PC-File* * * *....* * regards* * * * * *....* * regards* * * -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2019 14.50, James Knott wrote:
On 2019-10-02 08:39 AM, Anton Aylward wrote:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA. indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure.
Way back in the dark ages, I used WordStar 2000 at work and was familiar with many of the key sequences. The big complaint with Word back then was that doing many things required moving a hand from the keyboard to the mouse and back. This would really slow down experienced typists.
Yes. I used both, and WS 2000 was better, but it lost. WP was even better - the MsDOS versions, specially when one had a ribbon printer, and even more if it was 9 pin, not 24. Mind, WS 2000 used a different keyboard layout than WS "classic". Programmers IDE such as Borland's used the WS "classic" keyboard. Today, in Linux Lazarus uses it. And the plain jstar.
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
I don't recall using that one. :-? -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))
On 2019-10-02 11:23 AM, Carlos E. R. wrote:
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write I don't recall using that one. :-?
I still have the manual for it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 2 oktober 2019 17:23:07 CEST schreef Carlos E. R.:
On 02/10/2019 14.50, James Knott wrote:
On 2019-10-02 08:39 AM, Anton Aylward wrote:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA.
indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure.
Way back in the dark ages, I used WordStar 2000 at work and was familiar with many of the key sequences. The big complaint with Word back then was that doing many things required moving a hand from the keyboard to the mouse and back. This would really slow down experienced typists.
Yes. I used both, and WS 2000 was better, but it lost. WP was even better - the MsDOS versions, specially when one had a ribbon printer, and even more if it was 9 pin, not 24.
O yeah. And then create triangles as image in WP and have it printed properly ...... Those were the days. Yay, we have a triangle. A line? No, just dots in a pattern :-).
Mind, WS 2000 used a different keyboard layout than WS "classic".
Programmers IDE such as Borland's used the WS "classic" keyboard. Today, in Linux Lazarus uses it. And the plain jstar.
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
I don't recall using that one. :-?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/02/2019 07:50 AM, James Knott wrote:
Way back in the dark ages, I used WordStar 2000 at work and was familiar with many of the key sequences. The big complaint with Word back then was that doing many things required moving a hand from the keyboard to the mouse and back. This would really slow down experienced typists.
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
Novell WordPerfect anyone :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2019 21.06, David C. Rankin wrote:
On 10/02/2019 07:50 AM, James Knott wrote:
Way back in the dark ages, I used WordStar 2000 at work and was familiar with many of the key sequences. The big complaint with Word back then was that doing many things required moving a hand from the keyboard to the mouse and back. This would really slow down experienced typists.
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
Novell WordPerfect anyone :)
I used Wordperfect 5, but I did not remember what company owned it. Wonderful printer support. Awkward interface, needed to print labels for the keyboard. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-10-03 06:39 AM, Carlos E. R. wrote:
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
Novell WordPerfect anyone :)
I used Wordperfect 5, but I did not remember what company owned it. Wonderful printer support. Awkward interface, needed to print labels for the keyboard.
We also had WP at work back in those days, but I rarely used it. Back then you could buy keyboard templates for various apps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2019 12.55, James Knott wrote:
On 2019-10-03 06:39 AM, Carlos E. R. wrote:
Back in those days, I was using PC-Write on my home computer. It had some key strokes in common with WordStar. https://en.wikipedia.org/wiki/PC-Write
Novell WordPerfect anyone :)
I used Wordperfect 5, but I did not remember what company owned it. Wonderful printer support. Awkward interface, needed to print labels for the keyboard.
We also had WP at work back in those days, but I rarely used it. Back then you could buy keyboard templates for various apps.
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places. It was the only software where I really needed a keyboard template, which proves the interface was awkward. Of course, once I create that template, creating others was trivial. There were machines at the college with WP for us to use (at the library? I don't remember), and I heard it was the default editor at the Canadian administration (I was in Canada at the time). -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places.
I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2019 14.34, James Knott wrote:
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places.
I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side.
I saw both types somewhere. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-10-03 09:32 AM, Carlos E. R. wrote:
On 03/10/2019 14.34, James Knott wrote:
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places. I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side.
I saw both types somewhere.
https://en.wikipedia.org/wiki/IBM_PC_keyboard BTW, I'm typing on a Model M keyboard right now. It's excellent and built like a tank. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2019 15.37, James Knott wrote:
On 2019-10-03 09:32 AM, Carlos E. R. wrote:
On 03/10/2019 14.34, James Knott wrote:
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places. I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side.
I saw both types somewhere.
https://en.wikipedia.org/wiki/IBM_PC_keyboard
BTW, I'm typing on a Model M keyboard right now. It's excellent and built like a tank.
I meant this: <https://images.app.goo.gl/CT9J3QFAhRzPK75N7> <https://images.app.goo.gl/pSxWS2xhfZ9PvjNk7> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [10-03-19 09:37]:
On 03/10/2019 14.34, James Knott wrote:
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places.
I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side.
I saw both types somewhere.
please move to off-topic. nothing to do with opensuse. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2019-10-03 15:32 (UTC+0200):
James Knott wrote:
On 2019-10-03 07:03 AM, Carlos E. R. wrote:
I wrote the template :-) First an exactly sized box that had to be cut out, where the function keys where, then I added the text at the exact places.
I did the same for PC-Write. However, this was for the old PC/XT layout, with the function keys to the left side.
I saw both types somewhere.
Something like the best keyboards ever made, for one handed operation of shifted function keys, and snappy WP I/O? I still have templates made to fit the space where function key meanings can be written. Note the location of the CAPS lock, and the sizes of ENTER and BS, and the extra locations of = and *. I wish I had known to buy three times as many as I did of these (only 3, of which two escaped, and one died). https://commons.wikimedia.org/wiki/File:Omnikey102p3248.jpg https://commons.wikimedia.org/wiki/File:ErgoLogicFlexProKB2652.jpg still work, but they're really tired after more than two decades of service. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos, et al -- ...and then Carlos E. R. said... % % On 02/10/2019 21.06, David C. Rankin wrote: % > % > Novell WordPerfect anyone :) % % I used Wordperfect 5, but I did not remember what company owned it. It wasn't always Novell. But, heck, they own UNIX as well, right? :-) % Wonderful printer support. Awkward interface, needed to print labels for % the keyboard. ZOMG that's right! I'd forgotten the keyboard overlay that came in every box ... and then usually got lost. Thank heavens for standard keyboards, too, so that they could ship a one-size-fits-all sheet. Good times ... :-) % % -- % Cheers / Saludos, % % Carlos E. R. % (from 15.0 x86_64 at Telcontar) HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Anton Aylward <opensuse@antonaylward.com> [10-02-19 08:42]:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA.
indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure.
yes, wordstar came very early in the pipe, cp/m, and it's key-combinations are repeated in many apps. once one learns an editor, ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/2/19 4:29 PM, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [10-02-19 08:42]:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA. indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure. yes, wordstar came very early in the pipe, cp/m, and it's key-combinations are repeated in many apps. once one learns an editor, ...
& see wiki remark: "The cross-platform JOE editor is a very WordStar-like alternative. When invoked as jstar Joe emulates many WordStar keybindings. JOE lacks formatting options and essentially only operates in nondocument mode, but formatted documents can be authored in HTML/CSS, Markdown or another markup language." .... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2019 09:29, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [10-02-19 08:42]:
On 01/10/2019 20:15, Carlos E. R. wrote:
Vi was designed for programmers. Word Star was designed for touch typists. None is CUA.
indeed. A touch typist will think WordStar/Wordperfect is a great editor (I don't know about MS-Word; the tt's I dated who raved about Wordstar hated being forced to change to MS-word). Its about familiarity and early exposure.
yes, wordstar came very early in the pipe, cp/m, and it's key-combinations are repeated in many apps. once one learns an editor, ...
You can, of course, redefine the VIM keymaps in a variety of ways. Googing might be confusing since most of what it returns is about creating shot cuts. Then there are plugins to extend core functionality ... https://adamdelong.com/5-vim-plugins-helped-switch-sublime/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 01/10/2019 19:00, Carlos E. R. wrote:
Then if you like, learn one or both in depth: both are very very powerful. I never did. I prefer other editors, as I come from the DOS/WIN world, where the design of interfaces is, I have to recognize, better than in Linux.
You think it is better because it is what you grew up, what you first encountered. For me, the DOW/WIN editors are ... well, awkward and unnatural. VIM is so much better!
The "which editor is better" discusssion is best left for the Stammtisch, but on a Unix/Linux system, a good sysadmin ought to know at least some basic vi. -- Per Jessen, Zürich (15.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-)
Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering "sudo crontab -e" and pasting "@reboot /usr/bin/festival --server" and entering in Vi [Esc] :wq [Enter ] exits to the command prompt. If I do from the command line "festival --server", then the server runs. What is the way to check if I edited the crontab file correctly? Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Gustav Degreef wrote:
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-)
Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering
"sudo crontab -e"
and pasting "@reboot /usr/bin/festival --server"
and entering in Vi
[Esc] :wq [Enter ] exits to the command prompt.
If I do from the command line "festival --server", then the server runs.
What is the way to check if I edited the crontab file correctly? Gustav
cat /var/spool/cron/tabs/root Maybe check that the 'festival' binary is actually in /usr/bin ? -- Per Jessen, Zürich (8.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/3/19 3:09 AM, Per Jessen wrote:
Gustav Degreef wrote:
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-) Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering
"sudo crontab -e"
and pasting "@reboot /usr/bin/festival --server"
and  entering in Vi
[Esc] :wq [Enter ] exits to the command prompt.
If I do from the command line "festival --server", then the server runs.
What is the way to check if I edited the crontab file correctly? Gustav cat /var/spool/cron/tabs/root
Silly me, cat /var/spool/cron/tabs/root shows that I left " at the end of the command. That's why it didn't work. Thanks, Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2019 08.43, Gustav Degreef wrote:
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-)
Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering
"sudo crontab -e"
and pasting "@reboot /usr/bin/festival --server"
and entering in Vi
[Esc] :wq [Enter ] exits to the command prompt.
If I do from the command line "festival --server", then the server runs.
What is the way to check if I edited the crontab file correctly? Gustav
Just repeat the "sudo crontab -e" and check what you typed. It is cron, and cron *mails* to you the errors it finds at runtime. So check your system mail. Not your personal mail account. :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, 3 Oct 2019 12:42:46 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 03/10/2019 08.43, Gustav Degreef wrote:
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-)
Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering
"sudo crontab -e"
and pasting "@reboot /usr/bin/festival --server"
and entering in Vi
[Esc] :wq [Enter ] exits to the command prompt.
If I do from the command line "festival --server", then the server runs.
What is the way to check if I edited the crontab file correctly? Gustav
Just repeat the "sudo crontab -e" and check what you typed.
Or safer to check: $ sudo crontab -l
It is cron, and cron *mails* to you the errors it finds at runtime. So check your system mail. Not your personal mail account. :-)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Gustav Degreef <gustav97@gmail.com> [10-03-19 02:43]:
On 10/1/19 7:00 PM, Carlos E. R. wrote:
snip You only need the very basics of vi, enough you change the default editor to one of your liking, and that's it. That there is a command mode and an insert or overwrite mode, how to exit saving or not saving, and that's it ;-)
Well, I thought that I had done it right, but reading your message and David's, I am not sure I did it right. I also say that, because "festival" server is not running despite opening a terminal and entering
"sudo crontab -e"
and pasting "@reboot /usr/bin/festival --server"
and entering in Vi
[Esc] :wq [Enter ] exits to the command prompt.
If I do from the command line "festival --server", then the server runs.
What is the way to check if I edited the crontab file correctly? Gustav
sudo crontab -l -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/1/19 2:42 PM, David C. Rankin wrote:
On 09/30/2019 07:08 AM, Gustav Degreef wrote:
Thank you!!! Yes, Esc :wq enter, did the trick. Now to reboot and see if TTS is working with festival. And I specified reboot instead of restart. It's been several years (on and off, not steady) trying to get the TTS voice to change. I'll post later, Gustav Take the 20-30 minutes to do a basic vim tutorial -- it will save you untold amounts of grief for years to come and make working from the command-line on almost any Unix/Linux machine you sit down to a breeze.
Well worth the time spent. I used to just keep a cheatsheet handy. Any decent one will do. This one isn't bad:
https://www.cs.cmu.edu/~15131/f17/topics/vim/vim-cheatsheet.pdf
Just remember vim _has 2 modes_ (1) command mode and (2) insert mode.
In command mode you can yank (copy) cut (del) paste search, etc. and interact with vim's command line. E.g. ':command` (type `:` followed by command)
You type text into the document in insert mode. 'i' enters insert mode, ('R' enters it in replace mode). You hit [Esc] to exit insert mode and return to command mode.
**so just remember to bang the [Esc] key twice** after entering text (one to exit, once more just to make you feel better) and you will be returned to the friendly command mode.
vim is incredibly powerful, you can do just about anything you need by learning a few basic commands. Spend a bit more time with it and you will find it is more like the Swiss-Army knife of editors and there really isn't much you can't do with it.
(now emacs is just a capable and a fine editor too, I use both, I've just spent more time vim than emacs, so this is no editor flame war)
Thanks, looks like solid, sound advice. Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 03/10/2019 à 08:11, Gustav Degreef a écrit :
Thanks, looks like solid, sound advice. Gustav
and don't forget there is a GUI version (gvim), much easier if you have to copy/paste and be warned that much harder version of vi than vim are around, and on an other computer you may have to cope with them :-) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
I think '@reboot' is the correct instruction, but maybe '@restart' will also work. It is not listed in the man page. -- Per Jessen, Zürich (16.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2019 07.46, Per Jessen wrote:
Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
I think '@reboot' is the correct instruction, but maybe '@restart' will also work. It is not listed in the man page.
In crontab(5) :-) EXTENSIONS These special time specification "nicknames" which replace the 5 initial time and date fields, and are prefixed with the '@' character, are supported: @reboot : Run once after reboot. @yearly : Run once a year, ie. "0 0 1 1 *". @annually : Run once a year, ie. "0 0 1 1 *". @monthly : Run once a month, ie. "0 0 1 * *". @weekly : Run once a week, ie. "0 0 * * 0". @daily : Run once a day, ie. "0 0 * * *". @hourly : Run once an hour, ie. "0 * * * *". -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 9/30/19 1:46 AM, Per Jessen wrote:
Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
I think '@reboot' is the correct instruction, but maybe '@restart' will also work. It is not listed in the man page.
Yes, reboot was the correct instruction. I managed to get festival server running, but can't get festival to work with speech-dispatcher. The configuration program indicates that there is a missing package: festival-freebsoft-utils A search on opensuse sofware search page shows that festival is the ONLY rpm available in any of the repos. I found the "homepage", https://freebsoft.org/festival-freebsoft-utils which shows that there are nearly 50 packages available for other distros, but not opensuse. The page links to the source code: "The source code is managed using Git. You can use the Git web interface <https://github.com/brailcom/festival-freebsoft-utils> or clone the repository from: https://github.com/brailcom/festival-freebsoft-utils.git" Is there a way that this package can get into the opensuse distro? Festival itself is in the defalut distro, but without the utils, it is non-functional. thanks, Gustav.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 3 Oct 2019 08:02:55 -0400 Gustav Degreef <gustav97@gmail.com> wrote:
On 9/30/19 1:46 AM, Per Jessen wrote:
Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
I think '@reboot' is the correct instruction, but maybe '@restart' will also work. It is not listed in the man page.
Yes, reboot was the correct instruction. I managed to get festival server running, but can't get festival to work with speech-dispatcher. The configuration program indicates that there is a missing package:
festival-freebsoft-utils
A search on opensuse sofware search page shows that festival is the ONLY rpm available in any of the repos. I found the "homepage",
https://freebsoft.org/festival-freebsoft-utils
which shows that there are nearly 50 packages available for other distros, but not opensuse. The page links to the source code:
"The source code is managed using Git. You can use the Git web interface <https://github.com/brailcom/festival-freebsoft-utils> or clone the repository from:
I'm sorry but the install instructions say to just download the package and copy it to the appropriate location. Why do you need a version packaged for opensuse? See https://github.com/brailcom/festival-freebsoft-utils i.e. please read the documentation.
Is there a way that this package can get into the opensuse distro? Festival itself is in the defalut distro, but without the utils, it is non-functional. thanks, Gustav.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/3/19 8:32 AM, Dave Howorth wrote:
On Thu, 3 Oct 2019 08:02:55 -0400 Gustav Degreef <gustav97@gmail.com> wrote:
On 9/30/19 1:46 AM, Per Jessen wrote:
Gustav Degreef wrote:
Hello,
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
I think '@reboot' is the correct instruction, but maybe '@restart' will also work. It is not listed in the man page.
Yes, reboot was the correct instruction. I managed to get festival server running, but can't get festival to work with speech-dispatcher. The configuration program indicates that there is a missing package:
festival-freebsoft-utils
A search on opensuse sofware search page shows that festival is the ONLY rpm available in any of the repos. I found the "homepage",
https://freebsoft.org/festival-freebsoft-utils
which shows that there are nearly 50 packages available for other distros, but not opensuse. The page links to the source code:
"The source code is managed using Git. You can use the Git web interface <https://github.com/brailcom/festival-freebsoft-utils> or clone the repository from:
https://github.com/brailcom/festival-freebsoft-utils.git" I'm sorry but the install instructions say to just download the package and copy it to the appropriate location. Why do you need a version packaged for opensuse?
See https://github.com/brailcom/festival-freebsoft-utils i.e. please read the documentation.
Is there a way that this package can get into the opensuse distro? Festival itself is in the defalut distro, but without the utils, it is non-functional. thanks, Gustav.
Thanks for the suggestions. I am a regular user not programmer or technician. I am visually impaired and I have serious problems reading. That is one of the reasons for my interest in festival. Maybe festival is not siri or alexa, but I am looking for a more human voice than espeak. If I can get festival to work without a os rpm, I would be satisfied. But I have spent years trying and I have failed repeatedly, so I posted mainly asking for assistance. I did read the README file and I found the directory where to put the .scm files indicated in the readme. However, as in previous attempts to use git, I can not download the files. I have trouble navigating websites and I havee never been able to download software from a git repository (not sure I am using the correct term). It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Gustav Degreef wrote:
It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils To install it, the documentation says: ---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line (require 'speech-dispatcher) to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). -------------------------- The scm files look like a bunch of macros, but I don't recognise the language. -- Per Jessen, Zürich (8.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 04 Oct 2019 07:36:25 +0200 Per Jessen <per@computer.org> wrote:
Gustav Degreef wrote:
It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). --------------------------
The scm files look like a bunch of macros, but I don't recognise the language.
I think it is Scheme. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/10/2019 07.36, Per Jessen wrote:
Gustav Degreef wrote:
It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). --------------------------
That's a complicated procedure for him (he said: «I am visually impaired and I have serious problems reading.»), as compared to a zypper command to just install a single rpm. Now, if someone posts an exact command line to download and install those files, and the config change... I guess that would be easier for him. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 10/4/19 7:56 AM, Carlos E. R. wrote:
On 04/10/2019 07.36, Per Jessen wrote:
Gustav Degreef wrote:
It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). -------------------------- That's a complicated procedure for him (he said: «I am visually impaired and I have serious problems reading.»), as compared to a zypper command to just install a single rpm.
Now, if someone posts an exact command line to download and install those files, and the config change... I guess that would be easier for him.
Thanks, the rpm is not necessary, since I understood what I was told about the ease of installation (read the readme) and where I could get the tarball. The difficulty was dealing with the git webpage (I'm sure it's not so hard once you know how). I am very grateful to everyone who gave input in helping me finally solve this. The sound of the espeak voice never bothered me. It bothers my partner and recently a very dear friend who first heard it. It made me realize that it gives a very bad impression of linux. I am very much encouraged by people's help, and I am going to try to find even bette voices. In the process of getting festival to work, I saw that the code has essentially not changed in 13 years! I recently read an article on the state of the art of linux TTS, it gave me a push to find a voice that sounds more human and gives a better impression to others. Thanks! Gustav
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 04/10/2019 07.36, Per Jessen wrote:
Gustav Degreef wrote:
It is very frustrating that opensuse, such a great distro, is not more accessible (festival is only one of two alternatives to espeak and it is crippled and maddeningly difficult to get working. Any help would be appreciated, Gustav
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). --------------------------
That's a complicated procedure for him (he said: «I am visually impaired and I have serious problems reading.»), as compared to a zypper command to just install a single rpm.
Now, if someone posts an exact command line to download and install those files, and the config change... I guess that would be easier for him.
Gustav seems perfectly capable to me, I'm sure he will manage just fine. The procedure will look something like this: - retrieve tarball: https://freebsoft.org/pub/projects/festival-freebsoft-utils/festival-freebso... - unpack tarball (tar xzvf festival-freebsoft-utils-0.10.tar.gz) - (as root) cp -a festival-freebsoft-utils-0.10/*scm /usr/share/festival - edit /etc/festival.scm to add that line -- Per Jessen, Zürich (13.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/4/19 1:36 AM, Per Jessen wrote:
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
Yes, thanks very much, that is what I did. It was then easy to get the .scm files from the tarball. And finally!! Festival works! You can;t imagine the satisfaction. The voice is still far from human, but it is an improvement over espeak. And with what I learned (a great deal) in the process, I will sometime in future test other voices.
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). Wow, sounds good, it will take me a bit to process and digest that. Thanks a lot, Gustav
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Gustav Degreef wrote:
On 10/4/19 1:36 AM, Per Jessen wrote:
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
Yes, thanks very much, that is what I did. It was then easy to get the .scm files from the tarball. And finally!! Festival works! You can't imagine the satisfaction.
Cool! Congrats!
The voice is still far from human, but it is an improvement over espeak. And with what I learned (a great deal) in the process, I will sometime in future test other voices.
Many years ago, in the 90s, my Creative AWE32 soundcard came with text-to-speech synthesis. AFAIR it worked fairly well. -- Per Jessen, Zürich (16.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/10/2019 18.35, Per Jessen wrote:
Gustav Degreef wrote:
On 10/4/19 1:36 AM, Per Jessen wrote:
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
Yes, thanks very much, that is what I did. It was then easy to get the .scm files from the tarball. And finally!! Festival works! You can't imagine the satisfaction.
Cool! Congrats!
The voice is still far from human, but it is an improvement over espeak. And with what I learned (a great deal) in the process, I will sometime in future test other voices.
Many years ago, in the 90s, my Creative AWE32 soundcard came with text-to-speech synthesis. AFAIR it worked fairly well.
It did, nicely. Linux sounds pretty awful. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 4 Oct 2019 10:47:46 -0400 Gustav Degreef <gustav97@gmail.com> wrote:
On 10/4/19 1:36 AM, Per Jessen wrote:
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
Yes, thanks very much, that is what I did. It was then easy to get the .scm files from the tarball. And finally!! Festival works! You can;t imagine the satisfaction. The voice is still far from human, but it is an improvement over espeak. And with what I learned (a great deal) in the process, I will sometime in future test other voices.
Hmm, perhaps you or somebody else can help me now. As part of investigating this issue, I installed festival and tried to use SayText "I say hello and you say goodbye" but got silence, with no error messages. I tried the same text in the demo at http://www.cstr.ed.ac.uk/projects/festival/onlinedemo.html but that resulted in silence too. Sound usually works. I can play youtube videos and recorded radio programmes etc. So I'm stuck as to why festival wouldn't be working.
To install it, the documentation says:
---------------------------- Installation itself is easy, just copy all the @file{*.scm} files to one of the directories present in the Festival's load-path. This is typically @file{/usr/share/festival/}, you can get the exact list of the directories by evaluating @code{load-path} in the Festival command line interface. Then you can load the whole system at Festival startup by adding the line
(require 'speech-dispatcher)
to the Festival initialization file (typically @file{/etc/festival.scm} system wide or @file{~/.festivalrc} for a particular user). Wow, sounds good, it will take me a bit to process and digest that. Thanks a lot, Gustav
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/4/19 2:48 PM, Dave Howorth wrote:
On Fri, 4 Oct 2019 10:47:46 -0400 Gustav Degreef <gustav97@gmail.com> wrote:
On 10/4/19 1:36 AM, Per Jessen wrote:
As Dave suggested, you can use "festival-freebsoft-utils" as it is. I would suggest you get it as a tarball from https://freebsoft.org/festival-freebsoft-utils
Yes, thanks very much, that is what I did. It was then easy to get the .scm files from the tarball. And finally!! Festival works! You can;t imagine the satisfaction. The voice is still far from human, but it is an improvement over espeak. And with what I learned (a great deal) in the process, I will sometime in future test other voices. Hmm, perhaps you or somebody else can help me now. As part of investigating this issue, I installed festival and tried to use
SayText "I say hello and you say goodbye"
but got silence, with no error messages. I tried the same text in the demo at http://www.cstr.ed.ac.uk/projects/festival/onlinedemo.html but that resulted in silence too.
Sound usually works. I can play youtube videos and recorded radio programmes etc. So I'm stuck as to why festival wouldn't be working. There are a number of possible issues. One of the most helpful things for me was to run the coand
spd-conf
which is the speech-dispatcher configuration utility. It will create a file speechd.conf in ~/.config/.speech-dispatcher/
It is an interactive script which will ask for your input, but it is very easy. The speechd.conf file contains your selections. If set up right, it speech-dispatcher will use it to select festival as the speech engine. Towards the end of the script it will ask if you want to run diagnostic tests. It will give interactive feedback on whether things are working correctly or not. Hope that helps, Gustav
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29/09/2019 21:40, Gustav Degreef wrote:
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
How archaic! And the server dies. if you don't know how to manually restart the server you have to restart the machine. BoHo! This is the sort of idiocy that systemd is there to address. Start the server when the system starts and restart the server if it dies ... unless there are specific instruction not to. Actually systemd offers a number of ways to do that.. Like everything else, its there in the manual pages, but the manual pages are often densely packed, so its useful to Google for examples and how-to. https://dev.to/setevoy/linux-systemd-unit-files-edit-restart-on-failure-and-... https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b9... Now we want this script to run at all times, be restarted in case of a failure (unexpected exit), and even survive server restarts. That’s where systemd comes into play. Well that "on-failure" option looks good; lets you do a legal shut-down without restart :-) of course you end up going back to the man pages to find all the options available that the how-to pages don't discuss. And you might need to experment a bit. But the reality is that as far as server management goes, systemd is a lot more capable, a lot more flexible, than using cron -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2019 15.36, Anton Aylward wrote:
On 29/09/2019 21:40, Gustav Degreef wrote:
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
How archaic!
And the server dies. if you don't know how to manually restart the server you have to restart the machine. BoHo!
I'm not sure that it is a systemwide service, it may a user service. Root in my machine can not always play sounds, it belongs to the user (pulseaudio). -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 30/09/2019 15.36, Anton Aylward wrote:
On 29/09/2019 21:40, Gustav Degreef wrote:
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
How archaic!
And the server dies. if you don't know how to manually restart the server you have to restart the machine. BoHo!
I'm not sure that it is a systemwide service, it may a user service. Root in my machine can not always play sounds, it belongs to the user (pulseaudio).
You're right, although Gustav did edit the main crontab, not a user crontab. As Anton says, a service unit would be a better option. -- Per Jessen, Zürich (18.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2019 16.03, Per Jessen wrote:
Carlos E. R. wrote:
On 30/09/2019 15.36, Anton Aylward wrote:
On 29/09/2019 21:40, Gustav Degreef wrote:
I am trying to use festival TTS. It needs to be run as a server. The instructions are to enter in a console " sudo crontab -e" command then to add
@restart /usr/bin/festival --server
How archaic!
And the server dies. if you don't know how to manually restart the server you have to restart the machine. BoHo!
I'm not sure that it is a systemwide service, it may a user service. Root in my machine can not always play sounds, it belongs to the user (pulseaudio).
You're right, although Gustav did edit the main crontab, not a user crontab.
Ah, yes, I missed the "sudo".
As Anton says, a service unit would be a better option.
Certainly. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 30/09/2019 10:16, Carlos E. R. wrote:
On 30/09/2019 16.03, Per Jessen wrote:
As Anton says, a service unit would be a better option.
Certainly.
And if necessary, the unit can specify the user/group the server is to be run as. And that's in a clean manner, not a sudo indirection kludge. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (14)
-
Anton Aylward -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
David C. Rankin -
David T-G -
ellanios82 -
Felix Miata -
Gustav Degreef -
James Knott -
jdd＠dodin.org -
Knurpht-openSUSE -
Patrick Shanahan -
Per Jessen