On Thu, Dec 4, 2014 at 11:12 AM, Davy Cottet cottet.d...@gmail.com wrote:
For my experimental version of leoDist.leo, I use abspath(c.fileName) to
get the path of the opened outline, in this case /path/of/leo/dist
I don't know why this weird example has problem, but you should use::
On Thu, 4 Dec 2014 09:12:55 -0800 (PST)
Davy Cottet cottet.d...@gmail.com wrote:
Hi,
For my experimental version of leoDist.leo, I use abspath(c.fileName)
to get the path of the opened outline, in this case /path/of/leo/dist
I've noticed a strange behaviour, that unfortunately implies bugs.
On Thu, 4 Dec 2014 11:35:38 -0600
'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote:
On Thu, 4 Dec 2014 09:12:55 -0800 (PST)
Davy Cottet cottet.d...@gmail.com wrote:
Hi,
For my experimental version of leoDist.leo, I use
abspath(c.fileName) to get the path of the opened
On Thu, Dec 4, 2014 at 11:35 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Unless I'm missing something, that's what @path nodes are supposed to
do. If you created a @edit file.txt under the @path node, the text
directory would be created for saving file.txt in.
Thank Edward, again you solve my problem :
So instead of g.os_path_abspath(c.fileName) that I was wrongly using since
it kind of worked I have to use : g.os_path_dirname(c.fileName*()*)
I fact, I didn't understand what was this strange *c.fileName *comander
followed by a string that
