Hacker Newsnew | past | comments | ask | show | jobs | submit | boreq's commentslogin

The author's quite reasonable and polite request to not change the appearance of the project is pretty straightforward so morally no, it cannot. Feel free to write your own version though. I hope I helped.


So what you are saying is that it's anubis that saved their website.


https://glenda.0x46.net/ Website resembling the Plan 9's rio desktop environment.


It is your lucky day - there is a standard for this as well https://wiki.archlinux.org/index.php/XDG_user_directories


I've only been using Linux for around 10 years as my only desk and laptop OS and this is the first I heard of XDG user dirs! This laptop runs Arch. Thanks for the heads up.

I'll drop "/etc/papersize" in return. If you are not familiar with this and do not print to letter paper then you will find it very, very useful.


Oh wow. If this does what I think it does, I'll be forever grateful for that comment.


It really does make CUPS, Libre Office and all the rest believe you when you say "I want to print on A4, yes A4, no not fucking Letter, A4, end of!" Obviously, substitute your paper size of choice. It probably even lends itself to some form of scripting and perhaps could be changed in reaction to events from say NetworkManager. Whatever.

My life at home is now worth living every time the wife hits print. Such a simple idea - brilliant.


Which is especially sad as supporting the standard described in my post is a non breaking change if you are still going to read the old location of the configuration and data files as well.


That is the exact problem that the standard I talk about was designed to solve (apart from the clutter in the home directory).


I think saagarjha's point was that an even simpler standard would be for the creating application to use file metadata to annotate the files. And a simpler standard is generally more likely to be followed, especially if it's unilateral.

This doesn't help with installation, obviously, but it helps with cleanup.


The classic MacOS had exactly this concept: Creator Code[0], similar to the Type Code[1] but storing a file's creator rather than its "mimetype".

[0] https://en.wikipedia.org/wiki/Creator_code

[1] https://en.wikipedia.org/wiki/Type_code


Good point, I had almost forgotten about those!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: