Re: [O] Using link abbrevations for EXPORT_FILE_NAME ?

On 08/11/15 20:11, Nicolas Goaziou wrote: Hello, AW writes: on orgmode 8.3.2 I've got a large org-file. Offen, I need to export a subtree like this: - * Subtree to be exported :PROPERTIES: :EXPORT_FILE_NAME: /PATH/TO/FOLDER/filename

[O] #+SETUPFILE with #+TODO

Hi all With today's release_8.3.2-308-g6c1f63b when I open the attached org_todo_test.org when it is writable then the customized todo keyword CNCL is recognized, when the file is read only then not. I expect CNCL to be recognized as a todo keyword in both cases. Michael org_todo_setup.org

Re: [O] Emacs+org-mode in a Docker?

This sounds a lot like what I have in mind. Have you tried doing this yet? Grant Rettke writes: > On Wed, Nov 4, 2015 at 7:07 PM, John Kitchin wrote: >> Thanks for all the notes! It looks like a not too trivial exercise that >> might have to be a summer project for me.

Re: [O] Testers / Feedback wanted: Gantt charts via org-gantt.el

* Bernhard Schmitz wrote: > > Hi Karl, hi Eric, > > I know it has been a while. I was off-mailinglist for a couple of months. Sorry. > Karl: > >> Oh, I was too lazy to write a working example. >> >> ,[ working example ] >> | ** DONE My pretty task >>

Re: [O] Changes to contrib

Hi, Kosyrev Serge <_deepf...@feelingofgreen.ru> writes: > Rasmus writes: >> Serge Kosyrev <_deepf...@feelingofgreen.ru> writes: >>> I'm not sure how wise it would be to raise barriers for contribution, >>> given the current state of the thing.. >> >> I don't know what state you

Re: [O] Changes to contrib

Rasmus writes: > Kosyrev Serge <_deepf...@feelingofgreen.ru> writes: [..] >> I don't know what is the proper way to submit patches for the contrib/ >> directory, so I made a branch on github: >> >> https://github.com/deepfire/org-mode/commits/ox-taskjuggler-fixes >> >> Please, do

Re: [O] Changes to contrib

Rasmus writes: > Serge Kosyrev <_deepf...@feelingofgreen.ru> writes: >> I'm not sure how wise it would be to raise barriers for contribution, >> given the current state of the thing.. > > I don't know what state you refer to. Well, I couldn't use it, without significant tweaking.

Re: [O] Using link abbrevations for EXPORT_FILE_NAME ?

Am Sonntag, 8. November 2015, 20:11:23 schrieb Nicolas Goaziou: > Hello, > > AW writes: > > on orgmode 8.3.2 I've got a large org-file. Offen, I need to export a > > subtree like this: > > > > - > > * Subtree to be exported > > > > :PROPERTIES: >

Re: [O] generating org headings from a source block

Matt Price writes: > I would like to be able to insert into an org-buffer the text extracted from > a pdf file. PDF-Tools ( > https://github.com/politza/pdf-tools/) provides some excellent tools for > doing this.  I've written > (well, msotly stolen) a defun that finds all

Re: [O] BUG: emacs orgmode ob-R.el function org-babel-R-evaluate-session over aggressively performs "; ; cleanup extra prompts left in output" and a possible workaround

> [...] > > > > > > > [...] > > > > > > > > I've wondered if there is not a better way for Babel to share an > > > > interactive session with the user. For instance, if we wanted to > > > > support a new form of results processing on addition to value and > > > > output Namely,

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

On 2015-11-09, at 21:49, Nick Dokos wrote: > Marcin Borkowski writes: > >> On 2015-11-09, at 19:54, Martin Steffen wrote: >> >>> Hi, >>> >>> Perhaps it's not really a "fault" of org (nor of auctex), but both >>> things interact

Re: [O] Allowing loose ordering in Org files

On 09/11/15 21:04, Achim Gratz wrote: John Wiegley writes: You will find that the argument really wasn't about performance, but complexity. I can accept a complexity argument, I meant O() complexity, not implementation complexity. if my request were really "a separate code-path". I'm not

Re: [O] Allowing loose ordering in Org files

> Stelian Iancu writes: > John, if you end up writing an advice for this function, please share it > with the list, as I would like the 8.2 behavior as well (I unfortunately > don't know enough elisp and org internals to do such a thing). To Achim I would say that these

Re: [O] Changes to contrib

Hi, Rasmus writes: > Kosyrev Serge <_deepf...@feelingofgreen.ru> writes: >> The question is.. the only documentation for ox-taskjuggler that exists >> in Worg, seems to only cover the surface aspects of export -- none of >> the existing documentation touches on the multitude of

Re: [O] exporting from org-mode to latex

Hi Sharon, > I'm having a strange problem with exporting from org-mode to latex using > the latex back-end. When the file that I've written is exported to latex > and I look at the tex file that is created, I see that it has one > "\usepackage{grffile}" that I didn't place in my list to be

[O] exporting from org-mode to latex

I'm having a strange problem with exporting from org-mode to latex using the latex back-end. When the file that I've written is exported to latex and I look at the tex file that is created, I see that it has one "\usepackage{grffile}" that I didn't place in my list to be included. In fact, I'd

Re: [O] exporting from org-mode to latex

Sharon Kimble writes: > I'm having a strange problem with exporting from org-mode to latex using > the latex back-end. When the file that I've written is exported to latex > and I look at the tex file that is created, I see that it has one > "\usepackage{grffile}"

Re: [O] Allowing loose ordering in Org files (Was: bug in org-habits)

Hi John, 2015ko azaroak 9an, John Wiegley-ek idatzi zuen: [...] > Lately there seems to be a push to sacrifice some of this freedom in order to > gain efficiency and regularity. I imagine this is for the benefit of machine > parsers; but what if one doesn't use any machine parsers? I don’t

Re: [O] Allowing loose ordering in Org files

> Aaron Ecay writes: > Adding knobs to this parser increases the burden of those who have to build > and maintain it. Thank you for your reply, Aaron, I found it most illuminating. If the answer from the maintainers is "It's more work than we want to do", that's

[O] org export customization: why do #+EXCLUDE_TAGS: settings have no effect?

Hi, I want selective export in org (for instance, exporting to beamer/latex, and html etc). I seem to understand the "theory" but it seems not really to work for me. what _works_ is as follows: I set directly a corresponding variable, in particular, for instance, set it "hard" to (setq

[O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

Hi, Perhaps it's not really a "fault" of org (nor of auctex), but both things interact unfortunate. The reason is: when I export org to LaTeX, and I visit the latex file afterwards, I want that auctex/emacs is instructed about some facts. Thus I like to have some lines such as %%% Local

Re: [O] Allowing loose ordering in Org files

Hi, I share my personal views on this below. John Wiegley writes: >> John Wiegley writes: > >> I spoke to Nicolas directly and he mentioned that a goal for syntax >> regularity is to make it possible to reliably read and manipulate Org files >> outside

Re: [O] Allowing loose ordering in Org files

> Rasmus writes: >> To those who repeat the performance argument: This is an opt-in only >> request. It is not about changing the performance of default Org, or making >> files more difficult to parse outside of Emacs for everyone. > I disagree with your last claim. I'm not

[O] Allowing loose ordering in Org files (Was: bug in org-habits)

> John Wiegley writes: > I spoke to Nicolas directly and he mentioned that a goal for syntax > regularity is to make it possible to reliably read and manipulate Org files > outside of Emacs. > > For this I *am* willing to give up order independence of PROPERTIES. Having > a

Re: [O] Lexical binding bug in org-list.el?

Thanks for fixing this.

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

Marcin Borkowski writes: > On 2015-11-09, at 19:54, Martin Steffen wrote: > >> Hi, >> >> Perhaps it's not really a "fault" of org (nor of auctex), but both >> things interact unfortunate. >> >> The reason is: when I export org to LaTeX, and I visit the

Re: [O] Allowing loose ordering in Org files

> Achim Gratz writes: > The whole point of defining a formal syntax for Org is that it becomes > possible to parse Org documents with something other than Emacs and still > make sense of them. To reap that benefit, you need to drop some of the > ad-hoc parsing that Org did

Re: [O] Allowing loose ordering in Org files

> Rasmus writes: > If the placement of properties is "free", the secondary interpreter /must/ > support this customization option to be able to interpret the org format. > Note, this matters for both interactive usage (being able to click/open a > reference) and for "export"

[O] generating org headings from a source block

I would like to be able to insert into an org-buffer the text extracted from a pdf file. PDF-Tools (https://github.com/politza/pdf-tools/) provides some excellent tools for doing this. I've written (well, msotly stolen) a defun that finds all my highlights and returns them in the form of an org

Re: [O] Allowing loose ordering in Org files

John Wiegley writes: >> John Wiegley writes: >> I spoke to Nicolas directly and he mentioned that a goal for syntax >> regularity is to make it possible to reliably read and manipulate Org files >> outside of Emacs. How about keeping the discussion on the list and stop Cc: and

Re: [O] Allowing loose ordering in Org files

John Wiegley writes: >> You will find that the argument really wasn't about performance, but >> complexity. > > I can accept a complexity argument, I meant O() complexity, not implementation complexity. > if my request were really "a separate > code-path". I'm not sure it is. For example, my

Re: [O] BUG: emacs orgmode ob-R.el function org-babel-R-evaluate-session over aggressively performs "; ; cleanup extra prompts left in output" and a possible workaround

> -Original Message- > From: Charles C. Berry [mailto:ccbe...@ucsd.edu] > Sent: Saturday, November 07, 2015 6:33 PM > To: Cook, Malcolm > Cc: emacs-orgmode@gnu.org > Subject: Re: BUG: emacs orgmode ob-R.el function org-babel-R-evaluate- > session over

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

On 2015-11-09, at 19:54, Martin Steffen wrote: > Hi, > > Perhaps it's not really a "fault" of org (nor of auctex), but both > things interact unfortunate. > > The reason is: when I export org to LaTeX, and I visit the latex file > afterwards, I want that auctex/emacs is

Re: [O] Changes to contrib

Hi Serge, Serge Kosyrev <_deepf...@feelingofgreen.ru> writes: > I'm not sure how wise it would be to raise barriers for contribution, > given the current state of the thing.. I don't know what state you refer to. >> Some quick comments from skimming your code (note, I have no idea what a >>

Re: [O] Allowing loose ordering in Org files

Hi John, John Wiegley writes: >> Rasmus writes: > >>> To those who repeat the performance argument: This is an opt-in only >>> request. It is not about changing the performance of default Org, or making >>> files more difficult to parse outside of Emacs

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

Martin Steffen writes: > Hi, > > Perhaps it's not really a "fault" of org (nor of auctex), but both > things interact unfortunate. > > The reason is: when I export org to LaTeX, and I visit the latex file > afterwards, I want that auctex/emacs is instructed about some

Re: [O] BUG: emacs orgmode ob-R.el function org-babel-R-evaluate-session over aggressively performs "; ; cleanup extra prompts left in output" and a possible workaround

On Mon, 9 Nov 2015, Cook, Malcolm wrote: [...] > > > [...] > > > > I've wondered if there is not a better way for Babel to share an > > interactive session with the user. For instance, if we wanted to > > support a new form of results processing on addition to value and > > output Namely,

Re: [O] unfortunate "feature interaction" of org-export and emacs-latex-auctex mode

> "Marcin" == Marcin Borkowski writes: Marcin> Note: this is a terrible hack, so use it your own risk, only Marcin> if there's no sane alternative etc. Works for me, thanks (and for the suggestions of the others in the thread. Martin Marcin> #+BEGIN_COMMENT

Re: [O] exporting from org-mode to latex

Aloha Sharone Sharon Kimble writes: > I'm having a strange problem with exporting from org-mode to latex using > the latex back-end. When the file that I've written is exported to latex > and I look at the tex file that is created, I see that it has one >

Re: [O] Allowing loose ordering in Org files

John Wiegley writes: > > There is another vector to consider, and a far more nebulous one: How does it > impact Org's "luft"? That is, the feeling of ease and comfort Org conveys in > its use. > > There are many highly functional alternatives to Org that I've tried and >

Re: [O] org-mode and scrum

* Jude DaShiell wrote: > Have we got any software engineers on this list who use or have used > org-mode for doing scrum? How useable is org-mode for scrum anyway? I am using Org-mode as a Scrum product owner. With a few yasnippet templates, I'm fine with Org-mode. There

[O] [PATCH 0/8] A bunch of fixes for contrib/ox-taskjuggler.el

Good evening, folks! This is a bunch of solutions for the most direct obstacles that I encountered, mostly additions of direct Org-property -> TJ-attribute export pathways. Kosyrev Serge (8): ox-taskjuggler.el: allow direct 'leaves' specification ox-taskjuggler.el: factor

[O] [PATCH 3/8] ox-taskjuggler.el: :POST-INCLUDES lists files to include post-section

* ox-taskjuggler.el (org-taskjuggler-project-plan): allow for include directives to be inserted after resource and task sections. --- contrib/lisp/ox-taskjuggler.el | 48 ++ 1 file changed, 34 insertions(+), 14 deletions(-) diff --git

[O] [PATCH 6/8] ox-taskjuggler.el: interpret 'allocate' as a multivalued-property

* ox-taskjuggler.el (org-taskjuggler--build-task): interpret 'allocate' as a multivalued property, to pave the way for future completion-enabled entry of this property. --- contrib/lisp/ox-taskjuggler.el | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[O] [PATCH 2/8] ox-taskjuggler.el: factor 'org-export-map-special-nodes'

* ox-taskjuggler.el (org-taskjuggler-map-special-nodes): new function to capture mapping over tagged special nodes. (org-taskjuggler-project-plan): factor to use the new function. --- contrib/lisp/ox-taskjuggler.el | 17 ++--- 1 file changed, 10 insertions(+), 7 deletions(-) diff

[O] [PATCH 8/8] ox-taskjuggler.el: allow trimming the task ID from its title

* ox-taskjuggler.el (org-taskjuggler-trim-ids-from-titles): new custom (org-taskjuggler--build-task): trim task ids from titles, when the new custom variable asks for this (enabled by default). --- contrib/lisp/ox-taskjuggler.el | 18 +++--- 1 file changed, 15 insertions(+), 3

[O] [PATCH 7/8] ox-taskjuggler.el: allow 'priority' to be a directly-specified integer

* ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification by allowing it to be directly passed down, in case it parses as an integer. --- contrib/lisp/ox-taskjuggler.el | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git

Re: [O] Using orgstruct-mode (or just org-cycle) in emacs-lisp-mode

> #+BEGIN_SRC emacs-lisp > (add-hook 'elisp-mode-hook 'turn-on-orgtbl) > (add-hook 'elisp-mode-hook > (lambda () > (setq-local orgstruct-heading-prefix-regexp > ";; "))) > #+END_SRC It appears the stupid thing I did was that I

[O] [PATCH] ox-taskjuggler.el: allow direct 'depends' specification

* ox-taskjuggler.el (org-taskjuggler-valid-task-attributes): add depends to the list of valid task attributes --- contrib/lisp/ox-taskjuggler.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index

[O] [PATCH 1/8] ox-taskjuggler.el: allow direct 'leaves' specification

* ox-taskjuggler.el (org-taskjuggler-valid-resource-attributes): add leaves to the list of valid resource attributes --- contrib/lisp/ox-taskjuggler.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index

[O] [PATCH 5/8] ox-taskjuggler.el: add 'org-taskjuggler-multivalued-property'

* ox-taskjuggler.el (org-taskjuggler-multivalued-property): new function to operate on multivalued properties. --- contrib/lisp/ox-taskjuggler.el | 10 ++ 1 file changed, 10 insertions(+) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 82aaa7e..8036af3

[O] Spreadsheet error: invalid reference when using @> in range

Hi! | | 20 | 21 | 22 | 23 | 24 | | | :=vsum(@3..@>) ||||| |-+++++| | |||||| |-+++++| | | 1 | 1 ||| 1 | | Foo | 2

[O] [PATCH] ox-html.el ox.el: added list of figures support in html backend

Hi, this patch adds the list of figures to the html export backend. It also includes a translation entry-point for the label "List of Figures" with already one translation in: dutch. >From fab9105d04e5cb9f923c17d322d84a25527ec27a Mon Sep 17 00:00:00 2001 From: Joost Helberg Date:

Re: [O] Using orgstruct-mode (or just org-cycle) in emacs-lisp-mode

Aaron Ecay writes: > Thorsten Jolitz wrote the outshine library I know. I used it for a while and contributed a few commits. But I pretty much only used the cycling functionality at the time and when I discovered that `org-cycle' worked for that too, I stopped using

Re: [O] [PATCH 7/8] ox-taskjuggler.el: allow 'priority' to be a directly-specified integer

Hi Kosyrev, 2015ko azaroak 8an, Kosyrev Serge-ek idatzi zuen: > > * ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification > by allowing it to be directly passed down, in case it parses as an integer. > --- > contrib/lisp/ox-taskjuggler.el | 12 +--- > 1 file

Re: [O] [PATCH] ox-taskjuggler.el: allow direct 'depends' specification

Hi Kosyrev, 2015ko azaroak 8an, Kosyrev Serge-ek idatzi zuen: > > * ox-taskjuggler.el (org-taskjuggler-valid-task-attributes): add depends > to the list of valid task attributes > --- > contrib/lisp/ox-taskjuggler.el | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[O] [PATCH 4/8] ox-taskjuggler.el: :PROJECT-{END, DURATION} project attribute

* ox-taskjuggler.el (org-taskjuggler--build-project): Allow the project end and duration to be specified via properties of the root node. --- contrib/lisp/ox-taskjuggler.el | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/contrib/lisp/ox-taskjuggler.el

[O] [PATCH 7/8] ox-taskjuggler.el: allow 'priority' to be a directly-specified integer

* ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification by allowing it to be directly passed down, in case it parses as an integer. --- contrib/lisp/ox-taskjuggler.el | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git