From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 7397@debbugs.gnu.org
Subject: bug#7397: make-docfile should support the @FILE command line option
Date: Sun, 14 Nov 2010 04:31:50 -0500 [thread overview]
Message-ID: <E1PHYwA-0004fh-0F@fencepost.gnu.org> (raw)
In-Reply-To: <yxqhbfk5lef.fsf@fencepost.gnu.org> (message from Dan Nicolaescu on Sun, 14 Nov 2010 04:01:28 -0500)
> From: Dan Nicolaescu <dann@gnu.org>
> Date: Sun, 14 Nov 2010 04:01:28 -0500
> Cc:
>
> src/Makefile.in contains some ugliness just in order to reduce the
> command line length for make-docfile.
>
> Instead make-docfile could support the @FILE syntax. That would
> remove the command line length limitation.
I'm not against adding this feature to make-docfile, but are we sure
this problem is real nowadays? What systems cannot grok the full list
of Lisp files? shortlisp is 2.2KB long; how much longer can the full
list be? I don't think we have any system supported that cannot
handle at least 10K long commands, do we?
Maybe we should simply dump this ugliness, and see if someone hollers?
next prev parent reply other threads:[~2010-11-14 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 20:26 bug#8302: 23.3; Parallel make: some *.el files are byte-compiled twice Ulrich Mueller
2011-05-19 1:35 ` Glenn Morris
2011-05-19 2:18 ` Stefan Monnier
2011-05-19 6:15 ` Glenn Morris
2011-05-19 12:27 ` Dan Nicolaescu
2011-05-20 0:51 ` Glenn Morris
2011-05-24 16:46 ` Dan Nicolaescu
2011-05-24 17:31 ` bug#7397: " Glenn Morris
2011-05-25 3:30 ` Glenn Morris
2011-05-25 13:52 ` Stefan Monnier
2010-11-14 9:01 ` bug#7397: make-docfile should support the @FILE command line option Dan Nicolaescu
2010-11-14 9:31 ` Eli Zaretskii [this message]
2010-11-14 17:01 ` Dan Nicolaescu
2011-05-25 20:56 ` bug#7397: bug#8302: 23.3; Parallel make: some *.el files are byte-compiled twice Glenn Morris
2011-05-25 23:56 ` Stefan Monnier
2011-07-09 19:03 ` bug#7397: make-docfile should support the @FILE command line option Glenn Morris
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=E1PHYwA-0004fh-0F@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=7397@debbugs.gnu.org \
--cc=dann@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.