editing "The compact Org-Mode Guide"

editing "The compact Org-Mode Guide"

[Gregory Benjamin]

I started reading "orgguide.pdf", Release 7.9.3e and came across a
couple of grammatical errors right away.

I'd like to take a stab at making some corrections and would like to
have access to the source for this document. With some guidance, I
should be able to produce a patch that can be incorporated into the
next realease.

Please provide me with instructions on downloading the source, and
after I finish editing, uploading the diffs or updated version.

Thank you.

Best,
Greg Benjamin

Re: editing "The compact Org-Mode Guide"

[Thomas S. Dye]

Aloha Greg,
Gregory Benjamin <gregb@laserlab.com> writes:

> I'd like to take a stab at making some corrections and would like to
> have access to the source for this document. With some guidance, I
> should be able to produce a patch that can be incorporated into the
> next realease.

The source is /path/to/org-mode/doc/orgguide.texi

There is a file in that directory called Documentation_Standards.org,
which contains what the file name advertises.

>
> Please provide me with instructions on downloading the source, and
> after I finish editing, uploading the diffs or updated version.

Assuming you are using the git version of Org mode, you should create a
new branch, check it out, and edit orgguide.texi there.  

When you are happy with your edits, stage and commit them in the git
repository.  Once the edits have been committed, you can make a patch like
this:

git format-patch -o ~/temp/ HEAD~1

where ~/temp/ is what I use and might not be appropriate for your setup,
so should be changed accordingly.

You should read the instructions on formatting patches here:

http://orgmode.org/worg/org-contribute.html#sec-4

It saves the developers a lot of time if you follow these instructions.

Finally, if you're likely to go over the limits of a TINY CHANGE, then
you will want to assign your work to FSF so that it can be included in
Emacs.  See the instructions here:

http://orgmode.org/worg/org-contribute.html#sec-2

Hopefully, I've remembered all the steps. If this doesn't work for you,
come back to the list with queries.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: editing "The compact Org-Mode Guide"

[Evan Misshula]

Thanks for the instructions on how to play nice in the sandbox.  We
noobs are always afraid
we are going to cause more work than we fix.

:-)

On Tue, Feb 5, 2013 at 2:11 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Greg,
> Gregory Benjamin <gregb@laserlab.com> writes:
>
>> I'd like to take a stab at making some corrections and would like to
>> have access to the source for this document. With some guidance, I
>> should be able to produce a patch that can be incorporated into the
>> next realease.
>
> The source is /path/to/org-mode/doc/orgguide.texi
>
> There is a file in that directory called Documentation_Standards.org,
> which contains what the file name advertises.
>
>>
>> Please provide me with instructions on downloading the source, and
>> after I finish editing, uploading the diffs or updated version.
>
> Assuming you are using the git version of Org mode, you should create a
> new branch, check it out, and edit orgguide.texi there.
>
> When you are happy with your edits, stage and commit them in the git
> repository.  Once the edits have been committed, you can make a patch like
> this:
>
> git format-patch -o ~/temp/ HEAD~1
>
> where ~/temp/ is what I use and might not be appropriate for your setup,
> so should be changed accordingly.
>
> You should read the instructions on formatting patches here:
>
> http://orgmode.org/worg/org-contribute.html#sec-4
>
> It saves the developers a lot of time if you follow these instructions.
>
> Finally, if you're likely to go over the limits of a TINY CHANGE, then
> you will want to assign your work to FSF so that it can be included in
> Emacs.  See the instructions here:
>
> http://orgmode.org/worg/org-contribute.html#sec-2
>
> Hopefully, I've remembered all the steps. If this doesn't work for you,
> come back to the list with queries.
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>



-- 
Evan Misshula
Doctoral Student (Criminal Justice)
CUNY John Jay
"Let us reform our schools, and we shall find little reform needed in
our prisons."
       John Ruskin, Unto This Last, essay 2 (1862)
       English critic, essayist, & reformer (1819 - 1900)

"Instruction does much, but encouragement does everything." Johann
Wolfgang Von Goethe
www.snrg-nyc.org

Re: editing "The compact Org-Mode Guide"

[Bastien]

Evan Misshula <evanmisshula@gmail.com> writes:

> Thanks for the instructions on how to play nice in the sandbox.  We
> noobs are always afraid
> we are going to cause more work than we fix.

We are all n00bs!  Somehow.

-- 
 Bastien

Re: editing "The compact Org-Mode Guide"

[Bastien]

Hi Gregory,

Gregory Benjamin <gregb@laserlab.com> writes:

> I started reading "orgguide.pdf", Release 7.9.3e and came across a
> couple of grammatical errors right away.
>
> I'd like to take a stab at making some corrections and would like to
> have access to the source for this document. With some guidance, I
> should be able to produce a patch that can be incorporated into the
> next realease.

thanks in advance for this work!

Thomas gave all information you need to start -- one correction:
orgguide.texi is not part of Emacs, so you don't need to assign
your copyright to the FSF for them.

Another caveat: most of orgguide.texi comes from org.texi, so
it is very like that, if you find a typo in orgguide.texi, the 
typo will be in org.texi too.  If you want to provide a patch
for org.texi too, then you'll have to assign your copyright
to the FSF -- or to let Thomas or/and I backport your changes
into org.texi.

All best,

-- 
 Bastien

segfault on 'make test'

[Gregory Benjamin]

I did a 'git pull' just now, followed by 'make test' and this is what
happened (snippet shown for brevity):

################################################################
Code block evaluation complete.
   passed  281/342  test-org-property-accumulation-top-use
OVERVIEW
executing Emacs-Lisp code block...

(foo (quote 1))

(bar (quote 2))

Code block evaluation complete.
   passed  282/342  test-org-property-accumulation-top-val
OVERVIEW
Mark set
Fatal error (11)Segmentation fault
make: *** [test] Error 139
################################################################

So it looks like test number 283 blew up.
I'm happy to try investigating with some help...

The basic system info:

  $ uname -a
  Linux dbn66 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux

  $ lsb_release -sd
  Debian GNU/Linux 6.0.6 (squeeze)

Best,
Greg Benjamin

Re: segfault on 'make test'

[Bastien]

Hi Gregory,

Gregory Benjamin <gregb@laserlab.com> writes:

> Code block evaluation complete.
>    passed  282/342  test-org-property-accumulation-top-val
> OVERVIEW
> Mark set
> Fatal error (11)Segmentation fault
> make: *** [test] Error 139

What version of Emacs are you using?  I assume you are on the current
HEAD of the master branch, but M-x org-version RET can help too.

Thanks!

-- 
 Bastien

Re: segfault on 'make test'

[Achim Gratz]

Gregory Benjamin writes:
> I did a 'git pull' just now, followed by 'make test'

Nothing to do with your problem, but "ake up1" would do this with less
typing.  :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Agenda buffer behavior

[Gregory Benjamin]

Hi,

Org-mode version 7.9.3e

I am getting used to the various Agenda views. One thing that seems
'wrong' to me is that whenever I invoke the main agenda view with 'C-c
a a' it reuses (overwrites) the '*Org Agenda*' buffer. Similarly, if
invoke the all todos view with 'C-c a t' it overwrites the previous
content of the '*Org Agenda*' buffer. Thus it is difficult to view
both of these views at once since they share the same buffer. It would
be more natural, I think, if each Agenda view had its own buffer so
that one could display both the weekly agenda and the list of all
todos simultaneously.

Is there a setting to control this?

Greg Benjamin

Re: Agenda buffer behavior

[Marcin Borkowski]

Dnia 2013-03-11, o godz. 12:26:52
Gregory Benjamin <gregb@laserlab.com> napisał(a):

> Hi,
> 
> Org-mode version 7.9.3e
> 
> I am getting used to the various Agenda views. One thing that seems
> 'wrong' to me is that whenever I invoke the main agenda view with 'C-c
> a a' it reuses (overwrites) the '*Org Agenda*' buffer. Similarly, if
> invoke the all todos view with 'C-c a t' it overwrites the previous
> content of the '*Org Agenda*' buffer. Thus it is difficult to view
> both of these views at once since they share the same buffer. It would
> be more natural, I think, if each Agenda view had its own buffer so
> that one could display both the weekly agenda and the list of all
> todos simultaneously.
> 
> Is there a setting to control this?
> 
> Greg Benjamin
> 

Hi,

not /exactly/ what you are looking for, but maybe even better:
http://orgmode.org/org.html#Block-agenda

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

Re: Agenda buffer behavior

[Eric Abrahamsen]

Gregory Benjamin <gregb@laserlab.com> writes:

> Hi,
>
> Org-mode version 7.9.3e
>
> I am getting used to the various Agenda views. One thing that seems
> 'wrong' to me is that whenever I invoke the main agenda view with 'C-c
> a a' it reuses (overwrites) the '*Org Agenda*' buffer. Similarly, if
> invoke the all todos view with 'C-c a t' it overwrites the previous
> content of the '*Org Agenda*' buffer. Thus it is difficult to view
> both of these views at once since they share the same buffer. It would
> be more natural, I think, if each Agenda view had its own buffer so
> that one could display both the weekly agenda and the list of all
> todos simultaneously.
>
> Is there a setting to control this?

Yup, it's called `org-agenda-sticky'. You can turn it on by default, or
on the fly with "*" in the dispatcher, or by calling
`org-toggle-sticky-agenda'.

E