The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I'd be concerned of little animals, such as squirrels, rats, or mice in your attic chewing on wires. If you've got tree limbs near your house, they'll find a way to get inside to keep warm during the winter months.
Trust me, we've looked!
He's been throwing up for two weeks or so - and six or eight visits to the vet - but today he's started on "normal" food mixed with "prescription" food for the first time, and kept it all down so far. 30g doses, every two hours ...
We think he was allergic to the anti-puke medicine he was given - ranitidine - and it made him worse instead of better. Fortunately, cats can go a good time without food, but it's been worrying. Hopefully he's turned the corner, and can go outside again next weekend. He doesn't like to poo indoors at all and can "retain" for three or four days when eating normally, so a week while he's keeping little or nothing down is probably not too much difficulty for him.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Does your fan have an IR remote? If so, try putting a piece of black electrical tape over the pickup and see if that cures the problem.
Years ago, our TV used to occasionally turn off while we were watching it. I put a curtain over the window and that behavior stopped. When the neighbors moved out, I didn't need the curtain anymore. I figure they probably had the same brand TV as we did, and ours was picking up their remote's signal through the windows.
Of course, if that fan has a radio remote, try a jacob's ladder[^] in the corner of the room
We can program with only 1's, but if all you've got are zeros, you've got nothing.
I'm not looking for an answer per se but just discussing something I find interesting.
Recently, a coworker and I have experienced some errors when
1. Visual Studio / MSBuild attempts to clean files and build : my coworker would receive errors that the "file and path are too long".
The Unicode versions of the Win32 file handling functions allow a few thousand characters in paths, so there's that. I would assume that VS / AS are using those functions. Or there could be some trickery going on.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
Win32 file handling functions allow a few thousand characters in paths
That's interesting. How does the file system handle that*? How does it then, in turn, display those in File Explorer? Well, maybe that's the point, File Explorer doesn't quite handle those. Which doesn't exactly make sense why MS would not have File Explorer set up for that when they are the creators of the
API file handling functions.
Also, .NET uses Unicode by default, right? But I'm not sure you can actually create a file/path that is longer than 260 (max_path), right? This is interesting to me.
In the ANSI version of this function, the name is limited to MAX_PATH characters. To extend this limit to 32,767 wide characters, call the Unicode version of the function and prepend "\\?\" to the path. For more information, see Naming Files, Paths, and Namespaces.
For information on special device names, see Defining an MS-DOS Device Name.
To create a file stream, specify the name of the file, a colon, and then the name of the stream. For more information, see File Streams.
Tip Starting with Windows 10, version 1607, for the unicode version of this function (CreateFileW), you can opt-in to remove the MAX_PATH limitation without prepending "\\?\". See the "Maximum Path Length Limitation" section of Naming Files, Paths, and Namespaces for details.
*I remember how this is handled with long names versus 8.3 with the tilde-names, etc.
Was it ever possible to create file / path longer than 260? I'm not sure.
Yes. It's been possible using the alternate API set since early versions of NT (IIRC since NTFS was a thing). The default APIs had never supported it because of the amount of C/C++ code that looks like; char path; GetFilePath(path); that would buffer overflow if longer paths were allowed.
I first encountered extra long paths over a decade ago when (ir)Rational Clearcase would create >260 paths pulling from the server, and then a second part of the toolset (and most windows apps) would then barf on the path length being too long. This served as a check on my coworkers creating overly stupidly deep folder structures in our source (and document) control system at the time.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
Thanks for reading and posting in. Really appreciate the input.
I've actually written code that calls CreateFileW() API and I'm attempting to create long file names.
I've even drawn the interest of an "old MSFT system engineer" and we're discussing it further down a bit.
Check out the entire source and the explanation if you have interest and some time. My latest post with full source code you can run in LINQPad is at: CreateFileW() source :The Lounge[^]