Hello!
When using cygwin, i can't list, copy, remove files and directories with
128 utf-8 symbol long names.
useless examples that illustrates the problem:
it is OK with latin symbols:
$ a="$(perl -e 'print "x"x255')"; touch "$a" && { ls "$a"; rm "$a"; }
x
On Tue, Dec 10, 2013 at 03:42:04AM +, Guy Harrison wrote:
>It has likely been over a decade since Chris blasted me into orbit over
>something I stuck my head over the parapet for(*). Corinna I don't
>think I've ever wrangled with. Nevertheless, with the New Year
>beckoning it is about time I
Hi,
It has likely been over a decade since Chris blasted me into orbit over
something I stuck my head over the parapet for(*). Corinna I don't think
I've ever wrangled with. Nevertheless, with the New Year beckoning it is
about time I acknowledged just how much easier life has been because of
On Mon, Dec 09, 2013 at 05:08:20PM +0100, Bj?rn Kautler wrote:
>Ok, so you are telling me that it is "nothing" if a small - probably
>unintended - change breaks the whole vim functionality? o_O
>Especially if there is a fix as small as the erroneous change?
>C'mon, you're kidding me, aren't you?
M
On Mon, Dec 09, 2013 at 08:59:26PM +, Jon TURNEY wrote:
>On 09/12/2013 20:47, Christopher Faylor wrote:
>> On Sun, Dec 08, 2013 at 05:36:16PM +, Jon TURNEY wrote:
>>> I don't really understand the intricacies of cygwin signal delivery,
>>> but I see that it can suspend the target thread to
On 09/12/2013 20:47, Christopher Faylor wrote:
> On Sun, Dec 08, 2013 at 05:36:16PM +, Jon TURNEY wrote:
>> I don't really understand the intricacies of cygwin signal delivery,
>> but I see that it can suspend the target thread to determine if it's in
>> a safe place to deliver the signal (outs
On Sun, Dec 08, 2013 at 05:36:16PM +, Jon TURNEY wrote:
>I don't really understand the intricacies of cygwin signal delivery,
>but I see that it can suspend the target thread to determine if it's in
>a safe place to deliver the signal (outside a win32 API call). I think
>that sometimes the thr
On 12/09/2013 03:39 PM, Jim Cant wrote:
I have a problem with Cygwin's Perl. If a process started by Perl
(system(), `` (backticks) ) crashes, the system debugger never getsww
called so I can't get a dump.
Have you tried perl dump?
http://perldoc.perl.org/functions/dump.html
--
- Bartels
--
SQLite is a software library that implements a self-contained,
serverless, zero-configuration, transactional SQL database engine
Changes since 3.8.1-1
=
* Updated to upstream 3.8.2 release. Main features:
* Added support for WITHOUT ROWID tables.
* Extend the maximum path l
Ok, so you are telling me that it is "nothing" if a small - probably
unintended - change breaks the whole vim functionality? o_O
Especially if there is a fix as small as the erroneous change?
C'mon, you're kidding me, aren't you?
Whatever, I'll NOT continue on this topic.
I have a working workarou
On Mon, Dec 09, 2013 at 04:40:19PM +0100, Bj?rn Kautler wrote:
>If you mean. "Let's focus on the small bug Bj?rn reported instead of
>talking about vi vs. vim", I'm absolutely on your side Christopher.
http://en.wikipedia.org/wiki/Much_Ado_About_Nothing
--
Problem reports: http://cygwin.com
If you mean. "Let's focus on the small bug Björn reported instead of
talking about vi vs. vim", I'm absolutely on your side Christopher.
2013/12/9 Christopher Faylor:
> On Mon, Dec 09, 2013 at 03:03:37PM +0100, Frank Fesevur wrote:
>>2013/12/9 Corinna Vinschen:
>>> The new vim layout closely refle
On Mon, Dec 09, 2013 at 03:03:37PM +0100, Frank Fesevur wrote:
>2013/12/9 Corinna Vinschen:
>> The new vim layout closely reflects the Fedora packaging. It has a
>> minimal vi in the vim-minimal package and a full-featured vim in the
>> vim-enhanced package. I'm using a vi -> vim alias on Fedora
I have a problem with Cygwin's Perl. If a process started by Perl
(system(), `` (backticks) ) crashes, the system debugger never getsww
called so I can't get a dump.
I have submitted the problem (see
below) to this list but got no responses. Can anyone suggest somewhere
else I might look for an
The special handling of vi is just fine.
The whole problem is that not only the vi behaviour changed, but also
the vim behaviour.
Which is why I suggested the solutions I suggested.
2013/12/9 Frank Fesevur :
> 2013/12/9 Björn Kautler:
>> Again, what I talk about is NOT an issue of vi vs. vim.
>> W
2013/12/9 Björn Kautler:
> Again, what I talk about is NOT an issue of vi vs. vim.
> What I talk about is a breaking change in vim that was introduced
> while doing a change for vi.
> But it is NOT an issue of vi vs. vim.
That patch was introduced when people started to complain that they
got erro
2013/12/9 Corinna Vinschen:
> The new vim layout closely reflects the Fedora packaging. It has a
> minimal vi in the vim-minimal package and a full-featured vim in the
> vim-enhanced package. I'm using a vi -> vim alias on Fedora for ages.
That explains why Yaakov did this. I assume Yaakov is a
Again, what I talk about is NOT an issue of vi vs. vim.
What I talk about is a breaking change in vim that was introduced
while doing a change for vi.
But it is NOT an issue of vi vs. vim.
Here again my original mail:
Hi Yaakov,
I'm wondering that noone mentioned it before, but maybe everyone is
On Dec 9 13:34, Frank Fesevur wrote:
> 2013/12/9 Björn Kautler:
> > I don't have a problem with being mean.
> > Everyone makes mistakes.
> > I just wonder that it gets broken silently without obvious (to me) reason
> > and a question regarding it and with two proposed solutions just stays
> > igno
I'm sorry, but I don't really understand what you mean.
Alternatives are not a problem to me.
The patch I mentioned originally changes the file where the full vim
looks for its configuration file.
And beause of the missing configuration file at the new place, the
full vim behaves as if it were the
2013/12/9 Björn Kautler:
> I don't have a problem with being mean.
> Everyone makes mistakes.
> I just wonder that it gets broken silently without obvious (to me) reason
> and a question regarding it and with two proposed solutions just stays
> ignored while it would be very easy to fix.
To me, th
Hi Cygwin friends and users,
I just released Cygwin 1.7.27-2. It differes from 1.7.27-1 only by
this change:
- Fix include/cygwin/stdlib.h header to use the _XOPEN_SOURCE feature
test macro in a secure way. Without this change, you might encounter
an error when building an application whic
Hi Frank,
I don't have a problem with being mean.
Everyone makes mistakes.
I just wonder that it gets broken silently without obvious (to me) reason
and a question regarding it and with two proposed solutions just stays
ignored while it would be very easy to fix.
Regards
Björn
2013/12/9 Frank F
2013/12/7 Björn Kautler:
> And it is ok and accepted that such a patch breaks the functionality?
Apparently that depends on the maintainer.
One maintainer does his best not to break existing installations:
http://cygwin.com/ml/cygwin/2013-12/msg00059.html
And another introduces a new version
htt
24 matches
Mail list logo
