rtual Tabs endeavours, release frequency
>> should become lower now.
> Speaking of silly feature requests ...
> The main reason I'm not a fan of mintty (and as a result haven't switched to
> cygwin64 on my primary Windows machine - because it doesn't include the
> non-Xwindows versio
feature requests ...
The main reason I'm not a fan of mintty (and as a result haven't
switched to cygwin64 on my primary Windows machine - because it doesn't
include the non-Xwindows version of rxvt) is that it behaves different
than xterm/rxvt for copying/pasting text. I spend most of my time
I am experiencing a similar situation on a recently reimaged Windows 10
computer in a large corporate environment, namely:
* Either typing "exit" or clicking the Windows close [X] button from a
Cygwin bash terminal (mintty under the hood) results in the process hanging
with it either
I have uploaded mintty 2.8.1 with the following changes:
Character display
* Option Charwidth for built-in Unicode width or ambiguous wide mode
(#88, #671).
Window and session control
* Virtual Tabs: additional SessionGeomSync levels (#699).
* Window icons can optionally be shown
I have uploaded mintty 2.8.1 with the following changes:
Character display
* Option Charwidth for built-in Unicode width or ambiguous wide mode
(#88, #671).
Window and session control
* Virtual Tabs: additional SessionGeomSync levels (#699).
* Window icons can optionally be shown
I have uploaded mintty 2.8.0 with the following changes.
This release features 3 major enhancements:
* Virtual Tabs feature set, including a session switcher and launcher
* filled gaps in DEC terminal support up to VT300 series level
* simplified WSL integration
Details:
Window
On Wed, Aug 23, 2017 at 6:08 PM, Corinna Vinschen wrote:
> On Aug 23 10:33, Corinna Vinschen wrote:
>> On Aug 22 18:49, Erik Bray wrote:
>> > Hi folks,
>> >
>> > I noticed a strange discrepancy when running Cygwin through mintty, vs
>> > through a nor
On Aug 23 10:33, Corinna Vinschen wrote:
> On Aug 22 18:49, Erik Bray wrote:
> > Hi folks,
> >
> > I noticed a strange discrepancy when running Cygwin through mintty, vs
> > through a normal cmd.exe console. This is on a build from the latest
> > git master, bu
On Aug 22 18:49, Erik Bray wrote:
> Hi folks,
>
> I noticed a strange discrepancy when running Cygwin through mintty, vs
> through a normal cmd.exe console. This is on a build from the latest
> git master, but also on Cygwin 2.8.0. When run from a cmd.exe
> console, we can
Am 22.08.2017 um 18:49 schrieb Erik Bray:
Hi folks,
I noticed a strange discrepancy when running Cygwin through mintty, vs
through a normal cmd.exe console. This is on a build from the latest
git master, but also on Cygwin 2.8.0. When run from a cmd.exe
console, we can see the following
Hi folks,
I noticed a strange discrepancy when running Cygwin through mintty, vs
through a normal cmd.exe console. This is on a build from the latest
git master, but also on Cygwin 2.8.0. When run from a cmd.exe
console, we can see the following output from fhandler_dev::readdir:
$ ls -l /dev
Am 10.08.2017 um 16:09 schrieb Oleksandr Gavenko:
Is it possible to navigate across mintty buffer? Like in less but in line
oriented move.
I like to have search and copy-paste.
Search: Alt+F3
Copy: click and drag mouse
screen and tmux allow this but I have no practice of using them.
Shift
Is it possible to navigate across mintty buffer? Like in less but in line
oriented move.
I like to have search and copy-paste.
screen and tmux allow this but I have no practice of using them.
Shift+PgUp/PgDown are too limiting.
--
http://defun.work/
--
Problem reports: http
I have uploaded mintty 2.7.9 with the following changes:
Character display
* Fixed character attribute handling in scrollback buffer.
* Fixed rendering of some combining characters by heuristic tweaking.
* Avoid misplaced artefacts of combining doubles while moving cursor
over them
I have uploaded mintty 2.7.9 with the following changes:
Character display
* Fixed character attribute handling in scrollback buffer.
* Fixed rendering of some combining characters by heuristic tweaking.
* Avoid misplaced artefacts of combining doubles while moving cursor
over them
Ctrl-Tab, the window becomes dialog modal.
Any ideas on how to prevent this behavior?
$ mintty.exe -V
mintty 2.7.7 (x86_64-pc-cygwin)
There was a related fix but in 2.7.7:
* Avoid being pushed behind other windows on Ctrl+TAB (#652).
Please describe the issue more precisely.
...
Updating
the terminal I hit Ctrl-Tab, the window becomes dialog
modal.
> >
> > Any ideas on how to prevent this behavior?
> >
> > $ mintty.exe -V
> > mintty 2.7.7 (x86_64-pc-cygwin)
> There was a related fix but in 2.7.7:
>* Avoid being pushed behind other windows on
Am 11.07.2017 um 06:43 schrieb Jason Pyeron:
When launching C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - (from the
start menu)
And while in the terminal I hit Ctrl-Tab, the window becomes dialog modal.
Any ideas on how to prevent this behavior?
$ mintty.exe -V
mintty 2.7.7 (x86_64-pc
Achim Gratz writes:
> Yes. I'll have to figure out just why it tries to set the background to
> the named color "white" on startup, then. That must have got saved as
> an option somewhere, maybe I can still find an old enough backup to
> compare the startup files to.
Indeed on the same day that
I have uploaded mintty 2.7.8 with the following changes:
Font rendering
* Support for alternative fonts as selected via ECMA-48 SGR codes
11...19.
* Tweaked ambiguous width checking to not expand glyphs excessively
(#615).
Terminal features
* SGR 6 attribute "rapidly blinking"
I have uploaded mintty 2.7.8 with the following changes:
Font rendering
* Support for alternative fonts as selected via ECMA-48 SGR codes
11...19.
* Tweaked ambiguous width checking to not expand glyphs excessively
(#615).
Terminal features
* SGR 6 attribute "rapidly blinking"
Ken Brown writes:
> OK, so it's not a Cygwin issue. And I just learned about M-x
> list-colors-display. If you try this in emacs-nox in Mintty with
> TERM=xterm-256color, you'll see that white is #e5e5e5 and brightwhite
> is #ff. So I guess there's no bug here, just
learned about M-x
list-colors-display. If you try this in emacs-nox in Mintty with
TERM=xterm-256color, you'll see that white is #e5e5e5 and brightwhite is
#ff. So I guess there's no bug here, just a surprising definition
of "white".
Ken
--
Problem reports: http://
gt; I can also reproduce the
> problem in xterm, so I don't think Mintty is the culprit.
I already said in my original report that I can reproduce this from my
Linux box via konsole.
I don't know why I didn't think of that earlier, but I just fired up
emacs-nox from my Linux box and did 'M-x se
reproduce the problem in
xterm, so I don't think Mintty is the culprit.
What about ncurses? That was updated on 2017-01-27? I haven't tried
downgrading it yet, but I can probably try it later today.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://
Ken Brown writes:
>> No, it really was a Cygwin update (to 2.7.0-1). The Emacs update was
>> before that and it had worked right up to that update.
>
> Sorry, I misunderstood what you meant by "Cygwin update". I
> understand now. I'll try to do a bisection of the Cygwin sources. It
> may be a
On 6/16/2017 2:27 PM, Achim Gratz wrote:
Ken Brown writes:
Your original report, written on February 22, said that the problem
started after the latest Cygwin update. That means you would have
installed emacs-25.1, if Emacs was updated at all.
No, it really was a Cygwin update (to 2.7.0-1).
as
before that and it had worked right up to that update.
> But I've just checked that the problem already exists in emacs-24.5.
> So maybe the problem was triggered by an update of some package other
> than Emacs, Mintty being the most obvious guess. Can you check your
> /var/log/setup.log to
t
checked that the problem already exists in emacs-24.5. So maybe the
problem was triggered by an update of some package other than Emacs,
Mintty being the most obvious guess. Can you check your
/var/log/setup.log to see what was updated around February 22?
Ken
--
Problem reports: http://
round-color "#F8F8F8"). The background
> stayed gray.
That's most likely a result of your terminal not being recognized as
being able to use 256 colors.
> I need to investigate 3 and 4, but first I'd like to understand why
> you and I are seeing different things. One di
On 2017-06-15 07:35, Ken Brown wrote:
> On 6/15/2017 6:47 AM, Ken Brown wrote:
>> On 6/14/2017 3:00 PM, Achim Gratz wrote:
>>> Achim Gratz writes:
>>>> After the latest Cygwin update I'm hitting an interesting problem with
>>>> emacs-nox running
On 6/15/2017 6:47 AM, Ken Brown wrote:
On 6/14/2017 3:00 PM, Achim Gratz wrote:
Achim Gratz writes:
After the latest Cygwin update I'm hitting an interesting problem with
emacs-nox running in a mintty: when Emacs starts, it decides that the
background color is gray instead of the usual white
On 6/14/2017 3:00 PM, Achim Gratz wrote:
Achim Gratz writes:
After the latest Cygwin update I'm hitting an interesting problem with
emacs-nox running in a mintty: when Emacs starts, it decides that the
background color is gray instead of the usual white (for all but the
rightmost character
Achim Gratz writes:
> After the latest Cygwin update I'm hitting an interesting problem with
> emacs-nox running in a mintty: when Emacs starts, it decides that the
> background color is gray instead of the usual white (for all but the
> rightmost character in the status line, interest
tion of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the title bar showing "~ (Not Responding)".
I've seen this happen several times in the past few days.
This may be related to the fact that I'm inst
> Anything suspicious in logout script?
I don't think so. Until now, I didn't even know about such a script
(I guess it's "/etc/bash.bash_logout").
Thanks anyway.
--
Dani Moncayo
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
by double-clicking the desktop icon), an then type the "exit" command
> in the bash shell.
> I see a "logout" message for a fraction of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the
the "exit" command
in the bash shell.
I see a "logout" message for a fraction of a second, then the terminal
becomes empty (without text), but the mintty window remains visible
but unresponsive, with the title bar showing "~ (Not Responding)".
--
Dani Moncayo
I have uploaded mintty 2.7.7 with the following changes:
Font rendering and display handling
* Automatically disabling Uniscribe for ASCII-only chunks
(mintty/wsltty#36).
* Fixed bidi display while showing other screen with Bidi=1 (#592,
~#392, ~#605).
Window handling
* Avoid being
I have uploaded mintty 2.7.7 with the following changes:
Font rendering and display handling
* Automatically disabling Uniscribe for ASCII-only chunks
(mintty/wsltty#36).
* Fixed bidi display while showing other screen with Bidi=1 (#592,
~#392, ~#605).
Window handling
* Avoid being
I have uploaded mintty 2.7.6 with the following changes:
Font rendering and Screen handling
* Supporting cell overhang of italics (#418, #152, #638).
* Manual underline adds less thickness in bold mode (#641).
* Consistent search highlighting while scrolling (#85).
Bidirectional rendering
I have uploaded mintty 2.7.6 with the following changes:
Font rendering and Screen handling
* Supporting cell overhang of italics (#418, #152, #638).
* Manual underline adds less thickness in bold mode (#641).
* Consistent search highlighting while scrolling (#85).
Bidirectional rendering
I have uploaded mintty 2.7.5.
Highlights:
Font handling / Text rendering
* Changing default FontRender=uniscribe.
* Several special character rendering improvements.
Terminal
* Fixed Wraparound and Backspace compliance with xterm and terminfo.
* Changed Reverse Wraparound default
I have uploaded mintty 2.7.5.
Highlights:
Font handling / Text rendering
* Changing default FontRender=uniscribe.
* Several special character rendering improvements.
Terminal
* Fixed Wraparound and Backspace compliance with xterm and terminfo.
* Changed Reverse Wraparound default
After the latest Cygwin update I'm hitting an interesting problem with
emacs-nox running in a mintty: when Emacs starts, it decides that the
background color is gray instead of the usual white (for all but the
rightmost character in the status line, interestingly enough). I have
the normal mintty
Am 09.02.2017 um 20:41 schrieb Achim Gratz:
Thomas Wolff writes:
The man page speaks about speculative local echo which sounds like
asking for trouble...
It is indispensable when you have a long-latency link.
Anyway, I could reproduce effects as you described with
mintty – tmux – mosh
Thomas Wolff writes:
> The man page speaks about speculative local echo which sounds like
> asking for trouble...
It is indispensable when you have a long-latency link.
> Anyway, I could reproduce effects as you described with
> mintty – tmux – mosh localhost (no additional s
Am 07.02.2017 um 22:00 schrieb Thomas Wolff:
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
It may also be useful if mintty had some character hex value box
display mode switch to display the actual codes
about the setting of
Wraparound modes.
That will take a while. I'll have to set up something at home
specifically with the goal of reproducing the error. At the moment it
looks like some sort of race between decisions made at different levels
of the stack mintty / tmux / mosh / screen since so
.
That will take a while. I'll have to set up something at home
specifically with the goal of reproducing the error. At the moment it
looks like some sort of race between decisions made at different levels
of the stack mintty / tmux / mosh / screen since so far I've not been
able to reproduce if I take
ve to set up something at home
specifically with the goal of reproducing the error. At the moment it
looks like some sort of race between decisions made at different levels
of the stack mintty / tmux / mosh / screen since so far I've not been
able to reproduce if I take out one of these.
Are earl
7:13 schrieb Achim Gratz:
>>>>>> Thomas Wolff writes:
>>>>>>> I have uploaded mintty 2.7.4 with the following changes:
>>>>>> Since about November/December last year I'm having problems with
>>>>>> screen and tm
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
It may also be useful if mintty had some character hex value box
display mode switch to display the actual codes at each visual
position, or maybe a font used
Am 07.02.2017 um 08:30 schrieb Brian Inglis:
On 2017-02-06 12:46, Thomas Wolff wrote:
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
On 2017-02-05 11:35, Thomas Wolff wrote:
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following
On 2017-02-06 12:46, Thomas Wolff wrote:
> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>> On 2017-02-05 11:35, Thomas Wolff wrote:
>>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>>>> Thomas Wolff writes:
>>>>> I have uploaded mintty 2.7.4 with the
On 6 February 2017 at 12:46, Thomas Wolff wrote:
> Am 05.02.2017 um 21:36 schrieb Brian Inglis:
>>
>> On 2017-02-05 11:35, Thomas Wolff wrote:
>>>
>>> Hi Achim,
>>>
>>> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>>>>
>
Am 05.02.2017 um 21:36 schrieb Brian Inglis:
On 2017-02-05 11:35, Thomas Wolff wrote:
Hi Achim,
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with
screen
Am 06.02.2017 um 20:16 schrieb Achim Gratz:
Achim Gratz writes:
Thomas Wolff writes:
Is this within tmux or after leaving tmux (see comment below)? It
would be help to cross-test this; if it's mintty, which version would
show the behaviour first? What happens in xterm?
Within tmux or more
Achim Gratz writes:
> Thomas Wolff writes:
>> Is this within tmux or after leaving tmux (see comment below)? It
>> would be help to cross-test this; if it's mintty, which version would
>> show the behaviour first? What happens in xterm?
>
> Within tmux or more often scr
On 2017-02-05 11:35, Thomas Wolff wrote:
> Hi Achim,
>
> Am 04.02.2017 um 17:13 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> I have uploaded mintty 2.7.4 with the following changes:
>> Since about November/December last year I'm having problems with
>>
Thomas Wolff writes:
> Is this within tmux or after leaving tmux (see comment below)? It
> would be help to cross-test this; if it's mintty, which version would
> show the behaviour first? What happens in xterm?
Within tmux or more often screen within tmux. I'll have to try what
happens
Hi Achim,
Am 04.02.2017 um 17:13 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with screen
and tmux sessions in mintty not correctly refreshing and leaving garbage
characters
Thomas Wolff writes:
> I have uploaded mintty 2.7.4 with the following changes:
Since about November/December last year I'm having problems with screen
and tmux sessions in mintty not correctly refreshing and leaving garbage
characters displayed in the terminal. It seems that the terminal s
I have uploaded mintty 2.7.4 with the following changes:
Localization details:
* Fixed localized Bell field contents.
* Adapting Bell list contents from system localization.
* Fixed unlocalized Colour chooser label "Basic colours:" and Font
chooser initial font sample.
I have uploaded mintty 2.7.4 with the following changes:
Localization details:
* Fixed localized Bell field contents.
* Adapting Bell list contents from system localization.
* Fixed unlocalized Colour chooser label "Basic colours:" and Font
chooser initial font sample.
Am 20.01.2017 um 22:19 schrieb Emember MemberUS via cygwin:
...
Suggestion: produce an error message that would help identifying this
problem when mintty starts.
NOTE: this issue happens only in cygwin, and only when both files are
present: /bin/bash.exe and empty /bin/bash
- Original Message -
From: Emember MemberUS <emembe...@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Sent: Thursday, January 19, 2017 10:25 AM
Subject: mintty fails to start
This is a minor issue and probably not typical, but could be of interest
Am 19.01.2017 um 16:25 schrieb Emember MemberUS via cygwin:
...
Suggestion: produce an error message that would help identifying this problem
when mintty starts.
NOTE: this issue happens only in cygwin, and only when both files are present:
/bin/bash.exe and empty /bin/bash.
If no bash
This is a minor issue and probably not typical, but could be of interest to
cygwin developers/maintainers.
Problem:
After building a 3-party cross-toolchain (unrelated to cygwin), mintty is no
longer able to start.
While a few mintty windows that were still open worked ok, any NEW mintty
Brian,
Thanks, with all Cygwin processes stopped, opening an ash.exe window
via start/run, then cd /bin and running rebaseall fixed the errors
present when I start mintty.
Keith
On Mon, Dec 26, 2016 at 9:43 AM, Brian Inglis
<brian.ing...@systematicsw.ab.ca> wrote:
> On 2016-12-26 09:
d not matter)) when starting
> mintty:
> 0 [main] bash 6072 child_info_fork::abort:
> C:\cygwin\bin\cygncursesw-10.dll: Loaded to different address:
> parent(0x7526) != child(0x76)
> -bash: fork: retry: Resource temporarily unavailable
> 1 [main] bash 11040 child_inf
I created a cygcheck -s -r -v file to attach, but sourceware dot org blocked it
Updated Cygwin this morning, getting fork errors (even after
rebooting, (although reboots should not matter)) when starting mintty:
0 [main] bash 6072 child_info_fork::abort:
C:\cygwin\bin\cygncursesw-10.dll
I have uploaded mintty 2.7.3 with the following changes:
Character display:
* Tweaked surrogate handling to facilitate non-BMP display.
Localization:
* Persisting adaptation of font sample text.
* Disambiguated translations in different context for "Paste",
"Font", &
I have uploaded mintty 2.7.3 with the following changes:
Character display:
* Tweaked surrogate handling to facilitate non-BMP display.
Localization:
* Persisting adaptation of font sample text.
* Disambiguated translations in different context for "Paste",
"Font", &
On Wed, Dec 14, 2016 at 1:33 PM, David Karr <davidmichaelk...@gmail.com> wrote:
> On Wed, Dec 14, 2016 at 12:06 PM, Thomas Wolff <t...@towo.net> wrote:
>> I've checked with Caffeine and traced mintty. It receives F15 key down, the
>> key up. Caffeine claims to send key
On Wed, Dec 14, 2016 at 12:06 PM, Thomas Wolff <t...@towo.net> wrote:
> I've checked with Caffeine and traced mintty. It receives F15 key down, the
> key up. Caffeine claims to send key up only but that's not true. Please
> report this as a bug to Caffeine.
Understood. I just did
Greetings, David Karr!
> I use a tool called "Windows Caffeine" that is used to keep the
> display awake.
What's wrong with correctly configured power saving settings?…
--
With best regards,
Andrey Repin
Wednesday, December 14, 2016 23:07:16
Sorry for my terrible english...
Am 14.12.2016 um 18:48 schrieb David Karr:
On Mon, Dec 12, 2016 at 10:18 AM, David Karr <davidmichaelk...@gmail.com> wrote:
Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23 14:29".
I've been annoyed for a while with a symptom in my mintty windows. I
will
On Mon, Dec 12, 2016 at 10:18 AM, David Karr <davidmichaelk...@gmail.com> wrote:
> Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23
> 14:29".
>
> I've been annoyed for a while with a symptom in my mintty windows. I
> will be typ
Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23 14:29".
I've been annoyed for a while with a symptom in my mintty windows. I
will be typing along, or not, and suddenly a "~" character gets
injected into the stream. It often is the only character at
I have uploaded mintty 2.7.2 with the following changes:
Localization:
* Completion of localization support, covering font chooser and
colour chooser (#537).
* Hint in Theme field as feedback after dragging downloaded colour
scheme.
Other:
* Fix config dialog crash when trying to load
I have uploaded mintty 2.7.1 with the following changes:
Highlights:
* Tweaked and polished localization support; including German and
French translations in cygwin package.
* Uniscribe support and improved font fallback.
* Support for distinct colour attributes for combining characters
I have uploaded mintty 2.7.1 with the following changes:
Highlights:
* Tweaked and polished localization support; including German and
French translations in cygwin package.
* Uniscribe support and improved font fallback.
* Support for distinct colour attributes for combining characters
I have uploaded mintty 2.7.0.
Highlights in this release:
* Compose key
* User interface localization support
Full change log:
Character display:
* Check for misplaced underline by looking for underline only in
descender section to decide whether to draw it ourselves (#604).
* New
I have uploaded mintty 2.7.0.
Highlights in this release:
* Compose key
* User interface localization support
Full change log:
Character display:
* Check for misplaced underline by looking for underline only in
descender section to decide whether to draw it ourselves (#604).
* New
I have uploaded mintty 2.6.1 with the following changes:
* Released Sixel graphics support in a stable version. With this nice
feature, you can embed graphics output in the terminal, for example with
gnuplot.
* Tweaked DPI scaling to avoid terminal resizing on font selection
(~#492
I have uploaded mintty 2.6.1 with the following changes:
* Released Sixel graphics support in a stable version. With this nice
feature, you can embed graphics output in the terminal, for example with
gnuplot.
* Tweaked DPI scaling to avoid terminal resizing on font selection
(~#492
Hi James,
On 2016-09-15 22:47, David Karr wrote:
When I run mintty, the background is white, and normal text is black.
This is fine. However, there are some applications that are
displaying text in other colors, many of which are fine, but some apps
display some text in yellow, which
016-09-15 22:47, David Karr wrote:
>> When I run mintty, the background is white, and normal text is black.
>> This is fine. However, there are some applications that are
>> displaying text in other colors, many of which are fine, but some apps
>> display some text in ye
On 2016-09-15 22:47, David Karr wrote:
> When I run mintty, the background is white, and normal text is black.
> This is fine. However, there are some applications that are
> displaying text in other colors, many of which are fine, but some apps
> display some text in yellow, whic
On 2016-09-15 14:47, David Karr wrote:
When I run mintty, the background is white, and normal text is black.
This is fine. However, there are some applications that are
displaying text in other colors, many of which are fine, but some apps
display some text in yellow, which on a white
Greetings, David Karr!
> When I run mintty, the background is white, and normal text is black.
> This is fine. However, there are some applications that are
> displaying text in other colors, many of which are fine, but some apps
> display some text in yellow, which on a whit
When I run mintty, the background is white, and normal text is black.
This is fine. However, there are some applications that are
displaying text in other colors, many of which are fine, but some apps
display some text in yellow, which on a white background is almost
unreadable.
For instance
I have uploaded mintty 2.5.1 with the following changes:
* Revised DPI handling (#470; #492, #487); always consider individual
monitor DPI.
* Fixed font scaling behaviour in Windows 7 and XP (#492).
* Fixed DPI scaling of Options menu (#492).
* Fixed font description formatting
I have uploaded mintty 2.5.1 with the following changes:
* Revised DPI handling (#470; #492, #487); always consider individual
monitor DPI.
* Fixed font scaling behaviour in Windows 7 and XP (#492).
* Fixed DPI scaling of Options menu (#492).
* Fixed font description formatting
Am 23.08.2016 um 11:30 schrieb Frank Fesevur:
2016-08-23 1:29 GMT+02:00 Thomas Wolff:
I have also uploaded mintty 2.5.0 as a test release with the following
change:
* Revise DPI handling (#470; #492, #487); always consider individual
monitor DPI.
Note that this release introduces
2016-08-23 1:29 GMT+02:00 Thomas Wolff:
> I have also uploaded mintty 2.5.0 as a test release with the following
> change:
>
> * Revise DPI handling (#470; #492, #487); always consider individual
> monitor DPI.
>
> Note that this release introduces a slightly incompat
I have uploaded mintty 2.4.3 with the following changes:
* Fix trails when moving other window over mintty under certain
conditions (#576).
* Fix format of double child creation error message.
I have also uploaded mintty 2.5.0 as a test release with the following
change:
* Revise DPI
I have uploaded mintty 2.4.3 with the following changes:
* Fix trails when moving other window over mintty under certain
conditions (#576).
* Fix format of double child creation error message.
I have also uploaded mintty 2.5.0 as a test release with the following
change:
* Revise DPI
On Aug 16 15:36, Corinna Vinschen wrote:
> On Aug 16 06:40, Emily Jackson wrote:
> > I installed the latest test version of Cygwin, and afterward autorebase
> > hung for several minutes until I cancelled it. I ran setup.exe again and
> > got these errors:
> > [...]
>
> Confirmed. Something's
601 - 700 of 2214 matches
Mail list logo
