From: Karl Fogel <kfogel@red-bean.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Kyle Meyer <kyle@kyleam.com>,
Michael Albinus <michael.albinus@gmx.de>,
emacs-devel@gnu.org
Subject: Re: Improving documentation of Org Mode integration into Emacs.
Date: Mon, 10 Jan 2022 10:10:50 -0600 [thread overview]
Message-ID: <87zgo3fu5x.fsf@red-bean.com> (raw)
In-Reply-To: <87o84j6ehk.fsf@gmail.com> (Robert Pluim's message of "Mon, 10 Jan 2022 12:01:59 +0100")
On 10 Jan 2022, Robert Pluim wrote:
>>>>>> On Mon, 10 Jan 2022 03:13:22 -0600, Karl Fogel
>>>>>> <kfogel@red-bean.com> said:
>
> Karl> On 10 Jan 2022, Michael Albinus wrote:
> >> PS: doc/misc/org.texi is a generated file, no need to
> >> mention it.
>
> Karl> Interesting -- it is version-controlled, in both the
> Emacs and the Org
> Karl> Mode repositories:
>
> Karl> Emacs: doc/misc/org.texi
> Karl> Org Mode: doc/org.texi
>
>It was version controlled in Emacs, but was deleted by
>fddd63f8. Of
>course itʼs still in the git history.
Oh, sigh, thanks. Today I learned that using 'git log' is not the
way to check if a file is *currently* versioned at a certain path.
One should instead use
$ git ls-files doc/misc/org.texi
or better yet
$ git ls-files --error-unmatch doc/misc/org.texi
I'll take 'doc/misc/org.texi out of the change.
Best regards,
-Karl
next prev parent reply other threads:[~2022-01-10 16:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 21:14 Improving documentation of Org Mode integration into Emacs Karl Fogel
2021-12-04 21:18 ` Karl Fogel
2021-12-04 22:09 ` [External] : " Drew Adams
2021-12-05 5:16 ` Stefan Monnier
2021-12-05 6:38 ` Eli Zaretskii
2022-01-03 5:05 ` Karl Fogel
2022-01-03 5:44 ` Stefan Monnier
2022-01-05 3:09 ` Karl Fogel
2022-01-05 13:48 ` Eli Zaretskii
2022-01-05 14:17 ` Michael Albinus
2022-01-05 14:26 ` Eli Zaretskii
2022-01-06 12:40 ` Michael Albinus
2022-01-06 13:58 ` Eli Zaretskii
2022-01-07 10:41 ` Protesilaos Stavrou
2022-01-09 22:34 ` Karl Fogel
2022-01-10 8:46 ` Michael Albinus
2022-01-10 9:03 ` Michael Albinus
2022-01-10 9:13 ` Karl Fogel
2022-01-10 9:17 ` Michael Albinus
2022-01-10 11:01 ` Robert Pluim
2022-01-10 16:10 ` Karl Fogel [this message]
2022-01-10 9:06 ` Karl Fogel
2022-01-10 9:24 ` Michael Albinus
2022-01-10 16:20 ` Karl Fogel
2022-01-10 18:24 ` Eli Zaretskii
2022-01-11 7:49 ` Michael Albinus
2022-01-10 18:14 ` Eli Zaretskii
2022-01-10 19:08 ` Karl Fogel
2022-01-03 8:52 ` Michael Albinus
2022-01-03 12:06 ` Protesilaos Stavrou
2022-01-03 13:31 ` Eli Zaretskii
2022-01-03 20:45 ` Rudolf Adamkovič
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgo3fu5x.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=michael.albinus@gmx.de \
--cc=rpluim@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).