Saw the mistake I was making. Everything works well. Thanks.
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to
On Fri, May 22, 2015 at 3:23 PM, sbalt...@datatoolsinc.com wrote:
Hi,
Yes, I've never used Leo before on the new machine.
Good to know.
I tried loading some of the smaller files and they have worked
appropriately, but there is a fairly large one that hasn't. I will prune it
- should
Hi,
Yes, I've never used Leo before on the new machine.
I will try to run Leo from the command prompt this weekend.
I've been using Leo for a long time, so I have many files with all sorts of
directives, things I've tested over the years, etc.
I tried loading some of the smaller files and
On Thu, May 21, 2015 at 11:08 AM, sbalt...@datatoolsinc.com wrote:
I've been using LEO for quite some time. I got a new computer and decided
to update to LEO 5.1. The program opens to CheatSheet.leo. But I can't open
any of my old files. I click Open, see the files (I've moved them into the
On Fri, 22 May 2015 05:49:07 -0500
Edward K. Ream edream...@gmail.com wrote:
On Thu, May 21, 2015 at 11:08 AM, sbalt...@datatoolsinc.com wrote:
I've been using LEO for quite some time. I got a new computer and
decided to update to LEO 5.1. The program opens to CheatSheet.leo.
But I can't
The first thing to try is to run Leo from the command prompt. Diagnostic
information is often written to the shell.
Chris
On Thursday, May 21, 2015 at 3:34:24 PM UTC-7, sbal...@datatoolsinc.com
wrote:
Hi,
Though I'm not a Python programmer, I've been using LEO for quite some
time. I got
Hi,
Though I'm not a Python programmer, I've been using LEO for quite some
time. I got a new computer and decided to update to LEO 5.1. The program
opens to CheatSheet.leo. But I can't open any of my old files. I click
Open, see the files (I've moved them into the same directory as
On Mar 22, 7:59 pm, Largo84 larg...@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:
C:\Python32\pythonw.exe C:\Program
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..
On Wed, Mar 28, 2012 at 4:30 PM, Largo84 larg...@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
--
You received this message because
No, that's why I used the batch file so I can launch w/ a console. When I
do, it works fine.
Rob
On Thursday, March 22, 2012 10:43:14 PM UTC-4, Edward K. Ream wrote:
On Thu, Mar 22, 2012 at 7:59 PM, Largo84 larg...@gmail.com wrote:
I'm experimenting with the latest version
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...
On Friday, March 23, 2012 9:49:01 AM UTC-4, Largo84 wrote:
No, that's why I used the batch file so I can launch w/ a console.
On Fri, Mar 23, 2012 at 9:15 AM, Largo84 larg...@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
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
On Thu, Mar 22, 2012 at 7:59 PM, Largo84 larg...@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
Hi,
I've a strange problem with rev 1562 in kubuntu intrepid. I cannot
open files when I pass their filenames as arguments to leo in the
command line. The workbook.leo file is opened instead. For instance,
doing
$ launchLeo.py temari.leo
I see this in the konsole:
v...@deckard:~/oposicions$
On Mon, Feb 16, 2009 at 5:25 AM, uve...@gmail.com uve...@gmail.com wrote:
Hi,
I've a strange problem with rev 1562 in kubuntu intrepid. I cannot
open files when I pass their filenames as arguments to leo in the
command line. The workbook.leo file is opened instead. For instance,
doing
$
On Mon, Feb 16, 2009 at 7:11 AM, Edward K. Ream edream...@gmail.com wrote:
On Mon, Feb 16, 2009 at 5:25 AM, uve...@gmail.com uve...@gmail.comwrote:
Hi,
I've a strange problem with rev 1562 in kubuntu intrepid. I cannot
open files when I pass their filenames as arguments to leo in the
On Mon, Feb 16, 2009 at 3:27 PM, Edward K. Ream edream...@gmail.com wrote:
If you can, I would suggest putting a call to g.pdb() at the start of the
createFrame function in runLeo.py. Single-step through the code to
determine what is happening.
Or you can use winpdb...
sudo apt-get install
Hi,
thanks for the suggestion. After doing some tracing I've realised that
the problem was in the simple shell
script that I use to call leo from the console. It was oversimplified:
I've dropped the $1 argument so the
passed filename was ignored... following my instructions :-(
Thanks very much
20 matches
Mail list logo
