From: Yuri Khan <yuri.v.khan@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Alexander Shukaev <haroogan@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Whitespace in `${srcdir}' during `configure'
Date: Mon, 10 Nov 2014 21:28:07 +0700 [thread overview]
Message-ID: <CAP_d_8Ve01vHxZqV=dYuCO2=cC1a2uP=gN=ogefcHaya6G5dXw@mail.gmail.com> (raw)
In-Reply-To: <ds8ujjcvg9.fsf@fencepost.gnu.org>
On Mon, Nov 10, 2014 at 2:26 PM, Glenn Morris <rgm@gnu.org> wrote:
> But really, the only case I can think of is a user whose home directory
> contains spaces and is unable to use /tmp. In which case, I can only
> assume that their sysadmin hates them and wants them to be miserable.
> Compiling software is probably the least of their problems. :)
This case is *the* norm on Windows, starting with 2000 (where /home is
"C:\Documents and Settings") and up to but not including Vista (where
it was finally renamed "C:\Users"). Also, temporary directories (both
user’s and public) are within this subtree.
next prev parent reply other threads:[~2014-11-10 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 2:28 Whitespace in `${srcdir}' during `configure' Alexander Shukaev
2014-11-10 7:14 ` Glenn Morris
2014-11-10 7:20 ` Paul Eggert
2014-11-10 8:26 ` Glenn Morris
2014-11-10 14:28 ` Yuri Khan [this message]
2014-11-10 15:12 ` Eli Zaretskii
2014-11-10 16:03 ` Alexander Shukaev
2014-11-10 16:27 ` Eli Zaretskii
2014-11-10 17:17 ` Glenn Morris
2014-11-10 18:04 ` Alexander Shukaev
2014-11-10 19:25 ` Glenn Morris
2014-11-10 19:39 ` Glenn Morris
2014-11-17 2:24 ` Glenn Morris
2014-11-10 10:47 ` Eli Zaretskii
2014-11-10 7:17 ` Paul Eggert
2014-11-10 7:24 ` Glenn Morris
2014-11-10 9:04 ` Andreas Schwab
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='CAP_d_8Ve01vHxZqV=dYuCO2=cC1a2uP=gN=ogefcHaya6G5dXw@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=haroogan@gmail.com \
--cc=rgm@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.