Re: [PATCH 1/1] Cygwin: console: fix key input for native console application

2019-04-03 Thread Corinna Vinschen
On Apr 4 01:25, Takashi Yano wrote: > - After 24 bit color support patch, arrow keys and function keys > do not work properly in native console applications if they > are started in cygwin console. This patch fixes this issue. > --- > winsup/cygwin/fhandler_console.cc | 17 +

[PATCH 1/1] Cygwin: console: fix key input for native console application

2019-04-03 Thread Takashi Yano
- After 24 bit color support patch, arrow keys and function keys do not work properly in native console applications if they are started in cygwin console. This patch fixes this issue. --- winsup/cygwin/fhandler_console.cc | 17 + 1 file changed, 17 insertions(+) diff --git

[PATCH 0/1] Fix console again (Re: Pseudo console support in PTY)

2019-04-03 Thread Takashi Yano
Hi Corinna, I have made a patch for the issue reported in cygwin-developers mailing list as follows. Could you please check? On Wed, 3 Apr 2019 09:27:58 +0200 Corinna Vinschen wrote: > On Apr 3 09:18, Thomas Wolff wrote: > > > - cmd history works > > In the cygwin console, it does not, echos

Re: [PATCH fifo 0/2] Add support for duplex FIFOs

2019-04-03 Thread Ken Brown
On 4/3/2019 8:33 AM, Achim Gratz wrote: > Achim Gratz writes: >> OK, a bit more info: The whole thing runs from a perl script (actually a >> module) that opens pipes to gnuplot and ghostscript. This code is >> _really_ old and has seen a lot of Cygwin releases, so it has options to >> either use

Re: [PATCH fifo 0/2] Add support for duplex FIFOs

2019-04-03 Thread Achim Gratz
Achim Gratz writes: > OK, a bit more info: The whole thing runs from a perl script (actually a > module) that opens pipes to gnuplot and ghostscript. This code is > _really_ old and has seen a lot of Cygwin releases, so it has options to > either use temporary files, named pipes aka FIFO or

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

2019-04-03 Thread Achim Gratz
Michael Haubenwallner writes: > Before I really can tell what I need regarding the rebase, I need to learn > what > exactly is recorded into the rebase database, and probably how the recorded > data > does influence the rebase procedure right now. Just where the DLL resides in the filesystem,

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

2019-04-03 Thread Corinna Vinschen
On Apr 3 12:38, Michael Haubenwallner wrote: > Furthermore, with so called "Stacked Prefix", it is possible to have a second > level of Gentoo Prefix, so what I'm after is some option to tell the rebase > utility which database to record dll base addresses into, and which > multiple(!) >

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

2019-04-03 Thread Corinna Vinschen
On Apr 3 11:18, Michael Haubenwallner wrote: > On 4/1/19 5:56 PM, Corinna Vinschen wrote: > > On Apr 1 16:56, Corinna Vinschen wrote: > >> On Apr 1 16:28, Michael Haubenwallner wrote: > >>> On 3/28/19 9:30 PM, Corinna Vinschen wrote: > can you please collect the base addresses of all DLLs

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

2019-04-03 Thread Michael Haubenwallner
Hi Brian, hi Achim, Thanks a lot for your input! On 3/30/19 5:09 PM, Brian Inglis wrote: > On 2019-03-30 02:22, Achim Gratz wrote: >> Brian Inglis writes: >>> On 2019-03-29 14:23, Achim Gratz wrote: Brian Inglis writes: >> If you are packaging your own exes and dlls with your own local

Re: [PATCH RFC] fork: reduce chances for "address space is already occupied" errors

2019-04-03 Thread Michael Haubenwallner
On 4/1/19 5:56 PM, Corinna Vinschen wrote: > On Apr 1 16:56, Corinna Vinschen wrote: >> On Apr 1 16:28, Michael Haubenwallner wrote: >>> On 3/28/19 9:30 PM, Corinna Vinschen wrote: can you please collect the base addresses of all DLLs generated during the build, plus their size and