Re: Update of packages by non-maintainer

2020-05-21 Thread Andrey Repin
Greetings, Yasuhiro KIMURA!

>> You should discuss changes and intent on cygwin list, post patches on
>> cygwin-apps list.

> Thank you for reply. My first candidate is anthy. Original anthy
> projet has been inactive since 2009. But Debian forked it and made
> improvement and enhancement. So I would like to switch codebase to
> that of Debian. I just checked out cygwin anthy git repository and
> started working but I have one question.

> After project fork by Debian, release version scheme has changed.
> While latest version from original project (and one used by cygwin
> package) is "9100h", latest one from Debian is "0.4". That is, version
> number decreses if I chage codebase to Debian. I know that some
> packaging systems assume version number basically increases and that
> decrement causes package upgrade failure.  So I would like to know if
> it also apply to Cygwin.

It does. This is why you would see test and pre-release versions posted as
X.Y-0.Z and release versions posted as X.Y-Z.

> And if it does then I also would like to know how it should be handled.

An interesting question, given nonstandard original versioning.


-- 
With best regards,
Andrey Repin
Thursday, May 21, 2020 12:46:55

Sorry for my terrible english...

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Update of packages by non-maintainer

2020-05-21 Thread Marco Atzeri via Cygwin

On 21.05.2020 06:47, Yasuhiro KIMURA wrote:

From: Brian Inglis
Subject: Re: Update of packages by non-maintainer
Date: Wed, 20 May 2020 08:32:59 -0600


You should discuss changes and intent on cygwin list, post patches on
cygwin-apps list.


Thank you for reply. My first candidate is anthy. Original anthy
projet has been inactive since 2009. But Debian forked it and made
improvement and enhancement. So I would like to switch codebase to
that of Debian. I just checked out cygwin anthy git repository and
started working but I have one question.


the anthy pkg maintainer, Yaakov, is reducing his activity
and if you are interested you can take over.


After project fork by Debian, release version scheme has changed.
While latest version from original project (and one used by cygwin
package) is "9100h", latest one from Debian is "0.4". That is, version
number decreses if I chage codebase to Debian. I know that some
packaging systems assume version number basically increases and that
decrement causes package upgrade failure.  So I would like to know if
it also apply to Cygwin. And if it does then I also would like to know
how it should be handled.


currently we have no solution. There were in the past discussion
to overcome such problem but they are not yet implemented.

We can follow these two points on the cygwin-apps mailing list,
please subscribe to it.



Best Regards.

---
Yasuhiro KIMURA


Regards
Marco

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Trying to install older version (9.50) of ghostscript - still got 9.52

2020-05-21 Thread Maarten Hoes via Cygwin
On Wed, May 20, 2020 at 9:48 PM Jim Garrison via Cygwin 
wrote:

>
> I didn't have to go back to a snapshot of the entire Cygwin
> installation. I was able to get what I needed by downgrading
> libgs9 as well.
>
>
That's good to hear. Although I can also imagine situations where version
'X' of any given library is also linked against more programs than 'just' a
single executable you're using, and then you might end up in a situation
where you have to figure out which executable's these are (and what library
versions they were linked against).


- Maarten
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


[ANNOUNCEMENT] Updated: Perl distributions

2020-05-21 Thread Achim Gratz


The following Perl distributions have been updated to their latest
version on CPAN:

x86/x86_64
--
perl-Text-CSV_XS-1.42-1

noarch
--
perl-JSON-MaybeXS-1.004002-1
perl-Mozilla-CA-20200520-1
perl-Test-TrailingSpace-0.0400-1
perl-TimeDate-2.33-1


-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: [ANNOUNCEMENT] Updated: mintty 3.1.5

2020-05-21 Thread Ken Brown via Cygwin

On 5/20/2020 11:34 AM, Thomas Wolff wrote:

I have uploaded mintty 3.1.5 with the following changes:

Terminal features
   * Limit coordinates of all mouse reports to text area (#972).
   * Support bell volume escape sequence DECSWBV (#974) with wave files.
   * Support margin bell feature (#974), with DECSET 44 enabling sequence 
(xterm).
   * Support margin bell volume escape sequence DECSMBV (#974) with wave files.
   * Support visible space indication.
   * Fixed insert mode in single-width character mode (#964).
   * DECFRA (fill rectangular area) works with wide and non-BMP characters.
   * DECFRA works with NRCS and DEC Line Drawing characters (VT420).
   * New CSI > 0 q to report terminal name and version (#881).
   * New CSI 2/1 SP Z (ECMA-48 PEC) as character attribute to enforce 
single/double width (#615, #979, #973, #938, #638, ~#88, ~#671).

   * New CSI cps - p DECARR Select Auto Repeat Rate (VT520).
   * Support Ctrl+Alt-mouse clicks (#987).

Character encoding
   * Enhanced and documented GB18030 support (mintty/wsltty#224).

Keyboard handling
   * Unmapped AltGr combinations: don't fallback to ESC prefixing (~#969).
   * Guard Compose key against hotkey injection (~#877).

Unicode and Emoji data
   * Unicode 13.0 update.
   * Distinct support for EmojiOne (from unicode.org) and JoyPixels emojis.

Font rendering
   * Enable auto-narrowing for Private Use characters (#979, "Nerd Fonts").
   * Adjust and zoom rendering for geometric Powerline symbols (#979).
   * Support emoji style OpenMoji (#985).

Window handling
   * Tweak title bar dark mode adaptation to undocumented Windows changes (#983, 
mintty/wsltty#157).

   * Support dark mode for menus (#983, mintty/wsltty#157).
   * DropCommands secured against multiple placeholders.
   * DropCommands optionally pastes Windows format paths (#982).
   * Drag-and-drop import of itermcolors schemes (mintty/wsltty#227).
   * Workaround to interact with Hot Keyboard (#877, setting 
SupportExternalHotkeys=4).
   * Disable deprecated glass mode from interactive options (#501, 
mintty/wsltty#241).

   * Speedup of scrollback searching (#988, #986).

Other
   * Warning and error popups are placed on top of desktop.
   * Environment variables TERM_PROGRAM[_VERSION] provide unreliable info about 
terminal application (#776, #881).


Configuration
   * Options BellFile2 ... BellFile7 (#974).
   * Options DispSpace, DispTab, DispClear.
   * Options Suppress* are now resilient against space (mintty/wsltty#235).
   * Option value SupportExternalHotkeys=4 (#877).
   * Option value Emojis=openmoji (#985).

The homepage is at http://mintty.github.io/
It also links to the issue tracker.


After this release the right Alt key on my keyboard has lost some functionality. 
 Alt-f and Alt-b no longer move forward and backward across words, and Alt-d no 
longer deletes the following word.  Alt-Backspace still deletes the previous 
word.  I'm using a standard US keyboard.


Ken
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


STACKDUMP - mintty - Multiply crashes experienced following upgrade to mintty 3.1.5 - x86_64-pc-cygwin

2020-05-21 Thread Olaf Sulla via Cygwin
Hi,

I am now experiencing multiple crashes in mintty following the installation of
mintty v3.1.5 earlier this morning.

Typical stackdump:

Exception: STATUS_INTEGER_DIVIDE_BY_ZERO at rip=00100438534^M
rax=03E8 rbx=401C0001 rcx=^M
rdx= rsi=000D rdi=0001004CB540^M
r8 =BFA8 r9 =000180321C90 r10=^M
r11=0202 r12=4000 r13=76F256E4^M
r14= r15=00050576^M
rbp=000180321C90 rsp=BFB0^M
program=C:\cygwin64\bin\mintty.exe, pid 1791, thread main^M
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B^M
Stack trace:^M
FrameFunctionArgs^M
00180321C90  00100438534 (00076F078EC, 000, 001, 000C458)^M
000C3A0  00100440135 (02F0058, 00076F1908A, 00180132457, 001802BEDF0)^M
000C5C0  00076F19BBD (0010043F780, 001004CB9E0, 092EB10, 00D)^M
000C5C0  00076F198C2 (00076F139B0, 0010043F780, 00076F532B8, 0080001)^M
000C5C0  0010045133C (02F, 000, 0018022D780, 00180294A00)^M
000CCD0  0018004A826 (000, 000, 000, 000)^M
000  00180048353 (000, 000, 000, 000)^M
000FFF0  00180048404 (000, 000, 000, 000)^M
End of stack trace


Scenario:

The crashes occur if while moving the cursor it reaches or is near the bottom
of the screen. Crashes have occurred in vim, mutt, and man since installing
this version.


Regards,

-- 

Mutt 1.14.0 (2020-05-02)
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: [ANNOUNCEMENT] Updated: mintty 3.1.5

2020-05-21 Thread Marco Atzeri via Cygwin

On 21.05.2020 16:48, Ken Brown via Cygwin wrote:

On 5/20/2020 11:34 AM, Thomas Wolff wrote:

I have uploaded mintty 3.1.5 with the following changes:





The homepage is at http://mintty.github.io/
It also links to the issue tracker.


After this release the right Alt key on my keyboard has lost some 
functionality.  Alt-f and Alt-b no longer move forward and backward 
across words, and Alt-d no longer deletes the following word.  
Alt-Backspace still deletes the previous word.  I'm using a standard US 
keyboard.


these functionalities are on the left ALT key on my German Keyboard

the right ALT key when pressed for some time
is producing a strange effect

$ mintty
Floating point exception (core dumped)

$ cat mintty.exe.stackdump
Exception: STATUS_INTEGER_DIVIDE_BY_ZERO at rip=00100438534
rax=03E8 rbx=61380001 rcx=
rdx= rsi=0012 rdi=0001004CB540
r8 =BF18 r9 =000180321C90 r10=
r11=0246 r12=4000 r13=7FFC3DFE8DC0
r14= r15=
rbp=000180321C90 rsp=BF20
program=D:\cygwin64\bin\mintty.exe, pid 1879, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
FrameFunctionArgs
00180321C90  00100438534 (000601D0001, 00180321C90, 100, 
000)
000C310  00100440135 (001, 001, 000, 
000)
000C600  7FFC3DFD5C0D (0010043F780, 02B099E, 000C6A0, 
012)
000C600  7FFC3DFD5602 (7FFC3DFD9A70, 7FFC3E017160, 001004CB9E0, 
0080001)
000C600  0010045133C (020, 3000100FF00, 0018004A7BA, 
00180049800)
000CCD0  0018004A826 (000, 000, 000, 
000)
000  00180048353 (000, 000, 000, 
000)
000FFF0  00180048404 (000, 000, 000, 
000)

End of stack trace
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: [ANNOUNCEMENT] Updated: mintty 3.1.5

2020-05-21 Thread Ken Brown via Cygwin

On 5/21/2020 12:36 PM, Marco Atzeri via Cygwin wrote:

On 21.05.2020 16:48, Ken Brown via Cygwin wrote:

On 5/20/2020 11:34 AM, Thomas Wolff wrote:

I have uploaded mintty 3.1.5 with the following changes:





The homepage is at http://mintty.github.io/
It also links to the issue tracker.


After this release the right Alt key on my keyboard has lost some 
functionality.  Alt-f and Alt-b no longer move forward and backward across 
words, and Alt-d no longer deletes the following word. Alt-Backspace still 
deletes the previous word.  I'm using a standard US keyboard.


these functionalities are on the left ALT key on my German Keyboard


Prior to this update, these functionalities worked with both Alt keys on my 
keyboard.  Now they work only with the left Alt key.  I should have said that in 
my original report.


Ken
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


[ANNOUNCEMENT] Updated: mintty 3.1.6

2020-05-21 Thread Thomas Wolff

I have uploaded mintty 3.1.6 with the following changes:

Window handling
  * Fixed resource leak when displaying images (#995).
  * Fixed crash condition on keyboard auto-repeat (#996). (Apologies 
for this one.)


The homepage is at http://mintty.github.io/
It also links to the issue tracker.

--
Thomas
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: XWin problem (xinit launche twice)

2020-05-21 Thread Franz Fehringer via Cygwin
Hi Marco,

With a little delay i made some experiments as suggested by you
(disclaimer: i know that top posting is frowned upon in this group but
here it goes):
PATH=/usr/bin startxwin
-> only one xinit (started from mintty / bash)
startxwin -- -listen tcp -nowgl
-> same (only one)
C:\Programs\Cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec
/usr/bin/startxwin -- -listen tcp -nowgl"
two xinitS are started (started from cmd)
Tested on my business laptop with Windows 1903 latest and Cygwin latest
No .startxwinrc and no modification of /etc/X11/xinit/startxwinrc
With the cmd / run / quote variant also two xinitS on my private
notebook with Windows 1909 latest and Cygwin latest
But the cmd / run / quote exercise gives only ane xinit on my private
desktop (again Windows 1909 latest and Cygwin latest)?
In fact i start not via cmd but using a desktop icon / link.
The extra arguments are for starting WSL X11 clients.
LC_ALL=de_DE.utf8 (all three)
To be continued

Franz


Am 17.05.2020 um 18:42 schrieb Marco Atzeri via Cygwin:
> On 17.05.2020 13:00, Franz Fehringer via Cygwin wrote:
>>
>>
>> Am 17.05.2020 um 12:23 schrieb Marco Atzeri:
>>> On 17.05.2020 12:15, Franz Fehringer via Cygwin wrote:
 This is a repost, because sending to group gmane.os.cygwin seemingly
 did
 not get through.


> 
>>>
>>> Hi Franz,
>>>
>>> can you follow guideline and provide the cygcheck.out as attachement ?
 Problem reports:  https://cygwin.com/problems.html
>>>
>>> How are you starting Xwin ?
>>> Have you any custom setting ?
>>> (eg a .startxwinrc on your home, or similar)
> 
> and about these ?
> 
>>>
>>> Regards
>>> Marco
>>>
>>>
>>
>> Here it is.
>>
> 
> what happens if you run just
> 
>    PATH="/usr/bin" startxwin
> 
> -- 
> Problem reports:  https://cygwin.com/problems.html
> FAQ:  https://cygwin.com/faq/
> Documentation:    https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: XWin problem (xinit launche twice)

2020-05-21 Thread Franz Fehringer via Cygwin
path C:\Tools\Cygwin\usr\bin;%PATH% before the run --quote does not
change anything.

Am 21.05.2020 um 19:50 schrieb Franz Fehringer:
> Hi Marco,
>
> With a little delay i made some experiments as suggested by you
> (disclaimer: i know that top posting is frowned upon in this group but
> here it goes):
> PATH=/usr/bin startxwin
> -> only one xinit (started from mintty / bash)
> startxwin -- -listen tcp -nowgl
> -> same (only one)
> C:\Programs\Cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec
> /usr/bin/startxwin -- -listen tcp -nowgl"
> two xinitS are started (started from cmd)
> Tested on my business laptop with Windows 1903 latest and Cygwin latest
> No .startxwinrc and no modification of /etc/X11/xinit/startxwinrc
> With the cmd / run / quote variant also two xinitS on my private
> notebook with Windows 1909 latest and Cygwin latest
> But the cmd / run / quote exercise gives only ane xinit on my private
> desktop (again Windows 1909 latest and Cygwin latest)?
> In fact i start not via cmd but using a desktop icon / link.
> The extra arguments are for starting WSL X11 clients.
> LC_ALL=de_DE.utf8 (all three)
> To be continued
>
> Franz
>
>
> Am 17.05.2020 um 18:42 schrieb Marco Atzeri via Cygwin:
>> On 17.05.2020 13:00, Franz Fehringer via Cygwin wrote:
>>>
>>> Am 17.05.2020 um 12:23 schrieb Marco Atzeri:
 On 17.05.2020 12:15, Franz Fehringer via Cygwin wrote:
> This is a repost, because sending to group gmane.os.cygwin seemingly
> did
> not get through.
>
>
 Hi Franz,

 can you follow guideline and provide the cygcheck.out as attachement ?
> Problem reports:  https://cygwin.com/problems.html
 How are you starting Xwin ?
 Have you any custom setting ?
 (eg a .startxwinrc on your home, or similar)
>> and about these ?
>>
 Regards
 Marco


>>> Here it is.
>>>
>> what happens if you run just
>>
>>    PATH="/usr/bin" startxwin
>>
>> -- 
>> Problem reports:  https://cygwin.com/problems.html
>> FAQ:  https://cygwin.com/faq/
>> Documentation:    https://cygwin.com/docs.html
>> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: STACKDUMP - mintty - Multiply crashes experienced following upgrade to mintty 3.1.5 - x86_64-pc-cygwin

2020-05-21 Thread Thomas Wolff

Am 21.05.2020 um 17:42 schrieb Olaf Sulla via Cygwin:

Apologies,

Additional info:

Build:
CYGWIN_NT-6.1 shackleton 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1

Redacted cygcheck report attached.



On Thu 2020-05-21 16:13:08 +0100, Olaf Sulla wrote:

Hi,

I am now experiencing multiple crashes in mintty following the installation of
mintty v3.1.5 earlier this morning.

Typical stackdump:

Exception: STATUS_INTEGER_DIVIDE_BY_ZERO at rip=00100438534^M
rax=03E8 rbx=401C0001 rcx=^M
rdx= rsi=000D rdi=0001004CB540^M
r8 =BFA8 r9 =000180321C90 r10=^M
r11=0202 r12=4000 r13=76F256E4^M
r14= r15=00050576^M
rbp=000180321C90 rsp=BFB0^M
program=C:\cygwin64\bin\mintty.exe, pid 1791, thread main^M
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B^M
Stack trace:^M
FrameFunctionArgs^M
00180321C90  00100438534 (00076F078EC, 000, 001, 000C458)^M
000C3A0  00100440135 (02F0058, 00076F1908A, 00180132457, 001802BEDF0)^M
000C5C0  00076F19BBD (0010043F780, 001004CB9E0, 092EB10, 00D)^M
000C5C0  00076F198C2 (00076F139B0, 0010043F780, 00076F532B8, 0080001)^M
000C5C0  0010045133C (02F, 000, 0018022D780, 00180294A00)^M
000CCD0  0018004A826 (000, 000, 000, 000)^M
000  00180048353 (000, 000, 000, 000)^M
000FFF0  00180048404 (000, 000, 000, 000)^M
End of stack trace


Scenario:

The crashes occur if while moving the cursor it reaches or is near the bottom
of the screen. Crashes have occurred in vim, mutt, and man since installing
this version.


Regards,

Apologies. New release uploaded.
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: XWin problem (xinit launche twice)

2020-05-21 Thread Franz Fehringer via Cygwin
There is maybe a race (condition) i just managed starting xinit only
once (where it was started twice all the time).

Am 21.05.2020 um 19:50 schrieb Franz Fehringer:
> Hi Marco,
>
> With a little delay i made some experiments as suggested by you
> (disclaimer: i know that top posting is frowned upon in this group but
> here it goes):
> PATH=/usr/bin startxwin
> -> only one xinit (started from mintty / bash)
> startxwin -- -listen tcp -nowgl
> -> same (only one)
> C:\Programs\Cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec
> /usr/bin/startxwin -- -listen tcp -nowgl"
> two xinitS are started (started from cmd)
> Tested on my business laptop with Windows 1903 latest and Cygwin latest
> No .startxwinrc and no modification of /etc/X11/xinit/startxwinrc
> With the cmd / run / quote variant also two xinitS on my private
> notebook with Windows 1909 latest and Cygwin latest
> But the cmd / run / quote exercise gives only ane xinit on my private
> desktop (again Windows 1909 latest and Cygwin latest)?
> In fact i start not via cmd but using a desktop icon / link.
> The extra arguments are for starting WSL X11 clients.
> LC_ALL=de_DE.utf8 (all three)
> To be continued
>
> Franz
>
>
> Am 17.05.2020 um 18:42 schrieb Marco Atzeri via Cygwin:
>> On 17.05.2020 13:00, Franz Fehringer via Cygwin wrote:
>>>
>>> Am 17.05.2020 um 12:23 schrieb Marco Atzeri:
 On 17.05.2020 12:15, Franz Fehringer via Cygwin wrote:
> This is a repost, because sending to group gmane.os.cygwin seemingly
> did
> not get through.
>
>
 Hi Franz,

 can you follow guideline and provide the cygcheck.out as attachement ?
> Problem reports:  https://cygwin.com/problems.html
 How are you starting Xwin ?
 Have you any custom setting ?
 (eg a .startxwinrc on your home, or similar)
>> and about these ?
>>
 Regards
 Marco


>>> Here it is.
>>>
>> what happens if you run just
>>
>>    PATH="/usr/bin" startxwin
>>
>> -- 
>> Problem reports:  https://cygwin.com/problems.html
>> FAQ:  https://cygwin.com/faq/
>> Documentation:    https://cygwin.com/docs.html
>> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: [ANNOUNCEMENT] Updated: mintty 3.1.5

2020-05-21 Thread Thomas Wolff

Am 21.05.2020 um 18:56 schrieb Ken Brown via Cygwin:

On 5/21/2020 12:36 PM, Marco Atzeri via Cygwin wrote:

On 21.05.2020 16:48, Ken Brown via Cygwin wrote:

On 5/20/2020 11:34 AM, Thomas Wolff wrote:

I have uploaded mintty 3.1.5 with the following changes:





The homepage is at http://mintty.github.io/
It also links to the issue tracker.


After this release the right Alt key on my keyboard has lost some 
functionality.  Alt-f and Alt-b no longer move forward and backward 
across words, and Alt-d no longer deletes the following word. 
Alt-Backspace still deletes the previous word.  I'm using a standard 
US keyboard.


these functionalities are on the left ALT key on my German Keyboard


Prior to this update, these functionalities worked with both Alt keys 
on my keyboard.  Now they work only with the left Alt key.  I should 
have said that in my original report.
A change for the combination Ctrl+right-Alt was made on purpose 
following a discussion in https://github.com/mintty/mintty/issues/969. 
Apparently this change got too far. Please use the left Alt key until 
this gets sorted out for another release.

Thomas
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: XWin problem (xinit launche twice)

2020-05-21 Thread Marco Atzeri via Cygwin

On 21.05.2020 20:07, Franz Fehringer wrote:

There is maybe a race (condition) i just managed starting xinit only
once (where it was started twice all the time).



A race it is possible.

Sometimes I see xinit or Xwin stuck and I need to kill X,
while the second time goes fine.

May be in your case the first is stuck and a second istance is
risen again.


Running starxwin from mintty is more likely to work for me
the first time. I assume the AV is causing a delay in loading
the libraries and the second repetition takes less time and avoid the
race.

Regards
Marco
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


XWindows curiosity with two cygwin instances

2020-05-21 Thread Jim Garrison via Cygwin
I have my normal Cygwin+Cygwin/X instance at c:\cygwin64.  I've
temporarily set up another instance (no X) at u:\cygwin64.  I notice
that if I start up the X server on the first instance, X programs
started under the second instance cannot connect to the XServer.
They always get, for example:

jim@HOME10 ~
$ xclock
Error: Can't open display: :0

But this works just fine if I run the same command in a mintty window
launched under the first instance.

This happens even with "Disable access control" set, and also
"xhost +".  I also tried DISPLAY=localhost:0 but that doesn't
work because the X Server isn't listening on port 6000.

Is this an artifact of how Cygwin/X emulates unix sockets?

What option do I need to change to have the XServer listen on
port 6000?

TIA

-- 
Jim Garrison j...@acm.org
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


[ANNOUNCEMENT] minizip 2.9.2-1

2020-05-21 Thread Ken Brown via Cygwin-announce
The following packages have been uploaded to the Cygwin distribution:

* minizip-2.9.2-1
* libminizip2.5-2.9.2-1
* libminizip-devel-2.9.2-1

minizip is a drop-in replacement for zlib's minizip that includes
WinZip AES encryption, disk splitting, I/O buffering and some
additional fixes.

This release is a switch from the minizip that was packaged with zlib
to a fork of it maintained here:

  https://github.com/nmoinvaz/minizip

Ken Brown
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: XWindows curiosity with two cygwin instances

2020-05-21 Thread Jim Garrison via Cygwin
On 5/21/2020 5:28 PM, Jim Garrison via Cygwin wrote:
> I have my normal Cygwin+Cygwin/X instance at c:\cygwin64.  I've
> temporarily set up another instance (no X) at u:\cygwin64.  I notice
> that if I start up the X server on the first instance, X programs
> started under the second instance cannot connect to the XServer.
> They always get, for example:
> 
> jim@HOME10 ~
> $ xclock
> Error: Can't open display: :0

I figured out how to add the -listen tcp option in xlaunch, and was
able to connect over TCP between Cygwin instances.  So I assume the
earlier problem had to do with emulation of unix sockets between
two instances of cygwin.dll.

-- 
Jim Garrison j...@acm.org
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple