Odd behavior opening files using v4.10b1

[Largo84]

I'm experimenting with the latest version (WinXP). This is really odd. If I launch Leo using the desktop shortcut, I'm not able to open *any* valid .leo file except  LeoSettings.leo. This is the shortcut:
C:\Python32\pythonw.exe "C:\Program Files\Leo-4.10-b1\launchLeo.py"

However, if I launch using my Windows batch file, I'm able to open all files as expected. The code is:
C:\Python32\python "C:\Program Files\Leo-4.10-b1\launchLeo.py" %*

Anyone else experiencing this? Any possible explanation?

Rob............

[Edward K. Ream]

On Thu, Mar 22, 2012 at 7:59 PM, Largo84 <Lar...@gmail.com> wrote:
> I'm experimenting with the latest version (WinXP). This is really odd. If I
> launch Leo using the desktop shortcut, I'm not able to open *any* valid .leo
> file except  LeoSettings.leo. This is the shortcut:

Are you doing this in a console window? If so, what gets printed to
the console?

Edward

[Largo84]

No, that's why I used the batch file so I can launch w/ a console. When I do, it works fine.

Rob............

[Largo84]

I just installed on another box w/ Python 2.6.2
That works fine. The other box has Python 3.2, not sure why that matters, but it might be a clue.

Rob...............

[Edward K. Ream]

On Fri, Mar 23, 2012 at 9:15 AM, Largo84 <Lar...@gmail.com> wrote:
> I just installed on another box w/ Python 2.6.2
> That works fine. The other box has Python 3.2, not sure why that matters,
> but it might be a clue.

Thanks for the update. This is the kind of issue that turns up as the
distro process starts. I'll investigate thoroughly before the next
release.

Edward

[Edward K. Ream]

There are two differences between the two ways of launching.

1. pythonw.exe vs python.exe

2. The former has no "%*" argument. It's possible that you have no
workbook.leo file in your home directory, which might cause a failure,
iirc.

I suggest first changing pythonw to python. This will open a console,
but probably too briefly to read. To fix this, add a -i argument,
which will drop python into interactive mode, which has the side
effect of leaving the console open. This should tell you why exactly
nothing happens.

I suspect that adding the "%*" argument will fix the problem,
regardless of whether you use pythonw or python.

If not, please feel free to ask more questions.

Edward

[Largo84]

Yes, I changed pythonw to python (but did not add the %* argument). It seems to work fine now and the console stays open as long as Leo is running. Also, correct, I do not have a workbook.leo file in that directory.

Just curious, what does that argument do?

Rob......................

[Edward K. Ream]

On Wed, Mar 28, 2012 at 4:30 PM, Largo84 <Lar...@gmail.com> wrote:
> Yes, I changed pythonw to python (but did not add the %* argument).

> Just curious, what does that argument do?

It passes all the command-line arguments on to the program being run.

Edward