From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master dfaf150631: Add a new library to format variable-pitch tables
Date: Sat, 19 Feb 2022 16:49:15 +0200 [thread overview]
Message-ID: <835ypazzbo.fsf@gnu.org> (raw)
In-Reply-To: <87pmnjvxjt.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 19 Feb 2022 13:41:10 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 19 Feb 2022 13:41:10 +0100
> Cc: emacs-devel@gnu.org
>
> Po Lu <luangruo@yahoo.com> writes:
>
> >> doc/misc/vtable.texi | 521 +++++++++++++++++++++++++
> >
> > I really like the library, but does it warrant an entire manual?
> >
> > Emacs currently ships with 65 manuals, and I think we don't want any
> > more, certainly not for a core Lisp library which will hopefully be used
> > by many important features in the future.
>
> You'd rather have it in the main lispref manual? That was my original
> intention, but it grew kinda long, so I felt it would be better to keep
> it separate.
Yes, we should take extra care not to enlarge the ELisp manual too
much -- it already prints as 2 large volumes.
But we can include stuff in it that will not be included in the
printed copy, like we already do in the user manual: use @include
under @ifnottex condition.
I don't have a problem with either alternative, FWIW.
next prev parent reply other threads:[~2022-02-19 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164527299527.13254.13621180534925877627@vcs2.savannah.gnu.org>
[not found] ` <20220219121635.B1D3BC00894@vcs2.savannah.gnu.org>
2022-02-19 12:26 ` master dfaf150631: Add a new library to format variable-pitch tables Po Lu
2022-02-19 12:41 ` Lars Ingebrigtsen
2022-02-19 14:49 ` Eli Zaretskii [this message]
2022-02-19 16:04 ` Lars Ingebrigtsen
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=835ypazzbo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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.
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.