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 15:21:05 +0300	[thread overview]
Message-ID: <86msnbetou.fsf@gnu.org> (raw)
In-Reply-To: <874j9jvowr.fsf@localhost> (message from Ihor Radchenko on Sun, 23 Jun 2024 12:12:20 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 71732@debbugs.gnu.org, bjorn.bidar@thaodan.de
> Date: Sun, 23 Jun 2024 12:12:20 +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 do not ask to force the permissions.
> I am asking to provide an API function that will create XDG dir with
> appropriately assignment permissions. It will be up to the xdg.el caller
> to use that API function.

Like I said earlier: this is a two-liner:

  (with-file-modes 0700
    (make-directory DIR t))

where the value 0700 is something the Lisp program should control.

I see no reason to provide an API for such simple code, let alone do
that in xdg.el.

And if you still don't agree, let's at least agree to disagree.
because this argument begins to revisit what was already said.





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