Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

241–250 of 364 posts

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

#241

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.

Your parent being concerned about you browsing something about wine? You're definitely not be French/European. Here our parents give us wine :) American?

mormon family.

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

#242
post #184

Earlier quoted context omitted.

It doesn’t make sense tbh, it just causes confusion when someone is using terminal. Slashes in file names are forbidden everywhere except Mac, it needs to be changed in order to send it anywhere or use in some apps. But I think colon is used much more in names. I don’t get why did they do that.

Based on this logic, do we ban everything that is banned somewhere? Surely we can aim higher than the lowest common denominator.

Slashes are used in paths, so most programs that aren’t Mac-exclusive would use them to build a path to file. To make it work properly in cross-platform programs you’d need to write platform-specific code to handle that. It just adds complexity and possible errors. Even system terminal doesn’t display it as slash and it doesn’t work if you write slashes.

For users of other platforms (at least 90% of desktop market) it would just display as slashes. Just not implementing this workaround would make it predictable when moving and using files.

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

#243

Earlier quoted context omitted.

Your parent being concerned about you browsing something about wine? You're definitely not be French/European. Here our parents give us wine :) American?

mormon family.

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

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

#244

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.

I worked at a bank that had a windows-based trading system and for some reason created folders to hold the details of each book. There were issues when a trader decided to call a book "LPT1".

What is a 'book' in the context of trading?

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

#245
post #26

Earlier quoted context omitted.

Sometimes I wish we had fresh clean slate OS. Not the baggage of DOS or Unix... Something modern and sensible without insanity of either system.

You need to clean slate the entire world because everything is interconnected. If , for example, you want files to be more than streams of bytes then you basically have to re-invent the Internet as well. The older I get, the more I realize that we don't need a clean slate OS. If you pick any modern OS right now, the most annoying parts are never the parts that were from 30 years ago; it's almost always the newest thi…

The opposite is true. You can convert anything to anything at the boundary. The beauty of looser coupling

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

#246

Earlier quoted context omitted.

I used to love slackware, by far the best linux experience. It just worked well.

Probably. I just remember installing from a dozen+ 3.5" floppies onto my pizzabox '386 and breathing a sigh of relief when it booted.

I think I needed 17 floppies ... and I could only scrounge up about 8, so I assumed it wouldn't need the earlier ones again and reused them for later parts. It worked! I didn't use Slackware much though, as I had no way to connect that machine to the internet, so it was really hard to learn how to do stuff.

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

#247
post #244

Earlier quoted context omitted.

I worked at a bank that had a windows-based trading system and for some reason created folders to hold the details of each book. There were issues when a trader decided to call a book "LPT1".

What is a 'book' in the context of trading?

Just an old name for a portfolio of transactions

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

#248

Earlier quoted context omitted.

> Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. Arch, I suppose.

Arch wasn't around in 1998. I'm going to put my money on Slackware.

Ooooh that brought me memories. At the time testing (around '98) all the nerdy rage was on testing the different distros such as Caldera, Debian, Corel, Mandrake. I remember at the same time compiling my first kernel in FreeBSD (ordered the CDs from WalnutCreek website! what a time). My parents where not amused that I broke the home PC several times installing this thing over Windows

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

#249
post #184

Earlier quoted context omitted.

It doesn’t make sense tbh, it just causes confusion when someone is using terminal. Slashes in file names are forbidden everywhere except Mac, it needs to be changed in order to send it anywhere or use in some apps. But I think colon is used much more in names. I don’t get why did they do that.

Based on this logic, do we ban everything that is banned somewhere? Surely we can aim higher than the lowest common denominator.

Given the preponderance of 3 major operating systems, I'd think it's sensible for user-level applications to disallow creation of filenames that would cause problems on any of them. Except arguably that could even include using spaces or periods... obviously in an ideal world such restrictions wouldn't exist, but I'm not sure how to realistically push for such a world. E.g. my suggestion would be to reserve non-printable characters (below Ascii 32) for use as separators/delimiters in as many contexts where that's workable. Obviously some sort of convention would then need to exist as to how they were displayed and typed in, and I very much doubt I'll ever see it happen, but I'm sure it would solve a lot of mis-parsing bugs that show up with frustrating regularity.

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

#250
post #244

Earlier quoted context omitted.

I worked at a bank that had a windows-based trading system and for some reason created folders to hold the details of each book. There were issues when a trader decided to call a book "LPT1".

What is a 'book' in the context of trading?

Set of related trades.
Post reply on HN