DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=iLAxnsskG1+eK3tv
	FUmlH9+JGRw9wc12qtUEy2LGGJalfUHEOO42/e9od2hIC7D8Ny75pqMZJIQz5Fmu
	Aljkgc/d56TvFC0/KIpbhK37cG5eA4FgQmpuBmWS6YWx3Q0+yWOZi0akqQyIK1OZ
	f2OeAgYSbj+My587SIFiniO5tzg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: chere (=> windows explorer context menu) not working with German umlaut in Path
To: cygwin AT cygwin DOT com
References: <trinity-8fe5be0c-931f-4fc0-bc58-ae19dfe67321-1520588413836 AT 3c-app-gmx-bs45>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <0cb93e6b-53c8-7019-5de6-2735ec30040f@towo.net>
Date: Sat, 10 Mar 2018 12:56:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <trinity-8fe5be0c-931f-4fc0-bc58-ae19dfe67321-1520588413836@3c-app-gmx-bs45>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Am 09.03.2018 um 10:40 schrieb Josef Frank:
> The "chere" package installs an entry in the windows explorer context menu to open a mintty window running bash at an arbitrary location.
>
> However the context menu entry "Bash prompt here" does not work, when the directory path contains a German umlaut in any position. E.g.: using it for c:/temp/ö results in a Bash prompt opened in _c:/temp_, while opening a windows cmd prompt via context menu also works with umlauts in the path.
This has been reported before: 
https://cygwin.com/ml/cygwin/2016-09/msg00239.html
I though I had responded then but apparently I didn’t; the issue is 
described on the mintty Tips wiki page:
https://github.com/mintty/mintty/wiki/Tips#creating-a-folder-context-menu-entry-for-mintty

> How do I resolve this issue?
By fixing chere/xhere to handle the additional quoting magically added 
by Windows in this case,
or by using the mintty --dir option instead of xhere.

Thomas

> FYI:
>
> 1. created registry entry is c:\opt\cygwin\bin\mintty.exe -e /bin/xhere /bin/bash.exe "%L" (in extended context menu "%L" is replaced by "%V"; but this also does not work)
>
> 2. locale setting in cygwin: LANG=de_DE.UTF-8
>
> 3. File system is NTFS. Therefore file names are claimed to be stored in "Unicode", whatever this means in the respective documentation (Windows Dev Center description of encoding for file names[https://msdn.microsoft.com/en-us/library/windows/desktop/dd317748%28v=vs.85%29.aspx])
>
> 4. Codepage in CMD-window: 850 (according to powershell command [System.Text.Encoding]::Default)
>
> 5. Windows codepage: 1252
>
> 6. All three programs (windows explorer, cmd.exe, bash in mintty) show the umlaut in consistent manner despite different encodings
>
> 7. Renaming files is not possible as the problem mainly arises on network drives with folders/files that are a) referred to by lots of links (symbolic as well as windows shortcuts) and b) owned/shared by multiple different users
>
> Greatly would appreciate help
> Thanks in advance
> JF
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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