Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update FAQ #335

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update FAQ #335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions web/docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,23 @@ While having two locations for configuration can be confusing we want native
programs to follow Windows conventions and be independent from MSYS2. Also we
don't want to change the behavior of programs compared to their upstream
versions unless we have to.

That said, sharing the location for multiple installation of applications is
still possible, in the sense that:

* Packages with different prefixes may share the same configuration \
location (as the default of some native x86/x64 Win32 applications).
* The shared location is not actively checked against by the runtime, so it
is possible to have different path pointing to the same file system location
and the applications *may* actually work.

Shared location can be implemented by setting the value of `HOME` environment
varible (which can be interited from Windows environment) or symbolic link
on directories, for instance. This is not normally supported. Individual
applications may fail because they do not expect the configuration being
shared (e.g. a Unix application may be only compatible to LF as line endings
in its configuration files, and it will fail to parse CR+LF line endings
written by a Win32 native application). Some applications (like
[Mercurial](https://www.mercurial-scm.org/doc/hgrc.5.html)) have different
search paths for Win32/Unix environments. However, such layout may be useful
for testing. Use with your own risks when you really know the consequences.