Comments by "Anony Mousse" (@anon_y_mousse) on "Linux Dot Files Were Never Meant To Exist" video.

  1.  @schwingedeshaehers  Or you could do what I did and create a share folder in /home where you can put all files you want to share with other users. Everyone's part of the same group and the folder sticky bits everything to that group and provides read access.
    5
  2. Yes, they do. I don't work directly in ~ for anything I do anyway. I've added variables in my .bash_aliases for all of the commonly used directories. I've got 'd' for downloads and 'D' for documents, {g,p,v,m} are then obvious. And 'c' for all my own code projects.
    2
  3. Interesting perspective. I hardly ever work directly in my home folder so I don't even care what hidden files and folders are there. But I do like your username.
    2
  4. I honestly don't get why people are complaining. It's still better system than Windows, but why are people working directly in their home folder? That's what subdirectories are for and then you won't see dot files unless you explicitly create them. For that matter, I put commonly used directories in my ~/.bash_aliases so I can `cd $g` for instance to play a game, and since bash is set to auto-complete through shell variables I can navigate to a particular game rather easily.
    2
  5.  @Yxcell  If you're posting any URL's then it's being auto-deleted, otherwise it could be a shadowban.
    2
  6. How about `ls -FArt`?
    2
  7. I prefer not to show every file so I wrote a function to display the last $n files in a directory. I named it `lrt` and ended up writing a whole bunch of functions around the concept of `ls -rt` so I could focus more on what I was truly working on. I would have made it an alias, but I wound up doing a bit more than just `ls -rt | tail` because I wanted them to pretty print.
    1
  8. The example that I'm going to reiterate because it's a good one, say a program uses the folder "config" and hides it then the user comes along and wants to create a file named "config", either deleting the previous data, which could be really bad, or just confusing and frustrating them by saying it already exists. Linux doesn't need a hidden file attribute.
    1
  9.  @UltimatePerfection  And you misunderstood the point. An attribute means that a file or folder you don't want to see may easily conflict with one the user does want to see. By having it be part of the name it won't conflict with what the user wants to name their own files and/or folders.
    1
  10.  @UltimatePerfection  It's still better than Windows and prevents name conflicts with user files and folders.
    1
  11.  @Max128ping  It would only be triggering if it were true, but since it's not it's okay.
    1
  12. Why would you have settings that aren't human-readable at all?
    1
  13. With Windows it's part of the file system, FAT32 or NTFS. For Linux and other UNIX-esque systems it's literally just renaming the file to have a dot at the start, but not all tools use that as a metric for hiding things.
    1
  14. If anyone could actually agree on the same config file syntax that might be an interesting idea, but it would require yet another background process to handle requests and it would have to handle requests from every application. The current system makes it the responsibility of the kernel to multitask as everything reads or writes to config files through the FS driver.
    1
  15.  @friedrichdergroe9664  First, there are hidden folders so you should use `ls -d`, and second to list everything that's not '.' and '..' you could do `ls -d .[!.]*`. Third, don't ever use `chown -R`, especially if you don't understand why.
    1
  16.  @friedrichdergroe9664  How did you delete it? Did you use a wildcard where you shouldn't have?
    1