how to continue to have a separate window with this patch applied ?
this break some functions in wcmd. - cls isnt working anymore - some programs have keyboard entry used only after hitting enter. try debug.com from freedos or worse, wcmd itself. - debug messages are displayed in the same window
Trying to run this kind of program didnt work outside of the
console,
if I remember correct.
it's likely not to work, since nothing has changed in this area A+ -- Eric Pouech
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle wrote:
how to continue to have a separate window with this patch applied ?
this break some functions in wcmd.
- cls isnt working anymore
Old command.com output ESC[2J for cls, maybe we should, too.
- some programs have keyboard entry used only after hitting enter. try
debug.com from freedos or worse, wcmd itself.
If you're saying running nested wcmd isn't working, then yeah, that needs fixing.
- debug messages are displayed in the same window
That's ok. - Dan
If you're saying running nested wcmd isn't working, then yeah, that needs fixing.
this comes from wcmd using FindExecutable/SHGetFileInfo, and those API don't handle properly builtin executables A+
Eric Pouech wrote:
If you're saying running nested wcmd isn't working, then yeah, that needs fixing.
this comes from wcmd using FindExecutable/SHGetFileInfo, and those API don't handle properly builtin executables
A good reason for us to switch to generating PE format for all our builtin executables on x86. IMHO winelib apps are most useful on nonx86 platforms... - Dan
A good reason for us to switch to generating PE format for all our builtin executables on x86. IMHO winelib apps are most useful on nonx86 platforms...
that would be great, but you would loose the ability to ld-link to unix libraries easily for your winelib app A workaround would be to embed ELF-ld information into PE import sections
A+
Sylvain Petreolle wrote:
how to continue to have a separate window with this patch applied ?
you can't with current CVS (as I wrote in a previous mail, I'll submit something RSN)
this break some functions in wcmd.
you should run wineconsole wcmd not wcmd if you want console support A+
--- Eric Pouech eric.pouech@wanadoo.fr a écrit : > Sylvain Petreolle wrote:
how to continue to have a separate window with this patch applied ?
you can't with current CVS (as I wrote in a previous mail, I'll submit something RSN)
this break some functions in wcmd.
you should run wineconsole wcmd not wcmd if you want console support
agreed, but this doesnt allow to use the system menu anymore, and corrupts DOS application screen with debug messages.
I cant even do a mouse-copy on the text without doing a redirection.
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
agreed, but this doesnt allow to use the system menu anymore,
which system menu ? the one from the user backend ?
and corrupts DOS application screen with debug messages.
that's what you get with everything on the same console 2> /dev/null may be your friend there
I cant even do a mouse-copy on the text without doing a redirection.
the quick-edit/mouse emulation switch isn't in place yet (we're always in mouse emulation mode). I'll look into it
A+
and corrupts DOS application screen with debug messages.
that's what you get with everything on the same console 2> /dev/null may be your friend there
it isnt, we cannot debug our program this way. ugly workaround (and the only way to have "normal" display wuith keyboard events) : use wineconsole wcmd in a xterm, do a redirection 2>log and another window: tail -f log.
why I absolutely need this : im currently trying to get the sb emu for dos working. for the moment, I havent found a program than can use it properly.
the quick-edit/mouse emulation switch isn't in place yet (we're always in mouse emulation mode). I'll look into it
would be useful to have error messages from the applications, wouldn't be ?
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
it isnt, we cannot debug our program this way. ugly workaround (and the only way to have "normal" display wuith keyboard events) : use wineconsole wcmd in a xterm, do a redirection 2>log and another window: tail -f log.
btw, wineconsole wcmd doesn't work you must use wineconsole wcmd.exe.so
(or use the patch from yesterday evening which introduces the --backend wineconsole option)
the quick-edit/mouse emulation switch isn't in place yet (we're always in mouse emulation mode). I'll look into it
would be useful to have error messages from the applications, wouldn't be ?
well, as soon as you say I give full control of the screen console to one app (which is what the console means), I don't really see how you can easily mix the error streams from that
the only way I see is: 1/ in winconsole, redirect 2/stderr to a pipe (if it's a tty fd) 2/ this pipe (writing side) will be inherited by all wineconsole's children (ie the ones using the console as output) 3/ then wineconsole can decide what to do with the pipe's output (for example if the screen is big enough print that information too...)
but, this may require quite a big of an effort (especially for 3/)
A+
huh ? In which way are you seeing it not work ? 'wineconsole wcmd' is enough to open a shell
(wcmd.exe, symbolic link to wcmd.exe.so is already installed in c:\windows\system and is in %PATH%)
have you tried to do "wcmd /c wcmd" ? it fills the screen with "C:" or the windows drectory where you are, cannot stop it with ctrl-c !! I will make a report when the backend patch will be applied.
btw, wineconsole wcmd doesn't work you must use wineconsole wcmd.exe.so
(or use the patch from yesterday evening which introduces the --backend wineconsole option)
will try it .
I totally forgot pipes... thanks for poiting it out.
the only way I see is: 1/ in winconsole, redirect 2/stderr to a pipe (if it's a tty fd) 2/ this pipe (writing side) will be inherited by all wineconsole's children (ie the ones using the console as output) 3/ then wineconsole can decide what to do with the pipe's output (for
example if the screen is big enough print that information too...)
but, this may require quite a big of an effort (especially for 3/)
A+
-- Eric Pouech
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle wrote:
huh ? In which way are you seeing it not work ? 'wineconsole wcmd' is enough to open a shell
(wcmd.exe, symbolic link to wcmd.exe.so is already installed in c:\windows\system and is in %PATH%)
or it may be because I don't install wine and run it from the CVS tree
have you tried to do "wcmd /c wcmd" ? it fills the screen with "C:" or the windows drectory where you are, cannot stop it with ctrl-c !! I will make a report when the backend patch will be applied.
as already noted (see answer to Dan in this thread), wcmd doesn't behave correctly when launching CUI builtin executables
A+
Sylvain Petreolle wrote:
you should run wineconsole wcmd not wcmd if you want console support
agreed, but this doesnt allow to use the system menu anymore, and corrupts DOS application screen with debug messages.
I cant even do a mouse-copy on the text without doing a redirection.
So what's new? Copy and paste from wineconsole has always defeated me. It has literally never worked properly. All the backtraces I've posted have been done using redirection. - Dan
So what's new? Copy and paste from wineconsole has always defeated me. It has literally never worked properly. All the backtraces I've posted have been done using redirection.
turn the quick edit flag on A+
Eric Pouech wrote:
So what's new? Copy and paste from wineconsole has always defeated me. It has literally never worked properly. All the backtraces I've posted have been done using redirection.
turn the quick edit flag on
How would the average user learn that? It's counterintuitive.
Honestly, copy and paste should not require strange flags, should it? One or the other of the Windows or the Unix method of doing copy and paste should work out-of-the-box, don't you think? - Dan
Honestly, copy and paste should not require strange flags, should it? One or the other of the Windows or the Unix method of doing copy and paste should work out-of-the-box, don't you think?
it's conterintuitive for you, but folks using mouse driven programs like ida would also find it counterintuitive if mouse would be used for copy and paste
I'm not saying this is easy to find out, but there's no other way out of it (we could however have default values in our default registry to get correct behavior for most used apps)
A+
Eric Pouech wrote:
Honestly, copy and paste should not require strange flags, should it? One or the other of the Windows or the Unix method of doing copy and paste should work out-of-the-box, don't you think?
it's conterintuitive for you, but folks using mouse driven programs like ida would also find it counterintuitive if mouse would be used for copy and paste
How does ida work with the mouse in Windows? It should work exactly the same way in Wine. That would be the least confusing of all, I'd think.
I'm not saying this is easy to find out, but there's no other way out of it (we could however have default values in our default registry to get correct behavior for most used apps)
Can this flag be set like in NT, where you click on the upper left corner widget to bring up an edit menu?
- Dan
How does ida work with the mouse in Windows? It should work exactly the same way in Wine. That would be the least confusing of all, I'd think.
wineconsole has exactly the same behavior as windows... quick edit flag comes from Windows wineconsole registry layout is the same as Windows' and in Windows, quick edit flag is off by default
I'm not saying this is easy to find out, but there's no other way out of it (we could however have default values in our default registry to get correct behavior for most used apps)
Can this flag be set like in NT, where you click on the upper left corner widget to bring up an edit menu?
yes, in user backend mode, right click in the window, and select properties in the menu - you'll have the ability to pick up all the settings, either for current session, or to retain the settings for all further sessions of the same executable (in last dialog box after you click ok)... as Windows do!
A+
On Sat, Mar 01, 2003 at 10:22:13AM -0800, Dan Kegel wrote:
Eric Pouech wrote:
So what's new? Copy and paste from wineconsole has always defeated me. It has literally never worked properly. All the backtraces I've posted have been done using redirection.
Err, just press Shift and the select the area you want to copy.
Ciao, Marcus
Marcus Meissner wrote:
On Sat, Mar 01, 2003 at 10:22:13AM -0800, Dan Kegel wrote:
Eric Pouech wrote:
So what's new? Copy and paste from wineconsole has always defeated me. It has literally never worked properly. All the backtraces I've posted have been done using redirection.
Err, just press Shift and the select the area you want to copy.
That's not how it works under Windows, is it? I've never used shift when copying from a dos window in Windows. It's always "click on the mark icon", select, "click on the copy icon".
Maybe what I'm looking for is those icons in the toolbar of wineconsole...
Also, on those occasions where I've dared to try copy and paste in spite of the gyrations you have to go through to enable it, it produced corrupted data. In particular, duplications. That's right -- not only was it hard to try, but it didn't work right once I figured it out. This was three months ago or so, I think.
I'll try it again soon and see if it's improved. - Dan
Err, just press Shift and the select the area you want to copy.
That's not how it works under Windows, is it?
no, it's xterm behavior
I've never used shift when copying from a dos window in Windows. It's always "click on the mark icon", select, "click on the copy icon".
Maybe what I'm looking for is those icons in the toolbar of wineconsole...
that could be done. Any taker ?
Also, on those occasions where I've dared to try copy and paste in spite of the gyrations you have to go through to enable it, it produced corrupted data. In particular, duplications. That's right -- not only was it hard to try, but it didn't work right once I figured it out. This was three months ago or so, I think.
I fixed a bug last week on this issue (especially, if you increased the window size by hand before selecting/copying)
A+
Eric Pouech wrote:
Maybe what I'm looking for is those icons in the toolbar of wineconsole...
that could be done. Any taker ?
Sounds like a good little project. What's the procedure for enhancement requests? Is the bug tracking system the place to log them?
Also, on those occasions where I've dared to try copy and paste in spite of the gyrations you have to go through to enable it, it produced corrupted data. In particular, duplications. That's right -- not only was it hard to try, but it didn't work right once I figured it out. This was three months ago or so, I think.
I fixed a bug last week on this issue (especially, if you increased the window size by hand before selecting/copying)
Cool, thanks... I'll test when I get a chance. - Dan
Dan Kegel wrote:
Eric Pouech wrote:
Maybe what I'm looking for is those icons in the toolbar of wineconsole...
that could be done. Any taker ?
Sounds like a good little project. What's the procedure for enhancement requests? Is the bug tracking system the place to log them?
Yes, I think thats appropriate. Bugzilla has the severity field. (Set it to "enhancement"). Dimi might want to add it to his fun with wine page too.
On March 1, 2003 09:43 pm, Tony Lambregts wrote:
Yes, I think thats appropriate. Bugzilla has the severity field. (Set it to "enhancement"). Dimi might want to add it to his fun with wine page too.
That's a good idea. If you create the bug, let me know and I'll create an entry on the Fun page, referencing the bug...
Dimitrie O. Paun wrote:
On March 1, 2003 09:43 pm, Tony Lambregts wrote:
Yes, I think thats appropriate. Bugzilla has the severity field. (Set it to "enhancement"). Dimi might want to add it to his fun with wine page too.
That's a good idea. If you create the bug, let me know and I'll create an entry on the Fun page, referencing the bug...
Done.
http://bugs.winehq.com/show_bug.cgi?id=1304
On March 2, 2003 07:49 pm, Tony Lambregts wrote:
Added: http://www.dssd.ca/wine/Wine-Fun.html#wineconsole
Now, any takers? :)
-
Dan Kegel -
Dimitrie O. Paun -
Eric Pouech -
Marcus Meissner -
Sylvain Petreolle -
Tony Lambregts