Re: [O] DEADLINE: position in entry

2016-11-10 Thread Alan Tyree
On 11 November 2016 at 11:12, Nicolas Goaziou 
wrote:

> Alan Tyree  writes:
>
> > Will you please double check this? On my system, the entry does *not*
> show
> > up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show
> > up. So, for the important purpose under discussion, the timestamp is
> > ignored.
>
> You are right, the timestamp was ignored, but that's a bug. I fixed it.
> Thank you.
>
> Regards,
>

Glad it is all cleared up. Thanks for a great piece of software!
Alan

-- 
Alan L Tyreehttp://austlii.edu.au/~alan

Tel:  04 2748 6206sip:typh...@iptel.org


Re: [O] DEADLINE: position in entry

2016-11-10 Thread Nicolas Goaziou
Alan Tyree  writes:

> Will you please double check this? On my system, the entry does *not* show
> up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show
> up. So, for the important purpose under discussion, the timestamp is
> ignored.

You are right, the timestamp was ignored, but that's a bug. I fixed it.
Thank you.

Regards,



Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

2016-11-10 Thread Nicolas Goaziou
Hello,

Frederick Giasson  writes:

> No, what are the FSF papers?

See . Since the
patches no longer apply as tiny changes, we need these papers signed to
move forward.

Regards,

-- 
Nicolas Goaziou



Re: [O] Pubishing to a website generates tons of buffers

2016-11-10 Thread Nicolas Goaziou
Hello,

Éric Würbel  writes:

> All was working very well until I switched to orgmode 9.0
> yesterday. Since this update, org opens a buffer for each file in the
> site structure during publishing process, even if the publishing
> function is org-publish-attachment.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] helm-org-clock for using helm rather than orgmode select menu

2016-11-10 Thread cesar mena
"Tory S. Anderson"  writes:

> Are you sure? In my org 9.0 box, I still see a non-helm 
> "org-agenda" menu (one of the things I haven't gotten around to 
> helm-ifying yet). 

sorry, i mis-understood. this is only for things that use the
completion-read interface.


[...]




Re: [O] helm-org-clock for using helm rather than orgmode select menu

2016-11-10 Thread Tory S. Anderson
Are you sure? In my org 9.0 box, I still see a non-helm 
"org-agenda" menu (one of the things I haven't gotten around to 
helm-ifying yet). 


cesar mena  writes:


"Tory S. Anderson"  writes:

I've made the following adjustment to org-clock-select-task 
that 
allows you to (optionally) use helm to select, rather than 
orgmode's built in screens. Eventually I'd like to see all 
orgmode 
commands have the option of using helm rather than their custom 
screens, as Helm is a great package. Until then, hopefully you 
can 
find this useful or give useful suggestions.


https://github.com/WorldsEndless/helm-org-clock


from the 9.0 changelog it looks like this was done?

 Remove all options related to ido or iswitchb

 This includes org-completion-use-iswitchb and
 org-completion-use-ido. Instead Org uses regular functions, 
 e.g.,

 completion-read so as to let those libraries operate.

best,
- cm




Re: [O] helm-org-clock for using helm rather than orgmode select menu

2016-11-10 Thread cesar mena
"Tory S. Anderson"  writes:

> I've made the following adjustment to org-clock-select-task that 
> allows you to (optionally) use helm to select, rather than 
> orgmode's built in screens. Eventually I'd like to see all orgmode 
> commands have the option of using helm rather than their custom 
> screens, as Helm is a great package. Until then, hopefully you can 
> find this useful or give useful suggestions.
>
> https://github.com/WorldsEndless/helm-org-clock

from the 9.0 changelog it looks like this was done?

 Remove all options related to ido or iswitchb

 This includes org-completion-use-iswitchb and
 org-completion-use-ido. Instead Org uses regular functions, e.g.,
 completion-read so as to let those libraries operate.

best,
- cm




Re: [O] DEADLINE: position in entry

2016-11-10 Thread Alan Tyree
On 11 November 2016 at 02:08, Nicolas Goaziou 
wrote:

> Hello,
>
> Alan Tyree  writes:
>
> > Suggested wording:
> >
> > In 8.1:
> >
> >
> > timestamp can appear anywhere in the headline or body of an Org tree
> > entr UNLESS is is preceded by a keyword in which case it must be properly
> > positioned or it will be ignored: see 8.3 for details.
>
> This is wrong. Only the keyword is ignored, not the timestamp. This is
> why DEADLINE and SCHEDULED location is unrelated to section 8.1.
>

Hi Nicolas,
Will you please double check this? On my system, the entry does *not* show
up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show
up. So, for the important purpose under discussion, the timestamp is
ignored.

Emacs version 24.4.1 on Debian Stable

org-version: Org mode version 9.0 (9.0-elpaplus @
/home/alant/.emacs.d/elpa/org-plus-contrib-20161102/)




>
> > A timestamp may be preceded by special keywords to facilitate planning.
> > WARNING: both the timestamp and the keyword are ignored if not positioned
> > immediately following the headline. No space or other text is allowed.
>
> I think "immediately following the headline" is unambiguous. No need to
> specify "no space or other text is allowed".
>
> I modified section 8.3 accordingly.
>
> WDYT?
>
> Subject to the above, OK. Just so long as there is a good strong warning
about it.

Thanks,
Alan

Regards,
>
> --
> Nicolas Goaziou
>



-- 
Alan L Tyreehttp://austlii.edu.au/~alan

Tel:  04 2748 6206sip:typh...@iptel.org


Re: [O] Bug: Repeated tasks not shown from org-timeline [9.0 (9.0-dist @ c:/wlin/.emacs-lisp/org/lisp/)]

2016-11-10 Thread Nick Dokos
Nicolas Goaziou  writes:

> Hello,
>
> Nick Dokos  writes:
>
>> Found it:
>>
>> https://www.mail-archive.com/emacs-orgmode@gnu.org/msg39801.html
>
> Next question is: is there any need to keep timeline or could we
> deprecate it in, e.g., Org 9.1?
>

I don't use timeline, so I'm not the best person to answer it, but that
question has been hanging out there for 5+ years: unless somebody
speaks up with a compelling reason to keep it, I'd say get rid of it.

-- 
Nick




Re: [O] [bug] timed repeater shows up in wrong place

2016-11-10 Thread Samuel Wales
On 11/10/16, cesar mena  wrote:
> so the only thing i noticed is that your test case did not set
> org-agenda-files for me. specifically your regexp did not pick up the
> file (filename is test.org). i changed it as below, and it worked.

thanks.

i have documented my testcase for future purposes to be clear about this.

i did find one thing:

org-agenda-repeating-timestamp-show-all has changed its
meaning in org 9.

when nil
  my version of org 8 (and previous versions of org) will show the
task in the grid
  org 9 will not show the task in the grid

note that this is when nil.

is anything known about this change?

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.
  UPDATE 2016-10: home, but not fully free



Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

2016-11-10 Thread Frederick Giasson

Hi Nicolas,


I noticed that you included some of my previous fixes in
Org-babel-clojure, so here are the latest work I did. I updated it to
work with the latest code on Git. I did two things with these fixes:


   (1) I better handle any possible error or exceptions that may be
raised by nREPL by displaying any errors in the RESULTS section

   (2) I added a new header option called ":show-process" which create
a new window/buffer to display anything that is outputted by the
Clojure code in the code block.


In the past, I did refer to this as ":async", but as we discussed at
that time, it really was not async. So I changed the naming of this
new feature to remove this ambiguity.

OK.


In any case, I did update the worg documentation accordingly too.

Finally I updated ORG-NEWS in the 9.1 section.

I think you can merge patch 2 and 3. ORG-NEWS updates usually do not
require their own


See the patch files attached to this email.

Thank you. Some nit-picks follow.


Subject: [PATCH 1/2] Better error handling with nREPL. Displaying any possible
  errors or exceptions in the result block. Adding a new :show-process header
  option such that the underlying process of a Clojure block code get output in
  a new buffer and a new window such that the developer can see what is going
  on.

Could you provide a proper commit message? In particular, each modified
function has to be specified there.

  (defun org-babel-execute:clojure (body params)
-  "Execute a block of Clojure code with Babel."
+  "Execute a block of Clojure code with Babel. The underlying process 
performed by the

"The underlying..." has to go on the line below.


+  code block can be output using the :show-process parameter"
(let ((expanded (org-babel-expand-body:clojure body params))
-   result)
+(sbuffer "*Clojure Show Process Sub Buffer*")
+(show (if (assoc :show-process params) t nil))

   (show (assq :show-process params))


+(response (cons 'dict nil))

   (response (list 'dict))


+status
+result)
+ ; Check if the user want show the process in an output buffer/window

Need ";;" instead of ";". Also, full stop missing at the end.


+ (when show
+   ; Create a new window with the show output buffer

   ;; Create output buffer.


+   (switch-to-buffer-other-window sbuffer)
+
+   ; Run the Clojure code in nREPL

Ditto.


+   (nrepl-request:eval
+expanded
+(lambda (resp)
+  (when (member "out" resp)
+; Print the output of the nREPL in the output buffer

Ditto.


+(princ (nrepl-dict-get resp "out") (get-buffer sbuffer)))
+  (when (member "ex" resp)
+; In case there is an exception, then add it to the output 
buffer as well

Ditto.


+(princ (nrepl-dict-get resp "ex") (get-buffer sbuffer))
+(princ (nrepl-dict-get resp "root-ex") (get-buffer sbuffer)))
+  (when (member "err" resp)
+; In case there is an error, then add it to the output buffer 
as well

Ditto.


+(princ (nrepl-dict-get resp "err") (get-buffer sbuffer)))
+  (nrepl--merge response resp)
+  ; Update the status of the nREPL output session

Ditto.

+  (setq status (nrepl-dict-get response "status")))
+(cider-current-connection)
+(cider-current-session))
+
+   ; Wait until the nREPL code finished to be processed

Ditto.


+   (while (not (member "done" status))
+ (nrepl-dict-put response "status" (remove "need-input" status))
+ (accept-process-output nil 0.01)
+ (redisplay))
+
+   ; Delete the show buffer & window when the processing is finalized

Ditto.


+   (let ((wins (get-buffer-window-list sbuffer nil t)))
+ (dolist (win wins)
+   (delete-window win))
+ (kill-buffer sbuffer))

   (mapc #'delete-window (get-buffer-window-list sbuffer nil t))
   (kill-buffer sbuffer)


+
+   ; Put the output or the value in the result section of the code 
block

See above.


+   (setq result (concat (nrepl-dict-get response
+(if (or (member "output" 
result-params)
+(member "pp" 
result-params))
+"out"
+  "value"))
+(nrepl-dict-get response "ex")
+(nrepl-dict-get response "root-ex")
+(nrepl-dict-get response "err"
+ ; Check if user want to run code without showing the process

Ditto.


+ (when (not show)

   (unless show ...)


Ok good, will fix these issues and resend the patch.


BTW, did you sign FSF papers already? I cannot find any 

Re: [O] latex exporting to different directory with v9.0

2016-11-10 Thread Alex Fenton

Hello,

On 08/11/16 18:49, Nicolas Goaziou wrote:

Per above, you could use latexmk "-C" option and move both ".tex" and
".pdf" file to appropriate directories.


I wasn't aware of the "-C" option, it looks like it could - with some 
settings - blow away the intermediate files that latexmk uses to 
minimise compile passes.



This breaks the export process, because `org-compile-file' can no longer
find, and return, the produced file. `org-compile-file' has to know
where the output is.


Ah, OK. I'm curious, however, how a compiler (eg tex2dvi) cd'd to a 
different working directory can ever resolve links to image files.




One problem is that we already provide compilation commands that do not
set it (e.g., the "texi2dvi" command above). As I wrote, if we leave
default-directory alone, something else has to be fixed.

In any case, I removed default-directory setting and, hopefully, applied
the necessary changes to commands.


I'm very grateful for your help with this and for trying this 
change/reversion. I'll try it with the next release.


Best,
alex



[O] helm-org-clock for using helm rather than orgmode select menu

2016-11-10 Thread Tory S. Anderson
I've made the following adjustment to org-clock-select-task that 
allows you to (optionally) use helm to select, rather than 
orgmode's built in screens. Eventually I'd like to see all orgmode 
commands have the option of using helm rather than their custom 
screens, as Helm is a great package. Until then, hopefully you can 
find this useful or give useful suggestions.


https://github.com/WorldsEndless/helm-org-clock



[O] Specifing an agenda org-class time without hours in headline

2016-11-10 Thread Tory S. Anderson
The documentation [1] says that hour times can be specified on a 
recurring object with a given syntax, but I have never been able 
to make it work. Is the documentation wrong? I try:


--8<---cut here---start->8---
** [#A] 17:30 Parent Time
  <%%(org-class 2016 2 7 2016 12 31 4)> 5:30pm-8:30pm Parent Time
--8<---cut here---end--->8---

but if I remove the 17:30 from the title, it receives no time at 
all. Any help? 



Footnotes: 
[1]  http://orgmode.org/worg/org-faq.html#org-class





[O] Pubishing to a website generates tons of buffers

2016-11-10 Thread Éric Würbel
Hello list,

I developped my own website generator which relies on the publishing
functions of orgmode.

In the structure of my website, some directories contain only non-org
files (like css, fonts, images, etc...), so, for these dirs, i use
org-publish-attachment as the publishing function.

All was working very well until I switched to orgmode 9.0
yesterday. Since this update, org opens a buffer for each file in the
site structure during publishing process, even if the publishing
function is org-publish-attachment.

This bloats the buffer list and loads emacs with tons of unwanted
buffers.

Does anyone have any idea on what's going on, or has faced a similar
problem ?

Eric
-- 
Éric Würbel
http://eric.wurbel.perso.luminy.univ-amu.fr/
Enseignement: IUT R, directeur des études 1A
Recherche: LSIS, UMR7296 http://www.lsis.org/



Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

2016-11-10 Thread Nicolas Goaziou
Hello,

Frederick Giasson  writes:

> I noticed that you included some of my previous fixes in
> Org-babel-clojure, so here are the latest work I did. I updated it to
> work with the latest code on Git. I did two things with these fixes:
>
>
>   (1) I better handle any possible error or exceptions that may be
> raised by nREPL by displaying any errors in the RESULTS section
>
>   (2) I added a new header option called ":show-process" which create
> a new window/buffer to display anything that is outputted by the
> Clojure code in the code block.
>
>
> In the past, I did refer to this as ":async", but as we discussed at
> that time, it really was not async. So I changed the naming of this
> new feature to remove this ambiguity.

OK.

> In any case, I did update the worg documentation accordingly too.
>
> Finally I updated ORG-NEWS in the 9.1 section.

I think you can merge patch 2 and 3. ORG-NEWS updates usually do not
require their own

> See the patch files attached to this email.

Thank you. Some nit-picks follow.

> Subject: [PATCH 1/2] Better error handling with nREPL. Displaying any possible
>  errors or exceptions in the result block. Adding a new :show-process header
>  option such that the underlying process of a Clojure block code get output in
>  a new buffer and a new window such that the developer can see what is going
>  on.

Could you provide a proper commit message? In particular, each modified
function has to be specified there.
>  (defun org-babel-execute:clojure (body params)
> -  "Execute a block of Clojure code with Babel."
> +  "Execute a block of Clojure code with Babel. The underlying process 
> performed by the

"The underlying..." has to go on the line below.

> +  code block can be output using the :show-process parameter"
>(let ((expanded (org-babel-expand-body:clojure body params))
> - result)
> +(sbuffer "*Clojure Show Process Sub Buffer*")
> +(show (if (assoc :show-process params) t nil))

  (show (assq :show-process params))

> +(response (cons 'dict nil))

  (response (list 'dict))

> +status
> +result)
> + ; Check if the user want show the process in an output buffer/window

Need ";;" instead of ";". Also, full stop missing at the end.

> + (when show
> +   ; Create a new window with the show output buffer

  ;; Create output buffer.

> +   (switch-to-buffer-other-window sbuffer)
> +
> +   ; Run the Clojure code in nREPL

Ditto.

> +   (nrepl-request:eval
> +expanded 
> +(lambda (resp) 
> +  (when (member "out" resp)
> +; Print the output of the nREPL in the output buffer

Ditto.

> +(princ (nrepl-dict-get resp "out") (get-buffer sbuffer)))
> +  (when (member "ex" resp)
> +; In case there is an exception, then add it to the output 
> buffer as well

Ditto.

> +(princ (nrepl-dict-get resp "ex") (get-buffer sbuffer))
> +(princ (nrepl-dict-get resp "root-ex") (get-buffer sbuffer)))
> +  (when (member "err" resp)
> +; In case there is an error, then add it to the output 
> buffer as well

Ditto.

> +(princ (nrepl-dict-get resp "err") (get-buffer sbuffer)))
> +  (nrepl--merge response resp)
> +  ; Update the status of the nREPL output session

Ditto.
> +  (setq status (nrepl-dict-get response "status")))
> +(cider-current-connection) 
> +(cider-current-session))
> +   
> +   ; Wait until the nREPL code finished to be processed

Ditto.

> +   (while (not (member "done" status))
> + (nrepl-dict-put response "status" (remove "need-input" status))
> + (accept-process-output nil 0.01)
> + (redisplay))
> +
> +   ; Delete the show buffer & window when the processing is finalized

Ditto.

> +   (let ((wins (get-buffer-window-list sbuffer nil t)))
> + (dolist (win wins)
> +   (delete-window win))
> + (kill-buffer sbuffer))

  (mapc #'delete-window (get-buffer-window-list sbuffer nil t))
  (kill-buffer sbuffer)

> +
> +   ; Put the output or the value in the result section of the code 
> block

See above.

> +   (setq result (concat (nrepl-dict-get response 
> +(if (or (member "output" 
> result-params)
> +(member "pp" 
> result-params))
> +"out"
> +  "value"))
> +(nrepl-dict-get response "ex")
> +(nrepl-dict-get response "root-ex")
> +(nrepl-dict-get response "err"
> + ; Check if user want to run code without 

Re: [O] Bug: Broken TODO keywords highlighting after unbalanced quotes/parens [8.3.6 (8.3.6-7-g4d7d52-elpa @ /home/martin/.spacemacs.home/.emacs.d/elpa/org-20161017/)]

2016-11-10 Thread Nicolas Goaziou
Hello,

Martin Kampas  writes:

> With the minimal example pasted below, the second TODO keyword gets 
> highlighted with a noticeably lighter red color than the first one. In my big 
> org file it made a full rainbow with the other TODO keywords, making it 
> completely unusable. Note that only the length of the padding is significant, 
> not the characters used.
>
>  test.org begin 
> rrr
> rrr
> rrr
> rrr
> rrr
> rr
>
> * TODO foo
>   : "rrr 'rrr (rrr 'rrr)'
>
> * TODO baz
> - test.org end -

FWIW, I cannot reproduce it. You may want to try out Org latest release
and a minimal configuration.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: Repeated tasks not shown from org-timeline [9.0 (9.0-dist @ c:/wlin/.emacs-lisp/org/lisp/)]

2016-11-10 Thread Nicolas Goaziou
Hello,

Nick Dokos  writes:

> Found it:
>
> https://www.mail-archive.com/emacs-orgmode@gnu.org/msg39801.html

Next question is: is there any need to keep timeline or could we
deprecate it in, e.g., Org 9.1?

Regards,

-- 
Nicolas Goaziou



Re: [O] DEADLINE: position in entry

2016-11-10 Thread Nicolas Goaziou
Hello,

Alan Tyree  writes:

> Suggested wording:
>
> In 8.1:
>
>
> timestamp can appear anywhere in the headline or body of an Org tree
> entr UNLESS is is preceded by a keyword in which case it must be properly
> positioned or it will be ignored: see 8.3 for details.

This is wrong. Only the keyword is ignored, not the timestamp. This is
why DEADLINE and SCHEDULED location is unrelated to section 8.1.

> A timestamp may be preceded by special keywords to facilitate planning.
> WARNING: both the timestamp and the keyword are ignored if not positioned
> immediately following the headline. No space or other text is allowed.

I think "immediately following the headline" is unambiguous. No need to
specify "no space or other text is allowed".

I modified section 8.3 accordingly.

WDYT?

Regards,

-- 
Nicolas Goaziou



Re: [O] Obsolete org contrib package

2016-11-10 Thread Nicolas Goaziou
Hello,

Joost Kremers  writes:

> Like I said, I'd be happy to take over maintainance. Just let me know
> how to go about making it available to org-contrib. (If there is a way
> to keep the file in the main Ebib repository, that would be my
> preference.)

We don't need to make it available to Org contrib. Let me know when your
version of org-ebib.el is available to Org users (e.g., through ELPA)
and I'll remove it from contrib/ directory.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-contacts bug when completing tags in gnus

2016-11-10 Thread Alan Schmitt
On 2016-11-09 06:35, tory_ander...@byu.edu (Tory S. Anderson) writes:

> Yeah, I dodge around these sort of problems a lot with org-contacts. It is in
> need of a curator and probably a rewritten version; it also doesn't play nice
> with Helm. I haven't tried it with org 9.0 yet, though. 

I've tracked down the issue to a different behavior in completion
between the default one and helm/ivy approaches:
https://lists.gnu.org/archive/html/emacs-devel/2016-11/msg00269.html

Unfortunately I don't really know how to fix it.

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2016-10: 401.57, 2015-10: 398.29


signature.asc
Description: PGP signature


[O] Bug: Export (to latex) ignores :exports keyword in Org 9.0 [9.0 (9.0-elpa @ /Users/rodrigobelo/.emacs.d/elpa/org-20161102/)]

2016-11-10 Thread Rodrigo Belo

Hi, I believe the export function in  Org mode 9.0 is ignoring the
:exports variable.

Here's an example org-file:



* Test

How much is 3 + 4? 

#+BEGIN_SRC R :exports results
3 + 4
#+END_SRC

#+RESULTS:
: 7

---

This produces a pdf (or html) with the 3+4 snippet, which I believe is
not the intended output

Am I missing anything?

Thanks,

Rodrigo

Emacs  : GNU Emacs 25.1.1 (x86_64-apple-darwin15.5.0, NS appkit-1404.47 Version 
10.11.5 (Build 15F34))
of 2016-11-06
Package: Org mode version 9.0 (9.0-elpa @ 
/Users/rodrigobelo/.emacs.d/elpa/org-20161102/)

current state:
==
(setq
org-id-locations-file "/Users/rodrigobelo/.emacs.d/.cache/.org-id-locations"
org-export-babel-evaluate nil
org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
org-latex-classes '(("beamer" "\\documentclass[presentation]{beamer}" 
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("article" "\\documentclass[11pt]{article}" 
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
  ("\\paragraph{%s}" . "\\paragraph*{%s}") 
("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
 ("report" "\\documentclass[11pt]{report}" ("\\part{%s}" . 
"\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}") ("\\section{%s}" . 
"\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("book" "\\documentclass[11pt]{book}" ("\\part{%s}" . 
"\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}") ("\\section{%s}" . 
"\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 )
org-clock-persist-file "/Users/rodrigobelo/.emacs.d/.cache/org-clock-save.el"
org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
org-occur-hook '(org-first-headline-recenter)
org-imenu-depth 8
org-metaup-hook '(org-babel-load-in-session-maybe)
org-html-format-drawer-function '(closure
   (htmlize-buffer-places 
org-html-format-table-no-css htmlize-css-name-prefix
htmlize-output-type htmlize-output-type 
htmlize-css-name-prefix t)
   (_name contents) contents)
org-log-done 'time
org-src-window-setup 'current-window
org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
org-confirm-shell-link-function 'yes-or-no-p
org-image-actual-width nil
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-link-translation-function 'toc-org-unhrefify
org-present-mode-hook '(spacemacs//org-present-start)
org-agenda-restore-windows-after-quit t
org-latex-format-headline-function 'org-latex-format-headline-default-function
org-default-notes-file "~/org/notes.org"
org-startup-indented t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-latex-format-drawer-function '(closure (t) (_ contents) contents)
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '(org-display-inline-images
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-show-block-all append local] 5]
 (closure
  (org-bracket-link-regexp org-src-window-setup *this* 
org-babel-confirm-evaluate-answer-no
   org-src-preserve-indentation org-src-lang-modes 
org-edit-src-content-indentation
   org-babel-library-of-babel t)
  nil
  (add-hook (quote change-major-mode-hook) (quote 
org-babel-show-result-all) (quote append) (quote local))
  )
 org-babel-result-hide-spec org-babel-hide-all-hashes 
spacemacs/load-yasnippet toc-org-enable
 org-download-enable org-bullets-mode 
spacemacs//org-babel-do-load-languages flyspell-mode
 spacemacs/add-org-surrounds evil-org-mode org-eldoc-load 
spacemacs//init-company-org-mode company-mode)
org-archive-hook '(org-attach-archive-delete-maybe)
org-ascii-format-drawer-function '(closure (t) (_name contents _width) contents)
org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
org-publish-timestamp-directory 
"/Users/rodrigobelo/.emacs.d/.cache/.org-timestamps/"

Re: [O] Obsolete org contrib package

2016-11-10 Thread daimrod
On 11/10/16 10:50, Joost Kremers wrote:
> 
> On Tue, Nov 08 2016, Joost Kremers wrote:
>> Hi,
>>
>> On Tue, Nov 08 2016, Nicolas Goaziou wrote:
>>> So you mean there is no equivalent to both
>>>
>>>   (ebib-cur-entry-key)
>>
>> This one was what I was worried about, but on second thought, it
>> should be possible to simply use:
>>
>> (ebib--get-key-at-point)
>>
>>> and
>>>
>>>   (ebib-db-get-field-value 'title key ebib-cur-db)
>>
>> That one's easier:
>>(ebib-db-get-field-value "title" key ebib--cur-db)
>>
>>> "org-ebib.el" is already compatible with Org 9.0.
>>
>> Ah, good, I didn't realise that.
>>
>>> I'm Cc'ing the author. Ideally this library should be updated to new
>>> Ebib and moved to some ELPA.
>>>
>>> If Grégoire doesn't want to take care of it and no one volunteers to
>>> maintain that file, we can remove it.
>>
>> I was actually planning to add this functionality to Ebib itself. So
>> if Grégoire isn't interested in it anymore, I could put it in the Ebib
>> repo, or create a separate repo for it, either on Github or somewhere
>> else, wherever you prefer.
> 
> I received the following reply from Grégoire (which, although it was
> sent to the mailing list as well, apparently didn't show up there):
> 
> 
> ==
> 
> On 11/08/16 13:23, Nicolas Goaziou wrote:
>> I'm Cc'ing the author. Ideally this library should be updated to new
>> Ebib and moved to some ELPA.
>>
>> If Grégoire doesn't want to take care of it and no one volunteers to
>> maintain that file, we can remove it.
> 
> I don't use this package anymore.
> If anyone uses it, s/he take over it, otherwise we can just remove it
> from org-contrib.
> 
> ==
> 
> Like I said, I'd be happy to take over maintainance. Just let me know
> how to go about making it available to org-contrib. (If there is a way
> to keep the file in the main Ebib repository, that would be my preference.)

IMHO it's best if you can maintain org-ebib as part of ebib itself.
We can remove org-ebib from contrib and you can add it to ebib.

Best,

> Best,
> 
> Joost
> 
> 
> 
> 



Re: [O] Obsolete org contrib package

2016-11-10 Thread daimrod


On 11/08/16 13:23, Nicolas Goaziou wrote:
> Hello,
> 
> Joost Kremers  writes:
> 
>> I just ran into org-ebib.el, a file that's part of org-contrib.
>> I noticed that it uses functions from Ebib that were renamed pretty
>> much exactly two years ago. (They're internal functions and thus got
>> an extra dash.) This could in principle be fixed by changing the
>> relevant function calls in org-ebib.el, but as it happens I'm about to
>> push some changes to Ebib that will make it less straightorward to fix
>> org-ebib.el.
> 
> OK.
> 
> So you mean there is no equivalent to both
> 
>   (ebib-cur-entry-key)
> 
> and
> 
>   (ebib-db-get-field-value 'title key ebib-cur-db)
> 
> ?
> 
>> So perhaps it would be best to simply remove org-ebib.el from
>> org-contrib? It doesn't seem to have been used by anyone the past two
>> years and all it does is define a function to store an org link to an
>> Ebib entry, which, IIUC, is done in a completely different way in Org
>> 9.0.
> 
> "org-ebib.el" is already compatible with Org 9.0.
> 
> I'm Cc'ing the author. Ideally this library should be updated to new
> Ebib and moved to some ELPA.
> 
> If Grégoire doesn't want to take care of it and no one volunteers to
> maintain that file, we can remove it.

I don't use this package anymore.
If anyone uses it, s/he take over it, otherwise we can just remove it
from org-contrib.

Best,

> 
> We should at least wait for a week in any case.
> 
> Regards,
> 



signature.asc
Description: OpenPGP digital signature


[O] Bug: Broken TODO keywords highlighting after unbalanced quotes/parens [8.3.6 (8.3.6-7-g4d7d52-elpa @ /home/martin/.spacemacs.home/.emacs.d/elpa/org-20161017/)]

2016-11-10 Thread Martin Kampas
Hi,

With the minimal example pasted below, the second TODO keyword gets highlighted 
with a noticeably lighter red color than the first one. In my big org file it 
made a full rainbow with the other TODO keywords, making it completely 
unusable. Note that only the length of the padding is significant, not the 
characters used.

 test.org begin 
rrr
rrr
rrr
rrr
rrr
rr

* TODO foo
  : "rrr 'rrr (rrr 'rrr)'

* TODO baz
- test.org end -

Regards,
Martin

Emacs  : GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.20.9)
 of 2016-09-18
Package: Org-mode version 8.3.6 (8.3.6-7-g4d7d52-elpa @ 
/home/martin/.spacemacs.home/.emacs.d/elpa/org-20161017/)

current state:
==
(setq
 org-id-locations-file 
"/home/martin/.spacemacs.home/.emacs.d/.cache/.org-id-locations"
 org-clock-clocked-in-display 'frame-title
 org-clocktable-defaults '(:maxlevel 2 :lang "en" :scope file :block nil 
:wstart 1 :mstart 1
   :tstart nil :tend nil :step nil :stepskip0 nil 
:fileskip0 nil :tags
   nil :emphasize nil :link nil :narrow 80! :indent t 
:formula nil
   :timestamp nil :level nil :tcolumns nil :formatter 
nil)
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-clock-persist-file 
"/home/martin/.spacemacs.home/.emacs.d/.cache/org-clock-save.el"
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-time-clocksum-format '(:hours "%d" :require-hours t :minutes ":%02d" 
:require-minutes t)
 org-occur-hook '(org-first-headline-recenter)
 org-imenu-depth 8
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-html-format-drawer-function '(lambda (name contents) contents)
 org-log-done t
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-confirm-shell-link-function 'yes-or-no-p
 org-image-actual-width nil
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-link-translation-function 'toc-org-unhrefify
 org-time-stamp-custom-formats '("<%m/%d %a>" . "<%m/%d %a %H:%M>")
 org-present-mode-hook '(spacemacs//org-present-start)
 org-agenda-restore-windows-after-quit t
 org-display-internal-link-with-indirect-buffer t
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-default-notes-file "notes.org"
 org-todo-keyword-faces '(("PROG" . "orange") ("WAIT" . "OrangeRed") ("RESO" . 
"YellowGreen"))
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook org-show-block-all 
append local] 5]
 #[nil "\300\301\302\303\304$\207"
   [org-add-hook change-major-mode-hook 
org-babel-show-result-all append local]
   5]
 org-babel-result-hide-spec org-babel-hide-all-hashes 
spacemacs/load-yasnippet
 toc-org-enable org-download-enable org-bullets-mode
 spacemacs//org-babel-do-load-languages 
spacemacs/add-org-surrounds
 evil-org-mode org-eldoc-load spacemacs//init-company-org-mode 
company-mode)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-ascii-format-drawer-function '(lambda (name contents width) contents)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines 
org-optimize-window-after-visibility-change)
 org-publish-timestamp-directory 
"/home/martin/.spacemacs.home/.emacs.d/.cache/.org-timestamps/"
 org-present-mode-quit-hook '(spacemacs//org-present-end)
 org-export-async-init-file 
"/home/martin/.spacemacs.home/.emacs.d/layers/+emacs/org/local/org-async-init.el"
 org-cycle-include-plain-lists 'integrate
 org-download-annotate-function 'org-download-annotate-default
 org-clock-frame-title-format '(:eval org-mode-line-string)
 org-hide-emphasis-markers t
 org-confirm-elisp-link-function 'yes-or-no-p
 org-startup-with-inline-images t
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-babel-after-execute-hook 

Re: [O] org-contacts bug when completing tags in gnus

2016-11-10 Thread Tory S. Anderson
Yeah, I dodge around these sort of problems a lot with 
org-contacts. It is in need of a curator and probably a rewritten 
version; it also doesn't play nice with Helm. I haven't tried it 
with org 9.0 yet, though. 


Alan Schmitt  writes:


Hello,

I'm giving org-contacts a try, and I'm having an error when I'm 
trying
to complete a tag (something should be a sequence but it's a 
number).

Digging a little into it, it seems that the problem is during
hilighting, where a fontified string is returned by 
all-completions
instead of a list (in `completion-pcm--all-completions' in 
minibuffer.el),
which then make `completion-hilit-commonality' fail because it 
expects a
list. I'm only seeing this problem with org-contacts, so I'm 
wondering

if it might be the reason for this problem in emacs code.

My contacts file looks like this:

* Test 
:test:

:PROPERTIES:
:EMAIL: alan.schm...@polytechnique.org
:END:

To reproduce, save this in some path/contacts.org file, do the 
following


  (require 'org-contacts)
  (org-contacts-gnus-insinuate)
  (setq org-contacts-files (list "path/contacts.org"))
  
then start an email in gnus, in the To field write +, then hit 
TAB.


I'm using org-mode 9 and emacs 25.1.1. Is this a known problem 
with

them?

Thanks,

Alan




[O] Capture template to capture in current buffer

2016-11-10 Thread Rainer M Krug
Hi

I am trying to get an in-buffer logging to work. I want to log some
changes in the file and I am using the following template, which was
working some (longer?) time ago:

--8<---cut here---start->8---
(setq org-capture-templates
  `(
;; ::
;; In File Logging ::
;; ::
("c"   "Changes to be logged in buffer"
 entry   (file+headline (buffer-file-name) "CHANGES Log")   
 "* %^{Header of CHANGES item}\nLOGGED: %T \n- link :: %a \n- 
author   :: Rainer M Krug, email: rai...@krugs.de\n %?")
))
--8<---cut here---end--->8---

But now I get the following error message when using the capture
template:

,
| if: Target buffer ".notes" for file+headline should be in Org mode
`

Any suggestions on how I can get this to work?

Thanks,

Rainer

--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] outline-up-heading ignoring hidden levels of headings

2016-11-10 Thread Karl Voit
* Marco Wahl  wrote:
> Hi!

Hi!

>> Since I recently upgraded my Org-mode maint branch to 8.3.4
>> (release_8.3.4-1384-gc61ee8)[1], one behavior changed to a worse one.
>
> Possibly you can configure variable
> org-show-context-detail
> to meet your needs.

Exactly.

The default setting of this changed with Emacs 25.2 according to its
documentation.

Thanks for the pointer!

> Also consider command `org-reveal' (C-c C-r by default, I guess) to reveal
> more context at a location in an orgmode buffer.

Good point.

However, I prefer having the expanded view (lineage) in the first
place.

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github




Re: [O] Tangling flow control

2016-11-10 Thread Philip Hudson
On 10 November 2016 at 01:19, Charles C. Berry  wrote:
> when developing stuff like this `:wrap src org' will capture it and protect
> against messing up the rest of your *.org file.


My goodness, you think of everything! Thanks very much Charles.

-- 
Phil Hudson  http://hudson-it.ddns.net
Pretty Good Privacy (PGP) ID: 0x887DCA63



Re: [O] Obsolete org contrib package

2016-11-10 Thread Joost Kremers


On Tue, Nov 08 2016, Joost Kremers wrote:

Hi,

On Tue, Nov 08 2016, Nicolas Goaziou wrote:

So you mean there is no equivalent to both

  (ebib-cur-entry-key)


This one was what I was worried about, but on second thought, it 
should be possible to simply use:


(ebib--get-key-at-point)


and

  (ebib-db-get-field-value 'title key ebib-cur-db)


That one's easier: 


   (ebib-db-get-field-value "title" key ebib--cur-db)


"org-ebib.el" is already compatible with Org 9.0.


Ah, good, I didn't realise that.

I'm Cc'ing the author. Ideally this library should be updated 
to 
new

Ebib and moved to some ELPA.

If Grégoire doesn't want to take care of it and no one 
volunteers to

maintain that file, we can remove it.


I was actually planning to add this functionality to Ebib 
itself. 
So if Grégoire isn't interested in it anymore, I could put it in 
the Ebib repo, or create a separate repo for it, either on 
Github 
or somewhere else, wherever you prefer.


I received the following reply from Grégoire (which, although it 
was sent to the mailing list as well, apparently didn't show up 
there):



==

On 11/08/16 13:23, Nicolas Goaziou wrote:
I'm Cc'ing the author. Ideally this library should be updated to 
new

Ebib and moved to some ELPA.

If Grégoire doesn't want to take care of it and no one 
volunteers to

maintain that file, we can remove it.


I don't use this package anymore.
If anyone uses it, s/he take over it, otherwise we can just remove 
it

from org-contrib.

==

Like I said, I'd be happy to take over maintainance. Just let me 
know how to go about making it available to org-contrib. (If there 
is a way to keep the file in the main Ebib repository, that would 
be my preference.)


Best,

Joost




--
Joost Kremers
Life has its moments



Re: [O] org-contacts bug when completing tags in gnus

2016-11-10 Thread Alan Schmitt
On 2016-11-09 06:35, tory_ander...@byu.edu (Tory S. Anderson) writes:

> Yeah, I dodge around these sort of problems a lot with org-contacts. It is in
> need of a curator and probably a rewritten version; it also doesn't play nice
> with Helm. I haven't tried it with org 9.0 yet, though. 

This is really too bad. Are there alternatives for managing contacts
with org? Or is bbdb the solution?

Thanks,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2016-09: 401.03, 2015-09: 397.63


signature.asc
Description: PGP signature