From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: procedure for creating online Emacs manual?
Date: Sun, 1 Apr 2018 14:20:20 -0700 [thread overview]
Message-ID: <4874e6c5-7861-03db-bb2b-6cdc3b3a1292@cs.ucla.edu> (raw)
In-Reply-To: <luzi2pawo0.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On 03/30/2018 05:58 PM, Glenn Morris wrote:
>> I fixed the
>> problems that I found (e.g., we don't put refcards up on the web any
>> more)
> Yes we do?
> https://www.gnu.org/software/emacs/refcards/index.html
Ouch. These were not in my copy of the CVS repository of the Emacs web pages,
even after I did a "cvs update". Apparently my copy (which has been around for a
while) was incorrect, or was updated incorrectly, or something. I removed my bad
copy and got a fresh one from Savannah. Sorry about the false alarm. I restored
the refcards commentary to admin/make-tarball.txt on master (see attached).
I tried to take your comments into account in the attached further patch. Thanks.
It's still not clear that the refcards are worth the maintenance hassle. I can't
build them on either of my main build platforms right now, so I can't completely
update the Emacs web pages.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Further-improve-advice-in-make-tarball.txt.patch --]
[-- Type: text/x-patch; name="0001-Further-improve-advice-in-make-tarball.txt.patch", Size: 2228 bytes --]
From 7bedc8812bd7ca1d9cf36636322068b28b690a85 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Sun, 1 Apr 2018 14:16:48 -0700
Subject: [PATCH] Further improve advice in make-tarball.txt
See comments by Glenn Morris in:
https://lists.gnu.org/r/emacs-devel/2018-03/msg00968.html
* admin/make-tarball.txt: Bring back refcard advice.
---
admin/make-tarball.txt | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt
index f9ad217..9b9c964 100644
--- a/admin/make-tarball.txt
+++ b/admin/make-tarball.txt
@@ -87,6 +87,11 @@ General steps (for each step, check for possible errors):
make -C etc/refcards
make -C etc/refcards clean
+ If etc/refcards does not build you may need to downgrade or
+ upgrade your TeX installation, or do that part of the build by
+ hand. For clues, search for the string "refcard" in the file
+ admin/release-process.
+
5. Copy lisp/loaddefs.el to lisp/ldefs-boot.el.
Commit ChangeLog.N, etc/AUTHORS, lisp/ldefs-boot.el, and the
@@ -231,11 +236,16 @@ as follows:
gzip --best --no-name <../info/elisp.info >info/elisp.info.gz
gzip --best --no-name <../info/emacs.info >info/emacs.info.gz
+Update the refcards/pdf/ and ps/ directories, and also
+refcards/emacs-refcards.tar.gz (use make -C etc/refcards pdf ps dist).
+
FIXME: The above instructions are not quite complete, as they do not
-specify how to copy the generated files in the 'manual' directory to
-the corresponding web files. Also, they are missing some files, e.g.,
+specify the manual procuedure used to copy the generated files in the
+'manual' directory to the corresponding web files, and to cvs remove
+and add files as needed. Also, they are missing some files, e.g.,
they generate manual/html_mono/ada-mode.html but do not generate the
-top-level ada-mode.html file for the one-node-per-page version.
+top-level ada-mode.html file for the one-node-per-page version; this
+is currently done by hand.
Browsing <https://web.cvs.savannah.gnu.org/viewvc/?root=emacs> is one
way to check for any files that still need updating.
--
2.7.4
next prev parent reply other threads:[~2018-04-01 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 19:07 procedure for creating online Emacs manual? Paul Eggert
2018-03-30 19:32 ` Glenn Morris
2018-03-30 23:23 ` Paul Eggert
2018-03-31 0:58 ` Glenn Morris
2018-04-01 21:20 ` Paul Eggert [this message]
2018-04-02 18:26 ` 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=4874e6c5-7861-03db-bb2b-6cdc3b3a1292@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.