File->Export->write failed due to incorrect path

Bug #377907 reported by bpursley
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
leo-editor
Invalid
Medium
Edward K. Ream

Bug Description

My .leo file was saved to location /pa/xxx.leo in a linux environment using
leo-editor revision 1853.

I then proceeded to export the node to HTML.

In both
File->Export->Save Outline as HTML
File->Export->Save Node as HTML
the write failed due to each export function
inserting an incorrect path.

The correct path should have been: /pa/xxx.html

The path appearing in the log was /pa/c:/xxx.html

Revision history for this message
Edward K. Ream (edreamleo) wrote : Re: [Bug 377907] [NEW] File->Export->write failed due to incorrect path

On Mon, May 18, 2009 at 6:01 AM, bpursley <email address hidden> wrote:

> Public bug reported:
>
> My .leo file was saved to location /pa/xxx.leo in a linux environment using
> leo-editor revision 1853.
>
> I then proceeded to export the node to HTML.
>
> In both
> File->Export->Save Outline as HTML
> File->Export->Save Node as HTML
> the write failed due to each export function
> inserting an incorrect path.
>
> The correct path should have been: /pa/xxx.html
>
> The path appearing in the log was /pa/c:/xxx.html

Thanks for this report. Am I correct in assuming you are using a Windows
machine?

Edward

Changed in leo-editor:
assignee: nobody → Edward K. Ream (edreamleo)
importance: Undecided → High
Revision history for this message
bpursley (bernie-bpursley) wrote :

On Mon, May 18, 2009 at 10:19 AM, bpursley <email address hidden> responded by return email:

No. I am using native Ubuntu Jaunty (9.04). I do not have windows on this machine – nor have I for over two years:

> My .leo file was saved to location /pa/xxx.leo in a linux environment
> using leo-editor revision 1853.

If it helps in your trouble-shooting:

I do not use the default location for either storing or installing Leo. As I consider Leo part of my development environment, all of my Leo & Sphinx development is in its own Virtualenv .

Virtualenv allows me to leave Ubuntu in an undisturbed state and I am free to create as many unique development environments as I wish. I have a Leo launcher which executes the following .sh script:

cd /pa
 . /pa/ENV/bin/activate
python /pa/leo-bzr/leo-editor/launchLeo.py --gui=qt --ipython

The above script utilizes my python code from /pa/ENV/lib/python2.6/ to launch Leo which is kept fairly current using bzr pull. Though I know it is not necessary, I have on occasion installed Leo to /pa/ENV for some activities rather than your default location of /usr/local. However, the above error occurred in the launched leo-editor. Most of my current .leo files are located in the /pa directory.

Hope this helps. Thank you for your attention to this problem.

Bernie Pursley
Simsbury, CT

Revision history for this message
Edward K. Ream (edreamleo) wrote :

I'm going to mark this invalid, although the behavior of the plugin is way too confusing.

I added the following to the plugin's docstring:

QQQ
Configuration
~~~~~~~~~~~~~

At present, the file leo/plugins/leo_to_html.ini contains configuration settings.
In particular, the default export path, "c:\" must be changed for *nix systems.
QQQ

Furthermore, the plugin should use settings in leoSettings.leo rather than a wretched .ini file. I'm not going to fix this now, but it would be good if the plugin's author would make the conversion.

Edward

Changed in leo-editor:
importance: High → Medium
status: New → Invalid
Revision history for this message
zpcspm (zpcspm) wrote :

I've just bumped into this bug too.

Changed in leo-editor:
importance: Medium → Wishlist
status: Invalid → Confirmed
Changed in leo-editor:
importance: Wishlist → Medium
Revision history for this message
Edward K. Ream (edreamleo) wrote :

This bug is invalid. However, a minor wishlist bug has been filed:

https://bugs.launchpad.net/leo-editor/+bug/670421

Changed in leo-editor:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.