[O] define a new export backend
Hi, I try to define a new export backend in the new export framework. My export backend should behaves like the html except that it transcodes *bold* differently. I try to following the Worg tutorial http://orgmode.org/worg/dev/org-export-reference.html , ox-html.el and use org-export-define-derived-backend. I can see the new backend showing up in the export menu(C-c C-e), but my transcoder for bold is not used. Any help or reference pointer is appreciated. Shiyuan - (org-export-define-derived-backend 'my-html-enlish 'html :traslate-alist '((bold . my-org-html-english-bold)) :menu-entry '(?E Export to HTML-ENGLISH ((?H As HTML buffer my-org-html-english-export-as-html) ))) -- (defun my-org-html-english-export-as-html (optional async subtreep visible-only body-only ext-plist) This is almost copied from org-html-export-as-html except using my newly defined backend (interactive) (org-export-to-buffer 'my-html-enlish *Org HTML-ENG Export* async subtreep visible-only body-only ext-plist (lambda () (set-auto-mode t --- (defun my-org-html-english-bold (bold contents info) Transcode BOLD from Org to HTML. Intead of using ordinary bold, we use color to highlight the CONTENTS is the text with bold markup. INFO is a plist holding contextual information. (format span style=\color: #a020f0\ %s /span contents))
Re: [O] define a new export backend
Shiyuan gshy2...@gmail.com writes: Hi, I try to define a new export backend in the new export framework. My export backend should behaves like the html except that it transcodes *bold* differently. I try to following the Worg tutorial http://orgmode.org/worg/dev/org-export-reference.html , ox-html.el and use org-export-define-derived-backend. I can see the new backend showing up in the export menu(C-c C-e), but my transcoder for bold is not used. Any help or reference pointer is appreciated. Shiyuan - (org-export-define-derived-backend 'my-html-enlish 'html :traslate-alist '((bold . my-org-html-english-bold)) :translate-alist ? -- cheers, Thorsten
Re: [O] Bug: [PATCH] Make org-narrow-to-subtree usable out of Org mode [8.2.7b (release_8.2.7b-6-g07d470 @ /home/youngfrog/sourcetrees/org-mode/lisp/)]
Thorsten Jolitz tjol...@gmail.com writes: Nicolas Richard theonewiththeevill...@yahoo.fr writes: Thanks for the URL. The description looks great but why not patch outline.el instead of making it an external library ? Is there an incompatibility ? Well, outshine merges quite old extension libraries for outline like outline-magic (Carsten Dominik) and out-xtra (Per Abrahamsen) and adds lots of new stuff. Why did the old guys back then wrote extensions instead of patching outline? No idea ... Sorry, I only meant to speak about outline-magic. Thanks for the detailed descriptions though. -- Nico.
Re: [O] define a new export backend
Thorsten Jolitz tjol...@gmail.com writes: Shiyuan gshy2...@gmail.com writes: (org-export-define-derived-backend 'my-html-enlish 'html :traslate-alist '((bold . my-org-html-english-bold)) :translate-alist ? Perhaps org-export-define-derived-backend could do a sanity check that all keywords are known. use-package does that, and it has saved me multiple times ! Nicolas, what am I overlooking ? Modified lisp/ox.el diff --git a/lisp/ox.el b/lisp/ox.el index 03bd8bb..e931723 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -1187,9 +1187,9 @@ The back-end could then be called with, for example: \(org-export-to-buffer 'my-latex \*Test my-latex*\) (declare (indent 2)) - (let (blocks filters menu-entry options transcoders contents) + (let (blocks filters menu-entry options transcoders contents keyword) (while (keywordp (car body)) - (case (pop body) + (case (setq keyword (pop body)) (:export-block (let ((names (pop body))) (setq blocks (if (consp names) (mapcar 'upcase names) (list (upcase names)) @@ -1197,7 +1197,7 @@ The back-end could then be called with, for example: (:menu-entry (setq menu-entry (pop body))) (:options-alist (setq options (pop body))) (:translate-alist (setq transcoders (pop body))) -(t (pop body +(t (error Unknown keyword in `org-export-define-derived-backend': %s keyword (org-export-register-backend (org-export-create-backend :name child :parent parent -- Nico.
Re: [O] define a new export backend
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Perhaps org-export-define-derived-backend could do a sanity check that all keywords are known. Good idea, as long as `org-export-define-backend' does the same. - (let (blocks filters menu-entry options transcoders contents) + (let (blocks filters menu-entry options transcoders contents keyword) KEYWORD should be let-bound within the while loop. (while (keywordp (car body)) - (case (pop body) + (case (setq keyword (pop body)) (while (keywordp (car body)) (let ((keyword (pop body))) (case keyword (...) (t (error Unknown keyword: %s keyword) Regards, -- Nicolas Goaziou
Re: [O] [BUG] org-html export does not put section numbers in div id
Hello, Matt Lundin m...@imapmail.org writes: Take the following file: --8---cut here---start-8--- #+options: num:nil * Headline ** Subheading * Another headline --8---cut here---end---8--- When exported to html, the section headings are not numbered, as expected. However, the section numbers are missing from the outline container divs, which look like this: div id=outline-container-sec- class=outline-2 As a result, the table of contents links do not work. This should be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou
Re: [O] [POLL] Syntax change: make \[...\] non-inline (+1)
Federico Beffa be...@ieee.org writes: Who is entitled to vote? If I am then here is my vote in favor for the following reasons: 1. the construct \[...\] has been defined in LaTeX for equations which must stand out and therefore belong on separate lines. It would therefore make sense to conform to the borrowed syntax. Background: It works sensibly in latex-mode. If your text is My displayed \[equation\] is here M-q will make it My displayed \[equation\] is here But My displayed \[equation\] is here Is unaltered by M-q (though it was not obvious to me how tex-mode.el implemented this). I didn't read the other thread is details, but it seems the most sensible thing to do is alter the org fill function(s). These seems to rely on org-element, though, and I'm guessing that is why a syntax change is necessary, yes? —Rasmus -- You people at the NSA are becoming my new best friends!
Re: [O] define a new export backend
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Good idea, as long as `org-export-define-backend' does the same. Oops, I forgot to remove the verbosity (initially I had wrote it as a (warn ...)). Here's an updated patch. From 117623cec251cd036b601e2481643296cc4e2c37 Mon Sep 17 00:00:00 2001 From: Nicolas Richard theonewiththeevill...@yahoo.fr Date: Thu, 31 Jul 2014 10:48:54 +0200 Subject: [PATCH] Signal an error if keyword is unknown while defining backends * lisp/ox.el (org-export-define-backend): (org-export-define-derived-backend): Signal an error if keyword is unknown --- lisp/ox.el | 36 +++- 1 file changed, 19 insertions(+), 17 deletions(-) diff --git a/lisp/ox.el b/lisp/ox.el index 03bd8bb..e2965c4 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -1118,14 +1118,15 @@ keywords are understood: (declare (indent 1)) (let (blocks filters menu-entry options contents) (while (keywordp (car body)) - (case (pop body) -(:export-block (let ((names (pop body))) - (setq blocks (if (consp names) (mapcar 'upcase names) - (list (upcase names)) - (:filters-alist (setq filters (pop body))) - (:menu-entry (setq menu-entry (pop body))) -(:options-alist (setq options (pop body))) -(t (pop body + (let ((keyword (pop body))) + (case keyword + (:export-block (let ((names (pop body))) + (setq blocks (if (consp names) (mapcar 'upcase names) + (list (upcase names)) + (:filters-alist (setq filters (pop body))) + (:menu-entry (setq menu-entry (pop body))) + (:options-alist (setq options (pop body))) + (t (error Unknown keyword: %s keyword) (org-export-register-backend (org-export-create-backend :name backend :transcoders transcoders @@ -1189,15 +1190,16 @@ The back-end could then be called with, for example: (declare (indent 2)) (let (blocks filters menu-entry options transcoders contents) (while (keywordp (car body)) - (case (pop body) - (:export-block (let ((names (pop body))) - (setq blocks (if (consp names) (mapcar 'upcase names) - (list (upcase names)) -(:filters-alist (setq filters (pop body))) - (:menu-entry (setq menu-entry (pop body))) -(:options-alist (setq options (pop body))) -(:translate-alist (setq transcoders (pop body))) -(t (pop body + (let ((keyword (pop body))) + (case keyword + (:export-block (let ((names (pop body))) + (setq blocks (if (consp names) (mapcar 'upcase names) + (list (upcase names)) + (:filters-alist (setq filters (pop body))) + (:menu-entry (setq menu-entry (pop body))) + (:options-alist (setq options (pop body))) + (:translate-alist (setq transcoders (pop body))) + (t (error Unknown keyword: %s keyword) (org-export-register-backend (org-export-create-backend :name child :parent parent -- 1.8.5.5 -- Nico.
Re: [O] proposal for improved integration of cdlatex
Thanks for the suggestion. Please find attached the improved patch. Regards, Federico On Wed, Jul 30, 2014 at 10:25 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Hello, Federico Beffa be...@ieee.org writes: + (save-excursion +(org-mark-element) +(org-indent-region (point) (mark The function shouldn't set the mark. The following should be enough: (let ((element (org-element-at-point))) (when element (org-indent-region (org-element-property :begin element) (org-element-property :end element Regards, -- Nicolas Goaziou 0001-org.el-add-function-to-indent-environment-inserted-b.patch Description: Binary data
[O] Tracking time estimates for incomplete tasks
(Apologies if you're received this message already - I can't seem to get the mailing list to accept my emails) Hi all, I've been using org-mode to track the time spent on various tasks in a project, by clocking work time. I'm now planning additional tasks, and for these new tasks I am starting to add time estimates. The columnview dynamic block gives a nice summary of the time I've spent on tasks, and the time estimates. I'm interested in tracking the time estimates for only the incomplete tasks. I've created an additional column for this in the columnview table. Is there a way to add up the estimated times of only the incomplete tasks? Maybe a table formula could populate the additional column using this pseudo-code: if Status == TODO/NEXT then print estimated time else print 0 and then the sum could be calculated. Note that the time estimates can be specified in hours or days (1 day = 7 hours). The table already converts the clocked times and the time estimates into days using this rule, but the formula would have to handle it as well. A metric I would be interested in for tracking progress is (sum of time estimates for all incomplete tasks) / ((sum of time estimates for all incomplete tasks) + (clocked time of all completed tasks)), so maybe the table could calculate this as well. Hope this makes sense. Regards, Dan
Re: [O] allow multiline #+BIND
Hello, Vladimir Alexiev vladimir.alex...@ontotext.com writes: It would be nice to allow multiline BINDs. I'd much rather write this than put it all on one line: This was suggested already for other keywords, e.g., MACRO. and CALL (http://permalink.gmane.org/gmane.emacs.orgmode/69326). The usual continuation syntax of backslash before the EOL can be used. This can be an option. What would be needed is an unambiguous syntax (e.g., what happens to lines ending with a backslash, without meaning a continuation?). Bonus points if it is elegant, too. Or else, a new keyword #+BIND1: for each continuation line. No, BIND1 is also a valid keyword name. This could introduce a clash. The function to fix is ox.el::org-export--list-bound-variables No, keyword parsing happens in `org-element-keyword-parser' and `org-element-babel-call-parser' for the special #+CALL: keyword. Regards, -- Nicolas Goaziou
[O] Using org-mode for project replanning
Hi all,
I've been using org-mode to track the time spent on various tasks in a
project. I'm now planning additional tasks, and for these new tasks I am
adding time estimates. The columnview dynamic block gives a nice summary of
the time I've spent on tasks and the time estimates.
I'm specifying the time estimates in hours and days. These are the settings
I'm using, although I'm just experimenting with this at the moment
(setq org-global-properties (quote ((Effort_ALL . 1:00 2:00 3:00 4:00
5:00 6:00 .25d .5d 1d 2d 3d 4d 5d 1w 2w 3w 4w 0:00)
(STYLE_ALL . habit
I am using the following property to set up the column view.
:COLUMNS: %80ITEM(Task) %TODO(Status) %Effort(Estimated time){:}
%CLOCKSUM(Actual time) %10Effort(Outstanding){:}
What I'm interested in tracking is how much time the outstanding tasks will
take - this should go in the 'Outstanding' column. Is there a way to print
the estimated time for outstanding tasks only? Maybe a table formula would
work a bit like if Status == TODO then print estimated time else print 0.
It's a bit more complicated than it first looks because of how estimates in
days and weeks are interpreted.
Any ideas on how to populate the 'Outstanding' column?
Additionally, if possible, is there a way to make the table contain just
the outstanding tasks?
Many thanks.
Re: [O] Enabling another language in org-babel
Dear Ista,
I don't know if Bastien has already responded to your private message
(if so, please disregard this), but for what it's worth, it looks like
you are doing everything right to me. I am not an org-mode developer
so I can't speak with 100% certainty, but it looks like a permissions
issue on the org-mode.org side (read: your key hasn't been added just
quite yet) and nothing on your side.
Good luck, and best wishes.
Jay
On 07/30/14 12:47, Ista Zahn wrote:
I've made the suggested changes, with the exception of the part of
Emacs bit, as this should go in contrib not core.
I asked Bastien privately about getting access to the git repository,
but will ask here as well: When I run 'git clone
orgm...@orgmode.org:org-mode.git' I get a response saying
Permission denied (publickey).
fatal: Could not read from remote repository
Does that mean my key wasn't properly added, or did I miss some required
set-up?
Best,
Ista
On Tue, Jul 29, 2014 at 10:36 AM, Bastien b...@gnu.org wrote:
Hi Ista,
some comments on the code below.
Ista Zahn istaz...@gmail.com writes:
;; Copyright (C) 2014 Ista Zahn
;; Author: Ista Zahn, based on ob-julia.el by G. Jay Kerns, and ob-R.el
;; by Eric Schulte and Dan Davison
You need to reformat this -- see files with multiple authors in Org or
in Emacs.
;; This file is not part of GNU Emacs.
We plan to add this to Org's core, so this will be part of Emacs.
;; Stata and ESS are required.
Maybe add some links for the requirements.
(defcustom org-babel-stata-command inferior-STA-program-name
Name of command to use for executing stata code.
:group 'org-babel
:version 24.4
:package-version '(Org . 8.0)
^^^
This needs to be 8.3
;; The following was a very complicated write object command
;; The replacement needs to add error catching
;(defvar org-babel-stata-write-object-command
{function(object,transfer.file){object;invisible(if(inherits(try({tfile-tempfile();write.table(object,file=tfile,sep=\\\t\,na=\nil\,row.names=%s,col.names=%s,quote=FALSE);file.rename(tfile,transfer.file)},silent=TRUE),\try-error\)){if(!file.exists(transfer.file))file.create(transfer.file)})}}(object=%s,transfer.file=\%s\))
Maybe simply remove this, or make it more readable.
Thanks in advance for this contribution!
--
Bastien
[O] Tracking time estimates for incomplete tasks
Hi all, I've been using org-mode to track the time spent on various tasks in a project, by clocking work time. I'm now planning additional tasks, and for these new tasks I am starting to add time estimates. The columnview dynamic block gives a nice summary of the time I've spent on tasks, and the time estimates. I'm interested in tracking the time estimates for only the incomplete tasks. I've created an additional column for this in the columnview table. Is there a way to add up the estimated times of only the incomplete tasks? Maybe a table formula could populate the additional column using this pseudo-code: if Status == TODO/NEXT then print estimated time else print 0 and then the sum could be calculated. Note that the time estimates can be specified in hours or days (1 day = 7 hours). The table already converts the clocked times and the time estimates into days using this rule, but the formula would have to handle it as well. A metric I would be interested in for tracking progress is (sum of time estimates for all incomplete tasks) / ((sum of time estimates for all incomplete tasks) + (clocked time of all completed tasks)), so maybe the table could calculate this as well. Hope this makes sense. Regards, Dan
Re: [O] [PATCH] ob-java.el: Add `:var' variables import
Hi Bastien, On Mon, Jul 28, 2014 at 4:25 PM, Bastien b...@gnu.org wrote: Bart Post bart.p...@gmail.com writes: Thanks for your reply! I already started the copyright assignment process, for now I need to wait for a disclaimer form from my employer, but I will notify you as soon as there is progress. Did you get this sorted out? Not yet, sorry. But I'm on it! While discussing the patch with a roommate, we came to the conclusion that a java class which implements, extends or throws, may not compile correctly with the added data. So the patch will need some rework, or documentation about (im-)possible usage situations. Thanks for letting us know -- thanks! No problem, I hope to be able to help out there, too. Best, Bart
[O] [BUG] org-element-headline-parser - missing keyword in docstring
In docstring ,[ C-h f org-element-headline-parser RET ] | org-element-headline-parser is a compiled Lisp function in | `org-element.el'. | | (org-element-headline-parser LIMIT optional RAW-SECONDARY-P) | | Parse a headline. | | Return a list whose CAR is `headline' and CDR is a plist | containing `:raw-value', `:title', `:alt-title', `:begin', | `:end', `:pre-blank', `:contents-begin' and `:contents-end', | `:level', `:priority', `:tags', `:todo-keyword',`:todo-type', | `:scheduled', `:deadline', `:closed', `:archivedp', `:commentedp' | and `:footnote-section-p' keywords. | [...] ` property :post-blank is missing. -- cheers, Thorsten
Re: [O] [BUG] org-element-headline-parser - missing keyword in docstring
Hello, Thorsten Jolitz tjol...@gmail.com writes: In docstring ,[ C-h f org-element-headline-parser RET ] [...] property :post-blank is missing. Fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Enabling another language in org-babel
Hi Ista, Ista Zahn istaz...@gmail.com writes: I asked Bastien privately about getting access to the git repository, but will ask here as well: When I run 'git clone orgm...@orgmode.org:org-mode.git' I get a response saying Permission denied (publickey). fatal: Could not read from remote repository This should be fixed now, let me know, -- Bastien
Re: [O] [PATCH] ob-stata.el: new file for stata code evaluation
Hi Ista, Ista Zahn istaz...@gmail.com writes: Here is a patch (against master) adding babel support for evaluating stata code. As discussed in a previous thread[1] there is a lot of work that should be done to clean it up and make it more useful. It does work for basic code evaluation, so I'm submitting it here in the hope that others find it useful. Applied, thanks a lot! You might also consider adding examples and documentation on Worg. All best, -- Bastien
Re: [O] Enabling another language in org-babel
On Thu, Jul 31, 2014 at 6:52 AM, Bastien b...@gnu.org wrote: Hi Ista, Ista Zahn istaz...@gmail.com writes: I asked Bastien privately about getting access to the git repository, but will ask here as well: When I run 'git clone orgm...@orgmode.org:org-mode.git' I get a response saying Permission denied (publickey). fatal: Could not read from remote repository This should be fixed now, let me know, Yes working now, thank you! -- Bastien
Re: [O] define a new export backend
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Oops, I forgot to remove the verbosity (initially I had wrote it as a (warn ...)). Here's an updated patch. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] [bug, beamer] Frame parameters taken from example code block
Hello, Bastien b...@gnu.org writes: Well, we can poll users and see how inconvenient this change would be. (I'm certainly biased here, as I never use blank lines between the headline and the properties drawer.) Blank lines between the headline and the properties drawer is not enough, because you still have to `re-search-forward', possibly far away from the headline. A better place would be the line below planning info, if any, or below the headline otherwise. Regards, -- Nicolas Goaziou
[O] [babel] Shell session output problem
Hello, When running org-babel shell snippets in *session*, I stumbled upon the following problem: Output shown in my .org file is already formatted: 1. Starting white spaces are lost 2. All code before first , $ or # (prompt related?) is lost Here is a minimal example (run it twice, first time when opening a new session it is working) #+begin_src sh :results output :session org-sh-test echotoo$ foo echo too$ foo #+end_src #+RESULTS: : : foo : too$ foo Is there a way or some org-babel options to avoid this behavior? I see how this formatting can be beneficial in many cases, but this doesn't apply for mine. Best regards, Luka
[O] Launching Emacs org-mode commands from Windows 7 command line?
I want to use a shell command in Windows 7 command prompt (cmd.exe) to create a search agenda view in Emacs org-mode (in the active frame). I tried like that: emacsclient --eval (org-search-view nil search string) but with no success. In the command line I get the error message: *ERROR*: End of file during parsing And I get no a search or search result in Emacs org-mode. Any tips are appreciated. Im using Windows 7, Emacs 24.3 and org-mode 8.2.6 Kind regards Martin
[O] Export org-mode buffer to dynamic html document (collapse/expand details)
Hi, Im sorry, if this might be obvious, but I dont have much experience with org-mode export up to now and I urgently need to export much information from my notes and task lists in org-mode in a way that my colleagues (no experience with Emacs / org-mode at all) can use it during my absence. Therefore I need some advice from you: I have a lot of projects (hierarchically structured in headings with todo keywords, sub-headings, hyperlinks, notes, etc.) I want to export all this information into a text format to make it usable for my colleagues. However, there is A WHOLE LOT of text and to make it the least confusing possible, it would be great if the text below headings could be collapsed somehow or if there was an overview page listing all projects and some important sub-headings or remarks and a hyperlink pointing to the detailed notes concerning this project. Any hints appreciated Kind regards Martin
Re: [O] Export org-mode buffer to dynamic html document (collapse/expand details)
Martin Beck elwood...@web.de writes: Hi, I'm sorry, if this might be obvious, but I don't have much experience with org-mode export up to now and I urgently need to export much information from my notes and task lists in org-mode in a way that my colleagues (no experience with Emacs / org-mode at all) can use it during my absence. Therefore I need some advice from you: I have a lot of projects (hierarchically structured in headings with todo keywords, sub-headings, hyperlinks, notes, etc.) I want to export all this information into a text format to make it usable for my colleagues. However, there is A WHOLE LOT of text and to make it the least confusing possible, it would be great if the text below headings could be collapsed somehow or if there was an overview page listing all projects and some important sub-headings or remarks and a hyperlink pointing to the detailed notes concerning this project. Any hints appreciated I would recommend a look into https://github.com/SebastianRose/org-info-js/tree/master or http://orgmode.org/worg/code/org-info-js/index.org.html There are described various possible views in html with folding/unfolding, similar emacs folding. You can switch between the views with m, goto (n)ext or (p)revious item, help with ? IIRC You can realize this with the follwoing to lines in your org-file and export this to html with c-c c-e h h (or o): #+HTML_HEAD_EXTRA: link rel=stylesheet href=http://orgmode.org/worg/style/worg.css; type=text/css #+INFOJS_OPT: view:info toc:nil ftoc:yes ltoc:above mouse:underline buttons:0 path:http://orgmode.org/org-info.js The above lines make the toc flowing like www.orgmode.org/worg. The most important keys for navigating i would mention at the begin of the page. HTH, Robert
[O] Sort agenda tasks by most recent clock time
Is there a way to do this? I'd like to make a list of my TODOs in an agenda (say type 't'), And sort by time last clocked in (no clock time to the bottom) All the options in org-agenda-sorting-strategy appear to work on timestamps, not clocktime entries. Any ideas how this can be accomplished? Is there a relatively straightforward way to add say a 'LASTWORKED 2014-07-31 Thu 11:52' property with a hook to update in on clockout? Or do I need to tweak a setting to make org recognize the clock entries as time of day indicators? Thanks! Subhan Subhan Michael Tindall Program Analyst - FamilyCare Health Plans 825 NE Multnomah St, Suite 1400; Portland OR 97232 Direct: 503-471-3127 Fax: 503-471-3177 Email: subh...@familycareinc.orgmailto:subh...@familycareinc.org [Email-Signature-Logos June 20143] This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
Re: [O] Export org-mode buffer to dynamic html document (collapse/expand details)
I did a custom solution, very simple, with jQuery. You may use it: Demo: http://www.danielclemente.com/hacer/emacs.html Code: http://www.danielclemente.com/pagina/esquemadorg.js http://www.danielclemente.com/pagina/esquemadorg.css - The JS and CSS applies to the normal org export. - The index of contents is itself collapsable. - The hyperlinking was tricky because if the link destination is collapsed you have to open it automatically (including its parents). - There's a button to disable the outline (text: „ver todo seguido“) El Thu, 31 Jul 2014 17:50:03 +0200 Martin Beck va escriure: Hi, I'm sorry, if this might be obvious, but I don't have much experience with org-mode export up to now and I urgently need to export much information from my notes and task lists in org-mode in a way that my colleagues (no experience with Emacs / org-mode at all) can use it during my absence. Therefore I need some advice from you: I have a lot of projects (hierarchically structured in headings with todo keywords, sub-headings, hyperlinks, notes, etc.) I want to export all this information into a text format to make it usable for my colleagues. However, there is A WHOLE LOT of text and to make it the least confusing possible, it would be great if the text below headings could be collapsed somehow or if there was an overview page listing all projects and some important sub-headings or remarks and a hyperlink pointing to the detailed notes concerning this project. Any hints appreciated Kind regards Martin
Re: [O] Launching Emacs org-mode commands from Windows 7 command line?
On Thu 31 Jul 2014, Martin Beck wrote: I want to use a shell command in Windows 7 command prompt (cmd.exe) to create a search agenda view in Emacs org-mode (in the active frame). I tried like that: emacsclient --eval '(org-search-view nil search string)' but with no success. In the command line I get the error message: *ERROR*: End of file during parsing And I get no a search or search result in Emacs org-mode. Any tips are appreciated. I'm using Windows 7, Emacs 24.3 and org-mode 8.2.6 Kind regards Martin cmd.exe has strange quoting rules. Does this work for you ? emacsclient --eval (org-search-view nil search string) HTH AndyM
Re: [O] proposal to make C-c C-c not remove latex overlays
Bastien bzg at gnu.org writes: Hi Nick, Nick Dokos ndokos at gmail.com writes: getting rid of just latex fragment undoing in org-ctrl-c-ctrl-c and toggling with C-c C-x C-l is probably the best solution. Agreed, this is the case now in master. The docstring for `org-preview-latex-fragment' still says: The images can be removed again with \\[org-ctrl-c-ctrl-c]. Maybe change that to \\[org-preview-latex-fragment]? HTH, Chuck
Re: [O] define a new export backend
Oops, I've asked the dumpest question ever in the mailing list :) That's what happens when working late. Thanks for reply. On Thu, Jul 31, 2014 at 4:41 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Oops, I forgot to remove the verbosity (initially I had wrote it as a (warn ...)). Here's an updated patch. Applied. Thank you. Regards, -- Nicolas Goaziou
[O] Bug: org src block folds partially [8.2.6 (8.2.6-67-g9e09b2-elpa @ c:/Users/andrea/AppData/Roaming/.emacs.d/elpa/org-20140602/)]
Hi guys, I think I found a problem in folding a BEGIN_SRC block. When I: - create a BEGIN_SRC org block (let's call it the external BEGIN_SRC) - hit C-c ' to edit its contents - create two consecutive, non-nested BEGIN_SRC org blocks (let's call them the internal BEGIN_SRCs) - hit C-c ' to return back to the main org buffer - hit TAB on the external BEGIN_SRC to fold the whole block then the folding happens only for the first internal BEGIN_SRC block. Tentative guess: I suppose #+END_SRC is used as a regexp by the fold procedure, while something like [^,]#+END_SRC could be more appropriate. Can anyone please confirm if the described issue is reproducible? (if your answer is yes, but you think it's a very minor problem: I agree with you, it's just better if we know it :) Thanks for your attention, kindest regards. Andrea PS: a test case file is attached here: #+BEGIN_SRC org ,#+BEGIN_SRC org block1 ,#+END_SRC ,#+BEGIN_SRC org block2 ,#+END_SRC #+END_SRC Emacs : GNU Emacs 24.3.1 (i386-mingw-nt6.1.7600) of 2013-03-17 on MARVIN Package: Org-mode version 8.2.6 (8.2.6-67-g9e09b2-elpa @ c:/Users/andrea/AppData/Roaming/.emacs.d/elpa/org-20140602/)
[O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.
Hi all, i'm pleased to announce the initial release of org-vcard, a package for Org-based export and import of vCards: * Backwards-compatible with org-contacts.el. org-vcard comes with a built-in contacts style called 'flat', which adheres to org-contacts' method of structuring contacts and contact information. It not only supports the properties specified in org-contacts.el, but many other properties as well. * Basic support for vCard 4.0, 3.0 and 2.1. org-vcard is working towards full compliance with the vCard 4.0 (RFC 6350), 3.0 (RFC 2426 and RFC 4770) and 2.1 specifications. * New contacts style: 'tree'. org-vcard introduces a new style for Org contacts, called 'tree'. * Highly customisable, via Emacs' customize interface. Modify existing contact styles; change the labels used to map contact details in org-mode to various vCard properties/types, or add new ones. Create completely new contact styles by plugging in your own code to handle export and import. Further details are available on the GitHub page: https://github.com/flexibeast/org-vcard The package can be installed from MELPA, or downloaded and installed manually. Hope people find it useful! Alexis.
[O] [RFC] Rewrite `org-entry-properties' using parser
Hi List, here is my first take of rewriting `org-entry-properties'. The existing function predates the new parser and some Org variables, and thus does the parsing and the property classification itself. The new version leaves parsing to the parser and property classification (mostly) to existing Org variables, resulting in much simpler code. OTOH, the new version offers more fine-grained control over property selection. I was a bit unhappy when the use of property-drawers as simple key-val databases and meta-data stores for USERS was kind of deprecated with the introduction of the new parser (in favor of usage by the SYSTEM). This improved with introduction of the 'prop:t' export option, and the new version of `org-entry-properties' should be powerful and convenient enough to separate user and system data stored in the same property-drawers. Implementation goals were: 1. (almost) full backward-compability. The parser upcases user properties, thus case-sensitivity is lost after parsing and old applications that rely on the difference between foo, Foo and FOO as property keys will break 2. allow retrieving all property-classes defined in Org-mode separately 3. allow filtering out parser-specific properties 4. allow retrieving all non-org properties (user and application defined) 5. allow retrieving properties by regexp-matching, e.g. props prefixed with foo_ by application 'foo'. I did not bother to prepare a patch yet since this should be reviewed and tested: - Are some options useless? - Do the return values of the options make sense? - Is property-classification consistent (e.g. TODO in `org-special-properties', but :todo-keyword and :todo-type in the parse-tree)? - I actually reimplemented the docstring of the old function instead of the rather complicated code - did I get the semantics right? - are there bugs? - etc ... Here is an Org file with the new version of `org-entry-properties', helper functions and some 20 ERT-tests. Please have a look. * org-entry-properties ** new function (org.el) #+begin_src emacs-lisp (defun org-entry-properties (optional pom which specific) Get all properties of the entry at point-or-marker POM. This includes the TODO keyword, the tags, time strings for deadline, scheduled, and clocking, and any additional properties defined in the entry. The return value is an alist, except if WHICH has value `parser', then a plist filtered for the properties set by `org-element-parse-headline' is returned. Keys may occur multiple times if the property key was used several times. POM may also be nil, in which case the current entry is used. WHICH can have several meaningful values: - nil or `all' :: get all regular (non parser) properties - `special' :: get properties that are member of `org-special-properties' - `standard' :: get properties of that subclass - `parser' :: get properties set by parser (as plist) - `custom' :: get properties that are member of `org-custom-properties' - `default' :: get properties that are member of `org-default-properties' - `document' :: get properties that are member of `org-element-document-properties' - `file' :: get properties that are member of `org-file-properties' - `global' :: get properties that are member of `org-global-properties' - `global-fixed' :: get properties that are member of `org-global-properties-fixed' - `non-org' :: get properties that are not member of any of the preceeding classes (except `all') - any string :: get only exactly this property - form :: get properties string-matched by (rx-to-string form), with FORM being a regular expression in sexp form SPECIFIC can be a string, symbol or keyword, all types will be converted to an upcased string. It is the specific property we are interested in. This argument only exists for historical reasons and backward portability, since giving a string value to WHICH has the same effect as giving a value to SPECIFIC. However, if SPECIFIC is non-nil, it takes precedence over WHICH. (setq which (or which 'all)) (org-with-wide-buffer (org-with-point-at pom (when (and (derived-mode-p 'org-mode) (ignore-errors (org-back-to-heading t))) (let ((elem (org-element-at-point))) (when (eq (car elem) 'headline) (let* ((specific-prop (cond ((or (org-string-nw-p specific) (org-string-nw-p which)) (upcase (or (org-string-nw-p specific) (org-string-nw-p which ((keywordp specific) (car (org-split-string (format %s specific) :))) ((and (not (booleanp specific)) (symbolp specific)) (upcase (format %s specific))) (t nil)))
Re: [O] Export org-mode buffer to dynamic html document (collapse/expand details)
Martin Beck elwood...@web.de writes: Hi, I'm sorry, if this might be obvious, but I don't have much experience with org-mode export up to now and I urgently need to export much information from my notes and task lists in org-mode in a way that my colleagues (no experience with Emacs / org-mode at all) can use it during my absence. Therefore I need some advice from you: I have a lot of projects (hierarchically structured in headings with todo keywords, sub-headings, hyperlinks, notes, etc.) I want to export all this information into a text format to make it usable for my colleagues. However, there is A WHOLE LOT of text and to make it the least confusing possible, it would be great if the text below headings could be collapsed somehow or if there was an overview page listing all projects and some important sub-headings or remarks and a hyperlink pointing to the detailed notes concerning this project. This just sounds like a table of contents -- if you export to a format that supports hyperlinks, wouldn't a plain old TOC do?
Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.
Alexis flexibe...@gmail.com writes: * New contacts style: 'tree'. org-vcard introduces a new style for Org contacts, called 'tree'. I like store the contacts like tree, may be let org-contacts recognizes this tree is a important thing, are there any plans?
