Re: [O] [PATCH] org-manual: Dynamic Blocks: Fix explanation of :content

[Kyle Meyer]

Sebastian Miele  writes:

> * doc/org-manual.org (Dynamic Blocks): Correct the information given
> on :content in the plist passed to the writer function.

Looks correct to me.  Applied in 634880a2e. Thanks.

[O] [PATCH] org-manual: Dynamic Blocks: Fix explanation of :content

[Sebastian Miele]

* doc/org-manual.org (Dynamic Blocks): Correct the information given
on :content in the plist passed to the writer function.
---
 doc/org-manual.org | 9 -
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 59591894d..79257b7e0 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -20089,13 +20089,12 @@ These commands update dynamic blocks:
 
 Before updating a dynamic block, Org removes content between the
 =BEGIN= and =END= markers.  Org then reads the parameters on the
-=BEGIN= line for passing to the writer function.  If the function
-expects to access the removed content, then Org expects an extra
-parameter, =:content=, on the =BEGIN= line.
+=BEGIN= line for passing to the writer function as a plist. The
+previous content of the dynamic block becomes erased from the buffer
+and appended to the plist under ~:content~.
 
 The syntax for naming a writer function with a dynamic block labelled
-=myblock= is: ~org-dblock-write:myblock~.  Parameters come from the
-=BEGIN= line.
+=myblock= is: ~org-dblock-write:myblock~.
 
 The following is an example of a dynamic block and a block writer function
 that updates the time when the function was last run:
-- 
2.23.0

Re: [O] Bug: org manual 15.10.2 Packages that conflict with Org mode doesn't include EDE [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)]

[Nicolas Goaziou]

Hello,

Vladimir Nikishkin  writes:

> EDE is  Emacs Development Environment, is shipped with stock Emacs 

OK.

> and is recommended to be turned on as a global minor mode, in the
> official Emacs Manual, Section 25.4, page 330 of the printed version,
> or 352 of the pdf.

I don't see any such recommendation, but that doesn't matter.

> It's not a 'mere keybinding conflict', it's a conflict that anyone reading
> the official manual would be bumping into. It's not some obscure tiny
> extension no-one is using, it is an official part of Emacs, just as
> Org is.

You may be exaggerating a little bit. Well. Feel free to provide an
entry in "Conflicts", then.

Thank you!

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org manual 15.10.2 Packages that conflict with Org mode doesn't include EDE [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)]

[Vladimir Nikishkin]

EDE is  Emacs Development Environment, is shipped with stock Emacs and is
recommended to be turned on as a global minor mode, in the official Emacs
Manual, Section 25.4, page 330 of the printed version, or 352 of the pdf.

It's not a 'mere keybinding conflict', it's a conflict that anyone reading
the official manual would be bumping into. It's not some obscure tiny
extension no-one is using, it is an official part of Emacs, just as Org is.



On Sun, Jul 7, 2019, 05:05 Nicolas Goaziou  wrote:

> Hello,
>
> Vladimir Nikishkin  writes:
>
> > Although they actually do conflict is that the default bindings for EDE
> > start with C-c . ,
> > whereas Org uses this keybinding branch as an org-time-stamp binding.
>
> I don't know what is EDE. Anyway I don't think a mere key-binding
> conflict deserves an entry in the "Conflicts" section.
>
> It's true that Org shouldn't have used `C-c .` and `C-c !` in the first
> place, but that ship sailed long ago.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Bug: org manual 15.10.2 Packages that conflict with Org mode doesn't include EDE [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)]

[Nicolas Goaziou]

Hello,

Vladimir Nikishkin  writes:

> Although they actually do conflict is that the default bindings for EDE
> start with C-c . ,
> whereas Org uses this keybinding branch as an org-time-stamp binding.

I don't know what is EDE. Anyway I don't think a mere key-binding
conflict deserves an entry in the "Conflicts" section.

It's true that Org shouldn't have used `C-c .` and `C-c !` in the first
place, but that ship sailed long ago.

Regards,

-- 
Nicolas Goaziou

[O] Bug: org manual 15.10.2 Packages that conflict with Org mode doesn't include EDE [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)]

[Vladimir Nikishkin]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


Although they actually do conflict is that the default bindings for EDE
start with C-c . ,
whereas Org uses this keybinding branch as an org-time-stamp binding.

Emacs  : GNU Emacs 26.2 (build 1, x86_64-slackware-linux-gnu, Motif Version 
2.3.8)
 of 2019-05-30
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ 
/usr/share/emacs/26.2/lisp/org/)

current state:
==
(setq
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-babel-after-execute-hook '((lambda nil
 (if org-inline-image-overlays
  (progn (org-redisplay-inline-images)))
 )
)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-modules '(org-habits org-w3m org-bbdb org-bibtex org-docview org-gnus 
org-info org-irc
   org-mhe org-rmail)
 org-plantuml-jar-path "/usr/local/bin/plantuml.jar"
 org-mode-hook '(#[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-show-block-all append 
local] 5]
 #[0 "\300\301\302\303\304$\207"
   [add-hook change-major-mode-hook org-babel-show-result-all 
append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn 
ENTRY)"]
 org-babel-pre-tangle-hook '(save-buffer)
 org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-babel-load-languages '((plantuml . t))
 org-log-done 'time
 org-startup-align-all-tables t
 org-catch-invisible-edits t
 org-occur-hook '(org-first-headline-recenter)
 org-edit-src-auto-save-idle-delay 15
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-edit-src-turn-on-auto-save t
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-confirm-shell-link-function 'yes-or-no-p
 org-link-parameters '(("id" :follow org-id-open)
   ("rmail" :follow org-rmail-open :store 
org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link)
   ("irc" :follow org-irc-visit :store org-irc-store-link)
   ("info" :follow org-info-open :export org-info-export 
:store
org-info-store-link)
   ("gnus" :follow org-gnus-open :store org-gnus-store-link)
   ("docview" :follow org-docview-open :export 
org-docview-export :store
org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store 
org-bibtex-store-link)
   ("bbdb" :follow org-bbdb-open :export org-bbdb-export 
:complete
org-bbdb-complete-link :store org-bbdb-store-link)
   ("w3m" :store org-w3m-store-link) ("file+sys") 
("file+emacs")
   ("doi" :follow org--open-doi-link)
   ("elisp" :follow org--open-elisp-link)
   ("file" :complete org-file-complete-link)
   ("ftp" :follow (lambda (path) (browse-url (concat "ftp:" 
path
   ("help" :follow org--open-help-link)
   ("http" :follow (lambda (path) (browse-url (concat 
"http:" path
   ("https" :follow (lambda (path) (browse-url (concat 
"https:" path
   ("mailto" :follow (lambda (path) (browse-url (concat 
"mailto:; path
   ("news" :follow (lambda (path) (browse-url (concat 
"news:; path
   ("shell" :follow org--open-shell-link))
 org-confirm-babel-evaluate 'my-org-confirm-babel-evaluate
 )
-- 
--
Vladimir Nikishkin (MiEr, lockywolf)

Re: [O] [PATCH] org-manual: Small fixes

[Kyle Meyer]

Cheong Yiu Fung  writes:

> * doc/org-manual.org (Handling Links): update variable
> `org-id-link-to-org-use-id', which is changed in v7.9.2.

Thanks.  Because this was relevant for the maint branch as well, I
adjusted your commit to apply to maint (tweaking the commit message
slightly).

-- 
Kyle

[O] [PATCH] org-manual: Small fixes

[Cheong Yiu Fung]

* doc/org-manual.org (Handling Links): update variable
`org-id-link-to-org-use-id', which is changed in v7.9.2.
---
 doc/org-manual.org | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 54b89e5bf..c519d310b 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -3173,17 +3173,17 @@ current buffer:
   to the target.  Otherwise it points to the current headline, which
   is also the description[fn:28].
 
-  #+vindex: org-link-to-org-use-id
+  #+vindex: org-id-link-to-org-use-id
   #+cindex: @samp{CUSTOM_ID}, property
   #+cindex: @samp{ID}, property
   If the headline has a =CUSTOM_ID= property, store a link to this
   custom ID.  In addition or alternatively, depending on the value of
-  ~org-link-to-org-use-id~, create and/or use a globally unique =ID=
-  property for the link[fn:29].  So using this command in Org buffers
-  potentially creates two links: a human-readable link from the custom
-  ID, and one that is globally unique and works even if the entry is
-  moved from file to file.  Later, when inserting the link, you need
-  to decide which one to use.
+  ~org-id-link-to-org-use-id~, create and/or use a globally unique
+  =ID= property for the link[fn:29].  So using this command in Org
+  buffers potentially creates two links: a human-readable link from
+  the custom ID, and one that is globally unique and works even if the
+  entry is moved from file to file.  Later, when inserting the link,
+  you need to decide which one to use.
 
 - /Email/News clients: VM, Rmail, Wanderlust, MH-E, Gnus/ ::
 
-- 
2.21.0

Re: [O] [PATCH] org-manual: Fix typo

[Nicolas Goaziou]

Hello,

Sebastian Miele  writes:

> * doc/org-manual.org (Footnotes): Fix typo.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

[O] [PATCH] org-manual: Fix typo

[Sebastian Miele]

* doc/org-manual.org (Footnotes): Fix typo.
---
 doc/org-manual.org | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index cf58f75b4..3c16edc4a 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -21473,7 +21473,7 @@ through ~word-wrap~.
 
 [fn:149] Also see the variable ~org-adapt-indentation~.
 
-[fn:150] Because =LEVEL=2= has 3 stars, =LEVEL=3= has 4 stars, and so
+[fn:150] Because =LEVEL=2= has 3 stars, =LEVEL=3= has 5 stars, and so
 on.
 
 [fn:151] For a server to host files, consider using a WebDAV server,
-- 
2.21.0

Re: [O] [PATCH] org-manual: Minor fixes

[Nicolas Goaziou]

Hello,

Sebastian Miele  writes:

> * doc/org-manual.org (Motion): Fix the names of the four functions
>   bound to C-c C-n, C-c C-p, C-c C-f, and C-c C-b.

Applied. Thank you. I also fixed kindex values.

Regards,

-- 
Nicolas Goaziou

[O] [PATCH] org-manual: Minor fixes

[Sebastian Miele]

* doc/org-manual.org (Motion): Fix the names of the four functions
  bound to C-c C-n, C-c C-p, C-c C-f, and C-c C-b.
---
 doc/org-manual.org | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index b818b4bae..95f35a233 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -612,25 +612,25 @@ invisible edits and process them.
 
 The following commands jump to other headlines in the buffer.
 
-- {{{kbd(C-c C-n)}}} (~outline-next-visible-heading~) ::
+- {{{kbd(C-c C-n)}}} (~org-next-visible-heading~) ::
 
   #+kindex: C-c C-n
   #+findex: outline-next-visible-heading
   Next heading.
 
-- {{{kbd(C-c C-p)}}} (~outline-previous-visible-heading~) ::
+- {{{kbd(C-c C-p)}}} (~org-previous-visible-heading~) ::
 
   #+kindex: C-c C-p
   #+findex: outline-previous-visible-heading
   Previous heading.
 
-- {{{kbd(C-c C-f)}}} (~org-forward-same-level~) ::
+- {{{kbd(C-c C-f)}}} (~org-forward-heading-same-level~) ::
 
   #+kindex: C-c C-f
   #+findex: org-forward-same-level
   Next heading same level.
 
-- {{{kbd(C-c C-b)}}} (~org-backward-same-level~) ::
+- {{{kbd(C-c C-b)}}} (~org-backward-heading-same-level~) ::
 
   #+kindex: C-c C-b
   #+findex: org-backward-same-level
-- 
2.21.0

Re: [O] [PATCH] org-manual: revise markup section intro

[Nicolas Goaziou]

Hello,

Will Pierce  writes:

> This patch revises the markup section's introductory paragraph to read more
> smoothly.

Applied. I added two space after each sentence.
>
> I'll be slowly working the manual!

Great. Thank you.

Regards,

-- 
Nicolas Goaziou

[O] [PATCH] org-manual: revise markup section intro

[Will Pierce]

This patch revises the markup section's introductory paragraph to read more
smoothly.

I'll be slowly working the manual!


0001-org-manual-revise-markup-section-intro.patch
Description: Binary data

Re: [O] [BUG] Org manual without correct org-version

[Nicolas Goaziou]

Vladimir Lomov  writes:

> I thought that for software versions 9.1 < 9.1.9 and means that 9.1
> preceding the 9.1.9.

We are not talking about software version but manual version.

> And first thing that comes to my mind about recent
> changes is a "template" system, there was ' C-,'. The '9.1' version (org from git) has 'Structure Templates' while
> '9.1.9' version (org shipped with Emacs) doesn't have that section.

If you use Org from git master's branch (aka development branch), you
should know that it is, for the time being, akin to Org 9.2-alpha.
There, I suggest to use "org-manual.org" instead of Org info manual,
which is bound to be outdated.

If you use Org from maint branch, there is no such problem: the 9.1
manual is accurate.

> I prefer search for information in most recent docs than in "out-dated"
> (see example with 'Structure Templates' above). So simple check of
> version would help to find out what document is 'fresh' enough.

Again, this has nothing to do with manual version. See above.

Re: [O] [BUG] Org manual without correct org-version

[Vladimir Lomov]

Hello,
** Nicolas Goaziou [2018-04-14 16:43:31 +0200]:

> Vladimir Lomov  writes:
> 
>> Earlier there was "full" "git" version in Manual and I found it convenient
>> (I read the manual from time to time to find how to do something in org)
>> but now when I open Info with Org manual I'm a bit puzzled, it shows
>> version 9.1 while Org from Emacs (I use Emacs from git) shows version
>> 9.1.9 and that confuses me completely, which version is "fresh"?
> 
> Barring typos and rewording, Org 9.1.9 is expected to have the same
> manual as 9.1.0, or 9.1.13. An Org 9.1 manual means it is accurate for
> Org 9.1.9. There is nothing puzzling.

I thought that for software versions 9.1 < 9.1.9 and means that 9.1
preceding the 9.1.9. And first thing that comes to my mind about recent
changes is a "template" system, there was '> I understand that, but on the other hand, when I/someone uses Org from
>> git explicitly it would worth to show the "actual" version in Org Manual
>> (as seen by Info). WDYT?
> 
> If you use Org from git, you know the manual is on par with HEAD. As
> a developer, I don't need to know the "git" version in manual. I'm
> curious: what information are you missing?

I prefer search for information in most recent docs than in "out-dated"
(see example with 'Structure Templates' above). So simple check of
version would help to find out what document is 'fresh' enough.

---
WBR, Vladimir Lomov

-- 
Don't change the reason, just change the excuses!
-- Joe Cointment

Re: [O] [BUG] Org manual without correct org-version

[Nicolas Goaziou]

Vladimir Lomov  writes:

> Earlier there was "full" "git" version in Manual and I found it convenient
> (I read the manual from time to time to find how to do something in org)
> but now when I open Info with Org manual I'm a bit puzzled, it shows
> version 9.1 while Org from Emacs (I use Emacs from git) shows version
> 9.1.9 and that confuses me completely, which version is "fresh"?

Barring typos and rewording, Org 9.1.9 is expected to have the same
manual as 9.1.0, or 9.1.13. An Org 9.1 manual means it is accurate for
Org 9.1.9. There is nothing puzzling.

> I understand that, but on the other hand, when I/someone uses Org from
> git explicitly it would worth to show the "actual" version in Org Manual
> (as seen by Info). WDYT?

If you use Org from git, you know the manual is on par with HEAD. As
a developer, I don't need to know the "git" version in manual. I'm
curious: what information are you missing?

Re: [O] [BUG] Org manual without correct org-version

[Vladimir Lomov]

Hello,
** Nicolas Goaziou [2018-04-13 19:37:09 +0200]:

> Hello,
> 
> Vladimir Lomov  writes:
> 
>> I'm using org-mode from git and found that now it is not show the
>> 'git' version but simply 9.1 in Info file. In doc/ there is
>> 'org-version.inc', it is included into 'orgguide.texi' but not in
>> 'org.texi'.
>>
>> As I understand the 'org.texi' is generated from 'org-manual.org', so
>> 'org-manual.org' should either somehow includes that file or provide
>> other way to get version information.
> 
> Why should it include the exact commit? Manual is for users. I'm not
> sure this has any value.

Earlier there was "full" "git" version in Manual and I found it convenient
(I read the manual from time to time to find how to do something in org)
but now when I open Info with Org manual I'm a bit puzzled, it shows
version 9.1 while Org from Emacs (I use Emacs from git) shows version
9.1.9 and that confuses me completely, which version is "fresh"?

> Actually, "org-manual.org" strips, on purpose, the bugfix number and the
> commit release.

I understand that, but on the other hand, when I/someone uses Org from
git explicitly it would worth to show the "actual" version in Org Manual
(as seen by Info). WDYT?

> Regards,
> 
> -- 
> Nicolas Goaziou

---
WBR, Vladimir Lomov

-- 
After a time, you may find that "having" is not so pleasing a thing,
after all, as "wanting."  It is not logical, but it is often true.
-- Spock, "Amok Time", stardate 3372.7

Re: [O] [BUG] Org manual without correct org-version

[Nicolas Goaziou]

Hello,

Vladimir Lomov  writes:

> I'm using org-mode from git and found that now it is not show the
> 'git' version but simply 9.1 in Info file. In doc/ there is
> 'org-version.inc', it is included into 'orgguide.texi' but not in
> 'org.texi'.
>
> As I understand the 'org.texi' is generated from 'org-manual.org', so
> 'org-manual.org' should either somehow includes that file or provide
> other way to get version information.

Why should it include the exact commit? Manual is for users. I'm not
sure this has any value.

Actually, "org-manual.org" strips, on purpose, the bugfix number and the
commit release.

Regards,

-- 
Nicolas Goaziou

[O] [BUG] Org manual without correct org-version

[Vladimir Lomov]

Hello,
I'm using org-mode from git and found that now it is not show the
'git' version but simply 9.1 in Info file. In doc/ there is
'org-version.inc', it is included into 'orgguide.texi' but not in
'org.texi'.

As I understand the 'org.texi' is generated from 'org-manual.org', so
'org-manual.org' should either somehow includes that file or provide
other way to get version information.

P.S. I'm practially do the following:
1. git clone/"update" to/the local repo;
2. byte-compile the files;
3. make a package (for my distro).

---
WBR, Vladimir Lomov

-- 
Sattinger's Law:
It works better if you plug it in.

Re: [O] [PATCH] org-manual, org.texi: Fix typo in variable name

[Grégoire Jadi]

Nicolas Goaziou  writes:

> Hello,
>
> daim...@omecha.info (Grégoire Jadi) writes:
>
>> Hello,
>>
>> Here is a patch to fix a small typo in the manual.
>
> Applied. Thank you.

Thanks.

>> I haven't followed the recent development of org-mode so I don't know
>> what is the new process regarding the manual. Thus, I patched both the
>> =org-manual.org= and =org.texi=.
>
> For the time being, I suggest to patch "org-manual.org" only. "org.texi"
> will be re-generated from "org.texi" from time to time. You can also
> regenerate it just after modifying "org-manual.org", of course.

Ok.

Thank you.
Best,
> Regards,


signature.asc
Description: PGP signature

Re: [O] [PATCH] org-manual, org.texi: Fix typo in variable name

[Nicolas Goaziou]

Hello,

daim...@omecha.info (Grégoire Jadi) writes:

> Hello,
>
> Here is a patch to fix a small typo in the manual.

Applied. Thank you.

> I haven't followed the recent development of org-mode so I don't know
> what is the new process regarding the manual. Thus, I patched both the
> =org-manual.org= and =org.texi=.

For the time being, I suggest to patch "org-manual.org" only. "org.texi"
will be re-generated from "org.texi" from time to time. You can also
regenerate it just after modifying "org-manual.org", of course.

Regards,

-- 
Nicolas Goaziou

[O] [PATCH] org-manual, org.texi: Fix typo in variable name

[Grégoire Jadi]

Hello,

Here is a patch to fix a small typo in the manual. I haven't followed
the recent development of org-mode so I don't know what is the new
process regarding the manual. Thus, I patched both the =org-manual.org=
and =org.texi=.

From 9f030f2e8e37e4d36245234878435a79677b1511 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gr=C3=A9goire=20Jadi?= 
Date: Thu, 29 Mar 2018 08:29:55 +0200
Subject: [PATCH] org-manual, org.texi: Fix typo in variable name

---
 doc/org-manual.org | 4 ++--
 doc/org.texi   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 35ab95134..61a572084 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -6398,7 +6398,7 @@ prompted about what to do with it.
 
  #+cindex: @samp{CLOCK_MODELINE_TOTAL}, property
  #+cindex: @samp{LAST_REPEAT}, property
- #+vindex: org-clock-modeline-total
+ #+vindex: org-clock-mode-line-total
  #+vindex: org-clock-in-prepare-hook
  While the clock is running, Org shows the current clocking time
  in the mode line, along with the title of the task.  The clock
@@ -21022,7 +21022,7 @@ this to ~org-clock-in-prepare-hook~.
 [fn:73] The last reset of the task is recorded by the =LAST_REPEAT=
 property.
 
-[fn:74] See also the variable ~org-clock-modeline-total~.
+[fn:74] See also the variable ~org-clock-mode-line-total~.
 
 [fn:75] The corresponding in-buffer setting is: =#+STARTUP:
 lognoteclock-out=.
diff --git a/doc/org.texi b/doc/org.texi
index b78a22ef2..190e07fda 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7064,7 +7064,7 @@ clock stopped.
 
 @cindex @samp{CLOCK_MODELINE_TOTAL}, property
 @cindex @samp{LAST_REPEAT}, property
-@vindex org-clock-modeline-total
+@vindex org-clock-mode-line-total
 @vindex org-clock-in-prepare-hook
 While the clock is running, Org shows the current clocking time
 in the mode line, along with the title of the task.  The clock
@@ -7078,7 +7078,7 @@ the @samp{CLOCK_MODELINE_TOTAL} property.  It may have the values
 @samp{current} to show only the current clocking instance, @samp{today} to
 show all time clocked on this tasks today---see also the
 variable @code{org-extend-today-until}, @code{all} to include all time, or
-@code{auto} which is the default@footnote{See also the variable @code{org-clock-modeline-total}.}.  Clicking with
+@code{auto} which is the default@footnote{See also the variable @code{org-clock-mode-line-total}.}.  Clicking with
 @kbd{mouse-1} onto the mode line entry pops up a menu with
 clocking options.
 
-- 
2.16.2



signature.asc
Description: PGP signature

Re: [O] mobil org manual

[TonyMc]

On Sat, 12 Nov 2016 09:33:23 -0800
Matthew Pritchard  wrote:

> Does anyone know were I can get a manual for mobil org?
> 

Look at Appendix B in the org manual and
https://github.com/matburt/mobileorg-android/wiki/Documentation

Best,
Tony

[O] mobil org manual

[Matthew Pritchard]

Does anyone know were I can get a manual for mobil org?

Re: [O] The Org Manual

[Jonathan Leech-Pepin]

Hello,

On 24 September 2015 at 18:01, Rasmus  wrote:

> nascii boy  writes:
>
> > Org advancement manual in org
> >
> > https://github.com/nasciiboy/TheOrgManual
>
> Interesting.  Is this a port of the current org manual?  Does it produce
> good texi code with ox-texi?
>

Looking at it it looks as though it is an exact recreation of the
existing manual (did not verify version).

It includes all the texi-like section menus as manually created
targets.  This will not end up producing the expected out put in
ox-texinfo because those menu entries are dynamically generated in a
TOC-esque manner.  I did not look through to see if the various
indices and other texi-specific features were accounted for or just
hard coded in.

Regards,
Jon


> Thanks,
> Rasmus
>
> --
> Er du tosset for noge' lårt!
>
>
>

Re: [O] The Org Manual

[nascii boy]

org Hello dear community, the manual is a port of texi manually exported to
html, passed org Pandoc and formated by hand. texi okay to make books. but
PDFs and web pages are a nuisance as quick method of consultation (compared
to org).

is my ideal to have only with org books that can be read without further
Emacs and have a nice appearance, efficiency and puts org

the vension manual is an advance, do not understand much English but
have already
begun to introduce the Spanish. at the end I would like to take care of the
version of the manual in org-mode, but I leave the job for someone shares
this vision, to start from scratch ne

-- nasciiboy

# hola querida comunidad org, el manual es un port del manual texi
# exportado a html, pasado a org mediante pandoc y maquetado a
# mano. texi esta bien para hacer libros. pero los pdf's y las paginas
# web son un fastidio como metodo rapido de consulta ( comparados con
# org).
#
# es mi ideal contar con libros solo con org que se puedan leer en Emacs
# sin mas y que tengan una apariencia linda, la eficacia ya la pone org
#
# la vension del manual, es un adelanto, no entiendo mucho ingles pero
# ya he empezado a troducir al español. al terminar me gustaria
# encargarme de la version del manual en org-mode, sin enmbargo dejo el
# trabajo por si alguien comparte esta vision, para que ne empiese de
# cero La función sprintf realiza las mismas conversiones que printf,
# pero almacena la salida en de una cadena:

Re: [O] The Org Manual

[Rasmus]

nascii boy  writes:

> Org advancement manual in org
>
> https://github.com/nasciiboy/TheOrgManual

Interesting.  Is this a port of the current org manual?  Does it produce
good texi code with ox-texi?

Thanks,
Rasmus

-- 
Er du tosset for noge' lårt!

Re: [O] [PATCH] Org manual on :noweb-ref property

[Bastien]

Hi Tomas,

Tomas Grigera tgrig...@gmail.com writes:

 After Eric's fix a couple of days ago, setting :noweb-ref through a
 property now works as explained in the manual. However, the example
 given will only work if one turns on property inheritance. I think it
 is worthwhile noting this in the manual. The patch here adds that
 comment.

Thanks for the patch -- I've committed a slightly different version,
using a footnote.

 First time I send a patch, sorry if I screwd up.

You did right, thanks!

-- 
 Bastien

[O] [PATCH] Org manual on :noweb-ref property

[Tomas Grigera]

Hi

After Eric's fix a couple of days ago, setting :noweb-ref through a
property now works as explained in the manual. However, the example
given will only work if one turns on property inheritance. I think it
is worthwhile noting this in the manual. The patch here adds that
comment.

First time I send a patch, sorry if I screwd up.

Happy new year

Tomas
diff --git a/doc/org.texi b/doc/org.texi
index 3f02efb..618b287 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13627,7 +13627,9 @@ concatenated together to form the replacement text.
 By setting this header argument at the sub-tree or file level, simple code
 block concatenation may be achieved.  For example, when tangling the
 following Org mode file, the bodies of code blocks will be concatenated into
-the resulting pure code file.
+the resulting pure code file (note that this example needs that property
+inheritance be turned on for the @code{noweb-ref} property, see
+@ref{Property inheritance}).
 
 @example
  #+BEGIN_SRC sh :tangle yes :noweb yes :shebang #!/bin/sh

[O] [PATCH] Org manual: Fix double-spaces at the end of sentences

[Julian Gehring]

Org manual: Fix double-spaces at the end of sentences

* doc/org.texi: End sentences with two spaces.
From 19e39b67f4a8dbee3f1015f636fac4f77e59d3c2 Mon Sep 17 00:00:00 2001
From: Julian Gehring julian.gehr...@googlemail.com
Date: Mon, 12 Dec 2011 19:19:20 +0100
Subject: [PATCH] Org manual: Fix double-spaces at the end of sentences

* doc/org.texi: End sentences with two spaces.
---
 doc/org.texi |   36 ++--
 1 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index ff9bb7e..2cbb7d1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6023,7 +6023,7 @@ Insert a dynamic block (@pxref{Dynamic blocks}) containing a clock
 report as an Org-mode table into the current file.  When the cursor is
 at an existing clock table, just update it.  When called with a prefix
 argument, jump to the first clock report in the current document and
-update it.   The clock table always includes also trees with
+update it.  The clock table always includes also trees with
 @code{:ARCHIVE:} tag.
 @orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update}
 Update dynamic block at point.  The cursor needs to be in the
@@ -6642,7 +6642,7 @@ buffer again after capture is completed.
 
 In the template itself, special @kbd{%}-escapes@footnote{If you need one of
 these sequences literally, escape the @kbd{%} with a backslash.}  allow
-dynamic insertion of content. The templates are expanded in the order given here:
+dynamic insertion of content.  The templates are expanded in the order given here:
 
 @smallexample
 %[@var{file}] @r{insert the contents of the file given by @var{file}.}
@@ -10896,7 +10896,7 @@ newly created file.  For additional configuration options
 @pxref{x-overriding-factory-styles,,Overriding factory styles}.
 
 If you would like to choose a style on a per-file basis, you can use the
-@code{#+ODT_STYLES_FILE} option. A typical setting will look like
+@code{#+ODT_STYLES_FILE} option.  A typical setting will look like
 
 @example
 #+ODT_STYLES_FILE: /path/to/example.ott
@@ -10932,7 +10932,7 @@ internal links.  It creates Internet-style links for all other links.
 
 Export of native Org-mode tables (@pxref{Tables}) and simple @file{table.el}
 tables is supported.  However, export of complex @file{table.el} tables -
-tables that have column or row spans - is not supported. Such tables are
+tables that have column or row spans - is not supported.  Such tables are
 stripped from the exported document.
 
 By default, a table is exported with top and bottom frames and with
@@ -10944,7 +10944,7 @@ are interpreted as weighted ratios with the default weight being 1}
 @cindex #+ATTR_ODT
 If you are not satisfied with the default formatting of tables, you can
 create custom table styles and associate them with a table using
-the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} export}.
+the @code{#+ATTR_ODT} line.  @xref{Customizing tables in @acronym{ODT} export}.
 
 @node Images in @acronym{ODT} export, Math formatting in @acronym{ODT} export, Tables in @acronym{ODT} export, OpenDocument Text export
 @subsection Images in @acronym{ODT} export
@@ -11171,11 +11171,11 @@ that would be of interest to power users.
 @cindex doc, docx
 
 The @acronym{ODT} exporter adds support for exporting Org outlines to formats
-that are not supported natively by Org. It also adds support to convert
+that are not supported natively by Org.  It also adds support to convert
 document from one format to another.  To use these features, you need to
 configure a command-line converter.  Once a command-line converter is
 configured you can use it to extend the list of formats to which Org can
-export. @xref{x-export-to-other-formats,,Automatically exporting to other
+export.  @xref{x-export-to-other-formats,,Automatically exporting to other
 formats}.  You can also use it to perform one-off document conversion as
 detailed below.
 
@@ -11186,7 +11186,7 @@ detailed below.
 Convert an existing document from one format to another as determined by the
 variable @code{org-export-odt-convert-capabilities}
 (@pxref{x-odt-converter-capabilities,,Configure converter
-capabilities}). @strong{Please note} that you can use this command to even
+capabilities}).  @strong{Please note} that you can use this command to even
 convert documents that are produced outside of Org and in other formats than
 @acronym{ODT} format.
 @end table
@@ -11209,7 +11209,7 @@ distribution.
 
 @vindex org-odt-data-dir
 This converter is distributed as a LibreOffice extension and can be found in
-your Org distribution. See the subdirectory pointed to by the variable
+your Org distribution.  See the subdirectory pointed to by the variable
 @code{org-odt-data-dir}.
 
 @end enumerate
@@ -11360,11 +11360,11 @@ file.  The use of this feature is better illustrated with couple of examples.
 @item Embedding ODT tags as part of regular text
 
 You can include simple OpenDocument tags by prefixing them with
-@samp{@@}. 

[O] [Accepted] Org manual: Fix double-spaces at the end of sentences

[Bastien Guerry]

Patch 1069 (http://patchwork.newartisans.com/patch/1069/) is now Accepted.

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3Cjc5h3b%242jq%241%40dough.gmane.org%3E

Here is the original message containing the patch:

 Content-Type: text/plain; charset=utf-8
 MIME-Version: 1.0
 Content-Transfer-Encoding: 7bit
 Subject: [O] Org manual: Fix double-spaces at the end of sentences
 Date: Mon, 12 Dec 2011 23:27:55 -
 From: Julian Gehring julian.gehr...@googlemail.com
 X-Patchwork-Id: 1069
 Message-Id: jc5h3b$2jq$1...@dough.gmane.org
 To: emacs-orgmode@gnu.org
 
 Org manual: Fix double-spaces at the end of sentences
 
 * doc/org.texi: End sentences with two spaces.
 
 
 From 19e39b67f4a8dbee3f1015f636fac4f77e59d3c2 Mon Sep 17 00:00:00 2001
 From: Julian Gehring julian.gehr...@googlemail.com
 Date: Mon, 12 Dec 2011 19:19:20 +0100
 Subject: [PATCH] Org manual: Fix double-spaces at the end of sentences
 
 * doc/org.texi: End sentences with two spaces.
 ---
  doc/org.texi |   36 ++--
  1 files changed, 18 insertions(+), 18 deletions(-)
 
 diff --git a/doc/org.texi b/doc/org.texi
 index ff9bb7e..2cbb7d1 100644
 --- a/doc/org.texi
 +++ b/doc/org.texi
 @@ -6023,7 +6023,7 @@ Insert a dynamic block (@pxref{Dynamic blocks}) 
 containing a clock
  report as an Org-mode table into the current file.  When the cursor is
  at an existing clock table, just update it.  When called with a prefix
  argument, jump to the first clock report in the current document and
 -update it.   The clock table always includes also trees with
 +update it.  The clock table always includes also trees with
  @code{:ARCHIVE:} tag.
  @orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update}
  Update dynamic block at point.  The cursor needs to be in the
 @@ -6642,7 +6642,7 @@ buffer again after capture is completed.
  
  In the template itself, special @kbd{%}-escapes@footnote{If you need one of
  these sequences literally, escape the @kbd{%} with a backslash.}  allow
 -dynamic insertion of content. The templates are expanded in the order given 
 here:
 +dynamic insertion of content.  The templates are expanded in the order given 
 here:
  
  @smallexample
  %[@var{file}] @r{insert the contents of the file given by @var{file}.}
 @@ -10896,7 +10896,7 @@ newly created file.  For additional configuration 
 options
  @pxref{x-overriding-factory-styles,,Overriding factory styles}.
  
  If you would like to choose a style on a per-file basis, you can use the
 -@code{#+ODT_STYLES_FILE} option. A typical setting will look like
 +@code{#+ODT_STYLES_FILE} option.  A typical setting will look like
  
  @example
  #+ODT_STYLES_FILE: /path/to/example.ott
 @@ -10932,7 +10932,7 @@ internal links.  It creates Internet-style links for 
 all other links.
  
  Export of native Org-mode tables (@pxref{Tables}) and simple @file{table.el}
  tables is supported.  However, export of complex @file{table.el} tables -
 -tables that have column or row spans - is not supported. Such tables are
 +tables that have column or row spans - is not supported.  Such tables are
  stripped from the exported document.
  
  By default, a table is exported with top and bottom frames and with
 @@ -10944,7 +10944,7 @@ are interpreted as weighted ratios with the default 
 weight being 1}
  @cindex #+ATTR_ODT
  If you are not satisfied with the default formatting of tables, you can
  create custom table styles and associate them with a table using
 -the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} 
 export}.
 +the @code{#+ATTR_ODT} line.  @xref{Customizing tables in @acronym{ODT} 
 export}.
  
  @node Images in @acronym{ODT} export, Math formatting in @acronym{ODT} 
 export, Tables in @acronym{ODT} export, OpenDocument Text export
  @subsection Images in @acronym{ODT} export
 @@ -11171,11 +11171,11 @@ that would be of interest to power users.
  @cindex doc, docx
  
  The @acronym{ODT} exporter adds support for exporting Org outlines to formats
 -that are not supported natively by Org. It also adds support to convert
 +that are not supported natively by Org.  It also adds support to convert
  document from one format to another.  To use these features, you need to
  configure a command-line converter.  Once a command-line converter is
  configured you can use it to extend the list of formats to which Org can
 -export. @xref{x-export-to-other-formats,,Automatically exporting to other
 +export.  @xref{x-export-to-other-formats,,Automatically exporting to other
  formats}.  You can also use it to perform one-off document conversion as
  detailed below.
  
 @@ -11186,7 +11186,7 @@ detailed below.
  Convert an existing document from one format to another as determined by the
  variable @code{org-export-odt-convert-capabilities}
  (@pxref{x-odt-converter-capabilities,,Configure converter
 -capabilities}). @strong{Please note} that you can use this command to even
 +capabilities}).  @strong{Please note