<https://lh3.googleusercontent.com/-VCwhCDXTSxU/Uo4SfdtLg0I/AAAAAAAAACA/xfBBgEcMnZM/s1600/chrons.png> Thank you both for the clarification. I've written my post just after reading the tutorial 'Programming with Leo'. The screenshot above illustrates my usecase. I have a simple Leo file called 'Chronos'. In it, I have defined a path to folder in which I want to create a new Python package. The package contains the required __init__.py, a Python module (pycalcal.py), and the file I'm working on (calendar.py). Now, if I highlight calendar.py and press Ctrl-B to execute it, I_m getting an error message 'No module named __init__).
That's because Ctrl-B doesn't honor the context that is established by the @path directive. If I change to this folder and execute the script manually (using 'python calendar.py'), everything works fine. A Run-Command in an Python IDE (like i.e. PyCharm) changes the context automatically. And I just can keep my concentration on my files and don't have to care about the 'plumbing' (setting up the infrastructure, using the right excecute commands, whatever), because all the required information is already is contained in the @path directive (that is: before execution, change the directory, execute the script, return to the original directory; do whatever is required to reestablish the Leo context). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
