From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tests, Emacs-25 and Conditional Features
Date: Fri, 18 Mar 2016 11:54:55 -0400 [thread overview]
Message-ID: <jwvpour941p.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <83y49f94kt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 18 Mar 2016 17:41:06 +0200")
> That's one possibility, but it isn't the only one. Some of the
> features in system-configuration-options are detected automatically,
> so the user might not always be aware that a feature she assumed she
> has failed to auto-detect and is disabled.
Well, we need some concrete data from which we can guess what the user
might assume. `system-configuration-options' is one of them, but indeed
it doesn't cover all cases.
> Maybe a test that produced a report for which features are actually
> available and working would be a possible solution.
Not sure what you're thinking of. But maybe we could stash the summary
we emit at the end of ./configure and use that additionally to
`system-configuration-options'.
Stefan
next prev parent reply other threads:[~2016-03-18 15:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 13:36 Tests, Emacs-25 and Conditional Features Phillip Lord
2016-03-16 14:29 ` Michael Albinus
2016-03-17 10:14 ` Phillip Lord
2016-03-17 16:25 ` Eli Zaretskii
2016-03-18 10:41 ` Phillip Lord
2016-03-18 11:00 ` Michael Albinus
2016-03-18 17:19 ` Phillip Lord
2016-03-18 18:38 ` Eli Zaretskii
2016-03-18 11:07 ` Eli Zaretskii
2016-03-18 17:20 ` Phillip Lord
2016-03-18 18:37 ` Eli Zaretskii
2016-03-19 21:26 ` Phillip Lord
2016-03-18 15:15 ` Stefan Monnier
2016-03-18 15:41 ` Eli Zaretskii
2016-03-18 15:54 ` Stefan Monnier [this message]
2016-03-18 18:32 ` Eli Zaretskii
2016-03-18 17:22 ` Phillip Lord
2016-03-16 15:48 ` Dmitry Gutov
2016-03-16 16:12 ` Eli Zaretskii
2016-03-16 18:53 ` John Wiegley
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=jwvpour941p.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.