unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:24:36 +0300	[thread overview]
Message-ID: <86sex4dkij.fsf@gnu.org> (raw)
In-Reply-To: <87msncufil.fsf@localhost> (message from Ihor Radchenko on Sun, 23 Jun 2024 10:20:34 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 71732@debbugs.gnu.org, bjorn.bidar@thaodan.de
> Date: Sun, 23 Jun 2024 10:20:34 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> May you please add a functionality to xdg.el to create the directory
> >> with right permissions, so that xdg.el users do not need to know these
> >> technical details of the spec?
> >
> > xdg.el is not about creating directories, it is about returning their
> > names.
> >
> > The ability to create a directory with arbitrary permissions already
> > exists, and Emacs uses that in umpteen places.  So I'm not sure what
> > is missing here.  Not every two-liner needs a dedicated named API.
> 
> The missing part is creating a directory that follows XDG spec without
> having to consult that spec.
> 
> For example, I had no clue that applications using XDG are obliged to
> create XDG dirs with 0700 persmissions until someone pointed.

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.

> I believe that such technical details would fit within xdg.el API.

I disagree, mainly because the details are not part of XDG, they are
part of the design and the implementation of the particular Lisp
program using the XDG directories.





  reply	other threads:[~2024-06-23 10:24 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 [this message]
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
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=86sex4dkij.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).