From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>,
66308@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#66308: 30.0.50; DocView: Bump default value of doc-view-resolution
Date: Wed, 04 Oct 2023 11:37:48 +0300 [thread overview]
Message-ID: <87pm1uzstf.fsf@thaodan.de> (raw)
In-Reply-To: <CADwFkmmzM1QQ++r2h8SWGw1hd=gi6WJSzH7SX+VKsu8vsdQmWw@mail.gmail.com> (Stefan Kangas's message of "Tue, 3 Oct 2023 05:03:30 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>
>> Should we store this data on Unixes in `$XDG_CACHE_HOME` Instead
>> of temp?
>> Doing so would also allow to reuse it if the particular file is viewed
>> again.
>
> Probably, yes, at least on XDG compliant systems.
So e.g. Linux or *BSD.
On MacOS or Windows there are similar locations.
The Qt StandardPaths Docs provide a good overview of those:
https://doc.qt.io/qt-5/qstandardpaths.html#StandardLocation-enum
E.g. on MacOS there is ~/Library/Caches/<APPNAME> for CacheLocation.
next prev parent reply other threads:[~2023-10-04 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:55 bug#66308: 30.0.50; DocView: Bump default value of doc-view-resolution Stefan Kangas
2023-10-03 8:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 9:28 ` Stefan Kangas
2023-10-03 10:19 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 10:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 16:11 ` Eli Zaretskii
2023-10-03 12:03 ` Stefan Kangas
2023-10-04 8:37 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-05 10:24 ` Richard Stallman
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=87pm1uzstf.fsf@thaodan.de \
--to=bug-gnu-emacs@gnu.org \
--cc=66308@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
--cc=tsdh@gnu.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.
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.