From: Nick Dokos <nicholas.dokos@hp.com>
To: Daimrod <daimrod@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+PROPERTY documentation
Date: Tue, 22 Jan 2013 00:27:22 -0500 [thread overview]
Message-ID: <17633.1358832442@alphaville> (raw)
In-Reply-To: Message from Daimrod <daimrod@gmail.com> of "Mon, 21 Jan 2013 23:35:52 +0100." <87wqv6cgfr.fsf@casa.home>
Daimrod <daimrod@gmail.com> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
> > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod <daimrod@gmail.com> wrote:
> >> Hi,
> >>
> >> It would be nice if the documentation mentioned the need to reparse the
> >> org buffer with `C-c C-c' when a property is set with #+PROPERTY.
> >> (info "(org) Property syntax")
> >
> > As in adding to the header arguments? Yeah, probably wouldn't hurt,
> > though it is, as stated below, documented that *any* change to the
> > header arguments requires C-c C-c.
> >
> > On a side note, is there the possibility for "normal" users to submit
> > git based changes to the manual? I know how to do this for Worg, but
> > I'd be happy to update stuff in the manual, too, when I catch them.
> > These sorts of things could be tweaked by the finder and it would save
> > the maintenance team a bit -- just scan the commit and notes for
> > rationale and accept.
>
> Sure, one can modify the file doc/org.texi. And you're right, I should
> have submit a patch.
>
I believe that just as with code changes, doc changes also need FSF
copyright assignment.
Nick
next prev parent reply other threads:[~2013-01-22 5:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 18:41 #+PROPERTY documentation Daimrod
2013-01-21 22:21 ` John Hendy
2013-01-21 22:35 ` Daimrod
2013-01-21 22:47 ` John Hendy
2013-01-21 22:49 ` Daimrod
2013-01-22 0:21 ` Thomas S. Dye
2013-01-22 0:36 ` Daimrod
2013-01-22 5:27 ` Nick Dokos [this message]
2013-01-22 6:32 ` Achim Gratz
2013-01-22 13:19 ` Bastien
2013-01-22 10:19 ` Daimrod
2013-01-22 13:20 ` Bastien
2013-01-22 0:43 ` [PATCH] " Daimrod
2013-01-22 13:23 ` Bastien
2013-01-22 14:09 ` Daimrod
2013-01-22 14:34 ` Bastien
2013-01-24 12:20 ` Daimrod
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=17633.1358832442@alphaville \
--to=nicholas.dokos@hp.com \
--cc=daimrod@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).