macOS Command Line
git.herrbischoff.com
git.herrbischoff.com
It's unseemly that people have to beg like this. I would be happy to pay a small annual Github subscription if it were distributed back to repo maintainers. Same thing with all the 'buy me a coffee' tags and now the 'buy me a slice of pizza' ones. Instead of funding useful bodies of work with meaningful micro-grants you have projects competing to provide people with better cups to rattle.
Everyone paid a tax each year and gets token that they can attribute to the media they want. The fund are redistributed according to the tokens.
I don't really like the idea of an automated measurement of merit / popularity. Let users decide and choose few projects they want to sponsor each year. Maybe show the current number of sponsor so big projects don't get all the votes.
At the risk of being downvoted to oblivion, I’ll say this: asking for donations is great, complaining that people are “leeching” your CC-licensed content, not so much. If you don’t have the bandwidth to maintain a project, just stop. Humanity will be fine.
This move to monetize everything is a huge step backwards (or forwards into the abyss…).
Companies still have a ton of private code that never makes its way into the open source world.
The guy can't afford to replace his 10 year old laptop, meantime rents and profits are at an all-time high. Seems like there's a few segments missing in the virtuous circle.
The marginal value of these commands is really, really low when you start comparing it to all the stuff that people could spend.
Most everyone has high rents and old laptops.
What I am is struggling to make ends meet for some time. A new laptop is near the bottom of my priorities right now. Money will run out around the beginning of February. It makes me sad to read cynical comments like this. That's all I have to say.
I hope your fortune turns and you soon find a job.
The offputting thing to me was the faulty logic of 14% of people starred donated. That’s a phenomenal donation rate that’s unprecedented. So it’s like prefacing my work with “if money rained on my front yard” or something along those lines.
And I don’t like the discussion that guilts people who don’t donate. I donate to projects on GitHub. Not much and not to yours. But it’s something. But I contribute in other ways and would like to discourage nagging people (not by you as your preamble comment was pretty benign) who don’t donate.
> have all those ppl been playing free DF for 25 years and just waiting for an opportunity to pay $30?
> Yes
* times 50 pages
https://steamcommunity.com/app/975370/discussions/0/37093075...
Something about selling tools to developers just brings out the worst of "bah, I could build that in a weekend so it's not worth anything so I'm not going to pay for it"-ness.
The flipside would be if the author put it on steam, had barely any sales, and then started complaining about how people leeched on his work for 25 years.
I will continue "bookmarking with stars" and not using half the things I star :)
(Or come on board as a consultant, either approach can work wonders)
I occasionally stumble upon such secret troves of knowledge, but I'd love to find out how these are discovered.
Is there, like, a way to intercept all `defaults`/settings reads to discover what keys are checked?
For example, the NSToolbarTitleViewRolloverDelay setting, while valid per the article, isn't listed in the output of `defaults read`
You can see a huge list of settings by typing „defaults read“
In practice, people probably just read user defaults and try to reverse engineer what they do.
Skimming this list right now a lot of the stuff I'm seeing definitely has UI settings, so a lot of these are just useful for e.g. automating the setup of a new user.
CGFontRenderingFontSmoothingDisabled
is. I tried defaults read CGFontRenderingFontSmoothingDisabled
but got: Domain CGFontRenderingFontSmoothingDisabled does not exist defaults read | grep CGFontRenderingFontSmoothingDisabled`defaults read > old` -> change setting in GUI -> `defaults read > new` -> `diff old new`
If nothing is there, you're out of luck, most likely. (I think I've had luck using -currentHost or maybe sudo sometimes though...) If there is something, `less new` and search for the string, then find the path to the key. Do a test read with `defaults read <domain> <item>` to see if you got the path right.
You can also copy plist files (cp -r /Library/Preferences, or wherever) and then diff those. A useful alias to convert to xml:
alias plist='plutil -convert xml1 -o /dev/stdout'
This doesn't help with "secret" settings that aren't exposed through the UI, but can be handy for creating setup scripts.
Anyone have any ideas what I can do to resolve?
Machine details below:
Software:
System Software Overview:
System Version: macOS 12.6 (21G115)
Kernel Version: Darwin 21.6.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
Time since boot: 4:14
Hardware: Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro18,1
Chip: Apple M1 Pro
Total Number of Cores: 10 (8 performance and 2 efficiency)
Memory: 32 GB
System Firmware Version: 7459.141.1
OS Loader Version: 7459.141.1Edit: This post would indicate that it's a bug in the interaction between the Mac and the monitor and is not fixed: https://forums.macrumors.com/threads/fuzzy-text-with-lg-38wn...
> system_profiler SPDisplaysDataType | grep Resolution
Resolution: 3840 x 1600 (Ultra-wide 4K)
And ah dang, thanks for the link. Someone there mentioned that getting a higher PPI monitor could help and might be the only way to get HiDPI modes. I did notice when I used switchResX for a bit that the HiDPI mode was greyed out and unavailable. Guess I'm going to have to return this monitor :(* Remember to log out and log back in after you set font smoothing to 0. For me, this tweak helped a lot with clarity but I initially didn't think it was working because I didn't know you had to log out.
* In general I've found Macs just suck at DPI scaling. If I'm not mistaken, your monitor is around 109 PPI, which isn't really that high compared to the internal screen (~250ppi), and firmly in the "non-Retina" UI elements zone. Check out these blog posts (https://bjango.com/articles/macexternaldisplays/, part 2: https://bjango.com/articles/macexternaldisplays2/) for more info on how this stuff works.
Imagine my surprise when I found out my 27" 4K screens that look incredibly sharp on Windows at 163ppi are actually in the "bad zone" for Macs, and look bad at native resolution. As a workaround I run them scaled @ 3360 x 1890 and then set my browser to permanent 90% zoom level. Kind of embarrassing that Windows has completely lapped Apple in terms of good sharp UI at flexible scaling levels. I mean you can set Windows DPI scaling down the single % point, it's great.
I am not sure...? How can I find out? Thanks for that gist, I'll look into it after checking whether BetterDisplay resolves my issues as another commenter pointed me to.
> Remember to log out and log back in after you set font smoothing to 0
Hehe yeah. I have actually been operating under the assumption that I needed a full restart, which I have done several times :P (though this isn't so bad since the machine starts pretty dang quick).
> In general I've found Macs just suck at DPI scaling
I'm learning this :( It's very frustrating and disappointing.
Are there truly no displays in the 30"+ category that are good for retina?
[0]:https://bjango.com/images/articles/macexternaldisplays/displ...
EDIT: I'm seriously wondering whether I ought to just get the Studio Display. It's $1,599 (or $1,899) which is not that much more than I spent on the LG (~$1,160)
Personally I won't be upgrading from my 2x 27" 4k displays until
* I can get 2x 27" 4k with 144hz+ at a reasonable price
* I can get an ultrawide that matches the PPI and is just effectively 2x screen space
* 5k+ gets cheaper/commonplace
Thanks again for the replies.
This is all configured in the display's own settings, not in the OS.
What do you mean by "reset" exactly? You mean any and all display changes I've made?
The HDPI icon pop ups automatically on ventura in display settings.
I would also change the cable and try a different one if that doesn't work. Sometimes the DP cable end up causing issues with monitor recognition.
No. I meant if you have a DP to USB type C cable, you may switch to see if issue resolved.
Try plugging it in and out a few times (yes, it worked for me when it went back to not recognizing).
I have the same mac but a different 4K monitor. Sadly, I don't know any other solution.
Macbook display and scaling handling on external monitors is one of the worst I have experienced by a long margin so know you are not alone.
YES YES YES. It's how I learned my way around Unix back in SunOS days. I literally started with "man intro" and worked my way out from there. Sun's documentation was _excellent_.
Sadly, Linux and even BSD man pages are more hit or miss compared to Sun's documentation. But they are still a great place to start.
I personally gave up on Spaces completely because of this. Now I just have everything on a single space, and move through apps instantly using my rcmd app (https://lowtechguys.com/rcmd)
Anybody else experience similar things?
Now, I haven't tested your issue specifically, because I do not use Outlook.
But Rogue Amoeba is one of the best remaining Mac app developers (also: Panic), and they made an app that provides app-based sound control. Worth checking out if you can't solve it with Outlook's settings.
`set -o vi`
It applies vi rules to your command line.
The gory details: https://www.gnu.org/software/bash/manual/html_node/Miscellan...
If an app has this effect, I can't even imagine what an OS manual would feel like in these days.
I wish I could provide a proper manual but I can barely keep up with updating the app website with the rate of change in technologies. A major OS upgrade would need an army of writers to update manual on time.
Not that I wouldn't love it. It would be tremendously useful to have a PDF where I can Cmd-F obscure tidbits which I often need in building MacOS apps.
I just think it's impractical given the complexity of software in this age.
The only problem I've had is dylib files relentlessly moving forward in versions and old ones not being available anymore, but i don't _think_ that's really an apple problem. That and the M1 architecture transition has moved some folders around for reasons I don't understand.
My ancient scripts still work just fine.
The only difference is that people like to make excuses for Apple.
The web was built for lots of distributed servers hosting and users hitting them. Only using “big servers” is bad for the world.