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").
This was actually genius, though it was/is so annoying typing these verbose paths
MS Teams channels cannot contain MS-DOS device names
331–340 of 364 posts
Re: MS Teams channels cannot contain MS-DOS device names
#332Earlier quoted context omitted.
Brevity forces thought, which I prefer to "Putting a Sentence in a File Name.docx". FORTRAN originally had the same limitation for function names, and that lead to some classics such as GEMM and SAXPY.
When it comes to file names, I disagree that brevity serves a useful purpose. I name my files like I’m an Amazon reseller so that I’m sure to find it with Search later no matter which detail I remember. “Budget Spreadsheet (worked on with Jane) with projections with and without buying a new Tesla Model Y or Chevy Chevrolet Bolt - 2023 2024 2025.xlsx” that’s my idea of a file name.
Re: MS Teams channels cannot contain MS-DOS device names
#333Earlier quoted context omitted.
Yeah those 8+3 file names sure birthed some creative abbreviations. Necessity, mother, all that
Brevity forces thought, which I prefer to "Putting a Sentence in a File Name.docx". FORTRAN originally had the same limitation for function names, and that lead to some classics such as GEMM and SAXPY.
Woah, your examples: https://www.ibm.com/docs/en/essl/6.2?topic=vss-saxpy-daxpy-c...
Re: MS Teams channels cannot contain MS-DOS device names
#334I can't be the only one thinking that generally MS Team is offering probably worst experience in the messaging market.
Highlight some text, right click and select copy. Teams copies some other random text and not what you highlighted. Grrr!
Any product that can't even get basic copy and paste right is garbage in my opinion.
The only reason people use it is that it's bundled for "free" with MS Office.
Re: MS Teams channels cannot contain MS-DOS device names
#335This 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.
Microsoft, when confronted with a problem, think "I know, I'll build it on top of SharePoint."
If you think "I know, I'll build it on top of SharePoint" the problem was inside you all along.
Re: MS Teams channels cannot contain MS-DOS device names
#336Earlier 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…
(btw most IT folks prefer powershell, if only because all the management tools are powershell modules)
Re: MS Teams channels cannot contain MS-DOS device names
#337Earlier quoted context omitted.
they're SharePoint limits, man. Teams is backed by SharePoint and it's not a secret, nor is it embarrassing.
And SharePoint itself is backed by the Windows Filesystem, which respects a lot of old DOS stuff for backwards compatibility.
Re: MS Teams channels cannot contain MS-DOS device names
#338Earlier quoted context omitted.
Not similar, I built that house. (I'm Kenton.) Or do you mean the new one, alluded to on the site? It's almost done... not ready to share yet. ;)
Great site - I am reading all your posts about the LAN party house now. Do you have the real estate listing of the house when it was up for sale? I'm just curious as to where it was located - you mentioned a sliver of land, and I saw the asking price ($2M in Palo Alto) so I'm curious to see what it looked like from the outside and its location, if you don't mind sharing!
Sorry about that.
There are a few more pictures of the house on the architect's (my father's) web site: https://vardaarchitecture.com/
Look under "Residential - Palo Alto". But note that the furniture in these pictures was staging furniture that the real estate agents put in there to sell the house, NOT stuff I ever chose or used! (I hate it.)
Re: MS Teams channels cannot contain MS-DOS device names
#339Earlier quoted context omitted.
love this story very much. I had no idea WINE had been around for that long and was able to play starcraft etc. I have really great memories of playing starcraft with friends back in the day.... that game had enough staying power that we could all get into and out of in middle school and then again in college!
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.
Re: MS Teams channels cannot contain MS-DOS device names
#340Earlier quoted context omitted.
I used to love slackware, by far the best linux experience. It just worked well.
I still do. It still does...
I've been considering going back to it though, but I know that I need to do it in measured steps.
Care to share any more about your slackware experience?