Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Update get_standard_cache_dir for macOS
Date: Fri, 14 Sep 2018 19:07:00 -0000	[thread overview]
Message-ID: <87pnxf3njx.fsf@tromey.com> (raw)
In-Reply-To: <83bm8zkiwq.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Sep	2018 21:56:05 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> For the documentation, I'm happy to change it however you like.

Eli> I just voiced my opinion that this detail about macOS, and only about
Eli> it, seems at odds with our general tendency not to describe
Eli> proprietary systems in too much detail.  But I'm not going to block
Eli> this change just because I was surprised.  I wonder what others think.

I guess I didn't really give it much thought.  I wouldn't mind being
more vague.  What about something like:

    The default value for this directory depends on the host platform.  On
    most systems, the index is cached in the @file{gdb} subdirectory of
    the directory pointed to by the @env{XDG_CACHE_HOME} environment
    variable, if it is defined, else in the @file{.cache/gdb} subdirectory
    of your home directory.  However, on some systems, the default may
    differ according to local convention.

I think it's no big deal for users to use "show index-cache directory" 
if they really care about the value.

Tom


  reply	other threads:[~2018-09-14 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 14:59 Tom Tromey
2018-09-14 18:39 ` Eli Zaretskii
2018-09-14 18:46   ` Tom Tromey
2018-09-14 18:56     ` Eli Zaretskii
2018-09-14 19:07       ` Tom Tromey [this message]
2018-09-14 20:03         ` Eli Zaretskii

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=87pnxf3njx.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox