From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: yantar92@posteo.net, 71732@debbugs.gnu.org
Subject: bug#71732: 30.0.50; [FR] xdg: provide an ability to create XDG directory, if it does not exist
Date: Mon, 24 Jun 2024 14:39:20 +0300 [thread overview]
Message-ID: <864j9id0yf.fsf@gnu.org> (raw)
In-Reply-To: <87tthjgyct.fsf@> (message from Björn Bidar on Mon, 24 Jun 2024 00:09:38 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: Ihor Radchenko <yantar92@posteo.net>, 71732@debbugs.gnu.org
> Date: Mon, 24 Jun 2024 00:09:38 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Ihor Radchenko <yantar92@posteo.net>
> >> Cc: 71732@debbugs.gnu.org, bjorn.bidar@thaodan.de
> >> Date: Sun, 23 Jun 2024 11:42:47 +0000
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> According to
> >> https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html,
> >> 0700 permission is a part of XDG spec.
> >
> > I already explained that: we don't blindly follow any standards, and
> > this particular issue is up to the calling Lisp program. xdg.el has
> > no business forcing permissions on the caller.
>
> I guess the point was that the caller should follow XDG or the
> respective standard on non-xdg platforms and to at least advice in
> following those.
> Emacs should integrate into the target platform if possible saving files
> into the right directories should be something possible.
>
> "Blindly" following xdg or the respective platform for generic modus
> does not sound like a wrong idea to me good defaults are valuable.
The purpose of xdg.el is to represent the XDG directories to Emacs.
It is then the job of the Lisp programs which use xdg.el to decide
whether they create a directory and which permissions to give it.
next prev parent reply other threads:[~2024-06-24 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 9:40 bug#71732: 30.0.50; [FR] xdg: provide an ability to create XDG directory, if it does not exist Ihor Radchenko
2024-06-23 10:12 ` Eli Zaretskii
2024-06-23 10:20 ` Ihor Radchenko
2024-06-23 10:24 ` Eli Zaretskii
2024-06-23 10:35 ` Ihor Radchenko
2024-06-23 11:29 ` Eli Zaretskii
2024-06-23 11:42 ` Ihor Radchenko
2024-06-23 11:53 ` Eli Zaretskii
2024-06-23 12:12 ` Ihor Radchenko
2024-06-23 12:21 ` Eli Zaretskii
2024-06-23 12:28 ` Ihor Radchenko
2024-06-23 12:36 ` Eli Zaretskii
2024-06-23 21:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87tthjgyct.fsf@>
2024-06-24 11:39 ` Eli Zaretskii [this message]
2024-06-24 11:58 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=864j9id0yf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71732@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=yantar92@posteo.net \
/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).