Re: [O] [BUG] Inconsistency in src block hiding
Eric Schulte eric.schu...@gmx.com writes: [...] To my mind a better path moving forward would be to change the behavior of the :RESULTS: drawer so that it is exported but *not* to change the default drawer export behavior. This way with a :wrap header argument the code block results could be hidden with tab but would still be exported. PRO: allows hiding code block results with tab, makes it clear where results begin and end, uses drawers for hiding which is what they are designed for, avoids the potential for hiding anything with a name CON: more syntactic weight around results, changes the existing default behavior, makes the RESULTS drawer a special type of drawer There is likely a better option but this is the best that comes to mind. Personally I am also content with the current behavior in which anything under a #+name: may be hidden. Coming late to this thread, I just want to say, that I am on the PRO side for special results drawers. The fact that org mode uses drawers for wrapping results is an internal/technical choice that - I think - the user should not need to know. In the current state, in case the user switches result wrapping on, the results block disappears from the export, until the user has figured out, that exporting drawers has to be enabled now (with all drawers being exported...). So, I think, there *is* a difference between drawers as used in other places and drawers used for results, which are imposed onto the user by org mode. Thus, the CON just reflects this difference and is no real CON. Just my two cents. - Andreas
Re: [O] Why functions like org-show-subtree are undocumented?
Hi Alexander, Alexander Corvinus acr...@gmail.com writes: So the question is - why such useful functions like org-show-subtree, hide-subtree, show-children aren't documented in manual? Because of that, previously I thought that what I wanted was impossible (without source change). Please submit a patch. -- Bastien
Re: [O] LaTeX export: Keep point position in TeX file
Michael Bach pha...@gmail.com writes: Eric S Fraga e.fr...@ucl.ac.uk writes: If so, I suggest you could achieve what you want by using the org-export-* hooks to, for instance, save current position before export and then jump to that position after export? Maybe org-export-first-hook and org-export-latex-final-hook could be used? Thanks for your thoughts on this and sorry for being late to reply. I No problem! stumbled upon your reply and have tried it today with this: [...] The switching to latex file works, but `(goto-char temppoint)' does not - for a reason I do not understand. The only benefit of this is that I do not understand either. Putting in some (message ...) lines, it is trying to (goto-char ...) to the right place in the buffer but that goto doesn't seem to have any effect. Have you looked at the code in org that actually invokes that hook to see if maybe position is being changed afterwards? -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.03 (release_7.8.03.206.g10b06)
Re: [O] Scrolling down after Shift-TAB ?
Nick Dokos nicholas.do...@hp.com writes: Well, the proper thing is very much in the eye of the beholder :-) My mother, who was a musician and a painter, used to say: Des goûts et des couleurs, on ne discute pas... Mais il y en a de meilleurs que d'autres! The sentence is soft and spicy all at once! A bit hard to translate, though: It's not fruitful to compare tastes and colors... Yet, some have it better than others! The fun thing is that the standard proverb stops at the ellipsis. What follows slightly contradicts what precedes! And the lesson, for me, is to use some bits of courage at proposing or evaluating aspects of things which, being more on the subjective side than the objective side, might be prone to subtler debates. François
Re: [O] Scrolling down after Shift-TAB ?
Nick Dokos nicholas.do...@hp.com writes: Well, the proper thing is very much in the eye of the beholder :-) My mother, who was a musician and a painter, used to say: Des goûts et des couleurs, on ne discute pas... Mais il y en a de meilleurs que d'autres! The sentence is soft and spicy all at once! A bit hard to translate, though: It's not fruitful to compare tastes and colors... Yet, some have it better than others! The fun thing is that the standard proverb stops at the ellipsis. What follows slightly contradicts what precedes! And the lesson, for me, is to use some bits of courage at proposing or evaluating aspects of things which, being more on the subjective side than the objective side, might be prone to subtler debates. François
Re: [O] Why functions like org-show-subtree are undocumented?
On 23.1.2012, at 16:27, Alexander Corvinus wrote: Hi all, I just reviewed code in org.el and noticed that function org-show-subtree, which is called by org-cycle, unconditionally shows whole subtree (exactly what I wanted to have in my shortcuts!). So the question is - why such useful functions like org-show-subtree, hide-subtree, show-children aren't documented in manual? Because of that, previously I thought that what I wanted was impossible (without source change). Emacs outline-mode has a plethora of such specific commands, and exposes all of them as user interface. Org prides itself to have compressed that entire functionality into the TAB and S-TAB commands. You specific example, org-show-subtree is basically TAB TAB on a closed tree. SO yes, there are lots such commands, but I am no sure it would be good to expose them in the manual. - Carsten Thanks
Re: [O] export-as-hmtl fail
Hi Aaron aaron barclay aaron.diplo...@gmail.com writes: Hello, When I use a python code block in a document any export-as-html results in the error Invalid file-name. Without a code block the export goes without a hitch. Other exports work no probs such as export-as-ascii. The code block within the document acts as expected, it is only the export that fails. I was on org7.5 but updated to 7.8.03 but have the same result. Also, it is only the python code blocks that fail, others work. My babel setup is (org-babel-do-load-languages 'org-babel-load-languages '( (dot . t) (sh . t) (python . t) (emacs-lisp . t) )) (setq org-babel-python-command python2.6) My code block is #+begin_src python :results output print hi #+end_src #+results: : hi Does anyone have any tips on what I might do to troubleshoot this. Could it be something else in my setup or system? Any else ever experienced this? cheers, aaron. I can't replicate this error (see my versions below). Even breaking `org-babel-python-command' does not break your code for me in the way you describe. For diagnostic purposes, you may run the command: - `M-x toggle-debug-on-error' ...prior to exporting as html. This should give you a useful backtrace. Note also that if you are wishing to export the python results as opposed to the python code, you will also need :exports results since the default is `:exports code' . HTH Best, Martyn --- Org-mode version 7.8.03 (release_7.8.03.192.ga38b.dirty) GNU Emacs 24.0.92.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2011-12-02 on bob.porkrind.org
[O] using first heading as h1 in batch export to html
If I batch export a test.org looking like this -- test.org * heading1 some text to html I get a h1 class=titletest/h1 as result. If I open the file and do C-c @ on the first heading the result contains h1 class=titleheading1/h1 How do I achieve the latter in batch export? Btw: Reading the manual I get the impression the latter is what should happen anyway? http://orgmode.org/manual/Document-title.html#Document-title says -- Document title The title of the exported document is taken from the special line #+TITLE: This is the title of the document If this line does not exist, the title is derived from the first non-empty, non-comment line in the buffer. If no such line exists, or if you have turned off exporting of the text before the first headline (see below), the title will be the file name without extension. If you are exporting only a subtree by marking is as the region, the heading of the subtree will become the title of the document. If the subtree has a property EXPORT_TITLE, that will take precedence. So, no TITLE here, first non-empty line is * heading1 , nothing was prevented from being exported. I would expect heading1 as title from reading this. thx Detlef
[O] Question about Sorting All Day Events in Agenda View
Hello, I use Org-Mode with Calendar/Diary integration turned on. This works well for me, but the only issue I have is that in the agenda view, all day events such as holidays and anniversaries are displayed at the bottom. I have many tasks, so sometimes I need to scroll down quite a bit to see those events. Is there a way to put them at the top? What I see Monday 16 January 2012 W03 [Task1] [Task2] [Task3] ... Diary: Martin Luther King Day Diary: My Friend's anniversary What I would like to see Monday 16 January 2012 W03 Diary: Martin Luther King Day Diary: My Friend's anniversary [Task1] [Task2] [Task3] ... Thank you,
Re: [O] [PATCH] Save undo history after org-edit-src-save.
Hi Peter, Peter Danenberg p...@roxygen.org writes: It's been irritating me that after saving an edit buffer, the undo history disappears; the attached patch restores the undo history. Applied. Next time, please provide a full patch (with an Emacs ChangeLog message) with git format-patch. Thanks, -- Bastien
Re: [O] Prompts for `C-c .' and `C-c !'
Hi François, pin...@iro.umontreal.ca (François Pinard) writes: Could it be: Date+time [2012-01-23]: = [2012-01-23 lun] when appropriate? This is now the case. Thanks for the suggestion. -- Bastien
Re: [O] C-a in lists when org-special-ctrl-a/e
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: It all depends if we read the letter or the spirit of the second sentence. [ ] is a kind of TODO, and [X] is a kind of DONE, as demonstrated by the commands `C-x -' and `C-x *'. That's why I quite naturally expect the cursor to be positioned after the check box. Ok, then, let's read the spirit. I've implemented this behaviour in master branch. We'll see how it goes. I think this is a good change, thanks for implementing it! -- Bastien
Re: [O] customize agenda time boundaries
Hi Sergio, Bernt Hansen be...@norang.ca writes: You might be able to use org-agenda-span to accomplish some of this. Yes -- a combination of `org-agenda-starting-day' and `org-agenda-span' should do. HTH, -- Bastien
Re: [O] Capitalisation and good taste ?
Eric S Fraga e.fr...@ucl.ac.uk writes: Indeed. Attached is a very simple patch to fix these missing s. Untested. Applied, thanks a lot! -- Bastien
Re: [O] using first heading as h1 in batch export to html
Hi Detlef, Detlef Steuer detlef.ste...@gmx.de writes: -- test.org * heading1 some text to html I get a h1 class=titletest/h1 as result. If I open the file and do C-c @ on the first heading the result contains h1 class=titleheading1/h1 How do I achieve the latter in batch export? Please try to use #+OPTIONS: skip:t and let us know what title is used in the batch export. HTH, -- Bastien
Re: [O] latex export of #+header: lines
Hi Jambunathan, Jambunathan K kjambunat...@gmail.com writes: I think the problem is not with the latex or odt backends as such but in the export pre-processor. Just to make sure: are you suggesting `org-export-preprocess-string' should normalize comment lines like ^.+#header.*) and move them to column 0 of the buffer? Thanks in advance for any detail! -- Bastien
Re: [O] using first heading as h1 in batch export to html
Hi Bastien! Detlef Steuer detlef.ste...@gmx.de writes: -- test.org * heading1 some text to html I get a h1 class=titletest/h1 as result. If I open the file and do C-c @ on the first heading the result contains h1 class=titleheading1/h1 How do I achieve the latter in batch export? Please try to use #+OPTIONS: skip:t and let us know what title is used in the batch export. HTH, No, it doesn't ... test.org: #+OPTIONS: skip:t * heading1 some text Result contains: h1 class=titletest/h1 Detlef -- Bastien
Re: [O] Org-edit-special and C-x C-s strange behavior
Hi Leo, Leo Alekseyev dnqu...@gmail.com writes: Folks, I still think that the fact that buffer-file-name is not nil is a bug and should be fixed. So do I. I think this is fixed now -- thanks! -- Bastien
Re: [O] [Bug] Auto-fill and *bold-face* at line-begin
Hi Maximilian, Maximilian Matthe maxi.mat...@googlemail.com writes: Filling paragraphs where the first word is *bold-face* fills the following lines beginning in the 2nd column. See attached file for details. Regards, Max * A *this is a test* where the line begins with a bold-face-star. When the line is auto-filled, it starts in the 2nd column. Here's another paragraph starting without bold-face and filling it starts lines in 1st column. The problem is not specific to org-mode and also happens in text-mode. Can you please report this as an emacs bug? M-x report-emacs-bug RET Thanks, -- Bastien
[O] [babel][patch] provide consistent result removal (type `wrap')
Patch to fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. Prior to this fix multiple (org-ctrl-c-ctrl-c) commands will add multiple newlines to the end of results (one newline per block execution). This patch also fixes the test `test-ob/org-babel-remove-result--results-wrap' which is uncommented in the patch. Best, Martyn From a4b2f8484ec4810e7a891b4db0caf5463e96a58d Mon Sep 17 00:00:00 2001 From: Martyn Jago martyn.j...@btinternet.com Date: Tue, 24 Jan 2012 15:39:30 + Subject: [PATCH] Fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. * lisp/ob.el: Fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. Prior to this fix multiple (org-ctrl-c-ctrl-c) commands will add multiple newlines to the end of results (one newline per block execution). This fixes the test `test-ob/org-babel-remove-result--results-wrap' * testing/lisp/test-ob.el: Uncomment test since it now passes. --- lisp/ob.el |3 ++- testing/lisp/test-ob.el | 28 ++-- 2 files changed, 16 insertions(+), 15 deletions(-) diff --git a/lisp/ob.el b/lisp/ob.el index e8a6d88..895a5b6 100644 --- a/lisp/ob.el +++ b/lisp/ob.el @@ -1920,7 +1920,8 @@ code the results are extracted in the syntax of the source (prvs (org-list-prevs-alist struct))) (org-list-get-list-end (point-at-bol) struct prvs))) ((looking-at ^\\([ \t]*\\):RESULTS:) - (re-search-forward (concat ^ (match-string 1) :END:))) + (progn (re-search-forward (concat ^ (match-string 1) :END:)) + (forward-char 1)) (t (let ((case-fold-search t)) (if (looking-at (concat [ \t]*#\\+begin_\\([^ \t\n\r]+\\))) diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el index 178556e..7dccd22 100644 --- a/testing/lisp/test-ob.el +++ b/testing/lisp/test-ob.el @@ -771,20 +771,20 @@ replacement happens correctly. * next heading)) -;; TODO FIXME Activate when Eric's trailing newline fix has been committed -;; (ert-deftest test-ob/org-babel-remove-result--results-wrap () -;; (test-ob-verify-result-and-removed-result -;;:RESULTS: -;; hello there -;; :END: -;; -;; * org-babel-remove-result -;; -;; +begin_src emacs-lisp :results wrap -;; \hello there\ -;; #+end_src -;; -;; * next heading)) +(ert-deftest test-ob/org-babel-remove-result--results-wrap () + Test `org-babel-remove-result' with :results wrap. + (test-ob-verify-result-and-removed-result + :RESULTS: +hello there +:END: + + * org-babel-remove-result + +#+begin_src emacs-lisp :results wrap +\hello there\ +#+end_src + +* next heading)) (ert-deftest test-ob/org-babel-remove-result--results-org () Test `org-babel-remove-result' with :results org. -- 1.7.3.4
Re: [O] LOGBOOK opening
Hi François, The default behavior of SPC in the agenda view stays the same, but you can now also use `C-u SPC' to avoid unfolding of logbooks and drawers. HTH, -- Bastien
[O] [Accepted] [O, 1/3] Document max number of stars in headings in docstring of org-inlinetask-minlevel
Patch 1124 (http://patchwork.newartisans.com/patch/1124/) is now Accepted. Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C20120122131516.GC21012%40shi.workgroup%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, 1/3] Document max number of stars in headings in docstring of org-inlinetask-minlevel Date: Sun, 22 Jan 2012 18:15:16 - From: Gregor Zattler telegr...@gmx.net X-Patchwork-Id: 1124 Message-Id: 20120122131516.GC21012@shi.workgroup To: emacs-orgmode emacs-orgmode@gnu.org Clocking only works with headings indented with less than `30' stars (hardcoded `lmax' value in `org-clock-sum'). Since especially inline tasks may dupe someone into using more stars, document the limit in the docsring of `org-inlinetask-min-level'. --- lisp/org-inlinetask.el |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/lisp/org-inlinetask.el b/lisp/org-inlinetask.el index a14e404..b8e8437 100644 --- a/lisp/org-inlinetask.el +++ b/lisp/org-inlinetask.el @@ -90,6 +90,9 @@ (defcustom org-inlinetask-min-level 15 Minimum level a headline must have before it is treated as an inline task. +Don't set it to something higher than `29' or clocking will break since this +is the hardcoded maximum number of stars `org-clock-sum' will work with. + It is strongly recommended that you set `org-cycle-max-level' not at all, or to a number smaller than this one. In fact, when `org-cycle-max-level' is not set, it will be assumed to be one less than the value of smaller than
[O] [Accepted] [O, 2/3] Document max number of stars in headings in manual
Patch 1123 (http://patchwork.newartisans.com/patch/1123/) is now Accepted.
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C20120122131506.GB21012%40shi.workgroup%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,2/3] Document max number of stars in headings in manual
Date: Sun, 22 Jan 2012 18:15:06 -
From: Gregor Zattler telegr...@gmx.net
X-Patchwork-Id: 1123
Message-Id: 20120122131506.GB21012@shi.workgroup
To: emacs-orgmode emacs-orgmode@gnu.org
Clocking only works with headings indented with less than `30' stars
(hardcoded `lmax' value in `org-clock-sum').
---
doc/org.texi |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index b238210..9e873ea 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1164,7 +1164,8 @@ Headlines define the structure of an outline tree. The
headlines in Org
start with one or more stars, on the left margin@footnote{See the variables
@code{org-special-ctrl-a/e}, @code{org-special-ctrl-k}, and
@code{org-ctrl-k-protect-subtree} to configure special behavior of @kbd{C-a},
-@kbd{C-e}, and @kbd{C-k} in headlines.}. For example:
+@kbd{C-e}, and @kbd{C-k} in headlines.} @footnote{Clocking only works with
+headings indented less then 30 stars.}. For example:
@example
* Top level headline
[O] [Accepted] [O, 3/3] Document max number of stars in clocking section
Patch 1125 (http://patchwork.newartisans.com/patch/1125/) is now Accepted.
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C20120122133050.GD21012%40shi.workgroup%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,3/3] Document max number of stars in clocking section
Date: Sun, 22 Jan 2012 18:30:50 -
From: Gregor Zattler telegr...@gmx.net
X-Patchwork-Id: 1125
Message-Id: 20120122133050.GD21012@shi.workgroup
To: emacs-orgmode emacs-orgmode@gnu.org
Clocking only works with all headings indented with less than `30'
stars (hardcoded `lmax' value in `org-clock-sum').
---
doc/org.texi | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 9e873ea..46aa1e2 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5917,12 +5917,14 @@ created for this purpose, it is described in
@ref{Structure editing}.
@cindex time clocking
Org mode allows you to clock the time you spend on specific tasks in a
-project. When you start working on an item, you can start the clock.
-When you stop working on that task, or when you mark the task done, the
-clock is stopped and the corresponding time interval is recorded. It
-also computes the total time spent on each subtree of a project. And it
-remembers a history or tasks recently clocked, to that you can jump quickly
-between a number of tasks absorbing your time.
+project. When you start working on an item, you can start the clock. When
+you stop working on that task, or when you mark the task done, the clock is
+stopped and the corresponding time interval is recorded. It also computes
+the total time spent on each subtree@footnote{Clocking only works if all
+headings are indented with less than 30 stars. This is a hardcoded
+limitation of `lmax' in `org-clock-sum'.} of a project. And it remembers a
+history or tasks recently clocked, to that you can jump quickly between a
+number of tasks absorbing your time.
To save the clock history across Emacs sessions, use
@lisp
Re: [O] Problem at capture time
Hi David, David Maus dm...@ictsoc.de writes: Sorry for my silence, haven't looked into the Orgmode mailing list for a while. I just pushed a fix for this problem: If the :exact-position for a list item is supplied we don't search for the position in an existing list at all but insert the item whereever :exact-position points to. Thanks a lot for the fix. I'll mark the patch in patchwork as superseeded this evening as soon as I recover my password. I just did so -- hope you'll recover your password! Otherwise John might help. Best, -- Bastien
Re: [O] [BUG][PATCH] document number of stars limitation with respect to org-clock-sum
Hi Gregor, Gregor Zattler telegr...@gmx.net writes: Since I don't know if the hardcoded lmax value `30' serves other purposes too I don't change it but document the fact in org-inlinetask.el and the manual. Applied, thanks. -- Bastien
Re: [O] [babel][patch] provide consistent result removal (type `wrap')
[...] Oops - patch provided at start of this thread is malformed and should be ignored. The correct patch is provided below for consideration. Apologies for the noise. Best, Martyn Martyn Jago martyn.j...@btinternet.com writes: Patch to fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'From 7b6f37164848931321c0f25d567cf65df2e5a4af Mon Sep 17 00:00:00 2001 From: Martyn Jago martyn.j...@btinternet.com Date: Tue, 24 Jan 2012 16:12:29 + Subject: [PATCH] Fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. * lisp/ob.el: Fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. Prior to this fix multiple (org-ctrl-c-ctrl-c) commands will add multiple newlines to the end of results (one newline per block execution). This fixes the test `test-ob/org-babel-remove-result--results-wrap' * testing/lisp/test-ob.el: Uncomment test since it now passes. --- lisp/ob.el |3 ++- testing/lisp/test-ob.el | 28 ++-- 2 files changed, 16 insertions(+), 15 deletions(-) diff --git a/lisp/ob.el b/lisp/ob.el index e8a6d88..4541226 100644 --- a/lisp/ob.el +++ b/lisp/ob.el @@ -1920,7 +1920,8 @@ code the results are extracted in the syntax of the source (prvs (org-list-prevs-alist struct))) (org-list-get-list-end (point-at-bol) struct prvs))) ((looking-at ^\\([ \t]*\\):RESULTS:) - (re-search-forward (concat ^ (match-string 1) :END:))) + (progn (re-search-forward (concat ^ (match-string 1) :END:)) + (forward-char 1) (point))) (t (let ((case-fold-search t)) (if (looking-at (concat [ \t]*#\\+begin_\\([^ \t\n\r]+\\))) diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el index 178556e..7dccd22 100644 --- a/testing/lisp/test-ob.el +++ b/testing/lisp/test-ob.el @@ -771,20 +771,20 @@ replacement happens correctly. * next heading)) -;; TODO FIXME Activate when Eric's trailing newline fix has been committed -;; (ert-deftest test-ob/org-babel-remove-result--results-wrap () -;; (test-ob-verify-result-and-removed-result -;;:RESULTS: -;; hello there -;; :END: -;; -;; * org-babel-remove-result -;; -;; +begin_src emacs-lisp :results wrap -;; \hello there\ -;; #+end_src -;; -;; * next heading)) +(ert-deftest test-ob/org-babel-remove-result--results-wrap () + Test `org-babel-remove-result' with :results wrap. + (test-ob-verify-result-and-removed-result + :RESULTS: +hello there +:END: + + * org-babel-remove-result + +#+begin_src emacs-lisp :results wrap +\hello there\ +#+end_src + +* next heading)) (ert-deftest test-ob/org-babel-remove-result--results-org () Test `org-babel-remove-result' with :results org. -- 1.7.3.4 .
Re: [O] [babel][patch] provide consistent result removal (type `wrap')
Martyn Jago martyn.j...@btinternet.com writes: Patch to fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap'. Prior to this fix multiple (org-ctrl-c-ctrl-c) commands will add multiple newlines to the end of results (one newline per block execution). This patch also fixes the test `test-ob/org-babel-remove-result--results-wrap' which is uncommented in the patch. Best, Martyn Hi Martyn, Thanks for the patch I tried to apply it and it generated a syntax error (missing paren). I then re-placed the missing paren (at least where I thought it would be) and re-ran the test suite to many new failures. Could you resubmit? Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel][patch] provide consistent result removal (type `wrap')
Applied, Thanks, Martyn Jago martyn.j...@btinternet.com writes: [...] Oops - patch provided at start of this thread is malformed and should be ignored. The correct patch is provided below for consideration. Apologies for the noise. Best, Martyn Martyn Jago martyn.j...@btinternet.com writes: Patch to fix `org-babel-result-end' command to provide consistent result removal where result is type `wrap' . -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Question about Sorting All Day Events in Agenda View
Tatsuhito Koya tkoy...@gmail.com writes: Hello, I use Org-Mode with Calendar/Diary integration turned on. This works well for me, but the only issue I have is that in the agenda view, all day events such as holidays and anniversaries are displayed at the bottom. I have many tasks, so sometimes I need to scroll down quite a bit to see those events. Is there a way to put them at the top? Have a look at ,[ C-h v org-agenda-sorting-strategy RET ] | org-agenda-sorting-strategy is a variable defined in `org-agenda.el'. | Its value is ((agenda habit-down time-up priority-down category-keep) | (todo priority-down category-keep) | (tags priority-down category-keep) | (search category-keep)) | | | Documentation: | Sorting structure for the agenda items of a single day. | This is a list of symbols which will be used in sequence to determine | if an entry should be listed before another entry. The following | symbols are recognized: | | time-upPut entries with time-of-day indications first, early first | time-down Put entries with time-of-day indications first, late first | category-keep Keep the default order of categories, corresponding to the | sequence in `org-agenda-files'. | category-upSort alphabetically by category, A-Z. | category-down Sort alphabetically by category, Z-A. | tag-up Sort alphabetically by last tag, A-Z. | tag-down Sort alphabetically by last tag, Z-A. | priority-upSort numerically by priority, high priority last. | priority-down Sort numerically by priority, high priority first. | todo-state-up Sort by todo state, tasks that are done last. | todo-state-downSort by todo state, tasks that are done first. | effort-up Sort numerically by estimated effort, high effort last. | effort-downSort numerically by estimated effort, high effort first. | user-defined-upSort according to `org-agenda-cmp-user-defined', high last. | user-defined-down Sort according to `org-agenda-cmp-user-defined', high first. | habit-up Put entries that are habits first | habit-down Put entries that are habits last | alpha-up Sort headlines alphabetically | alpha-down Sort headlines alphabetically, reversed | | The different possibilities will be tried in sequence, and testing stops | if one comparison returns a not-equal. For example, the default | '(time-up category-keep priority-down) | means: Pull out all entries having a specified time of day and sort them, | in order to make a time schedule for the current day the first thing in the | agenda listing for the day. Of the entries without a time indication, keep | the grouped in categories, don't sort the categories, but keep them in | the sequence given in `org-agenda-files'. Within each category sort by | priority. | | Leaving out `category-keep' would mean that items will be sorted across | categories by priority. | | Instead of a single list, this can also be a set of list for specific | contents, with a context symbol in the car of the list, any of | `agenda', `todo', `tags', `search' for the corresponding agenda views. | | Custom commands can bind this variable in the options section. | | You can customize this variable. | | [back] ` HTH, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.03 (release_7.8.03.212.g2395c)
Re: [O] Problem at capture time
Bastien b...@altern.org writes: David Maus dm...@ictsoc.de writes: I just pushed a fix for this problem Thanks a lot for the fix. After removing my patch and installing the official code here, things continue to work nicely for the few tests I did. Let me thank you as well! François
[O] [mobileorg/org] Problem when pulling data
Hey guys, I have encryption ON both on mobileorg and orgmode. I wasn't sure what was the point of encryption on mobileorg and I'm fine deactivating it if the problem persists, but I'd like to know if anyone knows why the following happens during the process of (org-mobile-pull): http://minus.com/mehDiIAHH Thanks, -Marcelo.
Re: [O] LOGBOOK opening
Bastien b...@altern.org writes: The default behavior of SPC in the agenda view stays the same, but you can now also use `C-u SPC' to avoid unfolding of logbooks and drawers. That's good news! HTH, Yes, it will indeed help! I felt the need many times this morning, so this correction is very welcome! Thanks for it. François P.S. While I'm happy, I think that for the consistency and elegance of Org mode, `C-u SPC' and `SPC' meanings should be reversed. The manual still defines drawers by this intent of keeping their contents hidden.
[O] Wrapping of e-mail address in table when exporting to pdf through latex
Hi,
I have some e-mail addresses in a table that I want to export to pdf
thorugh latex. However, the e-mail addresses do not wrap nicely (not at
all) in the table, is there any way to make the latex export from org
enable wrapping?
Example:
#+ATTR_LaTeX: align=llp{2cm}
| ITEM| Comment| e-mail |
|-++--|
| Listed item | Some text here | this.email@shouldbe.wrapped |
| || |
Thanks!
--
Johnny
Re: [O] [PATCH] Save undo history after org-edit-src-save.
Thanks, Bastien! Just found the Preferred way of submitting patches document. Quoth Bastien on Prickle-Prickle, the 24th of Chaos: Hi Peter, Peter Danenberg p...@roxygen.org writes: It's been irritating me that after saving an edit buffer, the undo history disappears; the attached patch restores the undo history. Applied. Next time, please provide a full patch (with an Emacs ChangeLog message) with git format-patch. Thanks, -- Bastien
Re: [O] [BUG] Inconsistency in src block hiding
Hello, Eric Schulte eric.schu...@gmx.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: Changing the default drawer export behavior from don't export to do export would be surprising Probably at first, but not for too long. would break many existing work flows Not at all, since it's just a d:nil away from old behaviour. Note that the current behavour is _not_ a d:t away from what I want to implement. Indeed, even with d:t, you still need to change default handler for drawers (org-export-format-drawer-function) as the default one (org-export-format-drawer) will change drawer's contents into a fixed-width area. For that task, an example block would have achieved the same (hiding + verbatim). would likely make drawers less useful. Certainly not, but I will that explain later. In general I think the Org-mode specification is best defined by how Org-mode is used and how it may be more easily and intuitively used in the future. Org-mode doesn't currently have a formal specification, and I think that is a good thing. Formal specification don't prevent bugs, they just move them from the code to the spec. Then we may be running into problems, since my objective, with org-element, is to provide a formal specification and normalization of Org syntax. Along the way, some parts (hopefully few) in Org syntax will need to be defined or re-defined. Because only a very small number of persons can pretend to know every part of Org syntax and even less (if any) to actually use them, we definitely need guidelines to offer relevant future improvements. Some current uses just don't fit in a global view: a recent example was given by the caption syntax, which was heavily LaTeX oriented. To my mind a better path moving forward would be to change the behavior of the :RESULTS: drawer so that it is exported but *not* to change the default drawer export behavior. This way with a :wrap header argument the code block results could be hidden with tab but would still be exported. PRO: allows hiding code block results with tab, makes it clear where results begin and end, uses drawers for hiding which is what they are designed for, avoids the potential for hiding anything with a name CON: more syntactic weight around results, changes the existing default behavior, makes the RESULTS drawer a special type of drawer There is likely a better option but this is the best that comes to mind. Personally I am also content with the current behavior in which anything under a #+name: may be hidden. Drawers should not add any semantics to the contents they are hiding. They should be, as a default, neutral entities useful to hide stuff in an Org buffer but certainly not to interfere with export. 1. There are already many ways to remove arbitrary contents from export. Among them, one can find the :noexport: tag, comment blocks... There's absolutely no need to add more. 2. They are better handled with regards to visibility cycling, which in not the case of single keywords. Allowing to hide every single Org syntax with a #+name: keyword could potentially be a mess. 3. By essence, drawers are better suited for hiding stuff than keywords, since they allow to group any number of elements, whereas keywords only apply to one keyword at a time. 4. Drawers are flexible. All major back-ends allow to configure behaviour of drawers with regards to export. You can always decide to keep :FOO: drawers transparent but remove any :BAR: drawer. It will be even simpler with the new export engine. On the other hand, I don't think that adding another special type for drawers is the way to go. In general, adding new syntax should be done with parsimony. In this case, it unnecessarilyrestricts possibilities: why enforce a special behaviour for :RESULTS: since (point 4) you can choose it? I still vote for neutral drawers. Regards, -- Nicolas Goaziou
[O] problem with orgstruct/outline-minor-mode with indented headlines
Hi all. I'm still trying to get orgstruct to work right. One thing I found is that I was getting confused with outline-magic which set up outline-minor-mode-map but not orgstruct-mode-map. I'm working inside verilog-mode, which uses the same // comment as c. So I defined outline-regexp: (setq outline-regexp \\s-*// [*]+ ) ;; any line that starts with // (possibly preceeded with whitespace) and some number of stars and a space This works fine. I needed the whitespace in front since verilog-mode indents comments along with code. The problem is when I run org-cycle on a headline. The following headline ends up on the same line (also in outline-minor-mode). For example, in plain org mode I have this: * head 1 ** head 2 *** head 3 head 3 text head 3 text ** head 2b head 2b text head 2b text I now run org-cycle on headline head 2 and it looks like this: * head 1 ** head 2... ** head 2b head 2b text head 2b text p.s. - is there a way to copy/export exactly what the collapse buffer looks like? I had to manually create this since copy/paste of the text includes the hidden parts. If I change to verlog-mode with orgstruct minor mode and add // at the beginning of headlines, everything is still good: // * head 1 // ** head 2 // *** head 3 head 3 text head 3 text // ** head 2b head 2b text head 2b text and // * head 1 // ** head 2 // ** head 2b head 2b text head 2b text Where it breaks is the case of indented comments: // * module declaration module a ( // * ports // ** inputs input b, input c, // ** outputs output d, output e ); // module code assign d = b c; assign e = d | e; // * end module declaration endmodule // a If I run org-cycle on headline ports I get this: // * module declaration module a ( // * ports // * end module declaration endmodule // a Instead of this: // * module declaration module a ( // * ports // * end module declaration endmodule // a Likewise, collapsing inputs gives this: // * module declaration module a ( // * ports // ** inputs // ** outputs output d, output e ); // module code assign d = b c; assign e = d | e; // * end module declaration endmodule // a Not this: // * module declaration module a ( // * ports // ** inputs ... // ** outputs output d, output e ); // module code assign d = b c; assign e = d | e; // * end module declaration endmodule // a What's going on? There's some confusion about the headline level being based on the indent and the number of stars. I'm so close, but need help figuring out this last problem. Thanks, David
[O] Custom agenda skips next todos if deadlined/scheduled (by default)
I have a simple block agenda view that I use with a script and conky to display as on my background. It's like so: -- (setq org-agenda-custom-commands '((e Export ((agenda ((org-agenda-ndays 7))) (todo next ((org-agenda-overriding-header Next Actions) )) -- I guess I must not usually use deadlines or schedules with next actions, as when I just did, the next action stopped being shown in that agenda view. Here are my todo-related options from .emacs: -- ;; todos (setq org-agenda-todo-ignore-scheduled (quote future)) (setq org-agenda-todo-ignore-deadlines (quote far)) (setq org-agenda-skip-scheduled-if-done t) (setq org-agenda-skip-deadline-if-done t) (setq org-todo-keywords '((sequence todo(t) next(n) proj(p) | waiting(w@/@) done(d) cancelled(c@/@ -- Turning off both todo-ignore-scheduled and todo-ignore-deadlines above produces the same effect. Removing the scheduled or deadlined date settings from the headlines shows it in the agenda view as expected. I also looked at the org-agenda-skip-entry-if settings... the problem is that I want *all* next todos to show, whether scheduled, deadlined or not. The settings seem mutually exclusive and I'm not sure what the default is. I did verify that using =org-agenda-entry-types'(:deadline)= works... I'm not sure why I need to do this. I assumed the default is that I want to see *all* of my listed entry types and only use a skip or limiting function if I want to. Thanks, John
Re: [O] LOGBOOK opening
pin...@iro.umontreal.ca (François Pinard) writes: Bastien b...@altern.org writes: The default behavior of SPC in the agenda view stays the same, but you can now also use `C-u SPC' to avoid unfolding of logbooks and drawers. snip P.S. While I'm happy, I think that for the consistency and elegance of Org mode, `C-u SPC' and `SPC' meanings should be reversed. The manual still defines drawers by this intent of keeping their contents hidden. If you're going to make this change then maybe provide a new variable so the prefix behaviour can be selected. SPC in the agenda (without a prefix) is the only way I know of to quickly see the reason why a WAITING task is waiting and having to hit the prefix each time I want to look at one of those is going to make it less convenient (for me). Just my 2 cents :) Regards, Bernt
Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails
If /inline blocks/ above don't replace their results above then that is
expected. If you can find instances where call lines or blocks don't
replace their results then that is a bug.
Yes, I was finding that neither inline nor regular blocks replace: run
the following with C-c C-v b a few times and look at the block output
-snip--
#+property: session *R-babel*
#+NAME: foo
#+HEADER: :var a=a1.png
#+BEGIN_SRC R :results output silent
cat(in foo block\n)
cat.a - function() { cat(a,\n,sep=) }
cat.a()
#+END_SRC
#+call: foo(a=a1.png)
#+begin_src R :results output raw replace :exports results
cat.a()
#+end_src
--snip-
Finally, in the last file of my original message I try to use #+call's
everywhere instead of source blocks. Cleaned up example is pasted
below. It looks broken (the first #+call bar is out of order, the
second and third #+call bar's don't run), see
http://pastebin.com/LqYK0Ps2 with my annotation where the output looks
broken
Ah, this is a different issue, but one which should be discussed. I'm
happy we're working through all of these before the Emacs24 release.
The problem below is not order of evaluation but rather insertion of
results. The elements are evaluated in order, but the results from the
bar() call lines are all inserted in the same place. In the current
code the raw text of the call line is used to insert the results, so
identical call lines replace each other's results.
...
Although the above is a workaround, it may be cumbersome. I'm on the
fence about whether to try to change the existing behavior. If each
identical call line is thought of as a token of the same call then maybe
it makes sense to have only one location in which to insert the results
of that call (also it is possible that some users are relying on the
current behavior). That said it is certainly confusing...
I see no reason why we should think of each call line as a token of
the same call; do you? In fact, it's probably a fundamentally flawed
way of thinking, because nothing guarantees that the global state of
the session hasn't changed between call invocations. In fact, in that
sense, we can't even technically regard the _same_ call line as being
a token of the same call, if we consider it at different times :)
Referring to what I said in another thread (the principle of least
surprise): it makes a lot of sense for the call lines to behave the
same way a function call, or a source() statement would behave in the
interpreter session of the original language. From that perspective,
the current behavior seems wrong. Can you come up with a scenario /
usage pattern where the current behavior is more desirable?
--Leo
Re: [O] [BUG] Inconsistency in src block hiding
Bernt Hansen be...@norang.ca wrote: Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Bernt Hansen be...@norang.ca writes: I tried :results wrap but that didn't work for me. If I add RESULTS to my list of drawers then I can hide the block with TAB but I can't export my diagrams to HTML anymore which isn't very satisfying. Why can't you? Wouldn't it be related to drawers configuration (org-export-with-drawers for example)? Yes... but I don't think I can configure which drawers I get, and I don't want my LOGBOOK drawer with all my clock lines in my export. The following exports JUNK drawers but not GARBAGE drawers - isn't that exactly what you want? or am I misunderstanding? --8---cut here---start-8--- #+DRAWERS: JUNK GARBAGE #+OPTIONS: d:(JUNK) * foo hunoz :GARBAGE: what garbage is hidden here :END: bar :JUNK: Hide some junk in here. :END: baz --8---cut here---end---8--- Nick
[O] How do I create a drawer?
The only way I found so far to create a drawer is to actually type the damn thing in (I'm talking about my own drawers, not the special drawers that org knows something about). I didn't find any utility functions to insert drawers (except for :PROPERTIES:), and somewhat to my surprise, completion does not seem to work for drawer names: I expected typing a colon and M-TAB would allow me to use drawer names for completion, but it seems to only care about property keys, even if I'm not in the context of a :PROPERTIES: drawer. Am I missing something? Thanks, Nick
[O] org-insert-timestamp issue
Hi guys, I have bound org-insert-timestamp to C-c C-y, like so: (global-set-key (kbd C-c C-y) (lambda() (interactive) (org-insert-time-stamp nil t nil nil nil nil))) However, once in an org-mode buffer, when I press C-c C-y, I get the following in the mini-buffer: if: Not at a time-stamp range, and none found in current line What does that mean and how could I fix it so that the current timestamp is inserted (current datetime)? Thanks in advance, -Marcelo.
[O] elisp: link type isn't working
I've been using an elisp function to open an encrypted file. I borrowed this setup from, I think, Sacha Chua's blog. It's worked unfailingly for at least a couple of years, until tonight. I keep some sensitive information in a file, junk.org. when encrypted using bcrypt, the file is renamed junk.org.bfe. In my init files is a little function that runs bcrypt on the file, prompting for the password: (defun open-encrypted-file (fname) (interactive FFind file: \n) (let ((buf (create-file-buffer fname))) (shell-command (concat echo (read-passwd Decrypt password: ) | bcrypt -o fname) buf) (set-buffer buf) (kill-line)(kill-line) (toggle-read-only) (not-modified)b) ) I use a file of links as a directory to some of my projects. In this file is a headling that stores this link (an org file): [[elisp:(open-encrypted-file ~/WB/org/junk.org.bfe)][PassWord]] Anymore, as of today, when I try to run this link, the following is received: Symbol's function definition is void: org-in-clocktable-p I don't do anything with clocks. Can someone suggest what might be going on? Alan Davis
[O] overruling subscripts in latex export
I'm documenting some code including lists of parameters. These have
underscores in them which I don't want to interpret as subscripts.
According to the manual I can overrule this behaviour with an option
but it looks like I'm doing something wrong.
Here is the test file
#+OPTIONS: ^:{}
#+TITLE: test file
- p_c_in :: this is the first parameter
- g_c_in :: and this is the second
And here is the exported latex
% Created 2012-01-25 Wed 12:04
\documentclass[11pt]{article}
% package includes deleted
\title{test file}
\author{Peter Rayner}
\date{25 January 2012}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\begin{description}
\item[p$_c$$_{\mathrm{in}}$] this is the first parameter
\item[g$_c$$_{\mathrm{in}}$] and this is the second
\end{description}
\end{document}
Note those $ signs in the \item brackets. I would rather see
p\_c\_in or \verb|p_c_in|
I am probably misunderstanding how to set the option, could someone
please explain?
This is with
Org-mode version 7.5 (release_7.8.03.74.gd6e40f)
Thanks in advance
Peter
--
Peter Rayner
room 343
School of Earth Sciences, University of Melbourne, 3010, Vic, Australia
tel: work: +61 (0)3 8344 9708; fax: +61 (0)3 8344 7761
mobile +61 402 752 379, skype: petermorag
mail-to: pray...@unimelb.edu.au
and
CLIMMOD ENGINEERING
http://www.climmod.com
mail-to: peter.ray...@climmod.com
Re: [O] org-insert-timestamp issue
Marcelo de Moraes Serpa celose...@gmail.com wrote: --485b393aac6dde430a04b7500c79 Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I have bound org-insert-timestamp to C-c C-y, like so: (global-set-key (kbd C-c C-y) (lambda() (interactive) (org-insert-time-stamp nil t nil nil nil nil))) However, once in an org-mode buffer, when I press C-c C-y, I get the following in the mini-buffer: if: Not at a time-stamp range, and none found in current line What does that mean and how could I fix it so that the current timestamp is inserted (current datetime)? Org-mode rebinds C-c C-y to org-evaluate-time-range, so you are not calling the function that you think you are calling when you press C-c C-y in an org-mode buffer. It only works in *other* buffers :-) If you don't care about org-evaluate-time-range, you can probably rebind C-c C-y in a hook: (add-hook 'org-mode-hook (function (lambda () (local-set-key (kbd C-c C-y) (lambda() (interactive) (org-insert-time-stamp nil t nil nil nil nil)) Nick
Re: [O] org-insert-timestamp issue
Hi Nick, thank you very much! Why does org rebinds C-c C-y to that function? Is that a default binding for org? Marcelo. On Tue, Jan 24, 2012 at 7:46 PM, Nick Dokos nicholas.do...@hp.com wrote: Marcelo de Moraes Serpa celose...@gmail.com wrote: --485b393aac6dde430a04b7500c79 Content-Type: text/plain; charset=ISO-8859-1 Hi guys, I have bound org-insert-timestamp to C-c C-y, like so: (global-set-key (kbd C-c C-y) (lambda() (interactive) (org-insert-time-stamp nil t nil nil nil nil))) However, once in an org-mode buffer, when I press C-c C-y, I get the following in the mini-buffer: if: Not at a time-stamp range, and none found in current line What does that mean and how could I fix it so that the current timestamp is inserted (current datetime)? Org-mode rebinds C-c C-y to org-evaluate-time-range, so you are not calling the function that you think you are calling when you press C-c C-y in an org-mode buffer. It only works in *other* buffers :-) If you don't care about org-evaluate-time-range, you can probably rebind C-c C-y in a hook: (add-hook 'org-mode-hook (function (lambda () (local-set-key (kbd C-c C-y) (lambda() (interactive) (org-insert-time-stamp nil t nil nil nil nil)) Nick
[O] typo in org.texi
Hi. Bastien,
Japanese translation team of the manual found a small typo in org.texi.
Please check the attached patch.
Best regards,
Takaaki Ishikawa
@@ -15246,7 +15246,7 @@ not accept any arguments, and return the full link with
prefix.
@vindex org-ctrl-c-ctrl-c-hook
Org has several commands that act differently depending on context. The most
-important example it the @kbd{C-c C-c} (@pxref{The very busy C-c C-c key}).
+important example is the @kbd{C-c C-c} (@pxref{The very busy C-c C-c key}).
Also the @kbd{M-cursor} and @kbd{M-S-cursor} keys have this property.
Add-ons can tap into this functionality by providing a function that detects
Re: [O] Question about Sorting All Day Events in Agenda View
Thank you. I will take a look at this. Eric S Fraga wrote, On 01/24/2012 11:22 AM: Tatsuhito Koya tkoy...@gmail.com writes: Hello, I use Org-Mode with Calendar/Diary integration turned on. This works well for me, but the only issue I have is that in the agenda view, all day events such as holidays and anniversaries are displayed at the bottom. I have many tasks, so sometimes I need to scroll down quite a bit to see those events. Is there a way to put them at the top? Have a look at ,[ C-h v org-agenda-sorting-strategy RET ] | org-agenda-sorting-strategy is a variable defined in `org-agenda.el'. | Its value is ((agenda habit-down time-up priority-down category-keep) | (todo priority-down category-keep) | (tags priority-down category-keep) | (search category-keep)) | | | Documentation: | Sorting structure for the agenda items of a single day. | This is a list of symbols which will be used in sequence to determine | if an entry should be listed before another entry. The following | symbols are recognized: | | time-upPut entries with time-of-day indications first, early first | time-down Put entries with time-of-day indications first, late first | category-keep Keep the default order of categories, corresponding to the |sequence in `org-agenda-files'. | category-upSort alphabetically by category, A-Z. | category-down Sort alphabetically by category, Z-A. | tag-up Sort alphabetically by last tag, A-Z. | tag-down Sort alphabetically by last tag, Z-A. | priority-upSort numerically by priority, high priority last. | priority-down Sort numerically by priority, high priority first. | todo-state-up Sort by todo state, tasks that are done last. | todo-state-downSort by todo state, tasks that are done first. | effort-up Sort numerically by estimated effort, high effort last. | effort-downSort numerically by estimated effort, high effort first. | user-defined-upSort according to `org-agenda-cmp-user-defined', high last. | user-defined-down Sort according to `org-agenda-cmp-user-defined', high first. | habit-up Put entries that are habits first | habit-down Put entries that are habits last | alpha-up Sort headlines alphabetically | alpha-down Sort headlines alphabetically, reversed | | The different possibilities will be tried in sequence, and testing stops | if one comparison returns a not-equal. For example, the default | '(time-up category-keep priority-down) | means: Pull out all entries having a specified time of day and sort them, | in order to make a time schedule for the current day the first thing in the | agenda listing for the day. Of the entries without a time indication, keep | the grouped in categories, don't sort the categories, but keep them in | the sequence given in `org-agenda-files'. Within each category sort by | priority. | | Leaving out `category-keep' would mean that items will be sorted across | categories by priority. | | Instead of a single list, this can also be a set of list for specific | contents, with a context symbol in the car of the list, any of | `agenda', `todo', `tags', `search' for the corresponding agenda views. | | Custom commands can bind this variable in the options section. | | You can customize this variable. | | [back] ` HTH, eric
Re: [O] org-insert-timestamp issue
Marcelo de Moraes Serpa celose...@gmail.com wrote: Why does org rebinds C-c C-y to that function? Is that a default binding for org? Yes - see line 17340 in org.el.
Re: [O] [BUG] Inconsistency in src block hiding
Nick Dokos nicholas.do...@hp.com writes: Bernt Hansen be...@norang.ca wrote: Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Bernt Hansen be...@norang.ca writes: I tried :results wrap but that didn't work for me. If I add RESULTS to my list of drawers then I can hide the block with TAB but I can't export my diagrams to HTML anymore which isn't very satisfying. Why can't you? Wouldn't it be related to drawers configuration (org-export-with-drawers for example)? Yes... but I don't think I can configure which drawers I get, and I don't want my LOGBOOK drawer with all my clock lines in my export. The following exports JUNK drawers but not GARBAGE drawers - isn't that exactly what you want? or am I misunderstanding? #+DRAWERS: JUNK GARBAGE #+OPTIONS: d:(JUNK) * foo hunoz :GARBAGE: what garbage is hidden here :END: bar :JUNK: Hide some junk in here. :END: baz Nick Well sort of... except it was a wrapped PlantUML graphic which in a drawer doesn't display inline in my HTML export. :) I admit I didn't try hard to fix it though. -Bernt
Re: [O] overruling subscripts in latex export
Peter Rayner pray...@unimelb.edu.au wrote:
I'm documenting some code including lists of parameters. These have
underscores in them which I don't want to interpret as subscripts.
According to the manual I can overrule this behaviour with an option
but it looks like I'm doing something wrong.
Here is the test file
#+OPTIONS: ^:{}
#+TITLE: test file
- p_c_in :: this is the first parameter
- g_c_in :: and this is the second
...
\begin{description}
\item[p$_c$$_{\mathrm{in}}$] this is the first parameter
\item[g$_c$$_{\mathrm{in}}$] and this is the second
\end{description}
I get
,
| \begin{description}
| \item[p\_{}c\_{}in] this is the first parameter
| \item[g\_{}c\_{}in] and this is the second
| \end{description}
`
which is what's expected. It might be that you didn't update the setup
of the buffer after you added the #+OPTIONS line (just press C-c C-c on
it). Equivalently, kill the buffer and find-file again: the option should
be active.
Assuming of course that you have a reasonably modern version of org. Mine is
Org-mode version 7.8.03 (release_7.8.03.230.g67cb2.dirty)
(which includes a few local patches)
Nick
Re: [O] elisp: link type isn't working
Alan E. Davis lngn...@gmail.com wrote: --f46d0442829ce6a93e04b750a2ca Content-Type: text/plain; charset=ISO-8859-1 I've been using an elisp function to open an encrypted file. I borrowed this setup from, I think, Sacha Chua's blog. It's worked unfailingly for at least a couple of years, until tonight. I keep some sensitive information in a file, junk.org. when encrypted using bcrypt, the file is renamed junk.org.bfe. In my init files is a little function that runs bcrypt on the file, prompting for the password: (defun open-encrypted-file (fname) (interactive FFind file: \n) (let ((buf (create-file-buffer fname))) (shell-command (concat echo (read-passwd Decrypt password: ) | bcrypt -o fname) buf) (set-buffer buf) (kill-line)(kill-line) (toggle-read-only) (not-modified)b) ) I use a file of links as a directory to some of my projects. In this file is a headling that stores this link (an org file): [[elisp:(open-encrypted-file ~/WB/org/junk.org.bfe)][PassWord]] Anymore, as of today, when I try to run this link, the following is received: Symbol's function definition is void: org-in-clocktable-p I don't do anything with clocks. Can someone suggest what might be going on? M-x toggle-debug-on-error and post the backtrace. Nick
Re: [O] overruling subscripts in latex export
Yes, the problem was, indeed, that I had forgotten I needed to activate the option with C-c C-c. Many thanks Peter -- Peter Rayner room 343 School of Earth Sciences, University of Melbourne, 3010, Vic, Australia tel: work: +61 (0)3 8344 9708; fax: +61 (0)3 8344 7761 mobile +61 402 752 379, skype: petermorag mail-to: pray...@unimelb.edu.au and CLIMMOD ENGINEERING http://www.climmod.com mail-to: peter.ray...@climmod.com
Re: [O] elisp: link type isn't working
Nick Dokos nicholas.do...@hp.com wrote: Alan E. Davis lngn...@gmail.com wrote: [[elisp:(open-encrypted-file ~/WB/org/junk.org.bfe)][PassWord]] Anymore, as of today, when I try to run this link, the following is received: Symbol's function definition is void: org-in-clocktable-p M-x toggle-debug-on-error and post the backtrace. Never mind: you can probably work around the problem by adding (require 'org-clock) after org initialization in your .emacs (or wherever). If that works, then we can worry about why it is needed. Nick
[O] Indenting source code blocks in lists
Greetings. I am a big fan of org mode, but occasionally I feel that it is quite difficult to figure out how to do a relatively simple task. So sorry for this newbie question. The manual clearly states the following: Since indentation is what governs the structure of these lists, many structural constructs like #+BEGIN_... blocks can be indented to signal that they belong to a particular item. Ok. By searching in Emacs for different commands containing indent I was able to find out that pressing C-j in a list item indents the next line so that a subsequently written source block would also be indented. But let us assume that I already have a source block, and it is not indented correctly; what is the easy way to indent this block in a list? (I can always keep pressing spacebar, but it does not feel very intelligent.) -- Jarmo
Re: [O] LOGBOOK opening
Hi Bernt, Bernt Hansen be...@norang.ca writes: If you're going to make this change then maybe provide a new variable so the prefix behaviour can be selected. SPC in the agenda (without a prefix) is the only way I know of to quickly see the reason why a WAITING task is waiting and having to hit the prefix each time I want to look at one of those is going to make it less convenient (for me). I'm reluctant to create a new variable just for this. I documented the existence of C-u SPC in a footnote in the manual, so people won't have wrong expectations. -- Bastien
Re: [O] org-insert-timestamp issue
Hi Marcelo, Marcelo de Moraes Serpa celose...@gmail.com writes: Why does org rebinds C-c C-y to that function? Is that a default binding for org? Yes. But `C-c y' is free. HTH, -- Bastien
Re: [O] typo in org.texi
Hi Takaaki, Takaaki ISHIKAWA tak...@ieee.org writes: Japanese translation team of the manual found a small typo in org.texi. Please check the attached patch. Fixed, thanks. And hello to the team! Best, -- Bastien
Re: [O] Indenting source code blocks in lists
Hi Jarmo, Jarmo Hurri jarmo.hu...@syk.fi writes: But let us assume that I already have a source block, and it is not indented correctly; what is the easy way to indent this block in a list? (I can always keep pressing spacebar, but it does not feel very intelligent.) I select the region, then `C-x r t' to insert the whitespaces. But I don't feel very clever neither, we should have a better way for this -- something that deactivate folding and indent to the beginning of the list item above. -- Bastien
