On Thu, Dec 4, 2014 at 11:05 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
>
> But the "valuespace" command is rendering the result of the last
> executed code block using pprint.pprint, which includes the values and
> handles indentation and alignment.
>
Time to look at
On Thu, 4 Dec 2014 11:02:51 -0600
"Edward K. Ream" wrote:
> On Sat, Nov 29, 2014 at 1:11 AM, Matt Wilkie wrote:
>
> >
> >
> > Now how did you get that nicely formatted `c.db.keys()` in the first
> > section? I had to wrap it in `g.es(c.db.keys())`, and then it
> > prints all in one line.
> >
>
On Sat, Nov 29, 2014 at 1:11 AM, Matt Wilkie wrote:
>
>
> Now how did you get that nicely formatted `c.db.keys()` in the first
> section? I had to wrap it in `g.es(c.db.keys())`, and then it prints all
> in one line.
>
You don't need valuespace for this. For any dict d, the idiom is::
prin
On Fri, 28 Nov 2014 23:11:15 -0800
Matt Wilkie wrote:
> > for k in c.db.keys():
> > if k.split('/')[0] in (
> > "window_position_fcache",
> > "body_secondary_ratio_fcache",
> > "body_outline_ratio_fcache",
> > "current_position_fcache",
> > ):
> > d
> for k in c.db.keys():
> if k.split('/')[0] in (
> "window_position_fcache",
> "body_secondary_ratio_fcache",
> "body_outline_ratio_fcache",
> "current_position_fcache",
> ):
> del c.db[k]
>
Thanks Terry! That cured my problem and introduced me to
On Wed, 26 Nov 2014 22:38:43 -0800
Matt Wilkie wrote:
> ...Later: The pattern seems to be that any file I open from the
> command line, opens off-screen, while starting Leo with no params and
> then opening with File menu is ok. Weird.
>
> No, that's not it. It gets even weirder. Opens off-scree
Good evening gents,
I had a bit of a problem with Leo this evening, though I don't know if the
source was Leo, my laptop, or something else.
I use Dropbox to keep my project environment in sync across the 3 machines
I use most often (all Windows). %HOME% is set to C:\Users\{me}\Drobox,
mapped as
