Re: [O] #+PROPERTY documentation
Hi Daimrod, Daimrod writes: > Ok, I've already sent an assignment request for another patch and it > should be confirmed by the end of the week. Don't be too optimistic, it takes usually longer, at least three weeks. You can still send patches, we will apply them when the FSF confirmed your assignment is processed. This leaves a window for discussing the change, if needed. Thanks for your contributions! -- Bastien
Re: [O] #+PROPERTY documentation
Achim Gratz writes: > Nick Dokos writes: >> I believe that just as with code changes, doc changes also need FSF >> copyright assignment. > > The FSF owns the copyright to all of Org, including the > documentation. More precisely, the FSF owns the copyright of GNU Emacs, and assignments are signed but the contributors for contributions to GNU Emacs. Since Org is part of GNU Emacs, the FSF owns the copyright for the Org manual that is part of GNU Emacs. It does not own the copyright for changes that are ahead of GNU Emacs and not yet merged. But we ask contributors to proceed with the assignment ahead of the merge, that's easier. > So yes, anything over 20 lines non-trivial chnages needs to be assigned > to FSF. Indeed. -- Bastien
Re: [O] #+PROPERTY documentation
Nick Dokos writes: > Daimrod wrote: > >> John Hendy writes: >> >> > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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. Ok, I've already sent an assignment request for another patch and it should be confirmed by the end of the week. > Nick -- Daimrod/Greg pgpKUC7Fa73Fv.pgp Description: PGP signature
Re: [O] #+PROPERTY documentation
Nick Dokos writes: > I believe that just as with code changes, doc changes also need FSF > copyright assignment. The FSF owns the copyright to all of Org, including the documentation. So yes, anything over 20 lines non-trivial chnages needs to be assigned to FSF. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] #+PROPERTY documentation
Daimrod wrote: > John Hendy writes: > > > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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
Re: [O] #+PROPERTY documentation
t...@tsdye.com (Thomas S. Dye) writes: > Aloha Daimrod (Greg), > > Daimrod writes: > >> >> So, here is a patch for this: > > If you add [PATCH] to the email Subject, your patch will be brought to > the attention of the developers. I didn't know, thanks. > All the best, > Tom -- Daimrod/Greg pgpRUIidjPMtV.pgp Description: PGP signature
Re: [O] #+PROPERTY documentation
Aloha Daimrod (Greg), Daimrod writes: > > So, here is a patch for this: If you add [PATCH] to the email Subject, your patch will be brought to the attention of the developers. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] #+PROPERTY documentation
On Mon, Jan 21, 2013 at 4:35 PM, Daimrod wrote: > John Hendy writes: > >> On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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. Wasn't criticizing, for the record :) I actually didn't know one could do that! Glad I learned something, and hopefully I can give back to Org more, now! John > >> John >> >>> >>> And, IMO, it should also be mentioned here: >>> (info "(org) Buffer-wide header arguments"). >>> >>> A simple footnote like the one present here: >>> (info "(org) Tag inheritance") should be sufficient. >>> (1) As with all these in-buffer settings, pressing `C-c C-c' activates any changes in the line. >>> >>> -- >>> Daimrod/Greg > > -- > Daimrod/Greg
Re: [O] #+PROPERTY documentation
Daimrod writes:
> John Hendy writes:
>
>> On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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.
>
>> John
>>
>>>
>>> And, IMO, it should also be mentioned here:
>>> (info "(org) Buffer-wide header arguments").
>>>
>>> A simple footnote like the one present here:
>>> (info "(org) Tag inheritance") should be sufficient.
>>>
(1) As with all these in-buffer settings, pressing `C-c C-c'
activates any changes in the line.
>>>
So, here is a patch for this:
From 09e569a651e77e8f2c1c2d1f0a285c69688fbd05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gr=C3=A9goire=20Jadi?=
Date: Mon, 21 Jan 2013 23:45:47 +0100
Subject: [PATCH] add footnote to recall the user to refresh the org buffer
when settings are changed.
---
doc/org.texi |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 61f1ee5..c2bdd58 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4954,7 +4954,9 @@ publishers and the number of disks in a box like this:
@end example
If you want to set properties that can be inherited by any entry in a
-file, use a line like
+file, use a line like@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@cindex property, _ALL
@cindex #+PROPERTY
@example
@@ -13252,7 +13254,9 @@ of @code{#+PROPERTY:} lines placed anywhere in an Org mode file (see
For example the following would set @code{session} to @code{*R*}, and
@code{results} to @code{silent} for every code block in the buffer, ensuring
that all execution took place in the same session, and no results would be
-inserted into the buffer.
+inserted into the buffer.@footnote{As
+with all these in-buffer settings, pressing @kbd{C-c C-c} activates any
+changes in the line.}
@example
#+PROPERTY: session *R*
--
1.7.10.4
--
Daimrod/Greg
pgp6BspWNmlxz.pgp
Description: PGP signature
Re: [O] #+PROPERTY documentation
John Hendy writes: > On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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. > John > >> >> And, IMO, it should also be mentioned here: >> (info "(org) Buffer-wide header arguments"). >> >> A simple footnote like the one present here: >> (info "(org) Tag inheritance") should be sufficient. >> >>> (1) As with all these in-buffer settings, pressing `C-c C-c' >>> activates any changes in the line. >> >> -- >> Daimrod/Greg -- Daimrod/Greg pgpQh8xnK3Ubb.pgp Description: PGP signature
Re: [O] #+PROPERTY documentation
On Mon, Jan 21, 2013 at 12:41 PM, Daimrod 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. John > > And, IMO, it should also be mentioned here: > (info "(org) Buffer-wide header arguments"). > > A simple footnote like the one present here: > (info "(org) Tag inheritance") should be sufficient. > >> (1) As with all these in-buffer settings, pressing `C-c C-c' >> activates any changes in the line. > > -- > Daimrod/Greg
[O] #+PROPERTY documentation
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") And, IMO, it should also be mentioned here: (info "(org) Buffer-wide header arguments"). A simple footnote like the one present here: (info "(org) Tag inheritance") should be sufficient. > (1) As with all these in-buffer settings, pressing `C-c C-c' > activates any changes in the line. -- Daimrod/Greg pgplZQR3DFgvj.pgp Description: PGP signature
