I have uploaded mintty 2.2.2 with the following changes:
* Tweaked taskbar grouping behaviour (#486).
* Advice on avoiding trouble with taskbar grouping and icon
consistence in manual page and wiki Tips page (#420, #486, ~#471).
* Fixed New window option from window title menu on multi
etings, Brian Mathis!
>>>>>
>>>>>> I recently updated to the latest set of cygwin packages, and something
>>>>>> has broken the terminal icon when pinned to the start menu. When
>>>>>> starting from the Start menu "Cygwi
n pinned to the start menu. When
> > > starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> > > normally, loads my user profile, and the cwd is set to ~.
> >
> > > However, if I right-click the icon on the taskbar and select "Pin to
>
On Nov 11 06:53, Andrey Repin wrote:
> Greetings, Brian Mathis!
>
> > I recently updated to the latest set of cygwin packages, and something
> > has broken the terminal icon when pinned to the start menu. When
> > starting from the Start menu "Cygwin Terminal"
mething
> > > > has broken the terminal icon when pinned to the start menu. When
> > > > starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> > > > normally, loads my user profile, and the cwd is set to ~.
> > >
> &
; I recently updated to the latest set of cygwin packages, and something
>>>>> has broken the terminal icon when pinned to the start menu. When
>>>>> starting from the Start menu "Cygwin Terminal" icon, mintty comes up
>>>>> normally, loads my use
I recently updated to the latest set of cygwin packages, and something
has broken the terminal icon when pinned to the start menu. When
starting from the Start menu "Cygwin Terminal" icon, mintty comes up
normally, loads my user profile, and the cwd is set to ~.
However, if I r
Greetings, Brian Mathis!
> I recently updated to the latest set of cygwin packages, and something
> has broken the terminal icon when pinned to the start menu. When
> starting from the Start menu "Cygwin Terminal" icon, mintty comes up
> normally, loads my user profi
I have uploaded mintty 2.2.1 with the following changes:
Major New Search Feature (thanks to Kai (twitter:@sixhundredns)):
* Search scrollback buffer (#85); shortcuts Alt+F3 or Shift+Ctrl+H;
configuration options.
Window placement and Multi-Monitor support:
* Option -p @N to select
I have uploaded mintty 2.2.1 with the following changes:
Major New Search Feature (thanks to Kai (twitter:@sixhundredns)):
* Search scrollback buffer (#85); shortcuts Alt+F3 or Shift+Ctrl+H;
configuration options.
Window placement and Multi-Monitor support:
* Option -p @N to select
Self answered here.
This is an issue about 256 color support for vim background in tmux,
check the solution over
http://superuser.com/questions/399296/256-color-support-for-vim-background-in-tmux/399326#399326.
Thanks
2015-10-24 17:16 GMT+08:00 kuaf :
> Hi list,
>
> I want a
Hi list,
I want a perfect Vim edit environment based on Pencil theme [1].
Toggle light/dark background without Tmux, it looked well.
The configuration involved:
- .bashrc, add custom Pencil theme by way of `echo -ne ...`
- .bashrc, `export TERM=xterm-256color`
- .vimrc, add
set t_Co=256
am getting a
hang every time I try to exit a Mintty window after using SSH.
What makes this issue more interesting is that I cant always reproduce
it. It only happens after I have long standing SSH sessions.
After I press "CTL + a + d" the final time when I am back at the
cygwin login prompt.
Sorry for the extra replies.
I am going to try to do some more research on the issue. After letting
a mintty window sit open and typing absolutely nothing inside it and
then closing it about 5 minutes later it hangs on exit.
Very strange behavior. Im not seeing it so bad on my other computers
ge
set.
The problem continues on that installation as well.
On Thu, Sep 17, 2015 at 2:10 AM, Bryan Tong <cont...@nullivex.com> wrote:
> Hello,
>
> I recently upgraded to Windows 10 and ever since I have I am getting a
> hang every time I try to exit a Mintty window after using SSH.
>
; 32bit. I install nano, vim, ssh, ping as well was the base package
> set.
>
> The problem continues on that installation as well.
>
> On Thu, Sep 17, 2015 at 2:10 AM, Bryan Tong <cont...@nullivex.com> wrote:
>> Hello,
>>
>> I recently upgraded to Windo
st
>> linux-libertine-fonts, xorg-server, & xfs, but I can't get latest
mintty
>> to
>> offer it as a font, from either the console or X. (It does offer
>> Liberation Mono.) Suggestions on things I can try besides the reboot
>> I've
>> already done?
>
Am 27.09.2015 um 19:29 schrieb J.D. Laub:
In windows7 I've installed the Linux Libertine Mono O Mono font, and use
it for putty. Wanting to use the same in cygwin, I've installed the latest
linux-libertine-fonts, xorg-server, & xfs, but I can't get latest mintty to
offer it as a font,
In windows7 I've installed the Linux Libertine Mono O Mono font, and use
it for putty. Wanting to use the same in cygwin, I've installed the latest
linux-libertine-fonts, xorg-server, & xfs, but I can't get latest mintty to
offer it as a font, from either the console or X. (It does o
Hello,
I recently upgraded to Windows 10 and ever since I have I am getting a
hang every time I try to exit a Mintty window after using SSH.
What makes this issue more interesting is that I cant always reproduce
it. It only happens after I have long standing SSH sessions.
After I press &quo
On 17/09/2015 10:10, Bryan Tong wrote:
Hello,
I recently upgraded to Windows 10 and ever since I have I am getting a
hang every time I try to exit a Mintty window after using SSH.
What makes this issue more interesting is that I cant always reproduce
it. It only happens after I have long
On Sep 17, 2015, at 3:05 PM, Thomas Wolff wrote:
>
>> what happens if you type "exit" instead of "ctl + a + d" ?
> What is ctl+a+d anyway? Both ctrl+a and ctrl+d in sequence?
It’s probably some bit of voodoo learned in a situation where Ctrl-D alone
didn’t do what the OP wanted. Ctrl-A goes to
Am 17.09.2015 um 12:14 schrieb Marco Atzeri:
On 17/09/2015 10:10, Bryan Tong wrote:
Hello,
I recently upgraded to Windows 10 and ever since I have I am getting a
hang every time I try to exit a Mintty window after using SSH.
First: a hang is not a crash.
What makes this issue more
der if anyone can confirm or deny the issue.
>
> 1. Start mintty as `mintty.exe -` (i.e. login shell)
> 2. Execute a command. S.a. "ssh anywhere"
> 3. Exit all running apps. I.e. ^D out of all shells.
> 4. mintty remains running.
> There's no more child
Greetings, Thomas Wolff!
Am 22.08.2015 um 06:31 schrieb Sam Edge:
On 22/08/2015 05:05, John Hein wrote:
Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
Just noticed a weird thing. Wonder if anyone can confirm or deny the
issue.
1. Start mintty as `mintty.exe -` (i.e. login
On 22/08/2015 05:05, John Hein wrote:
Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
Just noticed a weird thing. Wonder if anyone can confirm or deny the issue.
1. Start mintty as `mintty.exe -` (i.e. login shell)
2. Execute a command. S.a. ssh anywhere
3. Exit all running apps
Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
Just noticed a weird thing. Wonder if anyone can confirm or deny the issue.
1. Start mintty as `mintty.exe -` (i.e. login shell)
2. Execute a command. S.a. ssh anywhere
3. Exit all running apps. I.e. ^D out of all shells.
4. mintty
Am 22.08.2015 um 06:31 schrieb Sam Edge:
On 22/08/2015 05:05, John Hein wrote:
Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
Just noticed a weird thing. Wonder if anyone can confirm or deny the issue.
1. Start mintty as `mintty.exe -` (i.e. login shell)
2. Execute a command
On 22/08/2015 05:54, Thomas Wolff wrote:
Am 22.08.2015 um 06:31 schrieb Sam Edge:
On 22/08/2015 05:05, John Hein wrote:
Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
Just noticed a weird thing. Wonder if anyone can confirm or deny
the issue.
1. Start mintty as `mintty.exe
Greetings, All!
Just noticed a weird thing. Wonder if anyone can confirm or deny the issue.
1. Start mintty as `mintty.exe -` (i.e. login shell)
2. Execute a command. S.a. ssh anywhere
3. Exit all running apps. I.e. ^D out of all shells.
4. mintty remains running.
There's no more child processes
I have uploaded mintty 2.1.5 with the following changes:
* Guard Shift-Ctrl-0 detection (#233) to avoid interference with
keyboard switchers (#472).
* Basic fixes for displaying child process list on exit confirmation
(#448).
The homepage is at http://mintty.github.io/
It also links
I have uploaded mintty 2.1.5 with the following changes:
* Guard Shift-Ctrl-0 detection (#233) to avoid interference with
keyboard switchers (#472).
* Basic fixes for displaying child process list on exit confirmation
(#448).
The homepage is at http://mintty.github.io/
It also links
Using mintty 2.1.4-0, I can't seem to disable font bolding. The font
is Lucida Console 8pt. I have unchecked Show bold as font and Show
bold as colour, but I still see bold fonts rendered with extra width.
Is there a way to disable this feature?
Thanks,
Jeremy Hetzler
--
Problem reports
Am 08.08.2015 um 18:31 schrieb Jeremy Hetzler:
Using mintty 2.1.4-0, I can't seem to disable font bolding. The font
is Lucida Console 8pt. I have unchecked Show bold as font and Show
bold as colour, but I still see bold fonts rendered with extra width.
Is there a way to disable this feature
Am 07.08.2015 um 11:12 schrieb Kptain:
Hi,
After starting mintty 2.1.4 based from Cygwin package 2.2.0 (windows 8.1),
I've still same issue as with previous packages 2.1.2 and 2.1.3:
PC is crashing with this message: UnexpectedKernelModeTrap
Please note also that:
- same mintty 2.1.4
Hi,
After starting mintty 2.1.4 based from Cygwin package 2.2.0 (windows 8.1),
I've still same issue as with previous packages 2.1.2 and 2.1.3:
PC is crashing with this message: UnexpectedKernelModeTrap
Please note also that:
- same mintty 2.1.4 is working well from Windows 7.
- old mintty
I have uploaded mintty 2.1.4 with the following changes:
• Not zooming font on Shift+Windows shortcuts (#467), by heuristic
analysis of Windows messages.
• Not daemonizing if started from ConEmu (#466), by heuristic check
of $ConEmuPID.
The homepage is at http://mintty.github.io/
It also
I have uploaded mintty 2.1.4 with the following changes:
• Not zooming font on Shift+Windows shortcuts (#467), by heuristic
analysis of Windows messages.
• Not daemonizing if started from ConEmu (#466), by heuristic check
of $ConEmuPID.
The homepage is at http://mintty.github.io/
It also
Thomas Wolff towo at towo.net writes:
Zooming:
* Control-middle-mouse click resets zooming, complementing
Control-mouse-wheel scroll in analogy to Control-+/-/0.
* New option ZoomMouse=off to disable mouse-wheel zooming.
* Enabled Shift-Ctrl-0 to reset zooming for font and window
:
https://github.com/mintty/mintty/issues/467
Apparently my idea to interpret Shift consistently in this context to
keep window and font zooming in sync wasn't that good,
considering that some special shortcuts need Shift.
On the other hand, I'd like to retain the function for those cases that
can
), with the
new feature being *enabled* by the -d switch? Wouldn't -daemon also
make more sense than -nodaemon?
Had the same question.
Because the purpose of the new behaviour is to ensure normal operation
when mintty is called from a cygwin console, i.e. within a normal cygwin
environment. Unfortunately
Greetings, Jim Reisert AD1C!
Please disregard this post. Checking the changelog reveals that this is
caused by a new feature, and can be overridden with the -d (--nodaemon)
switch.
Why isn't the old behavior the default (spawn one process), with the
new feature being *enabled* by the -d
Please disregard this post. Checking the changelog reveals that this is
caused by a new feature, and can be overridden with the -d (--nodaemon)
switch.
Why isn't the old behavior the default (spawn one process), with the
new feature being *enabled* by the -d switch? Wouldn't -daemon also
make
Please disregard this post. Checking the changelog reveals that this is
caused by a new feature, and can be overridden with the -d (--nodaemon)
switch. My fault for not R'ing TFM before posting. I apologize.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
As of update 2.1.3, MinTTY, when opening, spawns 2 child processes, the
second of which is the actual MinTTY window. This behavior is different
from MinTTY 2.1.2, which spawned one, and breaks interoperability with
ConEmu. Is there a reason why MinTTY needs to create a third process
After some trials with Cygwin 2.1.0, it appears:
mintty 2.1.2 call fails under Windows 8.
mintty 2.1.2 call succeed under Windows 7.
Could you let me knwow when package 64bits will be available for further
trials?
Regards,
K'ptain
--
View this message in context:
http://cygwin.1069669.n5
Mintty 2.1.3 has been uploaded.
Changes:
* With position option, centre or center can be specified (#208).
* Enabled new character attributes strikeout, doubly-underlined,
overlined.
Zooming:
* Control-middle-mouse click resets zooming, complementing
Control-mouse-wheel scroll in analogy
Mintty 2.1.3 has been uploaded.
Changes:
* With position option, centre or center can be specified (#208).
* Enabled new character attributes strikeout, doubly-underlined,
overlined.
Zooming:
* Control-middle-mouse click resets zooming, complementing
Control-mouse-wheel scroll in analogy
Mintty 2.1.3 has been uploaded.
Changes:
* With position option, centre or center can be specified (#208).
* Enabled new character attributes strikeout, doubly-underlined,
overlined.
Zooming:
* Control-middle-mouse click resets zooming, complementing
Control-mouse-wheel scroll in analogy
Hi Thomas,
Let me rephrase/summarize my findings:
Executing 'mintty -D' (i.e. v212)
from a shortcut to bash (i.e. Cygwin console),
will fork itself, where the child will turn itself into a session leader, as
desired.
i.e. the following code will be executed:
#if 1 // Thomas
Hi Thomas,
Moving load_dwm_funcs() did the trick ...
Tested on 32-bits and 64-bits, W7
See appendix (winmain.c)
Henri// win.c (part of mintty)
// Copyright 2008-13 Andy Koppe
// Based on code from PuTTY-0.60 by Simon Tatham and team.
// Licensed under the terms of the GNU General Public
the difference; if deselected, mintty crashes if called from
a console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread; however,
the result was kept static, so being called on a wrong assumption...
A release with the fix
Thomas Wolff sent the following at Thursday, July 23, 2015 6:15 PM
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances; mintty only detaches from the caller's terminal
if the option -D is given
Neither man mintty nor mintty --help document the new -D
styles on windows and
buttons,
that makes the difference; if deselected, mintty crashes if called from a
console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread;
Forked process, I hope :)
No, it doesn't. Loading a library
,
it is only the last of the flags, â Use visual styles on windows and
buttons,
that makes the difference; if deselected, mintty crashes if called from a
console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread;
Forked
visual styles on windows and
buttons,
that makes the difference; if deselected, mintty crashes if called from a
console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread;
Forked process, I hope :)
No, it doesn't. Loading
effects,
it is only the last of the flags, â Use visual styles on windows and
buttons,
that makes the difference; if deselected, mintty crashes if called from a
console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread
visual styles on windows and
buttons,
that makes the difference; if deselected, mintty crashes if called from a
console or somehow doubly isolated by
(setsid mintty ).
Apparently, LoadLibrary does not propagate to a forked thread;
Forked process, I hope :)
No, it doesn't. Loading
Am 27.07.2015 um 20:08 schrieb Buchbinder, Barry (NIH/NIAID) [E]:
Thomas Wolff sent the following at Thursday, July 23, 2015 6:15 PM
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances; mintty only detaches from the caller's terminal
if the option -D
On Sat, Jul 25, 2015 at 10:15 PM, Houder wrote:
...
Please, make a mental picture of the check boxes at your place at 'control
panel
performance information and tools adjust visual effects'.
I'll bet, all check boxes for eye candy has been checked at your place;
NONE of
them are
for best appearance :-))
As I totally do not appreciate the eye candy I got after enabling for best
appearance , I decided to select 'Windows Basic' (Personalization).
Guess what? 'mintty -D' crashes ...
Henri
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao
environment might be different from mine)
Confirmed.
Either
- changing to 'best appearance' (visual effects) or
- changing to 'Windows 7' (personalization)
does the trick ... i.e. mintty v211 (and v212 as modified by me, but W/O
removing the
invocation of update_transparency() ) will not crash
Hi Thomas,
Additionally ...
But first things, first ...
Please, make a mental picture of the check boxes at your place at 'control
panel
performance information and tools adjust visual effects'.
I'll bet, all check boxes for eye candy has been checked at your place;
NONE of
them are
) or at least if mintty is invoked from a
console.
Hi Thomas,
Let me rephrase/summarize my findings:
Executing 'mintty -D' (i.e. v212)
from a shortcut to bash (i.e. Cygwin console),
will fork itself, where the child will turn itself into a session leader, as
desired.
i.e. the following
at all (but
people would complain, I'm sure) or at least if mintty is invoked from a
console, as a workaround.
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info
Hi Thomas,
Maybe setsid() should not be called if fork() fails...
Could you try this please:
if (daemonize !isatty(0)) {
int pid = fork();
if (pid 0) exit(0);// exit parent process
if (pid == 0) setsid(); // detach child process
if (pid 0) {
are checked at my place ...
(I am an old fashioned guy, who wants his 8 cores to do useful things)
Now, I said, that I found the culprit, but I what I really meant, was that I
found
the function, that made mintty crash AT MY SIDE.
You still have to do all the hard work ... Sorry, I cannot help you
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
mintty only detaches from the caller's terminal if the option -D is given
Thank you, Thomas!
I extracted mintty.exe (and named it mintty-v212.exe) from
mintty-2.1.2-0.tar.xz, and
placed
Am 24.07.2015 um 15:18 schrieb Houder:
Hi Thomas,
Maybe setsid() should not be called if fork() fails...
Could you try this please:
if (daemonize !isatty(0)) {
int pid = fork();
if (pid 0) exit(0);// exit parent process
if (pid == 0) setsid(); // detach child
Hi Thomas,
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
To resolve this discomforting issue which I still cannot reproduce,
could please those who experience a crash report some details about
their calling environment?
Could the issue
As I wrote 'and I asked myself', I was wondering about something like:
'getpid() != 1'
s/getpid/getppid/
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Jul 24 13:40, Thomas Wolff wrote:
I wanted to check ttyname() for /cons but surprisingly ttyname() was null
when started from cygwin console;
Isn't mintty a subsystem=windows application which is supposed to
attach or create a console at some later point? Maybe that's the
reason. Off
On Jul 24 15:18, Houder wrote:
Hi Thomas,
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
To resolve this discomforting issue which I still cannot reproduce,
could please those who experience a crash report some details about
On 24.07.2015 09:50, Houder wrote:
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
To resolve this discomforting issue which I still cannot reproduce,
could please those who experience a crash report some details about
their calling environment
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
mintty only detaches from the caller's terminal if the option -D is given
32 bit package uploaded
64 bit package to follow
Thomas
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
mintty only detaches from the caller's terminal if the option -D is given
32 bit package uploaded
64 bit package to follow
Thomas
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren
On 7/23/2015 9:08 AM, Ismail Donmez wrote:
Hi,
Houder writes:
Hi,
Thomas Wolf writes:
mintty 2.1.1 has a bunch of requested tweaks and fixes which Iâm
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64.
Confirmed
Hi,
Thomas Wolf writes:
mintty 2.1.1 has a bunch of requested tweaks and fixes which I’m
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64. Already did a full
rebase but didn't help. Dump looks like:
Exception
On Thu, Jul 23, 2015 at 6:38 AM, Henri Houder wrote:
mintty 2.1.1 has a bunch of requested tweaks and fixes which I’m
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64.
Confirmed. Both Win7 x86 and Win7 x64
Hi,
Houder writes:
Hi,
Thomas Wolf writes:
mintty 2.1.1 has a bunch of requested tweaks and fixes which Iâm
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64.
Confirmed. Both Win7 x86 and Win7 x64
Hi,
Thomas Wolf writes:
mintty 2.1.1 has a bunch of requested tweaks and fixes which Iâm
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64.
Confirmed. Both Win7 x86 and Win7 x64.
Yes, I may be in error
Hi,
Thomas Wolf writes:
mintty 2.1.1 has a bunch of requested tweaks and fixes which Iâm
releasing before some restructuring around character attributes...
This seems to stackdump on startup for me on Win7 x64.
Confirmed. Both Win7 x86 and Win7 x64.
Henri
--
Problem reports
Ismail Donmez writes:
This seems to stackdump on startup for me on Win7 x64. Already did a full
rebase but didn't help. Dump looks like:
Sorry for the noise, this seems to be a local problem.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
mintty 2.1.1 has a bunch of requested tweaks and fixes which I’m
releasing before some restructuring around character attributes...
• The Shift key syncs font and window zooming (#233, #204).
— functions to zoom window with font (#233, Resize font and window
together):
◦ Shift+Ctrl
mintty 2.1.1 has a bunch of requested tweaks and fixes which I’m
releasing before some restructuring around character attributes...
• The Shift key syncs font and window zooming (#233, #204).
— functions to zoom window with font (#233, Resize font and window
together):
◦ Shift+Ctrl
On 21.07.2015 10:45, Houder wrote:
The trick is to make mintty NOT interact with a cons.
Not sure in what way mintty would interact with the console here.
Hi Thomas,
You are the expert on mintty now ... I only observed a pattern:
let's say maintainer... expert on terminal issues maybe
You are the expert on mintty now ... I only observed a pattern:
let's say maintainer... expert on terminal issues maybe, but not on
Windows API and specifics of POSIX process control...
Language, language, Henri!
Hi Thomas,
1. Re. You are the expert on mintty now ...
First of all, my
The trick is to make mintty NOT interact with a cons.
Not sure in what way mintty would interact with the console here.
Hi Thomas,
You are the expert on mintty now ... I only observed a pattern:
- when 'ps ax' shows that mintty is connected to a 'cons', SIGINT is ignored
- when 'ps ax
On Fri, Jul 17, 2015, at 21:03, Thomas Wolff wrote:
Am 14.07.2015 um 09:44 schrieb Ronald Fischer:
Using Cygwin 64 on Windows 7:
In a bash or zsh running inside mintty, pressing Control-C has no
effect. In a bash or zsh running in a Windows Console, it works fine.
Ronald, can you please
*this*, a mintty is started in the background.
But I can see the effect simpler in this way: Just open a DOS Command
Window, and in the command line type
c:\cygwin64\bin\zsh -c /usr/bin/mintty
and the error can be reproduced. BTW, same effect with bash instead of
zsh.
--
Problem reports
On Fri, Jul 17, 2015, at 21:03, Thomas Wolff wrote:
Am 14.07.2015 um 09:44 schrieb Ronald Fischer:
Using Cygwin 64 on Windows 7:
In a bash or zsh running inside mintty, pressing Control-C has no
effect. In a bash or zsh running in a Windows Console, it works fine.
Ronald, can you
*this*, a mintty is started in the background.
But I can see the effect simpler in this way: Just open a DOS Command
Window, and in the command line type
c:\cygwin64\bin\zsh -c /usr/bin/mintty
and the error can be reproduced. BTW, same effect with bash instead of
zsh.
Understood
But I can see the effect simpler in this way: Just open a DOS Command
Window, and in the command line type
c:\cygwin64\bin\zsh -c /usr/bin/mintty
and the error can be reproduced. BTW, same effect with bash instead of
zsh.
Understood.
For the moment, invoke mintty through
start a Ruby
program, and from *this*, a mintty is started in the background.
But I can see the effect simpler in this way: Just open a DOS Command
Window, and in the command line type
c:\cygwin64\bin\zsh -c /usr/bin/mintty
and the error can be reproduced. BTW, same effect with bash instead
I have a suspicion that the problem he is facing could be the same I
described in
https://sourceware.org/ml/cygwin/2015-02/msg00122.html
where the issue only occurs if mintty is started from the cygwin
console.
Sorry to interfere here, Thomas, but I had a hard time with your
description
... It seems to me, that SIGINT
is ignored if mintty is to interact with the dos console ...
Henri
Experiment:
1. mintty interacting with a dos console (SIGINT is ignored)
call flow:
cmd
bash
mintty ... a new window opens, where mintty/bash is NOT responsive to
SIGINT (mintty interacts with cons
Am 14.07.2015 um 11:27 schrieb Achim Gratz:
Ronald Fischer ynnor at mm.st writes:
In a bash or zsh running inside mintty, pressing Control-C has no
effect. In a bash or zsh running in a Windows Console, it works fine.
...
WJFFM. ...
I have a suspicion that the problem he is facing could
On 7/14/2015 9:44 AM, Ronald Fischer wrote:
Using Cygwin 64 on Windows 7:
In a bash or zsh running inside mintty, pressing Control-C has no
effect. In a bash or zsh running in a Windows Console, it works fine.
This can be verified in two ways:
(1) Using 'trap':
In the shell, we do
On Tue, Jul 14, 2015, at 11:27, Achim Gratz wrote:
Ronald Fischer ynnor at mm.st writes:
Using Cygwin 64 on Windows 7:
In a bash or zsh running inside mintty, pressing Control-C has no
effect. In a bash or zsh running in a Windows Console, it works fine.
This can be verified in two
All,
for your info
Regards
Marco
Forwarded Message
Subject: [No Reply] False Positive Submission [3822135]
Date: Wed, 15 Jul 2015 06:49:33 +0100
From: Symantec FP Incident Response falsepositi...@symantec.com
To: marco.atz...@gmail.com
In relation to submission [3822135].
801 - 900 of 2219 matches
Mail list logo