> you can do "g" motion, but I cant seem to get my muscle memory to remember that. to me "down" should always use whats visible on the screen, not just dumbly move to the next line.
You could always add key mappings to your .vimrc file so it works this way.
Wouldn't the results of that online visual contrast test depend on your monitor's color calibration, etc? Or is it designed in some way that avoids that affecting the results? I'd hate to think my body was infested with mold when I'm actually just using a crappy 10-year-old monitor.
Edit: I see from the FAQs there's some kind of display calibration portion at the start of the test; should have read the website more carefully before asking!
Yeah, agreed that it seems unlikely to be a problem for most typefaces. I just think it's a bit misleading to suggest it's guaranteed to unburden the typeface of any and all 'intellectual property' protections ("In the US, you can literally go and vectorize any font in the world and do whatever you want with it").
This sounds like a typeface is not copyrightable but only because the mechanism for protection is different (patent system). So by doing what the GP suggests you wouldn't be violating copyright, but you may be in violation of the design patent on the typeface?
How does the man page's "size_t fread(void *ptr, size_t size, size_t nmemb, FILE *stream);" disagree with the GP's "fread(buf, size_of_item, number_of_items, file_ptr)"? Both seem to support that "fread(buf, N-1, 1, f);" is "telling it to read one item of size N-1".
> ...due to yet more historical situations (e.g. struct sockaddr, which has a fixed-size trailing array that is not supposed to actually be treated as fixed-size), GCC and Clang actually treat all trailing arrays as flexible arrays.
But I don't know, that doesn't seem to match the result I am getting with clang 13.1.6. It does seem to respect the array size declared in the struct, not treat it as a flexible array. I get -Warray-bounds warnings if I try to access anything past o->variable[3]. Maybe I'm misunderstanding what they're saying or my example is screwed up.
Edit: Actually, I guess it does end up treating it like a flexible array -- it produces -Warray-bounds warnings when compiling, but the resulting binary works (and doesn't trigger asan). Not sure I entirely understand it though.
Don't you need to have an "GitHub-approved" fork (i.e. use the GitHub fork button) if you want to create pull requests on the upstream project in GitHub? Or is there a way to do that from the kind of repo you're describing?
Heh, repeatedly toggling some of the switches too rapidly on there causes some interesting growth. My "EXAM" switch ended up dangling down past much of the documentation.
As far as learning what it looks like, there are photos on the site too (under "The Artifact").
The incorporation of Facebook is a bit silly but it's a student project, I guess the point was really for the students to consider the sort of unusual constraints and considerations that are required for such a long-term design. Seems unlikely anyone involved really expected to be updating that Facebook page for the next thousand years.
> Also, continued public interest is probably one of the reasons that research grant money continues to be available to study something that was found 15 years ago.
Unfortunately for Dr. Holley, it doesn't seem to have been working out that way in this case (from his page linked above):
> ...state politics in previous years have meant that we have only been able to obtain limited funding for research and as a result little progress has been made.
This was actually discovered in 2007, not recently. From the archeologist who discovered it:
> This site seems to gain a life in the media about every six months or so. Sadly, much of the information out there is incorrect. For example, there is not a henge associated with the site and the individual stones are relatively small when compared to what most people think of as European standing stones. It should be clearly understood that this is not a megalith site like Stonehenge. This label has been placed on the site by individuals in the press who may have been attempting to generate sensation about the story and have not visited the site. The site in Grand Traverse Bay is best described as a long line of stones which is over a mile in length.
Is it a second factor? The article makes it sound as though the MyGovID authorization is all that's needed to log in, and the official site (https://www.mygovid.gov.au/) says it's used "instead of usernames and passwords."
The reason I read it as being a major issue is that it is apparently (maybe I'm misreading this) described as the reason the previous effort failed:
> Earlier attempts to turn the mist into usable water failed. In 1990 fog nets at Chungungo, a fishing village north of Los Tomes, captured 8,000 litres a day. Villagers argued about how to share responsibility for maintaining the atrapanieblas.
It sounds like the nets worked, and the only negative element of the project described in the article that could account for the failure is the issues around maintenance. And then it's mentioned again in the context of open "questions" of the current project. But maybe the emphasis wasn't intended by the author, I may be reading too much into it.
What sort of maintenance does it require? The article describes it as the biggest implementation hurdle, apparently to the extent that it doomed a previous effort along the same lines, but doesn't go into detail on what it entails. Repairing rips or tears in the nets themselves?
Various farming strategies have been severely restricted in recent versions of the game; puddings don't even drop real corpses now. There are definitely still plenty of ways to loiter around and boost your score, though.
As far as all the sources I can find say, 'hone in' originated as an error for 'home in', but has become widespread enough to be considered an acceptable variant. If one of them is being let in erroneously by the nasty descriptivists at Merriam-Webster, it'd be 'hone in'. But either one gets the meaning across, so I don't see the issue.
You could always add key mappings to your .vimrc file so it works this way.