From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: bjorn.bidar@thaodan.de, 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: Sun, 23 Jun 2024 14:29:19 +0300 [thread overview]
Message-ID: <86r0cnew34.fsf@gnu.org> (raw)
In-Reply-To: <87jziguesw.fsf@localhost> (message from Ihor Radchenko on Sun, 23 Jun 2024 10:35:59 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 71732@debbugs.gnu.org, bjorn.bidar@thaodan.de
> Date: Sun, 23 Jun 2024 10:35:59 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Emacs applications are not obliged to abide by what the XDG spec (or
> > any spec) says. Whether a directory we create under some XDG
> > directory should or should not have those permissions is something the
> > author of the Lisp program should consider and decide.
>
> Let me clarify: I did not mean creating a directory _under_ XDG
> directory. I meant creating XDG directory itself - it is regulated by
> XDG spec.
Yes, I understood, and my response includes that part as well.
next prev parent reply other threads:[~2024-06-23 11:29 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r0cnew34.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.