From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14799@debbugs.gnu.org, angelo.g0@libero.it
Subject: bug#14799: Request for building PDF manuals in A4 format
Date: Thu, 03 Oct 2019 19:48:24 +0300 [thread overview]
Message-ID: <83mueh7p2f.fsf@gnu.org> (raw)
In-Reply-To: <87muehuclg.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 03 Oct 2019 16:29:15 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: angelo.g0@libero.it, 14799@debbugs.gnu.org
> Date: Thu, 03 Oct 2019 16:29:15 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Why is it a virtue to avoid new Makefile targets?
>
> It seems like a combinatorial explosion of rules.
> bovine-a4-odd-page-open/bovine-letter-odd-page-open/bovine-a4-non-odd-page-open/bovine-letter-non-odd-page-open etc.
Did anyone ask for all those additional options?
And you can always make the addition targets just set a value of a
Make variable, which will then be picked up by -t.
Anyway, just an idea. If no one likes it, I'm okay.
next prev parent reply other threads:[~2019-10-03 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 8:10 bug#14799: Request for building PDF manuals in A4 format Angelo Graziosi
2019-08-15 4:20 ` Lars Ingebrigtsen
2019-08-15 10:01 ` Angelo Graziosi via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-09-29 12:12 ` Lars Ingebrigtsen
2019-09-30 16:26 ` Angelo Graziosi via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-01 12:22 ` Lars Ingebrigtsen
2019-10-01 12:30 ` Robert Pluim
2019-10-01 12:36 ` Lars Ingebrigtsen
2019-10-01 12:41 ` Eli Zaretskii
2019-10-02 11:44 ` Lars Ingebrigtsen
2019-10-02 15:16 ` Eli Zaretskii
2019-10-03 14:29 ` Lars Ingebrigtsen
2019-10-03 16:48 ` Eli Zaretskii [this message]
2019-10-07 3:54 ` Lars Ingebrigtsen
2019-10-01 19:18 ` Angelo Graziosi via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83mueh7p2f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14799@debbugs.gnu.org \
--cc=angelo.g0@libero.it \
--cc=larsi@gnus.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.