From: stardiviner <numbchild@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Which org mode document should I modify for new header argument?
Date: Tue, 10 Apr 2018 08:53:02 +0800 [thread overview]
Message-ID: <87vaczhogh.fsf@gmail.com> (raw)
In-Reply-To: <87sh86h5bu.fsf@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I try to find information in Org-mode web page
https://orgmode.org/worg/org-contribute.html#patches
But can't find which document should I modify. Recently I found both
`org.texi` and `org-manual.org` are modified. Really don't know which
one should I edit.
stardiviner <numbchild@gmail.com> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> I'm write a new feature for Org-mode, need to modify the document, which file should I modify?
> doc/org-manual.org or doc/org.texi?
> If it is doc/org-manual.org will be great. It is really hard for me to read TeX code.
> - --
> [ stardiviner ] don't need to convince with trends.
> Blog: https://stardiviner.github.io/
> IRC(freenode): stardiviner
> GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
>
> -----BEGIN PGP SIGNATURE-----
>
> iQEzBAEBCAAdFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAlrJa8YACgkQG13xyVro
> msMDQAgAxF+JmQ+hKb+w6AC6eFBZjFLWC5Fqunrxk/tReCCIKBNBXV7Wqcsx69t7
> LnBdPvgYVPQEYM+tNycsUPF9kPUhcdyklaoh3IIwQcDCr+b6Cbs8nhASQG/eibQa
> pdTUlkdt8yCG9VSZpOrNopt7LKR5mKTMsNFVdekSZvH50wolQYNn/Zpgi4vNThuB
> 0STqOT5W+Qjp2n04vAbIFm6Xd72UZab4w53SW7Q+lIoJw2FXytVCLVrwBOd11zGZ
> hG0fV2tMW5baSr7za7+2zBX/Z5S/65qSAMCaKP9d6M4Zc2shCz9oB2Z1VhjxPOwv
> C2296roDQaUgA7v8Cr2J4H3hzE7tPg==
> =6hmn
> -----END PGP SIGNATURE-----
- --
[ stardiviner ] don't need to convince with trends.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAlrMCu4ACgkQG13xyVro
msNvUAf/aeODxbZUshxZAX+T9yavqj65E1+SxxyydVABnjFEAcJvtbui9qLS9B6a
srp+mymWLyT0kxVKwRG6DNdZ+dV0l9jJ2GFQWTnQjfZGeqYEkTH/M8ViJFVW1xqw
Uv5C+HTkR2XUhYGZNlli3Z9x4NumdF5vYv+knCoP6h4TQ2WM1dt9Eyp35+xg+Pur
Br9zxVvlHcXXLc9bRkFC5FIv5FefP7PDelzyY4CNNXwkWwBl6718ugDDjldROPCP
fp4KB9r0Z3692qQtPK7lhtAKxLYozbPyEJ6h98BSbKmzi45ERb2Pmpn2msCVwlfm
7uZoSOKk6F14AiC71i07VkIQUd3Lug==
=Wg4e
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-04-10 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 1:09 Does doc/org-manual.org is now the document for editing? stardiviner
2018-04-08 2:08 ` Fwd: " stardiviner
2018-04-08 7:37 ` Nicolas Goaziou
2018-04-10 0:53 ` stardiviner [this message]
2018-04-10 18:12 ` Which org mode document should I modify for new header argument? Nicolas Goaziou
2018-04-26 23:34 ` Bastien
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=87vaczhogh.fsf@gmail.com \
--to=numbchild@gmail.com \
--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).