unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "francisco.colaco\@gmail.com" <francisco.colaco@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: xdg-directories.el
Date: Wed, 07 Sep 2016 20:32:27 +0300	[thread overview]
Message-ID: <837fanaa50.fsf@gnu.org> (raw)
In-Reply-To: <CACwYkzyzH12wrvT32NDJy9Qg-SJyHnCU8eRwE5jraV-hfRUQRg@mail.gmail.com> (francisco.colaco@gmail.com)

> From: "francisco.colaco@gmail.com" <francisco.colaco@gmail.com>
> Date: Wed, 7 Sep 2016 17:13:43 +0100
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> I can implement the functions for Windows and OSX.

Thanks.  However, I don't see your copyright assignment on file, so
unless it's in the works, perhaps you shouldn't do that yet.

> But we do have a problem: once this is implemented for all operating systems, XDG will become a
> meaningless package name and prefix. Maybe we should not have a prefix at all and find sensible names not
> used by Emacs at the moment.

I don't follow this logic.  Being able to locate the "My Documents"
directory on Windows has nothing to do with XDG.  The package will
simply use that as fallback on Windows, if XDG_HOME etc. is not found
in the environment.  So the package will still have its place, I
think.

Beyond that, as I wrote earlier, places that are used by core Emacs
features, like user-emacs-directory, will have to be defined in
preloaded files, outside of the XDG package.

> 1. (locate-user-emacs-config-file "init.el")
> 2. (locate-user-emacs-file "init.el")
> 3. ~/.emacs.d/init.el
> 4. ~/.emacs (and the rest of the present order, like terminal specific files).
> 
> Would that seem sensible to you?

I think so, but I'm not an expert on XDG related stuff.

We should also think whether we need to do anything if we find more
than one init.el in these places.



  parent reply	other threads:[~2016-09-07 17:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 15:24 xdg-directories.el francisco.colaco
2016-09-06 21:49 ` xdg-directories.el Noam Postavsky
2016-09-06 22:37   ` xdg-directories.el francisco.colaco
2016-09-07  0:35     ` xdg-directories.el Stefan Monnier
2016-09-07 14:18 ` xdg-directories.el Eli Zaretskii
2016-09-07 14:59   ` xdg-directories.el francisco.colaco
2016-09-07 15:21     ` xdg-directories.el Stefan Monnier
2016-09-07 15:31     ` xdg-directories.el francisco.colaco
2016-09-07 15:54       ` xdg-directories.el Eli Zaretskii
2016-09-07 16:13         ` xdg-directories.el francisco.colaco
2016-09-07 16:28           ` xdg-directories.el francisco.colaco
2016-09-07 17:32           ` Eli Zaretskii [this message]
     [not found]             ` <CACwYkzyjV2jsTX3Cb0Us4tz1WsUP=avurw04Kgq8k52oBZRg_Q@mail.gmail.com>
2016-09-07 18:21               ` xdg-directories.el Eli Zaretskii
2016-09-07 16:46         ` xdg-directories.el Stefan Monnier
2016-09-07 17:24           ` xdg-directories.el Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837fanaa50.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=francisco.colaco@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).