[O] [PATCH] Improve documentation + fix typos

p 17 00:00:00 2001 From: Rafael Laboissiere Date: Tue, 11 Oct 2011 00:22:09 +0200 Subject: [PATCH 1/3] Fix typos in variable description * lisp/org.el (org-link-search-must-match-exact-headline): fix typos --- lisp/org.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git

[O] Contradiction between code and doc as regards commented lines

Before Git commit e8046d2, lines like this were treated as comments in org-mode: ### This used to be a comment At present, lines as the above are not highlighted as comments and will be exported verbatim. Only lines like the following are considered to be comments, currently: # Onl

Re: [O] Contradiction between code and doc as regards commented lines

* Bastien [2012-10-27 21:44]: Rafael Laboissiere writes: Please, fix the documentation (or restore the previous behavior, if the documentation is meant to be correct). Done, thanks. Thanks. You might be interested in applying the patch attached below, which fixes the comments in the

Re: [O] Contradiction between code and doc as regards commented lines

* Bastien [2012-10-28 11:10]: Rafael Laboissiere writes: You might be interested in applying the patch attached below, which fixes the comments in the *Remember* buffer, allowing them to get correctly fontified. Applied, thanks! Thanks. I just noticed that my patch have a bad side

[O] Fix broken URL in org-bibtex.el

The patch attached below fixes a very minor problem in org-bibtex.el. Cheers, Rafael >From 852681cb0789b4d1a7c0081e634322690b9ae47d Mon Sep 17 00:00:00 2001 From: Rafael Laboissiere Date: Sun, 4 Nov 2012 09:14:44 +0100 Subject: [PATCH] org-bibtex.el: Fix broken URL * lisp/org-bibtex

[Orgmode] [PATCH] Better documentation for org-agenda-fontify-priorities

[I hope this is the appropriate mailing list for submitting patches] First of all, thanks for your wonderful work in developing and maintaining org-mode. I recently tried to custom-set the value of the org-agenda-fontify-priorities to get better visual cues from the agenda view. I was not able t

[O] [PATCH] Fix typo in org.texi

The patch below fixes (what i think) is a minor typo in the info documentation. Thanks for your great work on org-mode, Best, Rafael >From 65d995992fdcb5a04c413f83fe5c68edf4508835 Mon Sep 17 00:00:00 2001 From: Rafael Laboissiere Date: Sun, 19 Oct 2014 22:37:39 +0200 Subject: [PA

Re: [O] commit 7b9f2fba66 (was: commit 860bcfbf93)

* Achim Gratz [2016-01-25 19:34]: Achim Gratz writes: This commit is marked as TINYCHANGE, but committed by the author himself. How and why did someone not having assigned copyright to the FSF get push access to the Orgmode repository? The same thing again, with no previous communication

[O] call_*() is not working inside #+DATE

The following used to work for me in the past: #+NAME: date #+BEGIN_SRC sh :results silent :exports results :tangle no date #+END_SRC #+TITLE: Sample #+AUTHOR: Me #+DATE: call_date() and I saw the output of the shell command "date" when exporting the file to LaTeX. However

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Rafael Laboissiere [2016-03-07 02:58]: The following used to work for me in the past: #+NAME: date #+BEGIN_SRC sh :results silent :exports results :tangle no date #+END_SRC #+TITLE: Sample #+AUTHOR: Me #+DATE: call_date() and I saw the output of the shell command "date&

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Eric S Fraga [2016-03-12 08:51]: On Saturday, 12 Mar 2016 at 08:57, Rafael Laboissiere wrote: P.S.: For those who are reading this message and are interested in a solution for my original problem, here is the way I am getting around it right now. Thanks for this alternate solution. You

Re: [O] commit 7b9f2fba66

* Achim Gratz [2016-01-26 18:11]: Getting the copyright assigned would be good since if you've had some previous changes (not the two commits you did yourself), then quite likely you've already exhausted your TINYCHANGE budget. The papers have been signed with the Free Software Foundation.

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Nicolas Goaziou [2016-03-13 18:24]: Rafael Laboissiere writes: It would be much better if the following construct worked: #+DATE: src_sh{git show -s --date=short --format="%cd [%h]" HEAD} Unfortunately, it does not. This behavior (or misbehavior, I do not know) can be t

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Rafael Laboissiere [2016-03-12 08:57]: [snip] I investigated this issue further and discovered that the constructs call_(args) and src_{code} are not evaluated at all when they appear in a keyword line (starting with "#+:"). Org-babel behaves in this way probably on purpose. A

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Nicolas Goaziou [2016-03-14 20:41]: Rafael Laboissiere writes: * Rafael Laboissiere [2016-03-12 08:57]: [snip] I went ahead and committed the patch. I think this is a bit premature, as we're still discussing how to fix this issue, so this documentation patch is likely

Re: [O] [PATCH] call_*() is not working inside #+DATE

* Nicolas Goaziou [2016-03-15 19:50]: The problem is that the documentation patch is (partly) wrong. From maint, you can try calling `org-babel-execute-buffer' in the following document #+DATE: src_emacs-lisp{(+ 1 1)} It is possible to evaluate code snippets in keywords. It is strange, t