From: Stefan Kangas <stefan@marxist.se>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Philip K <philip@warpmail.net>,
41030@debbugs.gnu.org
Subject: bug#41030: [PATCH] Make EWW respect XDG download directory by default
Date: Tue, 5 May 2020 17:32:27 -0400 [thread overview]
Message-ID: <CADwFkmkRkKJ9En554_00iQGBkB8aUGn8h_R6gVADXpwxZtYerQ@mail.gmail.com> (raw)
In-Reply-To: <87o8r4ha42.fsf@tcd.ie>
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
>>> -(defcustom eww-download-directory "~/Downloads/"
>>> +(defcustom eww-download-directory (or (xdg-user-dir "DOWNLOAD")
>>> + "~/Downloads/")
>>
>> This makes sense conceptually. However, on my machine, evaluating
>> (xdg-user-dir "DOWNLOAD") just returns $HOME. That's a worse default
>> than "~/Downloads/", no?
>>
>> But I don't know enough about the XDG standard to propose a solution.
>> Nor do I know if this is because my setup is particularly unusual.
>
> It sounds like it could be specific to your environment; have a look at
> 'man 1 xdg-user-dirs-update'.
In my use-case, I don't think I have ever touched any of this stuff.
Not AFAIR, anyways.
So I wonder if the suggested code would mean to never use
"~/Downloads", since xdg-user-dir will always return something else?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-05-05 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 16:58 bug#41030: [PATCH] Make EWW respect XDG download directory by default Philip K
2020-05-03 22:52 ` Stefan Kangas
2020-05-03 23:28 ` Basil L. Contovounesios
2020-05-05 8:02 ` Lars Ingebrigtsen
2020-05-05 8:20 ` Philip K.
2020-07-17 13:09 ` Lars Ingebrigtsen
2020-07-29 5:14 ` Lars Ingebrigtsen
2020-05-05 21:32 ` Stefan Kangas [this message]
2020-05-06 0:04 ` Noam Postavsky
2020-05-06 0:17 ` Stefan Kangas
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=CADwFkmkRkKJ9En554_00iQGBkB8aUGn8h_R6gVADXpwxZtYerQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=41030@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=philip@warpmail.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.