Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

Post reply on HN
Print view View original

321–330 of 364 posts

Re: MS Teams channels cannot contain MS-DOS device names

#321

Post by neurocline »

saghm wrote: post #265
cogman10 wrote: post #206

Earlier quoted context omitted.

Wine is nearly as old as linux. First released in 1993. I had some awkward conversations with my parents as a teenage nerd looking into "winehq". They didn't believe me that it had nothing to do with alcohol.

Even today, Blizzard games tend to run pretty easily on Wine. I always attributed it to them using a fairly old tech stack, but maybe it's the reverse and Wine development has just continued to go above and beyond for those games.

It was mostly on purpose, that Blizzard games worked well in Wine. We even fixed a few things in our code from time to time that accidentally made Wine emulation hard.

Re: MS Teams channels cannot contain MS-DOS device names

#322

Post by stouset »

TazeTSchnitzel wrote: post #285
FirmwareBurner wrote: post #277

Earlier quoted context omitted.

>They're also good at getting security clearances since they never do anything I never understood why you should mass deny security clearances to people who like to "party".

They don't want people who might have done something embarrassing in their past, because foreign adversaries might try to blackmail them with that.

On the flip side, those are the exact people who often wouldn’t be embarrassed or ashamed of that kind of behavior. I’ve done a lot of things, and I’d openly admit just about all of it if anyone asked.

On the other hand if you do find a Mormon who took some liberties in an earlier time in their life…

Re: MS Teams channels cannot contain MS-DOS device names

#323

Post by m00dy »

CSMastermind wrote: post #284
ilyt wrote: post #158

Earlier quoted context omitted.

It's absolute fucking garbage when it comes to text chat. It boggles my mind that they had so many examples on how to do it right and fucked it up so badly

I honestly think they should fire every single PM on that team. Like literally just keep the engineers and give them no more direction than make it better and designers need to approve any UI changes. That's it.

I just called Satya and told him that he should talk to Pavel to get some advise for the UI experience.

Re: MS Teams channels cannot contain MS-DOS device names

#324

Post by toyg »

nullindividual wrote: post #300
conscion wrote: post #10

This is most likely due to those names not being allowed for files or folders in the Windows file system. MS Teams channels create a matching folder in SharePoint where file attachments are stored.

SharePoint stores files as binaries in a SQL database (or a reference to an Azure Blob Store). The filesystem doesn’t come into play.

But it now has a feature to integrate seamlessly with OneDrive, linking or replicating a folder on the user machine. Hence, I expect it has the same limitations in terms of naming.

Re: MS Teams channels cannot contain MS-DOS device names

#325

Post by Wildgoose »

minsc_and_boo wrote: post #141
gmiller123456 wrote: post #101

Earlier quoted context omitted.

Snopes is not a good reference to cite, they have changed many artlcles based on research they missed. They tend to just want to get a page up when a topic is popular, then research it later.

I mean, correcting factual errors is pretty good trait for a fact-checking site, right?

Yes, but surely you would do that first?

Re: MS Teams channels cannot contain MS-DOS device names

#326

Post by veave »

yjftsjthsd-h wrote: post #197
veave wrote: post #181

Earlier quoted context omitted.

I think the confusion comes from the fact that some platforms render it as a drawing as if it was an emoji. I never understood why...

Speaking only for myself, the confusion comes purely from the fact that I think of all text as "ASCII" or "Unicode" (...or "something else that nobody should use in the modern era"), and I don't really distinguish within "valid unicode that isn't ascii".

™ is part of extended ASCII :)

Re: MS Teams channels cannot contain MS-DOS device names

#328

Post by boffinAudio »

astrange wrote: post #274
FirmwareBurner wrote: post #243

Earlier quoted context omitted.

Thanks, Mormons are some of the most nicest and chill Americans I've met in Europe. Had no idea alcohol is taboo.

They're also good at getting security clearances since they never do anything, so those might've been CIA agents.

They're good at being CIA agents because they are supple and compliant and the CIA has tools to make that compliance into nationalistic zealotry that rivals the capabilities of most religions, having refined it through operations such as paperclip, etc..

Re: MS Teams channels cannot contain MS-DOS device names

#329

Post by keepamovin »

nomel wrote: post #320
Anthony-G wrote: post #139

Earlier quoted context omitted.

Unix shell scripts will break when filenames/paths have spaces if variable expansions are not quoted, resulting in word splitting and filename expansion (globbing). This is something that is drilled into learners by all good teachers, e.g., https://mywiki.wooledge.org/Quotes#When_Should_You_Quote.3F

Wait until you hear about `make`, completely cementing the idea of '_' as space for decades to come [1]! Related, any time I join a new group, that uses bash in any capacity, I introduce them all to the `shellcheck` utility [2], and run a shell script of the person with the largest ego through, as a "demo". [1] https://stackoverflow.com/a/9838604/1487072 [2] Online version: https://www.shellcheck.net/

Awesome! Thanks for introducing me to this. I mean my ego ha

Re: MS Teams channels cannot contain MS-DOS device names

#330

Post by keepamovin »

WirelessGigabit wrote: post #125
ChrisSD wrote: post #76

Earlier quoted context omitted.

On Unix perhaps. Windows forced IT folks to deal with the issue by having folders like "Program Files". Even the user's folder used to be in "Documents and Settings" (but they backed down from that eventually and now it's just "Users").

To this date one needs to be careful with executing applications and spaces in the path. For example: D:\test>dir ... 08/10/2023 09:29 AM . 08/10/2023 09:30 AM Foo Bar 08/10/2023 09:35 AM 79 Foo.bat ... D:\test>dir "Foo Bar" ... 08/10/2023 09:30 AM . 08/10/2023 09:29 AM .. 08/10/2023 09:35 AM 79 Foo.bat ... D:\test>type Foo.bat @echo off echo Executable: %0 echo Path to executable: %~dp0 echo Params: %* D:\test>type…

Nice example!
Post reply on HN