Big list of software that cannot handle spaces or accents in paths
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
There are legitimate cases where you actually want them to be able to rename files you're editing.
More importantly, since a file's name isn't the file, it makes no sense that renaming a file you're editing would create a new file at the old name.
Well, it depends on how you look at it. When you open a file in Microsoft Word, is the file the document itself or simply a record of it? If it's the document itself, then what you are saying makes sense. If it's a record of the document, then when you 'open' the file you are loading the document into Word and when you 'save' the file you are recording the document to disk. Thus, the file itself has no special significance and what matters is the location (from the user's point of view, i.e. file path) that the document gets recorded to.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@boomzilla said in Big list of software that cannot handle spaces or accents in paths:
@lb_ said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
The idea that a human being would ever see or, even worse, have to type in a path was completely alien to that platform.
Thankfully we do have at least one modern widely-used filesystem that works properly: Google Drive. Filenames can contain any characters at all, the concept of a path doesn't make sense and you never need to type it, a file can exist in multiple directories at once, etc. although I think unfortunately a file can only have one name, changing the name in one place changes it everywhere :(
I find it infuriatingly difficult to find stuff in there.
I find it difficult to find stuff anywhere. Seriously, it feels like if you don't spend the extra effort to keep your documents organized, your documents won't be organized.
Almost like a normal filesystem
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Fuck that. What happens when someone else renames the file?
Well in a modern system, don't give them permissions to it if you don't want them to dick with it.
In the old Macintosh system, yes there were not really any enforced permissions so this could happen.
That's also why they could get away with opening shit by ID in the first place, because they don't have to check permissions. On POSIX, access permissions are checked on every directory from the root down to determine whether you can access a file—that's essential for controlling access to other people's file systems that you can mount but not write to.
Of course you can stick that information in a separate database and enjoy watching it go inconsistent and full of outdated information. coughgrouppolicycough
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
I've never seen this. Is this some api in the kernel layer?
I think C itself is designed that way, isn't it? If you open a file and keep around the file descriptor, you have an ID to it which is entirely separated from the file's name. It's been ages since I did C.
That's the kernel API:
open(2)
gives you a file descriptor that you can keep around. It's called "keeping the file open" and every serious programming language I know has something equivalent. You can get the inode from that descriptor, which is an identifier for the file that is independent of the name, but there's no way to open a file using that for the above security reasons.
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Yeah, many OSs can't all follow one design.
The problem isn't that POSIX/Linux is a different design, the problem is that it's a bad design that makes it virtually impossible to write 100% correct code.
There's certainly something to improve about that. The Windows way of using a sequence of 16-bit values that may or may not be well-formed and is treated to half-assed transformations like case folding on a file system level which may or may not be consistent with your locale or even defined is just as certainly not the one to go.
-
@laoc said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Fuck that. What happens when someone else renames the file?
Well in a modern system, don't give them permissions to it if you don't want them to dick with it.
In the old Macintosh system, yes there were not really any enforced permissions so this could happen.
That's also why they could get away with opening shit by ID in the first place, because they don't have to check permissions. On POSIX, access permissions are checked on every directory from the root down to determine whether you can access a file—that's essential for controlling access to other people's file systems that you can mount but not write to.
I don't really see why the same permission system would be impossible to do with IDs instead if filenames. It's still identifying files, and files have metadata, and you can retrieve parent directory just as well.
Of course you can stick that information in a separate database and enjoy watching it go inconsistent and full of outdated information. coughgrouppolicycough
On the other hand, Unix doesn't let you give permissions to a specific group other than the owner. And it doesn't differentiate between permission to create and permission to delete.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
That's also why they could get away with opening shit by ID in the first place, because they don't have to check permissions. On POSIX, access permissions are checked on every directory from the root down to determine whether you can access a file—that's essential for controlling access to other people's file systems that you can mount but not write to.
I don't really see why the same permission system would be impossible to do with IDs instead if filenames. It's still identifying files, and files have metadata, and you can retrieve parent directory just as well.
If you don't support hardlinks then yes, you can. But it does.
Of course you can stick that information in a separate database and enjoy watching it go inconsistent and full of outdated information. coughgrouppolicycough
On the other hand, Unix doesn't let you give permissions to a specific group other than the owner.
Are you looking for the ancient group permissions or the ACLs from the 80s?
And it doesn't differentiate between permission to create and permission to delete.
Could be a nice-to-have, although I wouldn't know where I'd have needed more than the sticky bit supports.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@heterodox said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Macintosh was designed to refer to files by their identifier. The filename was just yet another piece of meta-data. So you could do reasonable stuff like this:
You may already know this, but the Win32 API allows you to refer to files by their identifier as well.
But can I traverse directories using only identifiers? Can I retrieve current working directory as an identifier? Can I receive files from drag'n'drop as identifiers?
Actually, I think yes. I remember looking into this when researching long file paths. Once you get a handle you can use that to do all sorts of things...
-
@laoc said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
That's also why they could get away with opening shit by ID in the first place, because they don't have to check permissions. On POSIX, access permissions are checked on every directory from the root down to determine whether you can access a file—that's essential for controlling access to other people's file systems that you can mount but not write to.
I don't really see why the same permission system would be impossible to do with IDs instead if filenames. It's still identifying files, and files have metadata, and you can retrieve parent directory just as well.
If you don't support hardlinks then yes, you can. But it does.
I still don't see how having names is relevant. You could have several IDs refer to the same inode. Also, I've never heard of a legit use case for hard links that wouldn't be better with sift links or regular copies.
Of course you can stick that information in a separate database and enjoy watching it go inconsistent and full of outdated information. coughgrouppolicycough
On the other hand, Unix doesn't let you give permissions to a specific group other than the owner.
Are you looking for the ancient group permissions or the ACLs from the 80s?
Have Unix permissions evolved beyond rwxr-xr-x? If so, TIL.
And it doesn't differentiate between permission to create and permission to delete.
Could be a nice-to-have, although I wouldn't know where I'd have needed more than the sticky bit supports.
It's kinda impressive how many hacks Linux people invent to get around not having actual features.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@heterodox said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Macintosh was designed to refer to files by their identifier. The filename was just yet another piece of meta-data. So you could do reasonable stuff like this:
You may already know this, but the Win32 API allows you to refer to files by their identifier as well.
But can I traverse directories using only identifiers? Can I retrieve current working directory as an identifier? Can I receive files from drag'n'drop as identifiers?
Actually, I think yes. I remember looking into this when researching long file paths. Once you get a handle you can use that to do all sorts of things...
I'm pretty sure you don't get a handle in drag'n'drop event. For the rest, [citation needed].
-
@boomzilla said in Big list of software that cannot handle spaces or accents in paths:
@lb_ said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
The idea that a human being would ever see or, even worse, have to type in a path was completely alien to that platform.
Thankfully we do have at least one modern widely-used filesystem that works properly: Google Drive. Filenames can contain any characters at all, the concept of a path doesn't make sense and you never need to type it, a file can exist in multiple directories at once, etc. although I think unfortunately a file can only have one name, changing the name in one place changes it everywhere :(
I find it infuriatingly difficult to find stuff in there.
You don't remember the Fake-UUIDs?
I've never had any trouble finding anything I put in Google Drive. Probably owing to the fact that I have less than 142 files in it at present.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@heterodox said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Macintosh was designed to refer to files by their identifier. The filename was just yet another piece of meta-data. So you could do reasonable stuff like this:
You may already know this, but the Win32 API allows you to refer to files by their identifier as well.
But can I traverse directories using only identifiers? Can I retrieve current working directory as an identifier? Can I receive files from drag'n'drop as identifiers?
Actually, I think yes. I remember looking into this when researching long file paths. Once you get a handle you can use that to do all sorts of things...
I'm pretty sure you don't get a handle in drag'n'drop event. For the rest, [citation needed].
You want a citation for my thoughts? That's... a rather strange request. I don't think I can really publicly serialize such to be honest....
-
@tsaukpaetra I want a citation from MSDN that your thoughts aren't bullshit you just made up and there's actually APIs that do that.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra I want a citation from MSDN that your thoughts aren't bullshit you just made up and there's actually APIs that do that.
Search yourself! I'm not your mother. I owe you nothing.
-
@tsaukpaetra that's not how it works. You made the claim, you support it.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra that's not how it works. You made the claim, you support it.
I made a claim that I thought something. There's no requirement to support anything. Fuck you.
-
@tsaukpaetra protip: if you don't explicitly state that you don't believe you're correct, people will assume you believe you're correct - and will hold you to the same standards as everyone else who tries to pass their statements as true.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra protip: if you don't explicitly state that you don't believe you're correct, people will assume you believe you're correct - and will hold you to the same standards as everyone else who tries to pass their statements as true.
Rejected. Next!
Edit:
I think the sky is actually a deep red.
Now, how many people ACTUALLY think I ACTUALLY believe this?
-
@tsaukpaetra When you state it like that, it sounds you're pretty serious about it. The most likely conclusion is that you're on vacation in Sydney.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra When you state it like that, it sounds you're pretty serious about it. The most likely conclusion is that you're on vacation in Sydney.
State it like what? What mystical context are you deriving from these latin symbols that I'm apparently conveying?
Thanks for the vacation destination recommendation though.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra When you state it like that, it sounds you're pretty serious about it. The most likely conclusion is that you're on vacation in Sydney.
State it like what? What mystical context are you deriving from these latin symbols that I'm apparently conveying?
When people start with "I think", it usually means they're pretty damn sure what they say, they just don't want to be financially or morally liable if their information turns out to be wrong and someone gets in trouble because of it. I know, it might be counterintuitive for robots that full phrases have different meaning than the words they're made of, but that's how human communication works.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
When people start with "I think", it usually means they're pretty damn sure what they say,
Citation. Fucking. Needed.
-
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
https://www.collinsdictionary.com/dictionary/english/i-think
Citation invalid, does not support posit.
-
@tsaukpaetra What do you mean invalid? It literally says "You use 'I think' in conversations or speeches to make your statements and opinions sound less forceful, rude, or direct." As in, the "I think" is meaningless fluff that people add for politeness, not to actually pass any sort of information. A sentence with "I think" has literally the same meaning as a sentence without "I think", save for the disclaimer property.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
As in, the "I think" is meaningless fluff that people add for politeness, not to actually pass any sort of information.
The lack of meaning does not suppose:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
they're pretty damn sure what they say,
-
@tsaukpaetra are you being purposely obtuse, or are you actually retarded?
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra are you being purposely obtuse, or are you actually retarded?
Which would you prefer?
Because all I ask is for you to do what you asked me.
And you repeatedly fail.
-
@laoc said in Big list of software that cannot handle spaces or accents in paths:
That's also why they could get away with opening shit by ID in the first place, because they don't have to check permissions. On POSIX, access permissions are checked on every directory from the root down to determine whether you can access a file—that's essential for controlling access to other people's file systems that you can mount but not write to.
Not sure what that has to do with anything. Just walking the chain of parent directory ids instead of fumbling around with slashes in a string seems just as possible a lot easier to me...
@laoc said in Big list of software that cannot handle spaces or accents in paths:
If you don't support hardlinks then yes, you can. But it does.
Again I'm not sure I see the problem. A hard link is basically just another directory entry for the same file, no? As such it would have its own ID, parent directory and chain of parents to walk to check permissions.
-
@ixvedeusi said in Big list of software that cannot handle spaces or accents in paths:
Again I'm not sure I see the problem. A hard link is basically just a
nothercopy of the directory entry for the same file, no? As such it would haveits ownthe same ID just in another list, parent directory and chain of parents to walk to check permissions.Clarified slightly. Not sure about the permissions part.
-
@tsaukpaetra I would prefer if you communicated like a normal human being and don't weasel out of your bullshit statements that Windows can do what it can't do. You said that you think that there's API and that you remember reading about it. I expressed skepticism due to never hearing of it, and said I won't believe it until I see it. To which you responded that I should google it up myself and not expect people telling me about the feature to actually show me the feature. Seriously, what the fuck is wrong with you!?
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
your bullshit statements that Windows can do what it can't do.
I never claimed this.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
You said that you think that there's API and that you remember reading about it.
Are all statements that you make from memory 100% infallible, and your memory is perfect? Please, by all means, apply your reality to mine, for sadly I have found this woefully incorrect.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I expressed skepticism due to never hearing of it, and said I won't believe it until I see it.
This if fine. However I am under no obligation to lead you to this proof you so desire.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
Seriously, what the fuck is wrong with you!?
I don't know. Perhaps you can "I think" it and tell me?
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
people telling me about the feature to actually show me the feature.
I think Cortana can help me bury bodies.
How would you go about showing that feature? Is it really that difficult to imagine what possible steps might be involved in undertaking such a task? Perhaps this is not the right thing for you then.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
your bullshit statements that Windows can do what it can't do.
I never claimed this.
You absolutely did claim this. A weak unsupported claim with lots of weasel wording is still a claim.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
You said that you think that there's API and that you remember reading about it.
Are all statements that you make from memory 100% infallible, and your memory is perfect?
No, but I don't act like asshole when people doubt my fallible, imperfect memory. Even when I say I just think and not actually know something.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I expressed skepticism due to never hearing of it, and said I won't believe it until I see it.
This if fine. However I am under no obligation to lead you to this proof you so desire.
You're not. You could just shut up then and there. But nooooo, you had to make that scene with "I ain't yo mama, google it yourself".
@gąska said in Big list of software that cannot handle spaces or accents in paths:
Seriously, what the fuck is wrong with you!?
I don't know. Perhaps you can "I think" it and tell me?
I think you're genuinely retarded.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
your bullshit statements that Windows can do what it can't do.
I never claimed this.
You absolutely did claim this. A weak unsupported claim with lots of weasel wording is still a claim.
I claim you're butthurt I won't suck your pussy.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
You said that you think that there's API and that you remember reading about it.
Are all statements that you make from memory 100% infallible, and your memory is perfect?
No, but I don't act like asshole when people doubt my fallible, imperfect memory. Even when I say I just think and not actually know something.
Like now? Indeed.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I expressed skepticism due to never hearing of it, and said I won't believe it until I see it.
This if fine. However I am under no obligation to lead you to this proof you so desire.
You're not. You could just shut up then and there. But nooooo, you had to make that scene with "I ain't yo mama, google it yourself".
Your the one who can't stand schoolyard name-calling. That's too sad.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
Seriously, what the fuck is wrong with you!?
I don't know. Perhaps you can "I think" it and tell me?
I think you're genuinely retarded.
Citation needed. Prove it, you made the claim, I asked you for the proof, now you must oblige.
Edit: after all,
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra that's not how it works. You made the claim, you support it.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
Clarified slightly.
That's not actually a clarification but a correction, it doesn't mean the same thing as I typed (or at least meant). I still can't see much of a problem with permissions checking either way.
Thinking about it, it seems to me that one could in fact rather easily implement such a file system on top of any file system which supports xattrs: Just let the wrapper file system generate random unique names for all files and directories, which it never shows to anyone. Use that as the file / directory's "ID", and stuff the actual user-visible file name into the xattrs.
-
@ixvedeusi well you weren't wrong exactly, which is why I wrote clarification.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
your bullshit statements that Windows can do what it can't do.
I never claimed this.
You absolutely did claim this. A weak unsupported claim with lots of weasel wording is still a claim.
I claim you're butthurt I won't suck your pussy.
And you're just as wrong as when you claimed you can get CWD as handle instead of path.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
You said that you think that there's API and that you remember reading about it.
Are all statements that you make from memory 100% infallible, and your memory is perfect?
No, but I don't act like asshole when people doubt my fallible, imperfect memory. Even when I say I just think and not actually know something.
Like now? Indeed.
When other people are assholes to me, sure, then I will totally act like an asshole.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I expressed skepticism due to never hearing of it, and said I won't believe it until I see it.
This if fine. However I am under no obligation to lead you to this proof you so desire.
You're not. You could just shut up then and there. But nooooo, you had to make that scene with "I ain't yo mama, google it yourself".
Your
I fucking hate you.
Your the one who can't stand schoolyard name-calling. That's too sad.
I can stand name calling. But I can't stand this attitude of making a bunch of statements and then acting like it's not your responsibility to prove them.
@gąska said in Big list of software that cannot handle spaces or accents in paths:
Seriously, what the fuck is wrong with you!?
I don't know. Perhaps you can "I think" it and tell me?
I think you're genuinely retarded.
Citation needed. Prove it, you made the claim, I asked him for the proof, now you must oblige.
In this very topic, you showed that you have no idea what "I think" means. This is preschool level of English language. If you have a job, you're at least 10 years too old for preschool. This is pretty much the definition of retarded.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
But I can't stand this attitude of making a bunch of statements and then acting like it's not your responsibility to prove them.
Why?
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I fucking hate you.
I love you!
@gąska said in Big list of software that cannot handle spaces or accents in paths:
pretty much the definition of retarded.
Citation needed.
-
@tsaukpaetra nope, I'm done. The discussion is over, and I will never engage in another one with you.
-
How exactly am I supposed to reference a file if not by name? You want me to remember the ID, too? Then I wouldn't need a file name in the first place.
Or, alternatively, if I still specify files by name you just introduced another layer in between but not fixed the problems in the layer above.Unless this is all a case of "you never select more than one file, and only by mouse, anything else is ".
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
@tsaukpaetra nope, I'm done. The discussion is over, and I will never engage in another one with you.
Much appreciated.
Mission accomplished!
Of course, I will hold you to your word.
-
@topspin said in Big list of software that cannot handle spaces or accents in paths:
How exactly am I supposed to reference a file if not by name?
you're not supposed to not use names, the programs and operating system that deals with your files are supposed to not use names.
Edit: of course, this presupposes that systems files and users files are different, otherwise yet another system entirely needs to be designed for system files to know about other relevant system files that the user may not need to know or care about.
-
@topspin the point is having an API where the only way to access files is through IDs, and the only way to retrieve IDs is through the API. Instead of asking for path, you fire up a file open dialog which returns you a (list of) ID(s) which you can use for opening. When you create a file, you don't make up its path but call API that returns you a new ID. Basically - what we normally do for memory pointers, but applied to files.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I don't really see why the same permission system would be impossible to do with IDs instead if filenames. It's still identifying files, and files have metadata, and you can retrieve parent directory just as well.
If you don't support hardlinks then yes, you can. But it does.
I still don't see how having names is relevant. You could have several IDs refer to the same inode. Also, I've never heard of a legit use case for hard links that wouldn't be better with sift links or regular copies.
Sure, if you didn't use the inode itself but kept another ID referring to the inode that was stored on disk separate from both inodes and directories, that would work. It would fail with any file system that didn't explicitly support it though, which is basically everybody else's. I don't know how MacOS hacked around it but say FAT disks were never pleasant to use with it.
On the other hand, Unix doesn't let you give permissions to a specific group other than the owner.
Are you looking for the ancient group permissions or the ACLs from the 80s?
Have Unix permissions evolved beyond rwxr-xr-x? If so, TIL.
Well, the second rwx is for a specific group. That the owner doesn't strictly have to be a member of, although only root can give files to such groups. And yes, POSIX.1e ACLs have been supported for about 15 years, too.
Could be a nice-to-have, although I wouldn't know where I'd have needed more than the sticky bit supports.
It's kinda impressive how many hacks Linux people invent to get around not having actual features.
What's your use case for those actual features? The sticky bit predates Linux by over half a decade BTW.
-
@laoc said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
I don't really see why the same permission system would be impossible to do with IDs instead if filenames. It's still identifying files, and files have metadata, and you can retrieve parent directory just as well.
If you don't support hardlinks then yes, you can. But it does.
I still don't see how having names is relevant. You could have several IDs refer to the same inode. Also, I've never heard of a legit use case for hard links that wouldn't be better with sift links or regular copies.
Sure, if you didn't use the inode itself but kept another ID referring to the inode that was stored on disk separate from both inodes and directories, that would work. It would fail with any file system that didn't explicitly support it though, which is basically everybody else's.
Filename is literally another ID referring to the inode. Every filesystem in existence already supports that.
On the other hand, Unix doesn't let you give permissions to a specific group other than the owner.
Are you looking for the ancient group permissions or the ACLs from the 80s?
Have Unix permissions evolved beyond rwxr-xr-x? If so, TIL.
Well, the second rwx is for a specific group. That the owner doesn't strictly have to be a member of, although only root can give files to such groups. And yes, POSIX.1e ACLs have been supported for about 15 years, too.
Huh. TIL. But it kinda misses my point - I meant that you cannot have more than one group for a given file that have permissions other than the default permissions that everyone has.
The sticky bit predates Linux by over half a decade BTW.
s/Linux/Unix/
. Happy now?
-
@gąska So does the user deal with IDs or is the user not allowed to talk about files without a GUI?
-
@topspin said in Big list of software that cannot handle spaces or accents in paths:
@gąska So does the user deal with IDs or is the user not allowed to talk about files without a GUI?
INB4 command-line is a sufficient UI to talk about file names and IDs both.
-
@gąska said in Big list of software that cannot handle spaces or accents in paths:
You absolutely did claim this. A weak unsupported claim with lots of weasel wording is still a claim.
At first I thought this was a clever imitation troll, but the longer it goes I think that you have learned the wrong lesson after certain interactions.
-
@pie_flavor said in Big list of software that cannot handle spaces or accents in paths:
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
@gąska said in Big list of software that cannot handle spaces or accents in paths:
There are legitimate cases where you actually want them to be able to rename files you're editing.
More importantly, since a file's name isn't the file, it makes no sense that renaming a file you're editing would create a new file at the old name.
Well, it depends on how you look at it. When you open a file in Microsoft Word, is the file the document itself or simply a record of it? If it's the document itself, then what you are saying makes sense. If it's a record of the document, then when you 'open' the file you are loading the document into Word and when you 'save' the file you are recording the document to disk. Thus, the file itself has no special significance and what matters is the location (from the user's point of view, i.e. file path) that the document gets recorded to.
Yeah, I think that while I can kind of understand where he's coming from his way is also more likely to lead to data loss. Applying his own standards to this concept, it's terrible.