Le 12/09/2010 14:09, Jerome Leclanche a écrit :
Set a 1440x900 virtual desktop in winecfg.
what do you mean by:
- run a program in winedbg (in my case, it was in a virtual desktop,
too) => does it mean you got 2 virtual desktops ? or got a shell running
in one virtual desktop ?
- (?) Term
Set a 1440x900 virtual desktop in winecfg.
J. Leclanche
On Sun, Sep 12, 2010 at 12:46 PM, Eric Pouech wrote:
> Le 12/09/2010 00:26, Jerome Leclanche a écrit :
>>
>> Hi Eric,
>>
>> Ive been running your patch for a couple of days and I just noticed
>> another case where it's not resetting term
Le 12/09/2010 00:26, Jerome Leclanche a écrit :
Hi Eric,
Ive been running your patch for a couple of days and I just noticed
another case where it's not resetting terminal properties:
- Run a program in winedbg (in my case, it was in a virtual desktop, too)
- Wait for program to crash
- Hi
Hi Eric,
Ive been running your patch for a couple of days and I just noticed
another case where it's not resetting terminal properties:
- Run a program in winedbg (in my case, it was in a virtual desktop, too)
- Wait for program to crash
- Hit ctrl-c
- (?) Terminate process in the virtual desk
Le 09/09/2010 18:13, Jerome Leclanche a écrit :
Eric,
When running a program with "r" in winedbg, I get:
fixme:winedbg:dbg_run_debuggee Re-running current program with "\r" as
args is broken
Does this have anything to do with the EOL conversion issues?
no, it has been broken for years
(if
Eric,
When running a program with "r" in winedbg, I get:
fixme:winedbg:dbg_run_debuggee Re-running current program with "\r" as
args is broken
Does this have anything to do with the EOL conversion issues?
J. Leclanche
On Wed, Sep 8, 2010 at 9:32 PM, Reece Dunn wrote:
> On 8 September 2010 21
On 8 September 2010 21:04, Eric Pouech wrote:
> does the attached patch help with some of the concerns ?
> I/ it should allow typing in the console (for all GUI programs) and still
> see output get buffer when the programs exits
> II/ reduce the number of cases where the console is in raw mode aft
does the attached patch help with some of the concerns ?
I/ it should allow typing in the console (for all GUI programs) and
still see output get buffer when the programs exits
II/ reduce the number of cases where the console is in raw mode after
wine exits
Not all the cases are supposed to be
On 6 September 2010 21:00, Eric Pouech wrote:
> B/ actually, it's likely a race (in the simple way of running one single
> program) about resetting the console in decent shape. Could the folks having
> the issue try the attached patch (file conclean) to see if it helps ? (I
> never could reproduce
On 09/06/2010 10:00 PM, Eric Pouech wrote:
Actually, there's another issue with the same symptoms:
1- program A is launched from shell
2- program A starts another program B (for example winedbg when a fault
occurs)
3- at this point, both A & B can read/write to the console
4- program A exits. As
Eric Pouech writes:
> among the potential fixes:
> S1: no longer do the console attribute management in server, but only
> in kernel32, and only for the livespan of the process creating the
> bare console. this means that the console will not be accessible to
> the children of this process after
Eric Pouech wrote:
> +void close_console( struct process* process)
Shouldn't it be named close_bare_console()? Otherwise it won't compile.
--
Dmitry.
Hi,
after the console patch series, it appears a couple of problems are left
over:
to summarize, the problems with their status:
A/ when a program is running, no echo is seen for characters being typed.
B/ after running a wine program, the console is a bad shape and needs
'reset' to get bac
On Thu, Sep 2, 2010 at 2:44 PM, Jerome Leclanche wrote:
> To be more specific, it happens on any and every wine program.
I see it as well, though an easy workaround is to run 'reset'. After
that, terminal returns to normal.
--
-Austin
On 09/02/2010 09:41 PM, Eric Pouech wrote:
Le 02/09/2010 03:29, Jerome Leclanche a écrit :
Anyone else's terminal emulators really acting up since the last git
batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
there is a wine process running, until it's killed. This is proba
To be more specific, it happens on any and every wine program.
J. Leclanche
On Thu, Sep 2, 2010 at 8:44 PM, Jerome Leclanche wrote:
> It's a GUI.
>
>
> J. Leclanche
>
>
>
> On Thu, Sep 2, 2010 at 8:41 PM, Eric Pouech wrote:
>> Le 02/09/2010 03:29, Jerome Leclanche a écrit :
>>>
>>> Anyone el
It's a GUI.
J. Leclanche
On Thu, Sep 2, 2010 at 8:41 PM, Eric Pouech wrote:
> Le 02/09/2010 03:29, Jerome Leclanche a écrit :
>>
>> Anyone else's terminal emulators really acting up since the last git
>> batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
>> there is a wine
Le 02/09/2010 03:29, Jerome Leclanche a écrit :
Anyone else's terminal emulators really acting up since the last git
batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
there is a wine process running, until it's killed. This is probably a
konsole bug, but still...
CC eric.
-
to summarize a bit:
- wineserver doesn't reset the terminal attributes if it's killed (to be
fixed)
- command line edition is not supported. it was not supported either in
previous console code (outside of wineconsole). this is to be provided in
next patches
- I have no idea on the blank outputs. i
On Thu, Sep 2, 2010 at 4:29 AM, Jerome Leclanche wrote:
> Anyone else's terminal emulators really acting up since the last git
> batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
> there is a wine process running, until it's killed. This is probably a
> konsole bug, but still.
* On Thu, 2 Sep 2010, Reece Dunn wrote:
> On 2 September 2010 02:29, Jerome Leclanche wrote:
> > Anyone else's terminal emulators really acting up since the last git
> > batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
> > there is a wine process running, until it's killed. T
On 2 September 2010 02:29, Jerome Leclanche wrote:
> Anyone else's terminal emulators really acting up since the last git
> batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
> there is a wine process running, until it's killed. This is probably a
> konsole bug, but still...
O
Anyone else's terminal emulators really acting up since the last git
batch? On konsole (2.5//4.5.00), I'm unable to see what I'm writing if
there is a wine process running, until it's killed. This is probably a
konsole bug, but still...
CC eric.
--
J. Leclanche
23 matches
Mail list logo
