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.

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

Please use XDG basedir paths for user config and data files #560

Open
aspell-helper opened this issue Jul 12, 2019 · 3 comments

Comments

@aspell-helper
Copy link
Collaborator

commented Jul 12, 2019

https://lists.gnu.org/archive/html/aspell-devel/2019-01/msg00000.html
https://bugs.debian.org/900164

Date: Thu, 31 Jan 2019 07:08:35
From: Agustin Martin <agmartin@debian.org>
To: aspell-devel@gnu.org
Subject: [aspell-devel] Suggestion in Debian#900164: Please use XDG basedir paths for user config and data files

Hi,

We have recevied following suggestion by Guillem Jover, in Debian bug
tracking system, see https://bugs.debian.org/900164

Guillem wrote:

---------- 8< ---------------------------------
The aspell config ~/.aspell.conf and user personal word and replace
files ~/.aspell.LL.prepl and ~/.aspell.LL.pws are read directly from
the user home directory. This makes for an untify home. :)

It would be nice if aspell would support the XDG basedir standard [X]
and those would be looked up first under something like:

  ${XDG_CONFIG_HOME:-~/.config}/aspell/aspell.conf
  ${XDG_DATA_HOME:-~/.local/share}/aspell/aspell.LL.prepl
  ${XDG_DATA_HOME:-~/.local/share}/aspell/aspell.LL.pws

[X] https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.htm
---------- 8< ---------------------------------

I also think it would be nice to have a configuration option at build time
to have this behavior or allow it in some way, so I am forwarding this bug
report in case someone thinks it worths (and writes the code).

Regards,

-- 
Agustin
@lhanson

This comment has been minimized.

Copy link

commented Sep 5, 2019

Please implement, there is no downside to respecting users' preferences.

@kevina

This comment has been minimized.

Copy link
Member

commented Sep 5, 2019

I think it would be a good idea, but there is the issue of migration when upgrading to a version (or build) that now expects the files in a different location than the previous version. I have not had the time to work out a good solution to the migration problem.

@lhanson

This comment has been minimized.

Copy link

commented Sep 5, 2019

Most applications tend to look for the files in the specified location and then fall back to the legacy paths if they aren't found. Should make it seamless for users.

@kevina kevina added this to the 0.62 milestone Sep 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.