From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Hongxu Chen <leftcopy.chx@gmail.com>
Subject: Re: What should I do when building Emacs again with different configure options?
Date: Sun, 28 Jul 2013 17:19:02 +0200 [thread overview]
Message-ID: <87fvuyvhjt.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAAF+z6Gp0PjYZtUVj-JH8PLG4u5rAJbiQf70oVGP7t5s41yw2g@mail.gmail.com> (Xue Fuqiao's message of "Sun, 28 Jul 2013 21:33:33 +0800")
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
() Xue Fuqiao <xfq.free@gmail.com>
() Sun, 28 Jul 2013 21:33:33 +0800
I've thought another way to describe it: "./configure
--your-different-option" before my last post, but IMO the previous
paragraph has stated this very clearly:
"If you want to build Emacs again with different configure options,
first clean the source directories:"
It already implies that we _need_ different configure option(s), so
we don't need the second extra line. What's your opinion?
I have two minds (at the moment :-D).
- Towards minimalism (i.e., providing only what is needed), the indented
block can be completely eliminated.
If you want to build Emacs again with different configure options,
first clean the source directories with "make distclean".
- Towards parallelism (i.e., providing a consistent patter for every
pitter), the second line line of the indented block can be as you
suggest:
./configure --your-different-option
However, i would use square braces as a further syntactical hint.
(Who knows, someone might try the literal "--your-different-option"!)
The latter appeals to at-rest aesthetics, while the former, in-motion.
Both get the job done (as does removing "./configure", i suppose, which
basically means: what i think is not as important as what you do).
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-07-28 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 1:59 What should I do when building Emacs again with different configure options? Xue Fuqiao
2013-07-27 2:06 ` Glenn Morris
2013-07-27 22:30 ` Xue Fuqiao
2013-07-27 22:53 ` Peter Dyballa
2013-07-28 13:38 ` Xue Fuqiao
2013-07-28 2:03 ` Hongxu Chen
2013-07-28 8:39 ` Thien-Thi Nguyen
2013-07-28 13:33 ` Xue Fuqiao
2013-07-28 15:19 ` Thien-Thi Nguyen [this message]
2013-07-28 15:44 ` Peter Dyballa
2013-07-28 22:56 ` Xue Fuqiao
2013-07-28 23:47 ` Glenn Morris
2013-07-29 1:32 ` Xue Fuqiao
2013-07-28 13:50 ` Xue Fuqiao
2013-07-27 9:17 ` Peter Dyballa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvuyvhjt.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=help-gnu-emacs@gnu.org \
--cc=leftcopy.chx@gmail.com \
--cc=xfq.free@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).