Updating Stuntman (Open source Stun Server) from C++ to modern C++. I ran
into an issue.
This code:
#include
#include
#include
int some_networking_code()
{
addrinfo* addr = NULL;
int flags = AI_NUMERICHOST;
return 0;
}
Compiles fine everywhere: wit
$ tclsh
% puts [expr 2+2]
4
% puts [expr 2.0+2.0]
(hangs, should return 4.0)
$ which tclsh
/usr/bin/tclsh
info tclversion returns 8.6, of course (8.6.8-1)
Linux tclsh doesn't have this issue.
This is on 32-bit cygwin; 64-bit cygwin seems a bit more robust,
but if you keep asking it to sum
If you create this file:
touch -- \''-#%.!$&(),;@[]^`{}=_~+9zZ'
Then enter "touch", "Tab", "Tab", you get this:
touch \'-#%.\!\$\&\(\)\,\;\@\[\]\^\`\{\}\=_~+9zZ
So the shell is saying that these characters need to be escaped:
' ! $ & ( ) , ; @ [ ] ^ ` { } =
but they dont, not all of
On Tue, 4 Sep 2018 23:43:16, Thomas Wolff wrote:
Traditionally, many terminals used to display the DEL character as a
checkered block, which is more or less the MEDIUM SHADE.
This makes the glyph appear somewhat "erroneous" by convention.
I see - now that Unicode has some dedicated characters
Good evening
Yes I would be happy to receive the fields from this list
Yours,
Le mar. 4 sept. 2018 à 18:25, Meghan Hudson <
meghan.hud...@corporatebizleads.com> a écrit :
> Hi,
>
>
>
> Hope you having a great day!
>
>
>
> I just wanted to be aware if you looking to acquire Microsoft Azure Users
Am 04.09.2018 um 21:53 schrieb Steven Penny:
On Tue, 4 Sep 2018 20:41:48, Thomas Wolff wrote:
...
the .notdef glyph is not an appropriate indication of illegal
encoding (like broken UTF-8 bytes)
true, but neither is U+2592. as far as i know U+2592 is not defined
officially
anywhere as being
On Tue, 4 Sep 2018 13:59:10, Doug Henderson wrote:
My preference is to remove the output fiddling code that Corrina has
been working on. It is trying to solve the wrong problem.
I think we have gone down a rabbit hole at the wrong end of cat's data flow.
this has nothing to do with "cat". it ha
On 2018-09-04 12:20, Steven Penny wrote:
> On Tue, 4 Sep 2018 16:18:21, Thomas Wolff wrote:
>> My vote is against the patch because the nodef glyph will often be just blank
>> space which is certainly worse than ▒.
Not according to the sample below: you would have to know that medium shade
means u
On 8/27/2018 10:26 AM, Corinna Vinschen wrote:
On 8/27/2018 3:50 AM, Corinna Vinschen wrote:
The only sane way to handle unknown SIDs in file ACLs is to ignore them
entirely. The result will be that you never see them in getfacl, nor
will they be stored by tar or rsync. They are just not there
On Sat, 1 Sep 2018 at 10:13, Steven Penny wrote:
> You get this result with Linux:
>
> $ cat alfa.txt
> �
>
> Where "cat" properly outputs Unicode 'REPLACEMENT CHARACTER' (U+FFFD). However
> with Cygwin you get this:
>
> $ cat alfa.txt
> ▒
>
> Where "cat" outputs Unicode Character
On Tue, 4 Sep 2018 20:41:48, Thomas Wolff wrote:
No idea what you consider dangerous. Anyway, we obviously agree that
hardly any available console font supports the REPLACEMENT CHARACTER.
You had previously suggested code that might work (using CreateFont(0,
0, )). Maybe you can sort out wi
Greetings, Thomas Wolff!
>>> My vote is against the patch because the nodef glyph will often be
>>> just blank space which is certainly worse than ▒.
>>> If conhost does not provide a reasonable way to enquire 0xFFFD
>>> availability it's conhost's fault, not cygwin's so why should cygwin
>>> im
Am 04.09.2018 um 20:20 schrieb Steven Penny:
On Tue, 4 Sep 2018 16:18:21, Thomas Wolff wrote:
My vote is against the patch because the nodef glyph will often be
just blank space which is certainly worse than ▒.
If conhost does not provide a reasonable way to enquire 0xFFFD
availability it's con
On Tue, 4 Sep 2018 16:18:21, Thomas Wolff wrote:
My vote is against the patch because the nodef glyph will often be just
blank space which is certainly worse than ▒.
If conhost does not provide a reasonable way to enquire 0xFFFD
availability it's conhost's fault, not cygwin's so why should cygwi
Hi,
Hope you having a great day!
I just wanted to be aware if you looking to acquire Microsoft Azure Users
Contact List for your marketing efforts?
Information Field: Names, Title, Email, Phone, Company Name, Company URL,
Company physical address, SIC Code, Industry and Company Size (Rev
On 4. 9. 2018 16:18, Thomas Wolff wrote:
My vote is against the patch because the nodef glyph will often be just blank
space which is certainly worse than ▒.
How often is "often"? Do the default Windows fonts have okay nodef glyphs?
By the way, how does this work with OEM fonts?
--
David Ma
On 04.09.2018 14:49, David Macek wrote:
On 4. 9. 2018 11:00, Corinna Vinschen wrote:
We either keep 0xfffd now and the user gets the nodef glyph, or I revert
the patch and let the console print 0x2592 MEDIUM SHADE again.
Decision has to be made today. I will release 2.11.1 tomorrow.
I vote
Greetings, Corinna Vinschen!
>> Result:
>>
>>DejaVu Sans Mono: SUCCESS
> Whereever you get DejaVu Sans Mono from. My W10 console only allows to
> specify a handful of fonts, Consolas, Courier New, Lucida, MS Gothic,
> NSimSun, Raster Fonts, SimSun-ExtB.
Something like
printf "DejaVu Sans
On 4. 9. 2018 11:00, Corinna Vinschen wrote:
We either keep 0xfffd now and the user gets the nodef glyph, or I revert
the patch and let the console print 0x2592 MEDIUM SHADE again.
Decision has to be made today. I will release 2.11.1 tomorrow.
I vote for keeping the patch and printing 0xFFFD.
On Tue, 4 Sep 2018 11:00:00, Corinna Vinschen wrote:
Whereever you get DejaVu Sans Mono from.
Cygwin provides it via the "dejavu-fonts" package, or you can get it here:
http://dejavu-fonts.github.io
My W10 console only allows to specify a handful of fonts, Consolas, Courier
New, Lucida, MS G
On Sep 3 15:15, Steven Penny wrote:
> On Mon, 3 Sep 2018 23:02:58, Corinna Vinschen wrote:
> > I can't. I only have a limited set of fonts available in the console.
>
> http://superuser.com/questions/390933/add-font-cmd-window-choices/956818
>
> > What I just did was calling the GetFontUnicodeRa
21 matches
Mail list logo
