it's a no brainer that you can catch most type errors with static
type checking. assuming people won't actively try and circumvent
the checks like you sometimes must with casts in the c languages.
no surprise that it's much easier to create tools in a static
type checked language when you nearly a
On Tue, 29 May 2012 18:38:34 -0500
"Edward K. Ream" wrote:
> It seems to appear more often with Python 3k, though I believe I have
> seen this problem with Python 2k.
I can see the problem in 3k and not 2k. I use 2k, so I wouldn't have
seen it until you pointed it out.
I wanted to check it exi
On Tue, May 29, 2012 at 6:53 PM, Terry Brown wrote:
> What was the problem / fix last time?
Actually, it could have been mostly the clipping problem.
However, the fix that I thought worked well was to use slower, more
general code in leoQTextEditWidget.setSelectionRangeHelper &
lengthHelper.
O
On Tue, 29 May 2012 18:46:20 -0500
"Edward K. Ream" wrote:
> > At no time, afaik, does Leo ever mess with any clipping region.
> > Although I suppose a plugin could be doing something "fancy"...
>
> There are no calls to clipWhatever except clipboard in Leo.
What was the problem / fix last ti
On Tue, May 29, 2012 at 6:32 PM, Edward K. Ream wrote:
> At no time, afaik, does Leo ever mess with any clipping region.
> Although I suppose a plugin could be doing something "fancy"...
There are no calls to clipWhatever except clipboard in Leo.
EKR
--
You received this message because you a
On Tue, May 29, 2012 at 6:32 PM, Edward K. Ream wrote:
> Ok. I see what the problem is. There is a Qt drawing bug here.
It seems to appear more often with Python 3k, though I believe I have
seen this problem with Python 2k.
It is now clear why the find command "discloses" this bug more often
On Tue, May 29, 2012 at 4:48 PM, Terry Brown wrote:
> Check the pylint edits didn't break the previous fix for this bug?
Ok. I see what the problem is. There is a Qt drawing bug here.
The bug "appears" if the found line is the last line of the *visible*
area. Now, if I scroll using the scrol
On Tue, 29 May 2012 16:40:10 -0500
"Edward K. Ream" wrote:
> Iirc, there was a bug that caused similar problems that was supposedly
> fixed. Again, iirc, it had to do with the qt cursor. It looks like
> something similar is happening again.
Check the pylint edits didn't break the previous fix
On Tue, May 29, 2012 at 1:08 PM, Terry Brown wrote:
> On Tue, 29 May 2012 12:50:38 -0500
> "Edward K. Ream" wrote:
>
>> Indeed, here is the context of the definition at line 306:
>>
>> for provider in splitter.root.providers:
>> if hasattr(provider, 'ns_provides'):
>>
On Tue, 29 May 2012 12:50:38 -0500
"Edward K. Ream" wrote:
> Indeed, here is the context of the definition at line 306:
>
> for provider in splitter.root.providers:
> if hasattr(provider, 'ns_provides'):
> for title, id_ in provider.ns_provides():
>
On Tue, May 29, 2012 at 12:40 PM, Edward K. Ream wrote:
> On Tue, May 29, 2012 at 11:29 AM, Terry Brown wrote:
>
> Next, I'll remove the pylint warnings, and all should be right.
This warning appears valid.
E0102:313:NestedSplitterHandle.splitter_menu.cb:
function already defined line 306
On Tue, May 29, 2012 at 11:29 AM, Terry Brown wrote:
> so nested_splitter.py wasn't changed by anything you did
That's what I expected. I "resolved" the conflict by taking your version.
Next, I'll remove the pylint warnings, and all should be right.
EKR
--
You received this message because
On Tue, 29 May 2012 10:52:50 -0500
"Edward K. Ream" wrote:
> Our nested_splitter changes clashed because I added a pylint: disable
> comment. I attempted to use your version, and it looks like I
> succeeded, because now pylint complains again.
>
> Please verify that all your changes remain inta
Under the File menu item I see 'Open With ... >' and then a selection for
IDLE
But when I select this, I do not understand what should happen I have a
node highlighted for a .py file, which I assumed would then open in a
IDLE window, but I only see a message in the log window that a LeoTemp
On Tue, May 29, 2012 at 10:52 AM, Edward K. Ream wrote:
> On Tue, May 29, 2012 at 9:32 AM, Terry Brown wrote:
> Please verify that all your changes remain intact.
Yech. Rev 5370 restores a change to leoProjects.txt. Please pull
that before verifying.
EKR
--
You received this message becaus
On Tue, May 29, 2012 at 9:32 AM, Terry Brown wrote:
> Anyway, previously you had to open a window and then pick what you
> wanted in it, now you can pick what the window should have in it from
> the open window submenu, once less menu interaction and much smoother.
Excellent. I've been meaning
Hi,
This is what I do (but with Fossil) when I write documentation on Leo
and also with the Leo trees. This happen after seeing that @auto trees
with @rst-ignore inside destroyed the meta-date contained in @rst-ignore
nodes. I would like that any @auto directive who contains @rst-ignore
nodes
The carefully concealed :-} context menu on the panel splitter handles
has an entry for opening new top level windows to contain parts of the
Leo interface. These top-level windows are themselves subdivideable
using splitters. I thought I'd announced this, although I can't find
the announcement.
Note: this post is essentially notes to myself. Feel free to ignore
it.
The spectrum of Python scripts runs from the utterly straightforward
to the truly complex.
A few days ago, as part of the ongoing revision of docstrings, I wrote
the following script. It prints a report, grouped by class na
On Tue, May 29, 2012 at 6:47 AM, Edward K. Ream wrote:
> It may take days, weeks or months of experimentation before I
> can discover exactly what makes each program tick.
Otoh, the experimentation will yield immediate results.
A new module, say leoTools.py, will probably contain support classe
On Tue, May 29, 2012 at 8:00 PM, Edward K. Ream wrote:
>
>Create a bzr repository for the code before importing it
>
>
Yep, I do this in a git repository.
--
Sincerely,
HaveF
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this
When I study a program, I like to import it into Leo. I have several
scripts that do this: some create @auto nodes; others create @file
nodes.
Either way, the import process has the potential to change many
files. Usually, I just change @auto and @file to @@auto or @@file, so
that any changes I
The last several days have produced some unexpected Ahas, and have
yielded a plan for a major new project. This project is something
I've always wanted to do, and it will benefit Leo.
= Motivation
The genesis of the plan lies in the observation that type inference
keeps cropping up in unexpe
I ran across the following comment while studying coverage.py::
# pylint: disable-msg=W0622
Eureka! At last I had found the way to disable pylint messages inside
source files. This is documented, but it takes some doing to find it,
even if you know what you are looking for. In fact, "disabl
24 matches
Mail list logo
