wxlua-users

[wxlua-users] editor.wx.lua output problem

[Andre <ar...@ki...>]

I have been playing around with editor.wx.lua THIS IS A GREAT PROGRAM I just
love it. I encountered the output to problem and tried to solve it.

I am new to this Lua world, so this may be really wrong, but it seems to works.

file wxLua\samples\editor.wx.lua
line 1513
from: local cmd = '"'..programName..'" '..'-c '..openDocuments[id].filePath
---
to: local cmd = '"'..programName..'" '..openDocuments[id].filePath

The ouputs goes to the console. Maybe this should be an option.

I am planning to see if I can fix other related problems and maybe add some
features. Should I report the changes here? Is anybody actively working on this
editor? 

Andre

Re: [wxlua-users] editor.wx.lua output problem

[John L. <jla...@gm...>]

On 12/5/06, Andre <ar...@ki...> wrote:
> I have been playing around with editor.wx.lua THIS IS A GREAT PROGRAM I just
> love it. I encountered the output to problem and tried to solve it.
>
> I am new to this Lua world, so this may be really wrong, but it seems to works.
>
> file wxLua\samples\editor.wx.lua
> line 1513
> from: local cmd = '"'..programName..'" '..'-c '..openDocuments[id].filePath
> ---
> to: local cmd = '"'..programName..'" '..openDocuments[id].filePath
>
> The ouputs goes to the console. Maybe this should be an option.

I have not looked too much at the console, doesn't this pop up a text
box to show the output in? It's a hack for MSW since usually stuff
printed to stdout goes nowhere. This would be a nice option though.

> I am planning to see if I can fix other related problems and maybe add some
> features. Should I report the changes here? Is anybody actively working on this
> editor?

That would be great. You can use the sourceforge patch tracker or just
post them here if they're small.

If you work on it could you use the CVS version of editor.wx.lua or at
least the most recent snapshot from the download page. I would
appreciate any fixes or enhancements.

I went through it a few months ago, adding comments and reordering it,
but got distracted by the socket code and switched to that.

Thanks,
    John Labenski

Re: [wxlua-users] editor.wx.lua output problem

[Andre <ar...@ki...>]

John Labenski <jlabenski@...> writes:

> 
> I have not looked too much at the console, doesn't this pop up a text
> box to show the output in? It's a hack for MSW since usually stuff
> printed to stdout goes nowhere. This would be a nice option though.
> 

Yes the console receives the stdout and stderr (I believe).

> > I am planning to see if I can fix other related problems and maybe add some
> 
> If you work on it could you use the CVS version of editor.wx.lua or at
> least the most recent snapshot from the download page. I would
> appreciate any fixes or enhancements.
I am using the CVS version.
> 
> I went through it a few months ago, adding comments and reordering it,
> but got distracted by the socket code and switched to that.
> 

You can have the socket code :)

> Thanks,
>     John Labenski
> 

Talk to you again

Andre

Re: [wxlua-users] editor.wx.lua output problem

[John L. <jla...@gm...>]

On 12/5/06, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
> >
> > I have not looked too much at the console, doesn't this pop up a text
> > box to show the output in? It's a hack for MSW since usually stuff
> > printed to stdout goes nowhere. This would be a nice option though.
>
> Yes the console receives the stdout and stderr (I believe).

I think you meant to add -c instead of remove it? Since it wasn't there before.

Anyway, I added -c and tweaked up the C++ console code, fixed saving
of the files before running them, and now print out the process id for
informational purposes.

Please try the latest CVS and see if it works a little more nicely.
I'll test tonight in Linux to see where the output goes, IIRC it goes
nowhere for a spawned process so we'll have to use the wxLuaConsole
there too.

Regards,
    John Labenski

Re: [wxlua-users] editor.wx.lua output problem

[Andre <ar...@ki...>]

John Labenski <jlabenski@...> writes:

> 
> I think you meant to add -c instead of remove it? Since it wasn't there 
before.

yes should have run diff the other way 

> 
> Anyway, I added -c and tweaked up the C++ console code, fixed saving
> of the files before running them, and now print out the process id for
> informational purposes.

Yes this is a good idea could save some aggravations

> 
> Please try the latest CVS and see if it works a little more nicely.
> I'll test tonight in Linux to see where the output goes, IIRC it goes
> nowhere for a spawned process so we'll have to use the wxLuaConsole
> there too.

I have tried the new version work's great 
> 
> Regards,
>     John Labenski
> 

Thank you

Andre