Help on print formatting please

2012-07-03 Thread F.S.
Hi, I have been using Leo 4.7 with Python 2.x for years mainly because my laptop was a bit too slow to handle the newer versions of Leo (but Leo 4.7 worked pretty well on it). Now I just bought a new laptop and decided to give the new Leo a try. I have now Leo 4.10 and the speed is very satisf

Re: Help on print formatting please

2012-07-03 Thread Terry Brown
On Mon, 2 Jul 2012 22:13:36 -0700 (PDT) "F.S." wrote: > Also in 4.7 the log pane used monospace fonts so one can print out a table > nicely using Python print formatting but in 4.10 the log pane seems to > default to a proportional font. You can copy the node `@data qt-gui-plugin-style-sheet`

Re: Help on print formatting please

2012-07-03 Thread Terry Brown
On Mon, 2 Jul 2012 22:13:36 -0700 (PDT) "F.S." wrote: > I seem to be getting line breaks inserted after each item in the print > statement: that is "print a, b, c" would insert line breaks after a and b I just fixed this on the trunk, it should appear at http://www.greygreen.org/leo/ tomorrow

Re: Help on print formatting please

2012-07-03 Thread F.S.
Thanks for the help. I installed the dejavu fonts, which didn't come with Windows 7. That solved the mono space fonts issue. The fonts look a bit peculiar on Windows, but I will either get used to it or find some other fixed width fonts, now that you showed me where the font settings are made.

Re: Help on print formatting please

2012-07-03 Thread F.S.
I downloaded the 20120703 snapshot from the website. Your fix didn't seem to make into it. I will try again tomorrow. In addition I noticed the following issues: For the newest release (Leo 4.11 devel, build 5416) whenever I attempt to move the cursor in the edit pane to the last few lines (400

Re: Help on print formatting please

2012-07-04 Thread F.S.
Snapshot 20120704 fixed the printing issuing. Thanks Terry! I will report more details on the scroll jumping issue in a new post. On Tuesday, July 3, 2012 11:11:40 AM UTC-7, F.S. wrote: > > I downloaded the 20120703 snapshot from the website. Your fix didn't seem > to make into it. I will try ag