I tried your example with my file and it hasn't worked. Could you tell me what am I doing wrong?

I add the following
cat README.txt | -w 250

and get this in bash and zsh
-w: command not found

Would it be possible to add a flag so no information is printed with the current word? For example, by default, it shows something like:

 netctl 250 wpm

With the minimal view, however, it would only show:

 netctl

Thanks :)

Now and then the program will print errors.

For example:

Use of the encoding pragma is deprecated at speedread-original/speedread line 39.

and

99918 wpmBytes implicitly upgraded into wide characters as iso-8859-1 at speedread-original/speedread line 194.

This is fixed by some minimal changes as proposed in this pull-request: #21

I have a lot of reading in Persian to do. The files are available as txt, but speedread seems to have some hiccups with Arabic alphabets.

Well, actually it's somewhat working out of the box, only that the current reading speed and the word to read change positions for some reason. Can someone point me into the right direction for fixing this?

A few things that came to mind when using this:

• Possibility to increase font size. I know that increasing my terminal font size would do the trick, but I'd like to keep my terminal configuration intact, but would like to increase just the speed reader text font size a bit to make it easier on the eyes.
• Possibility to configure how many words to show. I find it a bit difficult to keep up with the context, when only one word is showing, and found out a few other speed readers where one could set the amount of words to show at the same time. Three words seemed like a good amount at least for me.

Thanks for your time on the project! Keep up the good work.

When installed on MacOS Mojave 10.14.6 I get this:

The encoding pragma is no longer supported. Check cperl at /usr/local/bin/speedread line 39.
BEGIN failed--compilation aborted at /usr/local/bin/speedread line 39.

Installed via homebrew using https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/speedread.rb

'Bytes implicitly upgraded into wide characters as iso-8859-1 at ./speedread line 179' keep popping up whilst reading. Could it be that some German characters trigger this?

Hi,

I'm getting the following error trying to run the example:

Can't locate Term/Screen.pm in @INC (you may need to install the Term::Screen module) (@INC contains: /usr/lib/perl5/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/core_perl /usr/share/perl5/core_perl .) at /home/krypt0n/bin/speedread line 36.
BEGIN failed--compilation aborted at /home/krypt0n/bin/speedread line 36.

Well, probably I need http://search.cpan.org/~jstowe/Term-Screen-1.03/Screen.pm, anything else?
Would be nice if you could add a full list of all dependencies in the README.

echo "Möööööööööö" > t
speedread t

will yield:

Möööööööööö

echo "Möööööööööö" | speedread

does work though.

Often when paused, the highlit word is at the begining of physical line and you can't read the text prior to it to see a missed word.

Ideally (for me), pausing would place the highlit word at the end of the last line and fill the terminal right up with prior text or center the highlit word and fill in the terminal to and from it.

TL;DR Paused context is myopic!

Greetings!

Using the tea.txt example, I'm occasionally getting this error:

Bytes implicitly upgraded into wide characters as iso-8859-1 at /home/rtucker/bin/speedread line 172

I'm using xfce4-terminal on Linux Mint 16, and en_US.UTF-8 is my language. This is with revision fc18f1b.

Thanks!

(master) rtucker@racer-x:~/dev/speedread$ speedread tea.txt 
                    v
                  golden:                                       332 wpmBytes implicitly upgraded into wide characters as iso-8859-1 at /home/rtucker/bin/speedread line 172
                   has                                          332 wpmBytes implicitly upgraded into wide characters as iso-8859-1 at /home/rtucker/bin/speedread line 172
                   and                                          332 wpmBytes implicitly upgraded into wide characters as iso-8859-1 at /home/rtucker/bin/speedread line 172
                   tea.                                         332 wpmBytes implicitly upgraded into wide characters as iso-8859-1 at /home/rtucker/bin/speedread line 172
                   small                                        332 wpm
 49.71s, 230 words, 1006 letters, 277.61 true wpm

I created a Formula for home-brew but home-brew maintainers want to have a tagged commit to point to for the download. Therefore I would really like to see a tag so the Formula can be pushed upstream.

Hello,

When I try and run your script under Strawberry Perl, I get undefined value errors on $ch, $self and ver.

They seem to loop over and over, giving endless errors.

Any ideas?

I'd like to make use of this in a (free, open-source) project; would you mind putting it under a license?

Thanks!

P.S. My vote is for Apache 2.0, fwiw. :)

For example, if I start the program using cat tea.txt | ./speedread, and then press the right arrow key twice, it will go from 250 to 225 WPM. Repeatedly pressing this key decreased the speed further. The \ key does nothing on it's own, but pressing an arrow key and then \, makes it decrease in speed once.

It would be pretty useful to have a help command to list the controls, and arguments.

An elinks-based recipe for reading websites this way.

I am trying to figure out how to use
speedread with espeak. I think I have to

cat book.txt | ./speedread -w 230 | espeak

Works, but I cannot see the text words going by. I can
only hear espeak - speaking the book

Hello,

I use Fedora 18 (tried it both with xterm and lilyterm). Instead of flashing the text on a single line like in your demo, the text scrolls from the bottom to the top. I tried it in Ubuntu 12.04 and it worked OK.

Is there a way to fix this?

Long time ago I used a fast reading app which had a feature I never seen again in other apps but it was the most useful one.

Basically it "removed" the words before to show the next one, this means that the words "flashes" (show word1, unshow it, show word2, unshow it...) instead of showing them linearly one after the other, this increases the visibility of the chars for the brain by really-knowing what chars are drawn, instead of retaining the previous pixels in your memory