amateurfoki.blogg.se - Texmacs unix

#Texmacs unix portable
#Texmacs unix android
#Texmacs unix software

#Texmacs unix android

Location overview by Google does not mention XDG - paths could be hardcoded instead of using the proper variable, though that is unlikely as Intellij IDEA, which Android Studio is based on, implements it properly as well Please verify that your solution is correct and functional.

The last column should include any appropriate workarounds or solutions.

In the third, try to find the commit or version a project switched to XDG Base Directory or any open discussions and include them in the next two columns (two per line).

The second column is for any legacy files and directories the project had (one per line), this is done so people can find them even if they are no longer read.

The first column should be either a link to an internal article, a Template:Pkg or a Template:AUR.

Nothing should require code evaluation (such as vim and VIMINIT), patches or compile-time options to gain support and anything which does must be deemed hardcoded.Īdditionally, if the process is error prone or difficult, it should also be classified as hardcoded. When contributing make sure to use the correct section. Hopefully this will provide a source of information about exactly what certain kinds of dotfiles are and where they come from.

#Texmacs unix portable

The rationale for this is that configurations should be portable across systems and having compile-time options prevent that. The workarounds will be limited to anything not involving patching the source, executing code stored in environment variables or compile-time options. This is here to demonstrate the viability of this specification by listing commonly found dotfiles and their support status.įor those not currently supporting the Base Directory Specification, workarounds will be demonstrated to emulate it instead.

#Texmacs unix software

This section exists to catalog the growing set of software using the XDG Base Directory Specification introduced in 2003. (Discuss in Talk:XDG Base Directory#Add description of support categories) The tables could be merged into one (with more fields added on how the programs work with the specification) or differently named categories could be used. Reason: The current supported/partial/hardcoded split is not detailed enough and can be misleading. Should default to /usr/local/share:/usr/share.List of directories separated by : (analogous to PATH).pam_systemd sets this to /run/user/$UID.Should not store large files as it may be mounted as a tmpfs.Can only exist for the duration of the user's login.Modified every 6 hours or set sticky bit if persistence is desired.Filesystem fully featured by standards of OS.

$texmacs unix$

Must be owned by the user with an access mode of 0700.Not required to have a default value warnings should be issued if not set or equivalents provided.

Used for non-essential, user-specific data files such as sockets, named pipes, etc.Where user-specific state files should be written (analogous to /var/lib).Where user-specific data files should be written (analogous to /usr/share).Where user-specific non-essential (cached) data should be written (analogous to /var/cache).Where user-specific configurations should be written (analogous to /etc).See Environment variables#Globally for information on defining variables. It is up to the user to explicitly define the other variables according to the specification. Only XDG_RUNTIME_DIR is set by default through pam_systemd. This section will attempt to break down the essence of what it tries to achieve.