On Thu, Oct 29, 2009 at 5:04 PM, Terry Brown wrote:
>
> On Thu, 29 Oct 2009 16:58:32 -0500
> Kent Tenney wrote:
>
>> Is there compelling advantage to using a pickle?
>
> They keep better... sorry, long day.
:-]
>
> Um, leo's doing the pickling, not me.
Ah, right, been down this road before.
Ville M. Vainio wrote, On 10/29/2009 4:12 PM:
> For pedagogical purposes (no real need to change your code):
>
> [~]|3> s = "@auto foo.txt"
> [~]|4> s2 = s.split(None,1)
> [~]|5> s2
><5> ['@auto', 'foo.txt']
> [~]|7> os.path.splitext(s2[1])
><7> ('foo', '.txt')
>
No trouble, I might as
On Thu, 29 Oct 2009 16:58:32 -0500
Kent Tenney wrote:
> Is there compelling advantage to using a pickle?
They keep better... sorry, long day.
Um, leo's doing the pickling, not me. I think there is / was some
convention whereby v.u key/values where the keu started with 'str_' or
something wasn
Very cool, though I would prefer the data was plain text in
myfile.leo, making it more
useful to other consumers. Is there compelling advantage to using a pickle?
On Thu, Oct 29, 2009 at 12:44 PM, Terry Brown wrote:
> Attached screen shot shows the attrib_edit.py plugin I just pushed.
>
> Here's
Ville M. Vainio wrote, On 10/29/2009 3:51 PM:
> Are you using a recent bzr version?
Sorry, I was actually using 2.0.0. That 0.8.3 was the version of the bzr
explorer gui. I updated to 2.0.1.
Forgot to mention I got a similar error the first time I tried to push,
but then it worked the second
On Thu, Oct 29, 2009 at 11:04 PM, Rob Sheppard wrote:
>> since cursor.h in not the file name proper but the whole string (e.g.
>> "@thin foo.txt"), but splitext doesn't really care about it so it'll
>> work.
>
> Yeah, I thought that might be considered sloppy. I tried doing
> cursor.h.split() t
Ville M. Vainio wrote, On 10/29/2009 3:51 PM:
> You should "propose the branch for merging" so the review can be done
> on launchpad.
>
> You should also fix your bzr username and email address, so your work
> will be credited properly in change history.
Okay, will do.
> Since this branch is no
On Thu, Oct 29, 2009 at 10:32 PM, Rob Sheppard wrote:
> I've been keeping my eye out for a simple mod/fix that I might be able
> to contribute, and I thought this would be a good exercise for me.
Great that you are getting geared up for this :-).
You should "propose the branch for merging" so
Edward K. Ream wrote, On 10/29/2009 7:00 AM:
> The obvious heuristic would be to look up the tree for any @ node,
> and use extension in that node.
I've been keeping my eye out for a simple mod/fix that I might be able
to contribute, and I thought this would be a good exercise for me.
I made t
On Thu, Oct 29, 2009 at 5:26 PM, TL wrote:
>> I don't think that's too useful either. My idea would be to move the
>> widget to the body pane eventually (from separate "stickynote" window)
>> and hide the html.
>
> Can you clarify what you mean by "hide the html" . Microsoft's Rich-
> Text file
> I don't think that's too useful either. My idea would be to move the
> widget to the body pane eventually (from separate "stickynote" window)
> and hide the html.
Can you clarify what you mean by "hide the html" . Microsoft's Rich-
Text file format is not html.
TL
--~--~-~--~~
On Thu, Oct 29, 2009 at 2:12 PM, TL wrote:
>> May I assume that the interest in the feature waned when the
>> prototype is ready? Never fails... ;-).
>
> I don't understand why someone who is interested in creating/viewing/
> writing Rich-Text in Leo wants to see HTML code in the node's body
> p
> Are you sure, if the @language is not supported? Perhaps this is a
> bug with c.openWith.
The mod_tempfname.py plugin also exists which overrides the openWith
plugin's code for generating the temporary file's directory and file
extension.
TL
--~--~-~--~~~---~--~
> May I assume that the interest in the feature waned
Not at all -- I think having rich text capability is very helpful. For my
uses, a body pane that contained rst with a toolbar and/or keyboard
shortcuts for common formatting and that was transformed to html and
displayed as rendered text would
> May I assume that the interest in the feature waned when the
> prototype is ready? Never fails... ;-).
I don't understand why someone who is interested in creating/viewing/
writing Rich-Text in Leo wants to see HTML code in the node's body
pane.
I want the node's body pane to show Rich-Text a
On Wed, Oct 28, 2009 at 3:23 PM, Ville M. Vainio wrote:
>
> On Wed, Oct 28, 2009 at 10:14 PM, Edward K. Ream
> wrote:
>
> >> Are you sure, if the @language is not supported.
> >
> > I'm sure that @thin x.y never changes y.
>
> Of course. But when you try to edit the subnodes by right clicking an
16 matches
Mail list logo
