All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xaver =?unknown-8bit?q?H=C3=B6rl?= <hoe.dom@gmx.de>
To: iwd@lists.01.org
Subject: Re: Suggestion: make iwctl follow the XDG Base Directory Specification
Date: Tue, 10 Dec 2019 14:04:20 +0100	[thread overview]
Message-ID: <20191210130420.snypbt3q3hgp5nak@blumerang> (raw)
In-Reply-To: <B4E8E87E-8EE1-4487-AEFA-59EC699A3FE9@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Sure I will give it a try. Note though that I don't usually code in C
and have no experience contributing to this sort of stuff.

On Sat, Dec 07, 2019 at 04:47:39PM +0100, Marcel Holtmann wrote:
> Hi,
>
> > Currently iwctl writes its history to a file named .iwctl_history in the users home directory. The XDG Base Directory Specification tries to standardize these kind of things (see https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html for details). The bottom line would probably be to:
> > * check XDG_DATA_HOME (with fall back to .local/share/) and save the history in an iwd subfolder of that directory
> > * potentially read (and migrate?) .iwctl_history from the home directory for compatibility purposes
>
> I am fine with using $XDG_DATA_HOME/iwctl/history or $HOME/.local/share/iwctl/history as fallback if $XDG_DATA_HOME is not provided. Care to send a patch for this?
>
> Regards
>
> Marcel
>

  reply	other threads:[~2019-12-10 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 10:47 Suggestion: make iwctl follow the XDG Base Directory Specification hoe.dom
2019-12-07 15:47 ` Marcel Holtmann
2019-12-10 13:04   ` Xaver =?unknown-8bit?q?H=C3=B6rl?= [this message]
2019-12-10 13:06   ` [PATCH] client: Follow the xdg base directory specification Xaver =?unknown-8bit?q?H=C3=B6rl?=
2019-12-13  8:36     ` Marcel Holtmann

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=20191210130420.snypbt3q3hgp5nak@blumerang \
    --to=hoe.dom@gmx.de \
    --cc=iwd@lists.01.org \
    /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.
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.