[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_bac
From: |
Eli Zaretskii |
Subject: |
bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written |
Date: |
Wed, 21 Nov 2012 05:47:16 +0200 |
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <dancol@dancol.org>, <12911@debbugs.gnu.org>
> Date: Tue, 20 Nov 2012 13:47:38 -0800
>
> > "The file system directory used to physically store a user's common
> > repository of documents." What do you make of that? "User's
> > documents", not "user's files".
>
> A distinction without a meaning, in the present context. Trouncing user stuff
> is a no-no, whether that stuff is "documents" or files.
That's your interpretation. It isn't written anywhere.
> The distinction that matters here is user vs application.
There's no distinction.
> You do not seem to want to recognize any difference between a user's photo of
> his grandmother and a cache file used by a program to optimize access to that
> photo. (Hint: the user cares about Grandma; s?he does not care about the
> cache.)
Your hint is wrong. I care about my caches dearly.
> It's hard for me to believe this is even a point open to debate.
Well, it evidently is, and you fail to convince. You are just
repeating yourself.
> > Don't believe everything Wikipedia says.
>
> You don't seem to want to believe your own eyes.
I believe my experience.
> Store program-internal data where other programs do (on Windows).
Which is everywhere and nowhere.
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, (continued)
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Daniel Colascione, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Drew Adams, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Drew Adams, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written,
Eli Zaretskii <=
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Daniel Colascione, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Stefan Monnier, 2012/11/20