Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found

On 05/02/2022 14:25, Jon Turney wrote: On 27/01/2022 03:12, Ken Whitesell wrote: First, the bottom line: XWin.exe.manifest, line 21 change: PerMonitorV2,PerMonitor to PerMonitor Some details: I managed to get to a point where I could build the packages from source and install them. I

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found

issue, looking at the source, it seems that we don't re-consider the display dpi after a WM_DISPLAYCHANGE message, but keep on using the value determined at startup.  This is probably a bug. I'm curious enough to want to take a look at the code, but I've got no belief that I'm going to be able

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found

, it seems that we don't re-consider the display dpi after a WM_DISPLAYCHANGE message, but keep on using the value determined at startup.  This is probably a bug. I'm curious enough to want to take a look at the code, but I've got no belief that I'm going to be able to find an answer. (I'm

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified

in xorg-server 21.1.0-1, trying to fix problems in this area (See [1]) Thanks for the references. I've read all the messages in the thread - I was particularly intrigued by this comment: wrt the font scaling issue, looking at the source, it seems that we don't re-consider the display dpi

Re: Cygwin/X display scaling corrupting font display of typed characters;

On 2022/01/21 10:26, L A Walsh wrote: ... To summarize, I am not sure that the original issue has anything to do with 2nd monitor, nor any changes in the Xorg-sources. In _my_ case it was a matter of how the Xserver was started, and what dpi settings it was started with. If server was started

Re: Cygwin/X with Win[10]-^ display scaling corrupting font display of typed characters - Issue [identified]-????

adowDDNL [438305.385] winDetectSupportedEngines - Returning, supported engines 0005 [438305.385] winSetEngine - Multi Window or Rootless => ShadowGDI [438305.385] winScreenInit - Using Windows display depth of 32 bits per pixel [438306.883] winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 144

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified

problems in this area (See [1]) Thanks for the references. I've read all the messages in the thread - I was particularly intrigued by this comment: wrt the font scaling issue, looking at the source, it seems that we don't re-consider the display dpi after a WM_DISPLAYCHANGE message, but keep

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified

find that starting the server and specifying a fixed dpi value with the '-dpi' option might workaround this. [1] https://cygwin.com/pipermail/cygwin-announce/2021-November/010286.html If I change the scaling from 125% to 100% on the laptop's display, the problem appears until I restart Cygwin

Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified

On 1/17/2022 1:29 PM, Ken Whitesell wrote: Problem: When moving an XTerm window from the primary display to the second monitor, characters typed into that window are "clipped" at the top. Only about the bottom 75% is drawn. No lower-case letters taller than the "half-height&

Cygwin/X with Win10 display scaling corrupting font display of typed characters

Problem: When moving an XTerm window from the primary display to the second monitor, characters typed into that window are "clipped" at the top. Only about the bottom 75% is drawn. No lower-case letters taller than the "half-height" letters render properly. (Letters such a

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 2021-08-13 at 22:37 -0600, Brian Inglis wrote: > On 2021-08-13 22:05, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 23:46:35 -0400 > > > C Linus Hicks wrote: > > > > > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 13:35 +0900, Takashi Yano wrote: > On Sat, 14 Aug 2021 00:05:17 -0400 > C Linus Hicks wrote: > > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 23:46:35 -0400 > > > C Linus Hicks wrote: > > > > > > > On Fri, 2021-08-13 at 23:27 -0400, C

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On 2021-08-13 22:05, C Linus Hicks via Cygwin wrote: On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: On Fri, 13 Aug 2021 23:46:35 -0400 C Linus Hicks wrote: On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: On

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 14 Aug 2021 00:05:17 -0400 C Linus Hicks wrote: > On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > > On Fri, 13 Aug 2021 23:46:35 -0400 > > C Linus Hicks wrote: > > > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > > > > On Sat, 2021-08-14 at 11:48 +0900,

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 12:59 +0900, Takashi Yano wrote: > On Fri, 13 Aug 2021 23:46:35 -0400 > C Linus Hicks wrote: > > > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > > > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > > > On Fri, 13 Aug 2021 21:47:53 -0400 > >

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 13 Aug 2021 23:46:35 -0400 C Linus Hicks wrote: > On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > > On Fri, 13 Aug 2021 21:47:53 -0400 > > > C Linus Hicks wrote: > > > > On Mon, 2021-08-09 at 15:17 -0400, C

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 2021-08-13 at 23:27 -0400, C Linus Hicks via Cygwin wrote: > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > On Fri, 13 Aug 2021 21:47:53 -0400 > > C Linus Hicks wrote: > > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > > > On Sat, 2021-08-07 at 13:33

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 13 Aug 2021 23:27:44 -0400 C Linus Hicks wrote: > On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > > On Fri, 13 Aug 2021 21:47:53 -0400 > > C Linus Hicks wrote: > > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > > > On Sat, 2021-08-07 at 13:33 -0600, Brian

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Sat, 2021-08-14 at 11:48 +0900, Takashi Yano wrote: > On Fri, 13 Aug 2021 21:47:53 -0400 > C Linus Hicks wrote: > > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > > > Works Just Fine For Me! > > > > > > > This

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 13 Aug 2021 21:47:53 -0400 C Linus Hicks wrote: > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > > Works Just Fine For Me! > > > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck output > >

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Fri, 13 Aug 2021 21:47:53 -0400 C Linus Hicks wrote: > On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > > Works Just Fine For Me! > > > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck output > >

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

On Mon, 2021-08-09 at 15:17 -0400, C Linus Hicks via Cygwin wrote: > On Sat, 2021-08-07 at 13:33 -0600, Brian Inglis wrote: > > Works Just Fine For Me! > > > This is Cygwin 64 on Windows 10 in a VirtualBox VM, cygcheck output attached. > > It has been a while since I updated Cygwin; as long as

Re: Display text file using less in Cygwin terminal or xterm incorrect when lines are longer than window width

w; no lines or characters missing. If you add more lines to the file but still with fewer lines then lines in your display window, but the number of lines that should be displayed when wrapped is greater than your window, then you will get different behavior. And if your file has more lines than

Display text file using less in Cygwin terminal or xterm incorrect when lines are longer then window width

will fit in your window you will see the entire file in the bottom of your window. If you hit the 'g' key, it will jump to the top, but one or more lines at the top will be missing. If you add more lines to the file but still with fewer lines then lines in your display window, but the number of lines

Re: Can't open display issue from CMD

on! I didn't realize that xrdb was the cause of my issue, and I solved the problem as you suggested. if [[ -n $DISPLAY ]] then /usr/bin/xrdb -load ~/.Xdefaults fi On Sat, Jan 16, 2021 at 4:23 PM Hans-Bernhard Bröker wrote: > Am 16.01.2021 um 05:40 schrieb Marco Atzeri via Cyg

Re: Can't open display issue from CMD

Am 16.01.2021 um 05:40 schrieb Marco Atzeri via Cygwin: It seems the remote machine is expecting to run a X interface by default. Or could it be that the local machine has ssh X11 forwarding turned on (for this remote machine)? Turning it off explicitly (-x flag) would turn it off, so if

Re: Can't open display issue from CMD

please reply to the mailing list On 16.01.2021 06:36, Sal Bellofiore wrote: Hi Marco, Thanks for the prompt response.  The reason why I don't get asked for a password is because I have setup the RSA public key, and that works fine. When you say to check the remote scripts, what scripts are

Re: Can't open display issue from CMD

Luna Bellofiore via Cygwin writes: > C:\Users\bellsal>\cygwin\bin\ssh 192.168.0.8 pwd > /usr/bin/xrdb: Can't open display '' > /home/bellsal > > PWD should not require X11 connection, so I don't understand why I am > getting this issue. You need to saniti

Re: Can't open display issue from CMD

On 16.01.2021 05:22, Luna Bellofiore via Cygwin wrote: All, I am sending Linux commands from CMD (Windows) through SSH, and I am getting "Can't open display". Below I am capturing my issue, the IP number is the remote Linux machine. Microsoft Windows [Version 10.0.19042.746

Can't open display issue from CMD

All, I am sending Linux commands from CMD (Windows) through SSH, and I am getting "Can't open display". Below I am capturing my issue, the IP number is the remote Linux machine. Microsoft Windows [Version 10.0.19042.746] (c) 2020 Microsoft Corporation. All rights reserved. C:\Use

Re: evince 3.26.0-1 can't open/display .eps files

On 1/3/2021 12:26 PM, Scott T. Marshall wrote: Hello, I use evince to view .eps and .ps files (usually plots of scientific data). After my recent cygwin update, evince no longer is able to open .eps or .ps files. I get the following error.   Unable to open the initial device, quitting.

evince 3.26.0-1 can't open/display .eps files

Hello, I use evince to view .eps and .ps files (usually plots of scientific data). After my recent cygwin update, evince no longer is able to open .eps or .ps files. I get the following error.   Unable to open the initial device, quitting. fatal internal error -100 From a web search in

Re: GAWK Incorrect Data Display

On 12/19/2020 7:16 PM, Hans-Bernhard Bröker wrote: Am 20.12.2020 um 00:34 schrieb Jason McGee via Cygwin: I confirmed there is not a problem with my code by comparing Cygwin against Gawk for Windows. Your presentation of the problem is quite unclear, but the root cause is almost certainly

Re: GAWK Incorrect Data Display

Am 20.12.2020 um 00:34 schrieb Jason McGee via Cygwin: I confirmed there is not a problem with my code by comparing Cygwin against Gawk for Windows. Your presentation of the problem is quite unclear, but the root cause is almost certainly not in the code, but in the data. You're bound to

RE: GAWK Incorrect Data Display

link/?LinkId=550986> for Windows 10 From: Jason McGee<mailto:good...@hotmail.com> Sent: Saturday, December 19, 2020 6:34 PM To: cygwin@cygwin.com<mailto:cygwin@cygwin.com> Subject: GAWK Incorrect Data Display I confirmed there is not a problem with my code by comparing Cygwin again

GAWK Incorrect Data Display

I confirmed there is not a problem with my code by comparing Cygwin against Gawk for Windows. sp_array[++ sp_count] = d_quote "SP" d_quote ", " ticket "," d_quote type ", " volume ", " price ", " 0 I’m reading a file and writing the data to an array. I’ve tried multiple variations are the

Your outdoor led display resources page

Hey, I noted you have a web page about outdoor led display. URL: https://www.tweaking4all.com/video/gaming/split-screen-game-full-screen/ And the link to this web: Tweaking4All.com - Play any Split screen Game, Full-Screen on any 3D TV (like Dual Play) Title: Tweaking4All.com

Re: incorrect text mode graphic character display

Am 09.05.2020 um 22:37 schrieb bri...@pounceofcats.com: On Sat, 9 May 2020 08:32:17 +0200 Marco Atzeri via Cygwin wrote: Can you install a parallel Cygwin with only Base category ? I use C:\cygwin64T for my parallel Cygwin installation. This will help to check if a fresh version without any

Re: incorrect text mode graphic character display

On Sat, 9 May 2020 08:32:17 +0200 Marco Atzeri via Cygwin wrote: > > Please provide the cygcheck.out as attachment > https://cygwin.com/problems.html > > Which version of Julia are you running ? 1.4.1 > How are you running Julia? i'm running the julia.exe from the Julia install bin

Re: incorrect text mode graphic character display

Am 09.05.2020 um 09:30 schrieb Marco Atzeri via Cygwin: Am 09.05.2020 um 08:45 schrieb Thomas Wolff: Am 09.05.2020 um 08:32 schrieb Marco Atzeri via Cygwin: Am 08.05.2020 um 22:14 schrieb bri...@pounceofcats.com: On Fri, 8 May 2020 20:41:55 +0200 Marco Atzeri via Cygwin wrote: Am

Re: incorrect text mode graphic character display

Am 09.05.2020 um 08:45 schrieb Thomas Wolff: Am 09.05.2020 um 08:32 schrieb Marco Atzeri via Cygwin: Am 08.05.2020 um 22:14 schrieb bri...@pounceofcats.com: On Fri, 8 May 2020 20:41:55 +0200 Marco Atzeri via Cygwin wrote: Am 07.05.2020 um 17:18 schrieb bri...@pounceofcats.com: Hi, Doesn't

Re: incorrect text mode graphic character display

Am 09.05.2020 um 08:32 schrieb Marco Atzeri via Cygwin: Am 08.05.2020 um 22:14 schrieb bri...@pounceofcats.com: On Fri, 8 May 2020 20:41:55 +0200 Marco Atzeri via Cygwin wrote: Am 07.05.2020 um 17:18 schrieb bri...@pounceofcats.com: Hi, Doesn't matter what terminal i'm using, I'm having a

Re: incorrect text mode graphic character display

Am 08.05.2020 um 22:14 schrieb bri...@pounceofcats.com: On Fri, 8 May 2020 20:41:55 +0200 Marco Atzeri via Cygwin wrote: Am 07.05.2020 um 17:18 schrieb bri...@pounceofcats.com: Hi, Doesn't matter what terminal i'm using, I'm having a problem with the way graphic characters print. Julia

Re: incorrect text mode graphic character display

On Fri, 8 May 2020 20:41:55 +0200 Marco Atzeri via Cygwin wrote: > Am 07.05.2020 um 17:18 schrieb bri...@pounceofcats.com: > > Hi, > > > > Doesn't matter what terminal i'm using, I'm having a problem with the way > > graphic characters print. > > Julia uses unicode output, and will generate

Re: incorrect text mode graphic character display

Am 07.05.2020 um 17:18 schrieb bri...@pounceofcats.com: Hi, Doesn't matter what terminal i'm using, I'm having a problem with the way graphic characters print. Julia uses unicode output, and will generate output that should look like this: julia> x=DataFrame([(1,2,3), (4,5,6)]) 2×3 DataFrame

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 21:03:01 -0600 Brian Inglis wrote: > On 2020-05-07 16:12, Brian D wrote: > > On Thu, 7 May 2020 15:52:06 -0600, Brian Inglis wrote: > [please ensure all email addresses are stripped from the body] > >> As that env var is interpreted by the main Cygwin process cygwin1.dll, >

Re: incorrect text mode graphic character display

> >> of it > >> in setup.exe. That solved our issue with corrupted display of Maven. > >> You > >> can also install older versions of any package (but not all old > >> versions > >> ever published will be available to choose from, just a few ones

Re: incorrect text mode graphic character display

On 2020-05-07 16:12, Brian D wrote: > On Thu, 7 May 2020 15:52:06 -0600, Brian Inglis wrote: [please ensure all email addresses are stripped from the body] >> As that env var is interpreted by the main Cygwin process cygwin1.dll, which >> has >> to be unloaded and reloaded, I'd set

Re: incorrect text mode graphic character display

Brian wrote: __ success! That did it.  What i find particularly strange is that it fixes the problem in mintty as well as the terminals i'm running in x-windows, for example the xfce4-terminal. I had no idea such a thing as the cygwin.dll existed, i would have

Re: incorrect text mode graphic character display

On 2020-05-07 15:10, bri...@pounceofcats.com wrote: On Thu, 7 May 2020 23:26:37 +0200 Eric Lilja wrote: Cygwin itself is actually just DLL, you can select a previous version of it in setup.exe. That solved our issue with corrupted display of Maven. You can also install older versions of any

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 15:52:06 -0600 Brian Inglis wrote: > As that env var is interpreted by the main Cygwin process cygwin1.dll, which > has > to be unloaded and reloaded, I'd set CYGWIN=disable_pcon in the System > environment, then shut down all Cygwin processes, as you would before running >

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 23:26:37 +0200 Eric Lilja wrote: > Cygwin itself is actually just DLL, you can select a previous version of it > in setup.exe. That solved our issue with corrupted display of Maven. You > can also install older versions of any package (but not all old versions > ev

Re: incorrect text mode graphic character display

gt; Did not help. >> Thanks for that though, I had no idea those kind of env variables were >> available. >> Character display problems do not depend only on the program you run, in >> your case, "Julia", whatever that is, but also in which terminal or con

Re: incorrect text mode graphic character display

Cygwin itself is actually just DLL, you can select a previous version of it in setup.exe. That solved our issue with corrupted display of Maven. You can also install older versions of any package (but not all old versions ever published will be available to choose from, just a few ones). Anyway

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 22:22:56 +0200 Eric Lilja wrote: > You simply run the setup program, it's possible to select a few older > versions. > oh, i was thinking i could simply select a previous version of cygwin as a whole. are you talking about selecting previous versions of specific packages ?

Re: incorrect text mode graphic character display

> Thanks for that though, I had no idea those kind of env variables were > available. > > Brian > ____ > > Hi Brian, > > Character display problems do not depend only on the program you run, in your > case, "

Re: incorrect text mode graphic character display

You simply run the setup program, it's possible to select a few older versions. - Eric L On Thu, May 7, 2020 at 6:32 PM wrote: > On Thu, 7 May 2020 18:01:59 +0200 > Eric Lilja wrote: > > > Did you try to go back to Cygwin 3.0.7? At work, we had to do that, after > > output from Maven (which

Re: incorrect text mode graphic character display

vailable. Brian Hi Brian, Character display problems do not depend only on the program you run, in your case, "Julia", whatever that is, but also in which terminal or console you run it, as it is the terminal that does the actual character display. If you run in in mintty f

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 19:31:01 +0200 Marco Atzeri via Cygwin wrote: > > Any ideas on what i might try ? > > > > Thanks ! > > > > > Assuming Julia is a not Cygwin program, > you can try "CYGWIN=disable_pcon" before any Cygwin process Did not help. Thanks for that though, I had no idea those

Re: incorrect text mode graphic character display

coding and i can make the problem worse, but not better. , I've tried several terminal types, e.g. the xfce4 terminal, gnome terminal, rxvt. They all give me incorrect displays, but rxvt gives me a different incorrect display. lxterminal and rxvt-unicode give me the same output as shown in this

Re: incorrect text mode graphic character display

On Thu, 7 May 2020 18:01:59 +0200 Eric Lilja wrote: > Did you try to go back to Cygwin 3.0.7? At work, we had to do that, after > output from Maven (which is colored) gets corrupted after a change in 3.1.0 > and onwards. The output problem we saw manifests itself slightly different > from yours,

Re: incorrect text mode graphic character display

Γöé 5 Γöé 6 Γöé > > This was working until a recent upgrade. I have experimented with > terminal set encoding and i can make the problem worse, but not better. > , > I've tried several terminal types, e.g. the xfce4 terminal, gnome > terminal, rxvt. > They all give me in

incorrect text mode graphic character display

better. , I've tried several terminal types, e.g. the xfce4 terminal, gnome terminal, rxvt. They all give me incorrect displays, but rxvt gives me a different incorrect display. lxterminal and rxvt-unicode give me the same output as shown in this email. I've been trying to experiment with

Single-width display option

I have implemented a single-width display option for mintty (https://github.com/mintty/mintty/issues/964). With this feature enabled, CJK characters are rendered single-width. While this may appear alien for terminal users who are used to the established dual-width paradigm, some people may

Re: Cygwin programs display output incorrectly when run under conemu

Thank you. That explains the issue for me very well. Paul On Mon, 17 Feb 2020 at 01:07, Dr Hartmut Bartels wrote: > > I had the same issue and got answer from Takashi Yano > https://cygwin.com/ml/cygwin/2020-01/msg3.html > > My workareound is > using version ConEmuPack.170807.7z. This

Re: Cygwin programs display output incorrectly when run under conemu

I had the same issue and got answer from Takashi Yano https://cygwin.com/ml/cygwin/2020-01/msg3.html My workareound is using version ConEmuPack.170807.7z. This works together with cygwin 3.1.2-1. Versions of Comemu greater 170807 won't. Same for cmder, if replacing conemu with version

Cygwin programs display output incorrectly when run under conemu

This issue has also been reported to the ConEmu tracker as https://github.com/Maximus5/ConEmu/issues/2059. If I run a cygwin command (for example ls, or for a simpler example, "printf hello\nthere", although the latter needs care to get the correct level of \n escaping :-)) newlines are displayed

Re: getpriority() and top display for priority inconsistent

On 8/15/2019 1:04 PM, Houder wrote: > On Thu, 15 Aug 2019 12:20:38, Corinna Vinschen wrote: >> >> On Aug 15 09:41, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: git format-patch output with commit message, please? >>> =20 >>> Please educate me how to do that; I am just using "git

Re: getpriority() and top display for priority inconsistent

On Thu, 15 Aug 2019 12:20:38, Corinna Vinschen wrote: > > On Aug 15 09:41, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > > git format-patch output with commit message, please? > >=20 > > Please educate me how to do that; I am just using "git diff --no-color". > > $ git add > $

Re: getpriority() and top display for priority inconsistent

On 8/15/2019 11:41 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: >> git format-patch output with commit message, please? > > Please educate me how to do that; I am just using "git diff --no-color". > $ git format-patch --stdout If you want to request for comment you could use 'git

Re: getpriority() and top display for priority inconsistent

On Aug 15 12:20, Corinna Vinschen wrote: > On Aug 15 09:41, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > > git format-patch output with commit message, please? > > > > Please educate me how to do that; I am just using "git diff --no-color". > > $ git add > $ git commit -a

Re: getpriority() and top display for priority inconsistent

On Aug 15 09:41, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > git format-patch output with commit message, please? > > Please educate me how to do that; I am just using "git diff --no-color". $ git add $ git commit -a - opens editor to create a commit message. first line is

RE: getpriority() and top display for priority inconsistent

> git format-patch output with commit message, please? Please educate me how to do that; I am just using "git diff --no-color". > The commit message should describe what the problem is and how the patch > fixes it. One or > two sentences are enough. The commit message is there: > >

Re: getpriority() and top display for priority inconsistent

On Aug 14 20:01, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > Feel free to provide a patch, just, please, create a valid git commit > > message > > "getpriority() consistent with process priority > https://cygwin.com/ml/cygwin/2019-08/msg00122.html; > > The changeset is really

Re: getpriority() and top display for priority inconsistent

> Feel free to provide a patch, just, please, create a valid git commit message "getpriority() consistent with process priority https://cygwin.com/ml/cygwin/2019-08/msg00122.html; The changeset is really trivial: diff --git a/winsup/cygwin/syscalls.cc b/winsup/cygwin/syscalls.cc index

Re: getpriority() and top display for priority inconsistent

On Aug 8 13:45, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > I pushed your patch with a short commit message. > > Thanks! Thinking about that a little more, getpriority(PRIO_PROCESS) > returns the cached version of priority (since the last setpriority()) > but should return "live"

Re: getpriority() and top display for priority inconsistent

> I pushed your patch with a short commit message. Thanks! Thinking about that a little more, getpriority(PRIO_PROCESS) returns the cached version of priority (since the last setpriority()) but should return "live" version by re-getting and re-caching the actual thing from the system: 1. The

Re: getpriority() and top display for priority is inconsistent

On Aug 7 19:27, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > Please give it a try. > > diff --git a/winsup/cygwin/fhandler_process.cc > b/winsup/cygwin/fhandler_process.cc > index 2a06554..2305b53 100644 > --- a/winsup/cygwin/fhandler_process.cc > +++

[newlib-cygwin] Cygwin: getpriority() and top display for priority is inconsistent

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=5fa9a0e7083448ff02e378981dd9a6646fce45a3 commit 5fa9a0e7083448ff02e378981dd9a6646fce45a3 Author: Lavrentiev, Anton Date: Wed Aug 7 19:27:41 2019 + Cygwin: getpriority() and top display for priority is inconsistent

Re: getpriority() and top display for priority is inconsistent

> Please give it a try. diff --git a/winsup/cygwin/fhandler_process.cc b/winsup/cygwin/fhandler_process.cc index 2a06554..2305b53 100644 --- a/winsup/cygwin/fhandler_process.cc +++ b/winsup/cygwin/fhandler_process.cc @@ -1076,7 +1076,7 @@ format_process_stat (void *data, char *) unsigned long

Re: getpriority() and top display for priority is inconsistent

On Aug 7 00:45, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > > You seem to have worked it out already so please send a patch in > > git format-patch foramt to the cygwin-patches mailing list. > > I tried :-/ > > : > Sorry, only subscribers may post. (#5.7.2) There are no

Re: getpriority() and top display for priority is inconsistent

> You seem to have worked it out already so please send a patch in > git format-patch foramt to the cygwin-patches mailing list. I tried :-/ : Sorry, only subscribers may post. (#5.7.2) I do not use git to pull Cygwin sources. The last snapshot (that corresponds to the last-known-stable

Re: getpriority() and top display for priority is inconsistent

On Aug 6 18:54, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote: > I have noticed a discrepancy between the process priority shown by > "top" vs. what getpriority() returns. > > I'm using the procps-based "top", so it reads the priority value from > /proc/PID/stat. The value gets there

getpriority() and top display for priority is inconsistent

I have noticed a discrepancy between the process priority shown by "top" vs. what getpriority() returns. I'm using the procps-based "top", so it reads the priority value from /proc/PID/stat. The value gets there via code found in "fhandler_process.cc": /* The BasePriority returned to a 32

LED Display screen outdoor and indoor

Hi, If you need a quotation of LED Display (both for indoor, outdoor. rental or fixed installation). Please contact us. We can give your our best price. Kind regards, Roger Web: https://ylsoled.en.alibaba.com

Re: xrdb: can't open display 127.0.0.1:0.0

Am 16.10.2018 um 02:11 schrieb hacker...@protonmail.com: Hi I'm able to run an X11/ Motif application compiled using gcc on Cygwin within Cygwin/X. However, when I try running the app from Windows directly (say from File Manager), it errors out with: xrdb: can't open display 127.0.0.1:0.0

xrdb: can't open display 127.0.0.1:0.0

Hi I'm able to run an X11/ Motif application compiled using gcc on Cygwin within Cygwin/X. However, when I try running the app from Windows directly (say from File Manager), it errors out with: xrdb: can't open display 127.0.0.1:0.0 (Note: Cygwin/ X is running separately on the same PC

Re: XWin: Tiny fonts on high resolution display

On 9/29/2018 8:34 AM, Thomas Dickey wrote: > > > - Original Message - > | From: "Ken Brown" > | To: "Thomas Dickey" > | Cc: "cygwin" > | Sent: Friday, September 28, 2018 10:25:17 PM > | Subject: Re: XWin: Tiny fonts on high resolut

Re: XWin: Tiny fonts on high resolution display

- Original Message - | From: "Ken Brown" | To: "Thomas Dickey" | Cc: "cygwin" | Sent: Friday, September 28, 2018 10:25:17 PM | Subject: Re: XWin: Tiny fonts on high resolution display | On 9/28/2018 8:06 PM, Thomas Dickey wrote: |> - Original Me

Re: XWin: Tiny fonts on high resolution display

g00247.html), but I haven't >>> found a >>> good answer, except perhaps to use Gnome or some other desktop environment. >>> (I >>> haven't tried that yet.) >>> I just got a new laptop with a 3840x2160 display. When I start the X >>> se

Re: XWin: Tiny fonts on high resolution display

On 9/28/2018 10:25 PM, Ken Brown wrote: On 9/28/2018 8:06 PM, Thomas Dickey wrote: https://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize Thanks. The 10x20 font was still too small, but I was able to get a reasonable xterm by adding XTerm*faceName:

Re: XWin: Tiny fonts on high resolution display

On 9/28/2018 8:06 PM, Thomas Dickey wrote: > - Original Message - > | From: "Ken Brown" > | To: "cygwin" > | Sent: Friday, September 28, 2018 6:32:25 PM > | Subject: XWin: Tiny fonts on high resolution display > > | A Google search shows that

Re: XWin: Tiny fonts on high resolution display

.) I just got a new laptop with a 3840x2160 display. When I start the X server via startxwin, xterm and emacs open small windows with tiny fonts. Here are the xterm and emacs settings in my .Xresources: emacs.geometry: 80x34+340+40 XTerm*geometry: 80x45 XTerm*VT100*colorBDMode: on XTerm*VT100

Re: XWin: Tiny fonts on high resolution display

- Original Message - | From: "Ken Brown" | To: "cygwin" | Sent: Friday, September 28, 2018 6:32:25 PM | Subject: XWin: Tiny fonts on high resolution display | A Google search shows that this is a very frequently asked question (e.g., | https://sourceware.org/ml/cyg

Re: KDE Konsole does not display the special characters

Michel, There is a "[" missing in Formats] your reply above, chedk that the file on disk is OK. If making Format] ---> [Format] doesn't work, put the old file back and see if Konsole starts using it. Also check that the read permissions and ownership on the .config/plasma-localerc file

Re: KDE Konsole does not display the special characters

Thanks to answer I filled the file .config/plasma-localerc like this : Formats] LANG=fr_FR.UTF-8 LC_CTYPE=" fr_FR.UTF-8" LC_NUMERIC="fr_FR.UTF-8" LC_TIME="fr_FR.UTF-8" LC_COLLATE="fr_FR.UTF-8" LC_MONETARY="fr_FR.UTF-8" LC_MESSAGES="fr_FR.UTF-8" useDetailed=true [Translations] LANGUAGE=fr_FR I

Re: KDE Konsole does not display the special characters

On 2018-08-02 08:49, Michel Dubois wrote: > I went to install konsole KDE package on cygwin. I was surprised this > terminal is not managing well the accent or other special character and > replace them by "?" > ~ > ls > Desktop Documents GIT_workdir Images Mod��les Musique Public >

KDE Konsole does not display the special characters

Hi, I went to install konsole KDE package on cygwin. I was surprised this terminal is not managing well the accent or other special character and replace them by "?" ~ > ls Desktop Documents GIT_workdir Images Mod��les Musique Public T��l��chargements Vid��os ~ > locale LANG=fr_FR.UTF-8

Re: Eclipse running on debian with remote display to cygwin X11 starts all squashed to a point

> Jon Turney : > Probably the simplest way is to replace your existing > /usr/bin/XWin.exe with it (after making a copy of the original so you > can put it back afterwards) The XWin.20180308-git-3ca71c7f563c3e91.exe file did not work unfortunately: - With no

Re: Eclipse running on debian with remote display to cygwin X11 starts all squashed to a point

On 08/03/2018 20:16, Steinar Bang wrote: I've built a snapshot with some potential fixes. Perhaps you could try that and see if it improves things for you? ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20180308-git-3ca71c7f563c3e91.exe.bz2 Ok I will try this and see how it works out. I will

  1   2   3   4   5   6   7   8   9   >