Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: alfedotov@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/gdbsupport: Use LOCALAPPDATA for index cache on windows
Date: Tue, 08 Dec 2020 17:31:18 +0200	[thread overview]
Message-ID: <83pn3k71rt.fsf@gnu.org> (raw)
In-Reply-To: <93d41b96-d11e-ed21-2a63-6a8270b5fbfe@polymtl.ca> (message from Simon Marchi via Gdb-patches on Tue, 8 Dec 2020 09:46:47 -0500)

> Date: Tue, 8 Dec 2020 09:46:47 -0500
> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
> 
> 
> My only question is about:
> 
>    return string_printf ("%s/" HOME_CACHE_DIR "/gdb", abs.get ());
> 
> That would give a final path like:
> 
>    C:\Users\Simon\AppData\Local\.cache\gdb
> 
> The ".cache" part is not typical in this directory.  Should we instead 
> just have:
> 
>    C:\Users\Simon\AppData\Local\gdb
> 
> ?

IMO, it indeed should be in C:\Users\Simon\AppData\Local\gdb, as other
applications do.  Moreover, I think we should use APPDATA, not
LOCALAPPDATA, because it makes sense to be able to synchronize the
cache over the network if the computer joins some domain.  IOW, it
isn't necessarily local data, is it?

Thanks.

  parent reply	other threads:[~2020-12-08 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 10:16 Alexander Fedotov via Gdb-patches
2020-12-08 14:46 ` Simon Marchi via Gdb-patches
2020-12-08 14:48   ` Simon Marchi via Gdb-patches
2020-12-08 14:51     ` Alexander Fedotov via Gdb-patches
2020-12-08 15:10       ` Simon Marchi via Gdb-patches
2020-12-08 15:12         ` Alexander Fedotov via Gdb-patches
2020-12-08 15:16           ` Simon Marchi via Gdb-patches
2020-12-08 15:31   ` Eli Zaretskii via Gdb-patches [this message]
2020-12-09  9:15     ` Alexander Fedotov via Gdb-patches
2020-12-09 12:45       ` Christian Biesinger via Gdb-patches

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=83pn3k71rt.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=alfedotov@gmail.com \
    --cc=eliz@gnu.org \
    --cc=simon.marchi@polymtl.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox