[O] Is it possible to implement a TARGET date in addition to SCHEDULED and DEADLINE?

I wonder how difficult it would be to add a 3rd "TARGET" date to headings/tasks, which is treated similar to Deadline and Scheduled dates (can be used in agenda, can be easily set and modified, ...) : example: * TODO [#A] My org-mode task TARGET: <2015-04-01 Mi> SCHEDULED: <2015-03-30 Mo> Backg

Re: [O] Org-Mode and Mac OS X advice

On Thu, Mar 26, 2015 at 9:18 AM, Chris Willard wrote: > Hello All, > > I am thinking about changing to a Mac from Windows and wanted to check > that there are no issues with using org-mode in OS X. > No problems here; including exports to PDF via LaTeX. > > I would like to know what version of

Re: [O] bug in org-export-smart-quotes

Jay Dixit writes: > Thanks for the suggestion. Putting extra spaces in the original solves > the smart quotes issue, but creates unwanted spaces on either side of > the em dash: > I understand but I can't really help. If I'm right that the regexps are looking for a space[fn:1] (and that's a big

Re: [O] bug in org-export-smart-quotes

​Hi Nick, Thanks for the suggestion. Putting extra spaces in the original solves the smart quotes issue, but creates unwanted spaces on either side of the em dash: A new study published in Social Psychological and Persona

Re: [O] ':post' Direct execution via Emacs Lisp

that makes sense. Charles C. Berry writes: > On Fri, 27 Mar 2015, John Kitchin wrote: > >> I cannot see anyway to use direct execution of emacs lisp code in this >> (and nothing I have tried actually works). Any emacs-lisp code seems to >> get evaluated before running the block and *this* is not

Re: [O] bug in org-export-smart-quotes

Jay Dixit writes: > Hi everyone, > > I've noticed that when I use quotation marks in conjunction with an em dash > (—), org-export-smart-quotes gets confused and forgets > to activate smart quotes for the closing quotation mark. > > If my org-mode file contains a sentence like this... > > A > [

[O] bug in org-export-smart-quotes

Hi everyone, I've noticed that when I use quotation marks in conjunction with an em dash (—), org-export-smart-quotes gets confused and forgets to activate smart quotes for the closing quotation mark. If my org-mode file contains a sentence like this... A [[ http://spp.sagepub.com/content/early/

Re: [O] [bug?, ox-latex] creator not commented out

Rasmus writes: > Fixed in e9fd199. Thank you. > In e9fd199 meta-data is always available via the specs in ox-latex and > always inserted in ox-odt. An empty generator, which could be produced > before, is definitely wrong cf: > > http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-p

Re: [O] hiding the PROPERTIES drawer

Hello, Leo Ufimtsev writes: > I think he meant completely hiding the property drawer, so it wouldn't > even be a one-liner. This is not possible. Completely hiding data in a document sounds very wrong, anyway. Regards, -- Nicolas Goaziou

Re: [O] ':post' Direct execution via Emacs Lisp

On Fri, 27 Mar 2015, John Kitchin wrote: I cannot see anyway to use direct execution of emacs lisp code in this (and nothing I have tried actually works). Any emacs-lisp code seems to get evaluated before running the block and *this* is not defined then. The quoted part of the manual does sug

Re: [O] [ox, patch] #+SUBTITLE

Rasmus writes: > Andreas Leha writes: > >> I have not followed the discussion. But I like a uniform subtitle >> support across relevant backends. So, my only question is: this patch >> does not include ox-beamer, right? This is where I include my own latex >> subtitle most times > > Beamer

Re: [O] hiding the PROPERTIES drawer

I think he meant completely hiding the property drawer, so it wouldn't even be a one-liner. Leo Ufimtsev | Intern Software Engineer @ Eclipse Team - Original Message - From: "Richard Lawrence" To: emacs-orgmode@gnu.org Cc: "Randomcoder" Sent: Wednesday, March 25, 2015 10:18:32 AM Subj

Re: [O] [ox, patch] #+SUBTITLE

Andreas Leha writes: > I have not followed the discussion. But I like a uniform subtitle > support across relevant backends. So, my only question is: this patch > does not include ox-beamer, right? This is where I include my own latex > subtitle most times Beamer is derived from ox-latex.

Re: [O] [ox, patch] #+SUBTITLE

Hi Rasmus, Rasmus writes: > Hi, > > I'm starting a new thread as the previous discussion attracted much > dissuasion not directly related to the patch in question. Changes: > > - Html subtitles now follow the W3 recommendations, I think/hope. It > would be great if somebody who knows

Re: [O] org-drill problem: questions are blank

On Thu, 26 Mar 2015, at 17:26, J. David Boyd wrote: > Peter Westlake writes: > > > From time to time Org-drill shows me a blank window instead of a > > question. The frame, mode line and prompt to answer are visible, but > > there's nothing in the window at all. As a workaround I can type "t" to

[O] [ox, patch] #+SUBTITLE

Hi, I'm starting a new thread as the previous discussion attracted much dissuasion not directly related to the patch in question. Changes: - Html subtitles now follow the W3 recommendations, I think/hope. It would be great if somebody who knows css would check the styling.

Re: [O] ':post' Direct execution via Emacs Lisp

I cannot see anyway to use direct execution of emacs lisp code in this (and nothing I have tried actually works). Any emacs-lisp code seems to get evaluated before running the block and *this* is not defined then. As advertised, this works: #+name: wrap #+BEGIN_SRC emacs-lisp :var data="" (concat

Re: [O] :ignoreheading: works with LaTeX export, but not HTML

On Fri, Mar 27, 2015 at 6:53 AM, Nicolas Goaziou wrote: > :ignoreheading: is a feature implemented in "ox-beamer.el" only. This is > not a common feature for all back-ends. IIUC, this question is about performance of the filter shown in the OP, not about the built in feature in ox-beamer. Remove

Re: [O] org-ref and ODT export

The markdown file will not contain the bibliography. You have to use pandoc to get that, e.g. create a bibtex file containing the citations, and run something like pandoc --bibliography=test.bib --filter pandoc-citeproc test.md -o test.odt This works on a minimal kind of example for me. see also

Re: [O] [ox, patch] Keywords & what should go in ox?

Nicolas Goaziou writes: >> I have now reviewed this section twice, and I have no clue what you want >> me to change there. There's no :with-keywords or :with-description. > > I don't know either. I was sure that :keywords and :description were > here, but, oddly, it isn't the case. That's a docum

Re: [O] comment section with latex_header

Hi, On 03/27/2015 12:02 PM, Nicolas Goaziou wrote: > Andreas Leha writes: >> I completely agree. My question was, what a use case would be that >> requires a COMMENT that behaves different from #'ing the individual >> lines (and is not covered by :noexport: already). > > I don't think there is

Re: [O] Org-Mode and Mac OS X advice

Hello All, Just a quick email to say thanks for all the advice and tips. Regards, Chris

Re: [O] [bug?, ox-latex] creator not commented out

Nicolas Goaziou writes: > Rasmus writes: > >> Yeah, but I don't know what the right change is. I can remove the creator >> part from the ox-latex template and make the hyperref spec ignore >> :with-creator. > > What about keeping the creator part at the end of the template and > ignore :with-cr

Re: [O] comment section with latex_header

Hi Nicolas, Nicolas Goaziou writes: > Andreas Leha writes: > >> I see. I did not consider any possible slow-downs. I'd expect COMMENT >> to behave exactly like # in every regard -- not only export. That is a >> clearly defined behaviour, that should not produce confusion. > > As explained, th

Re: [O] [bug?, ox-latex] creator not commented out

Rasmus writes: > Yeah, but I don't know what the right change is. I can remove the creator > part from the ox-latex template and make the hyperref spec ignore > :with-creator. What about keeping the creator part at the end of the template and ignore :with-creator in the hyperref spec? Regards

Re: [O] comment section with latex_header

Andreas Leha writes: > I see. I did not consider any possible slow-downs. I'd expect COMMENT > to behave exactly like # in every regard -- not only export. That is a > clearly defined behaviour, that should not produce confusion. As explained, this is not realistic. > If COMMENT is only vali

Re: [O] :ignoreheading: works with LaTeX export, but not HTML

Hello, Richard Stanton writes: > I want to put some headers in my org file that don't get exported. If > I put :ignoreheading: after the title, it correctly does not get > exported to LaTeX, but it still appears when I export to HTML (with > the text :ignoreheading: on the same line). Am I missi

Re: [O] Updating to the current org-mode in emacs trunk, and Org stable

Hello, Rasmus writes: > Marc Ihm writes: > What's the schedule of merging these changes to the stable versions of Org and to Emacs trunk? >>> >>> My guess: After v8.3 is released. I don't think anybody is working >>> preparing a release at the moment. >>> >>> —Rasmus >>> >> >> which

Re: [O] [bug] fuzzy link not matching commented headlines

Martin Carlé writes: > Great, thanks for the quick fix! > > Well, besides exports there is also tangling. Still, thanks for the > warning. I am aware of the exports 'issue' but turned it into a feature > while automatically removing unresolvable internal links. As a result, > we get a nice privat

Re: [O] How to place things differently in dot

2015-03-27 7:57 GMT+01:00 Cecil Westerhof : > 2015-03-26 23:19 GMT+01:00 Cecil Westerhof : > >> 2015-03-26 22:49 GMT+01:00 Nick Dokos : >> >>> Cecil Westerhof writes: >>> >>> > ​In this way I do not get an empty column. It would be better when K >>> > would put between and below H and I, but I th

Re: [O] [bug] fuzzy link not matching commented headlines

Great, thanks for the quick fix! Well, besides exports there is also tangling. Still, thanks for the warning. I am aware of the exports 'issue' but turned it into a feature while automatically removing unresolvable internal links. As a result, we get a nice private comment system for notes only re

[O] ':post' Direct execution via Emacs Lisp

Hi, We can read in the manual: 14.8.2.25 ‘:post’ The ‘:post’ header argument is used to post-process the results of a code block execution. When a post argument is given, the results of the code block will temporarily be bound to the ‘*this*’ variable. This variable may then be included in head