viewing long pages, evince seems to choke on simple test file

Mon Sep 9 16:07:37 CEST 2019

On Sun, Sep 08, 2019 at 08:53:12AM +0000, Mike Marchywka wrote:
> On Sun, Sep 08, 2019 at 09:08:23AM +0100, David Carlisle wrote:
> >    You don't really need to look in the dvi, (la)tex will warn you already in the log about what is happening.
[...]
> Thanks, I guess commented out the wrong one, 
> 
> \usepackage[paperheight=80in,height=78in]{geometry}
> %\usepackage[paperheight=80in,height=120in]{geometry}
> 
> that and ignoring the output warnings... 
> That seems to fix it now. No idea how that happened although there are so
> many warnings typically I don't bother reading them any more  :)
> 

I guess there is some upper limit to page size though. I did not investigate
right now but thought someone may now offhand why this is needed.
400in does not seem excessive in terms of normal ranges although certainly
it is an uncommon sheet size. 
Thanks. 
grep geom dummailtemp.tex | grep -v "%"
\usepackage[paperwidth=6in,width=5in,paperheight=400in,height=398in]{geometry}
marchywka at happy:/home/documents/cpp/proj/mikemail$ pdflatex --output-format=dvi dummailtemp.tex 
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) (preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./dummailtemp.tex
LaTeX2e <2016/02/01>
Babel <3.9q> and hyphenation patterns for 12 language(s) loaded.
(./mikemail.tex) (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
! Dimension too large.
<to be read again> 
                   \relax 
l.994 \ProcessOptionsKV[p]{Gm}
                              %
? q

fwiw, I attached some screen shots of the play code so far. It is kind of
like a low-tech collapsible table of contents but I'm curious to
see what I can do with it or what already exists like this.
Each block defined in the latex source can either be displayed
normally or collapsed as a one word name inside a box. 
There are two documents, the email literature update I hacked up
which consists of a set of about 18 abstracts and pub info and then
a second document which is a collection of notes I hope to turn into
a paper. I don't know if anyone would compose a scientific work out of
post-it notes and tweets but in essence collapsing by paragraph
lets you view it that way. I kind of like it so far but it may just
be the novelty. The view is changed by either a mouse click or a command
line entry that can accept a stem  ( at some point a regex maybe )
and change visibility of all matching blocks.  
I can already envision some useful mouse click commands ( although
that may be all I do as I still can't even figure out how
to inject events into queue to update screen without dummy mouseover lol).

With this granularity of collapsibility, it makes citing and note
taking easier as I think Doug suggested in legal docs paragraph
numbers are helpful.I can collapse most of the clutter except for
what I want to use and then just copy normally with mouse in one
operation or from command line utility, "copy visible paragrphs to clipboard."

I guess one thing that may be nice is to include bibtex when copying
to clipboard. In my own docs I include "suggested bibtex" in human
readable form but if the clipboard knew about that it would make
it easier to cite ( maybe there is some latex gui or ide that
does stuff like that ). 

Thanks
-- 

mike marchywka
306 charles cox
canton GA 30115
USA, Earth 
marchywka at hotmail.com
404-788-1216
ORCID: 0000-0001-9237-455X
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-08-161651_1015x594_scrot.png
Type: image/png
Size: 63598 bytes
Desc: 2019-09-08-161651_1015x594_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-08-161710_1015x594_scrot.png
Type: image/png
Size: 51227 bytes
Desc: 2019-09-08-161710_1015x594_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-08-161732_1015x594_scrot.png
Type: image/png
Size: 41812 bytes
Desc: 2019-09-08-161732_1015x594_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-09-065832_1028x553_scrot.png
Type: image/png
Size: 34571 bytes
Desc: 2019-09-09-065832_1028x553_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-09-070446_1028x553_scrot.png
Type: image/png
Size: 65157 bytes
Desc: 2019-09-09-070446_1028x553_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-09-070713_1028x566_scrot.png
Type: image/png
Size: 46303 bytes
Desc: 2019-09-09-070713_1028x566_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-09-09-071809_1028x566_scrot.png
Type: image/png
Size: 27555 bytes
Desc: 2019-09-09-071809_1028x566_scrot.png
URL: <https://tug.org/pipermail/texhax/attachments/20190909/eb8defa9/attachment-0013.png>