I love Weavr, and use it extensively. However, in Ubuntu 14.04, if you have fully working texlive installation, you can also "roll your own" so to speak by using a script. Mine, which I called "glatex.sh", looks like this:
wget -O $2.tex "https://docs.google.com/document/export?format=txt&id=$1";
latexmk -pdf -f -interaction=nonstopmode $2.tex;
The bom-romove script is set out in this post bom_remover It is necessary because gdocs downloads with a "bom" included, which LaTeX will choke on.
Make both bom-remove script and glatex script executable (chmod +), and then either put them both in /usr/local/bin or put an alias to each there.
To use: a) Make a google doc, share it as a link and copy the link id
b)on the command line, type your script's name, the link id, and a name for your local file, then Enter
This will then download the google doc, name it and compile it as tex file, produce a like named pdf file and then pop up evince with the pdf loaded. To refresh when the google doc is changed run the script again.
Credit for the idea goes to Using GoogleDocs as Team editor for Latex-files
For those who might want to use a "beeline reader" effect, I adapted @phg's solution which is in LuaLaTeX. To do this I made 4 bash script files, two for black/red/blue beeline, and 2 for just black.
The reason for the black script files is that the header cannot be in the LuaLaTeX file containing the text, your header has to be set out in a separate document that calls "beegradients.tex" which I wrote into the bash script files texscript.sh (black) and color-texscript.sh (red/black/blue). These have to be used with glatex-beeline.sh and color-glatex-beeline.sh in order to work. If I didn't make a black color version of the files, I would have to cut and paste the header from color-texscript.sh to my document in order to allow it to compile. It seemed easier to just make a "beelines" version in black instead.
Please note that for some reason I had to make links to beegradients.lua and beegradients.tex and those links had to be present in my compilation directory.
To create "beelines" pdf's make sure all the *.sh files are in a system wide directory, (eg, /usr/local/bin), fire up your terminal type
color-glatex-beeline.sh <google doc id> <any-filename-you-want> (for red/black/blue text)
and it will produce a *.tex and a *.pdf and then pop up the pdf in evince pdf viewer.
For the black version of the same document do the same thing using glatex-beeline.sh
I have only tested this on Linux.
The scripts are set up expecting a file named "abbrev.tex" containing "abbrevs" package abbreviations. The
corrects for a bug that mis-spaces commas after abbreviations. LuaLaTeX complains about this, but I don't know what to do about that.