From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Correct Paths to Emacs C Sources after Installation
Date: Tue, 04 Nov 2014 09:53:33 +0100 [thread overview]
Message-ID: <87ppd3tkhe.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAKu-7WyfLpnEh9OzAJzT-BCth0QUiC3BvnNXtJFo=fGOnh0FMQ@mail.gmail.com> (Alexander Shukaev's message of "Tue, 4 Nov 2014 01:35:51 +0100")
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
() Alexander Shukaev <haroogan@gmail.com>
() Tue, 4 Nov 2014 01:35:51 +0100
there exist strict conventions
Hmm, that sounds like an oxymoron to my ears...
If you want to copy the C files on "make install" to DIR (a
laudable initiative, you are to be commended!), i suggest you:
- grok configure.ac
- add there support for option ‘--install-C-source DIR’
(with default not to install)
- arrange to tweak ‘source-directory’ on "make install"
- test a few times
- in "strict convention" contexts
- outside "strict convention" contexts
(use your imagination, or ask around;
weird and wonderful people abound!)
- post a patch for review
- bask in the glow once the revised^N patch is installed
- mention this (v.cool, IMHO) feature on EmacsWiki
Lastly, you can (optionally) prepare for the onslaught of
"next step" bug reports, wherein users stumble upon the
feature and wonder how to make a modification to the code
and see the effect immediately in action. That sweet
confusion is something we can address together, here. :-D
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-11-04 8:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 20:55 Correct Paths to Emacs C Sources after Installation Alexander Shukaev
2014-11-03 20:58 ` Eli Zaretskii
[not found] ` <CAKu-7Ww3nzB3SQmKpR73xSVoC=U1Tf5UaJCokm4fpBvMSqAoNQ@mail.gmail.com>
2014-11-03 21:31 ` Fwd: " Alexander Shukaev
2014-11-03 22:27 ` Alexander Shukaev
2014-11-03 22:45 ` Stefan Monnier
2014-11-03 23:05 ` Alexander Shukaev
2014-11-04 0:24 ` John Mastro
2014-11-04 0:35 ` Alexander Shukaev
2014-11-04 0:52 ` Alexis
2014-11-04 1:11 ` Alexander Shukaev
2014-11-04 1:17 ` Alexander Shukaev
2014-11-04 1:21 ` Alexander Shukaev
2014-11-04 1:26 ` Alexander Shukaev
2014-11-04 1:30 ` Alexis
2014-11-04 12:20 ` Alexander Shukaev
2014-11-04 8:53 ` Thien-Thi Nguyen [this message]
2014-11-04 15:47 ` Eli Zaretskii
2014-11-04 15:02 ` Stefan Monnier
2014-11-04 15:33 ` Alexander Shukaev
2014-11-04 15:51 ` Eli Zaretskii
2014-11-04 16:07 ` Alexander Shukaev
2014-11-04 16:18 ` Alexander Shukaev
2014-11-04 16:48 ` Eli Zaretskii
2014-11-04 16:26 ` Eli Zaretskii
[not found] ` <mailman.12770.1415117275.1147.help-gnu-emacs@gnu.org>
2014-11-04 17:48 ` Stefan Monnier
2014-11-04 18:39 ` Alexander Shukaev
2014-11-04 18:57 ` Glenn Morris
2014-11-04 19:20 ` Alexander Shukaev
2014-11-04 21:00 ` Bob Proulx
2014-11-05 2:43 ` Yuri Khan
[not found] ` <mailman.12848.1415155389.1147.help-gnu-emacs@gnu.org>
2014-11-05 14:26 ` Ted Zlatanov
2014-11-05 2:07 ` Stefan Monnier
[not found] ` <mailman.12847.1415153254.1147.help-gnu-emacs@gnu.org>
2014-11-07 4:17 ` Jason Rumney
[not found] ` <mailman.12759.1415115240.1147.help-gnu-emacs@gnu.org>
2014-11-04 17:41 ` Stefan Monnier
2014-11-04 15:45 ` Eli Zaretskii
2014-11-04 15:43 ` Fwd: " Eli Zaretskii
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=87ppd3tkhe.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@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.
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).