From: Paul Eggert <eggert@cs.ucla.edu>
To: Alexander Shukaev <haroogan@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Whitespace in `${srcdir}' during `configure'
Date: Sun, 09 Nov 2014 23:17:01 -0800 [thread overview]
Message-ID: <5460666D.1040805@cs.ucla.edu> (raw)
In-Reply-To: <CAKu-7WwZPAMgc3i0cju5Pv2tUnKVTcVEFZ_cbmFHxjVygwggZw@mail.gmail.com>
It'd be nice if Emacs 'configure' allowed arbitrary source-directory names.
Unfortunately, almost none of the changes in the patch that you sent fix any
bugs, and almost all the bugs in this area would remain unfixed by the patch.
If you'd like to help fix the many problems in this area, I suggest building and
configuring Emacs in a directory whose name contains spaces, tabs, and
characters from the set !"#$%&'()*+,-.:;<=>?@[\]^`{|}~ and make sure that
everything works; also, make sure that every change in the patch actually fixes
a bug. It could be that we can support some characters (e.g, spaces) but not
others (e.g., apostrophes, colons), but in any event the more characters that we
can support the better, and it'd be good to document the ones we can't.
next prev parent reply other threads:[~2014-11-10 7:17 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
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 [this message]
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=5460666D.1040805@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=haroogan@gmail.com \
/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.