Thanks Larry.
I think you're misunderstanding where the limitation is coming from.
I don't think I'm misunderstanding anything - I was actually thinking
along the same lines that you just wrote.
I feel that with increasing monitors sizes == increasing window sizes,
it might happen more often,
Greetings, Sous Lesquels!
Thanks Andrey.
You're misunderstanding Cygwin, if you are asking such questions.
Care to clarify how am I misunderstanding Cygwin?
I'm not in the mood of retyping the POSIX standard for you.
If you could convince ConEmu developers to provide adequate TTY
On 08/28/2015 09:23 AM, Sous Lesquels wrote:
Thanks Larry.
I think you're misunderstanding where the limitation is coming from.
I don't think I'm misunderstanding anything - I was actually thinking
along the same lines that you just wrote.
OK, good. We're on the same page then. :-)
I
Greetings, Sous Lesquels!
I'm not in the mood of retyping the POSIX standard for you.
But you are obviously always in the mood to be unhelpful...
If you do not like the answer to your question, it doesn't make the answer
wrong, or unhelpful, or what-you-have-called-it.
I'm personally
On Aug 28, 2015, at 2:49 PM, Sous Lesquels a9f5...@gmail.com wrote:
Console size to me sounds like some kind of buffer
overflow
Quite possibly.
not some intrinsically non-POSIX thing that MS console does.
Andrey wasn’t trying to tell you that the bug is happening because of a POSIX
On Aug 28, 2015, at 7:23 AM, Sous Lesquels a9f5...@gmail.com wrote:
I feel that with increasing monitors sizes == increasing window sizes,
You’re making an unwarranted assumption. Increasing monitor sizes do not
require increasing window widths.
As we saw in my original testing, the
I'm not in the mood of retyping the POSIX standard for you.
But you are obviously always in the mood to be unhelpful...
I'm personally acquainted with the creator of ConEmu and he's not working for
Microsoft.
And this breaks without ConEmu. If you forget I said that I use ConEmu
and run my
Thanks Larry.
OK, good. We're on the same page then. :-)
Indeed we are :)
it's hard to say there's going to be a good solution coming from Cygwin
itself soon, unless there's some developer that wants to chase this in the
near-term.
I certainly hope so. At least, to peek and determine
Thanks cyg Simple.
It depends on the level of support you want from this list
In this case, if Cygwin is supposed to work with the regular windows
console? If mintty was created due to Cygwin *not working as expected*
on default windows console, that's a good answer, as long as it's
correct. If
Thanks Andrey.
You're misunderstanding Cygwin, if you are asking such questions.
Care to clarify how am I misunderstanding Cygwin?
If you could convince ConEmu developers to provide adequate TTY functionality,
You mean Microsoft? You can reproduce the exact same issue with the
native windows
On 08/27/2015 11:39 AM, Sous Lesquels wrote:
Thanks cyg Simple.
It depends on the level of support you want from this list
In this case, if Cygwin is supposed to work with the regular windows
console? If mintty was created due to Cygwin *not working as expected*
on default windows console,
On 8/25/2015 12:35 PM, Sous Lesquels wrote:
Thanks Philip - I agree with that and it's even nicely described in ConEmu
docs:
http://conemu.github.io/en/CygwinAnsi.html
While it might be a hack to get this working, mintty is not something
that should be run in ConEmu, as both are terminal
Thanks Philip - I agree with that and it's even nicely described in ConEmu docs:
http://conemu.github.io/en/CygwinAnsi.html
While it might be a hack to get this working, mintty is not something
that should be run in ConEmu, as both are terminal emulators.
Anyway, I guess the question is - is
Greetings, Sous Lesquels!
Thanks Philip - I agree with that and it's even nicely described in ConEmu
docs:
http://conemu.github.io/en/CygwinAnsi.html
While it might be a hack to get this working, mintty is not something
that should be run in ConEmu, as both are terminal emulators.
For various usability reasons (tabs being the biggest I think), I'm
using ConEmu (https://github.com/Maximus5/ConEmu) and running bash
directly from it. I am not sure if it's even possible to use mintty -
it just might run console - mintty - bash, so might present the same
issue - but will
Thanks Warren.
After sending the window full-screen, lookee lookee:
2014/11/04 17:40:58 Ending cygwin install
112 [main] vi 4424 C:\cygwin64\bin\vi.exe: *** fatal error - cmalloc would
have returned NULL
/x: line 6: 4424 Hangup vi -c q /var/log/setup.log
It happened
On Aug 21, 2015, at 6:37 AM, Sous Lesquels a9f5...@gmail.com wrote:
It happened on the first run, with a 317x85 window and lines of
scrollback buffer.
OK, at least it's reproducible by one more person :)
A replicable bug is a dead bug. All that’s needed is for someone to spend the
Am 21.08.2015 um 14:37 schrieb Sous Lesquels:
However, assuming it is not possible to run mintty under ConEmu ...
It is.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Aug 20, 2015, at 10:34 AM, Sous Lesquels a9f5...@gmail.com wrote:
I don't think this message will thread correctly.
Actually, it did here.
However, just had a completely fresh Win7 and Cygwin install
You are aware that Microsoft is giving out free Windows 10 upgrades to valid
Windows 7
--- Prelude
I don't think this message will thread correctly. This is a reply to
this message:
https://cygwin.com/ml/cygwin/2014-07/msg00191.html
Message-ID: 20140717082423.gb15...@calimero.vinschen.de
I unsubscribed from the list in order not to get emails for the whole
list (most of which
Thanks Warren.
Actually, it did here.
I see it separate, at least in a Web browser:
- This thread: https://cygwin.com/ml/cygwin/2015-08/threads.html#00347
- The original thread I tried to reply to:
https://cygwin.com/ml/cygwin/2014-07/threads.html#00185
My intention was to reply to this
Greetings, Warren Young!
On Aug 20, 2015, at 10:34 AM, Sous Lesquels a9f5...@gmail.com wrote:
I don't think this message will thread correctly.
Actually, it did here.
However, just had a completely fresh Win7 and Cygwin install
You are aware that Microsoft is giving out free Windows 10
On Aug 20, 2015, at 4:21 PM, Sous Lesquels a9f5...@gmail.com wrote:
I continue to be unable to reproduce your symptom under Windows 10
Just to confirm - you did set the params of cmd.exe one to this:
Screen Buffer Size: 208w h
Window Size: 208w 69h
Oh, I’ve been assuming that it was
On Mon, Jul 21, 2014 at 12:32:34PM +, Nellis, Kenneth wrote:
From: sous lesquels
snip
If you can't wait, then read the message using your browser and click
on the Raw text link near the top. The first line will say something
like From cygwin-return-191383-listarch-cygwin=...
Note
From: sous lesquels
snip
If you can't wait, then read the message using your browser and click
on the Raw text link near the top. The first line will say something
like From cygwin-return-191383-listarch-cygwin=...
Note the message number 191383.
Then you send an empty message to
It's not reproducible for me. I just tried your ssh scenario with a
1000 and 2000 line buffers and it works fine for me every time, be it
with Cygwin 1.7.30 or the latest snapshot. I also raised the number of
loops. Is it possible that you're suffering a BLODA(*) problem?
Thanks,
On 07/18/2014 10:48 AM, sous lesquels wrote:
It's not reproducible for me. I just tried your ssh scenario with a
1000 and 2000 line buffers and it works fine for me every time, be it
with Cygwin 1.7.30 or the latest snapshot. I also raised the number of
loops. Is it possible that you're
Thanks Larry.
This is not the recommended way of handling this situation. You end up
with a .new extension if the DLL was in use at the time of your upgrade.
In this case, setup*.exe schedules a replace of your existing DLL with the
.new version on reboot. So if you find such a file on your
On Fri, Jul 18, 2014 at 12:59:10PM -0400, sous lesquels wrote:
Any suggestions? Or is this not as common use case as I think it is?
Craft your reply with the appropriate In-Reply-To header tag and it
will maintain threading.
There is no automated way to do that if you are using the digest.
From: Christopher Faylor
There is no automated way to do that if you are using the digest. Digests
are intended for casual perusal of the list, not for active communication.
FWIW, I get digest format, but still make threaded replies (such as this) with
a few extra steps that may not be
If you can wait for the digest, you can simply open the selected message from
the digest and reply to that, and it will be threaded.
Using Gmail, it doesn't seem to offer a way to see them as separate
mails or reply to a particular one, though. Oh, well...
If you can't wait, then read the
On Jul 16 16:29, sous lesquels wrote:
A few more things to add:
- This crashes under the regular Windows console, i.e. run cmd.exe,
then bash, then follow the above
- It also crashes under some other emulators (I actually noticed it
under ConEmu, see
On 7/17/2014 02:24, Corinna Vinschen wrote:
It's not reproducible for me. I just tried your ssh scenario with a
1000 and 2000 line buffers
Confirmed.
I tried up to , the maximum allowed.
This is under Windows 8.1 Pro, with Cygwin 1.7.30, both 32- and 64-bit.
--
Problem reports:
Environment
CYGWIN_NT-6.1 1.7.29(0.272/5/3) 2014-04-07 13:46
Windows 7
Steps to reproduce the issue:
- With vi.exe
Execute the following bash script:
#!/bin/bash
for i in {1..123}; do
echo -e \033[5A\033[50C\033[0;35mhello\033[0m
head -n1000 /var/log/setup.log
done
vi
A few more things to add:
- This crashes under the regular Windows console, i.e. run cmd.exe,
then bash, then follow the above
- It also crashes under some other emulators (I actually noticed it
under ConEmu, see
https://code.google.com/p/conemu-maximus5/issues/detail?id=1644),
though this is
On Wed, Jul 16, 2014 at 04:29:54PM -0400, sous lesquels wrote:
A few more things to add:
- This crashes under the regular Windows console, i.e. run cmd.exe,
then bash, then follow the above
You've discovered that Cygwin has limits. You can't run it with console
windows that are too big. Sorry.
36 matches
Mail list logo
