On Jun 17, 3:03 pm, Terry Brown [EMAIL PROTECTED] wrote:
On Tue, 17 Jun 2008 08:47:20 -0500
Terry Brown [EMAIL PROTECTED] wrote:
os.path is OS aware... but g.os_path_ may be the better option anyway,
saves importing os etc. Of course, I hope the active_path plugin will
be able to use
This discussion of g.os_path_x vs. os.path_x is off the mark.
The g.os_path_x wrappers exists for only one reason: to handle unicode
filenames properly. In all other respects g.os_path_x and os.path_x are
identical. Indeed, the g.os_path_x methods call the os.path methods.
Edward
Instead of using os.path directly, wouldn't it be better to use
g.os_path_?
It conditions the path and path seperators for cross platform
compatibility. Remeber us poor window$ users.
Bob
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On Tue, 17 Jun 2008 08:47:20 -0500
Terry Brown [EMAIL PROTECTED] wrote:
os.path is OS aware... but g.os_path_ may be the better option anyway,
saves importing os etc. Of course, I hope the active_path plugin will
be able to use leo's internal @path logic when it understands nesting.
Second
On Fri, Jun 13, 2008 at 8:38 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Why is the code very complex?
It's complex because there are lots of special cases. This is often the
case with code that looks simple. In this case, the special cases involve
issues such as the following:
- How to
On Fri, Jun 13, 2008 at 11:09 AM, Terry Brown [EMAIL PROTECTED]
wrote:
My active_path plugin is working quite well now. I'll commit it to
the trunk, it's only a plugin so it won't do anything unless you enable
it (active_path.py).
Very interesting. I'll add @thin active_path.py to
On Mon, Jun 16, 2008 at 10:04 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Fri, Jun 13, 2008 at 8:38 AM, Kent Tenney [EMAIL PROTECTED] wrote:
Why is the code very complex?
It's complex because there are lots of special cases. This is often the
case with code that looks simple. In this
On Fri, Jun 13, 2008 at 6:25 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 12:05 PM, Terry Brown [EMAIL PROTECTED]
wrote:
If filename is an absolute filename the location of the derived file is
specified only by the filename. Otherwise, if filename is a relative
My active_path plugin is working quite well now. I'll commit it to
the trunk, it's only a plugin so it won't do anything unless you enable
it (active_path.py).
You can dig down through directories by clicking on the status-iconbox,
also load or create files that way.
But, to create files it
On Tue, Jun 10, 2008 at 11:37 AM, Terry Brown [EMAIL PROTECTED] wrote:
On Sat, 7 Jun 2008 07:49:03 -0500
Kent Tenney [EMAIL PROTECTED] wrote:
On Thu, Jun 5, 2008 at 10:30 AM, Terry Brown
[EMAIL PROTECTED] wrote:
Does anyone use the at_folder plugin?
I don't, but I'm very interested
On Thu, Jun 5, 2008 at 10:30 AM, Terry Brown [EMAIL PROTECTED] wrote:
Does anyone use the at_folder plugin?
I don't, but I'm very interested in folder handling.
Do you create an empty node for each file in a folder?
Do you generate @path statements in the nodes generated?
I'm not sure what
11 matches
Mail list logo
