From: Greg Minshall <minshall@umich.edu>
To: emacs-orgmode@gnu.org
Subject: have =make cleanall= remove .texi files in doc/
Date: Fri, 21 May 2021 18:48:24 +0300 [thread overview]
Message-ID: <3034317.1621612104@apollo2.minshall.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
hi. neither =make clean= nor =make cleanall= remove the two .texi files
built (by, e.g., =make info=) in the doc subdirectory. this patch
removes those files with =make cleanall=. i wasn't sure which to use,
but it sort of looked like =cleanall= might be the place.
i also noticed that =make cleanall= invokes =find= on =./contrib=, which
no longer (i assume) exists so =find= complains (which is logged, but
then ignored, by =make=). i'm happy to do a patch for that (though it
would be, presumably, as trivial as this one).
cheers, Greg
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: cleanall .texi files --]
[-- Type: text/x-diff, Size: 855 bytes --]
From 0584aec533d556bed94f6e90affb3ff11faca3b0 Mon Sep 17 00:00:00 2001
From: Greg Minshall <minshall@umich.edu>
Date: Fri, 21 May 2021 18:42:35 +0300
Subject: [PATCH] doc/Makefile: `cleanall` target now deletes
doc/{org,orgguide}.texi
* doc/Makefile: `cleanall` target now deletes doc/{org,orgguide}.texi
In the past, at least one of these seems to have been a tracked
(source?) file. That is no longer the case.
---
doc/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/Makefile b/doc/Makefile
index da5a07ad9..d934258f3 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -58,6 +58,7 @@ clean:
org-version.tex *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys \
*.pg *.pgs *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps
cleanall: clean
+ $(RM) org.texi orgguide.texi
$(RMR) guide manual
clean-install:
--
2.31.1
next reply other threads:[~2021-05-21 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 15:48 Greg Minshall [this message]
2021-05-29 20:37 ` have =make cleanall= remove .texi files in doc/ Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3034317.1621612104@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).