Re: [O] Slight mistake in last ORG-NEWS file

Hello, Jean Luc writes: > There's a slight mistake in: >    File: ORG-NEWS >    version: elpa/org-20160229 > -- > * Version 8.3 > ** Incompatible changes > *** Default bindings of =C-c C-n= and =C-c C-p= changed > >

Re: [O] Checkbox cookies not shown anymore when refiling

Hello, -- writes: > With Org-mode version 8.3.4 (8.3.4-5-gdc68d2-elpa), it seems the > checkbox cookies are not shown in the possible refile locations > anymore when calling org-agenda-refile. Actually, that was the intent since commit

Re: [O] Bug: incorrect export for LaTeX [8.2.10 (release_8.2.10 @ c:/emacs25-91/share/emacs/25.0.91/lisp/org/)]

Hello, Rasmus writes: > I don’t think we need to do anything. Don't do anything? OK, done. > If we wanted to support this we’d probably need to load enumerate > (which is not a bad package...). We have worse offenders of manual > config. Local TOCs spring to mind.

[O] args-out-of-range #

This message just started appearing today when I open an agenda view "C-c a a". It is not obvious to me what I am doing or have done differently, and I would appreciate some advice how to diagnose the problem: Emacs: 24.5.1 Orgmode: 8.3.4-5 (20160229 elpa) Thank you, -- Britt The error trace

Re: [O] [PATCH] (fixed) ox-confluence.el: Do not generate filled paragraphs

Hello -- On Thu, Mar 3, 2016, at 07:42 PM, Nicolas Goaziou wrote: > Hello, > > "M. P. Ashton" writes: > > > * contrib/lisp/ox-confluence.el: Do not generate filled paragraphs > > > > ox-confluence was generating filled paragraphs. Since Confluence treats > > each newline as a

Re: [O] [PATCH] (fixed) ox-confluence.el: Do not generate filled paragraphs

Hello, "M. P. Ashton" writes: > * contrib/lisp/ox-confluence.el: Do not generate filled paragraphs > > ox-confluence was generating filled paragraphs. Since Confluence treats > each newline as a line break, this caused unexpected formatting. Added > a paragraph function to

[O] How to export casual letter without from and to address?

Hi list, I've been wondering for a while that when using org-mode to write letters, how do you export casual a letter that doesn't have from address and to address? Thanks in advance, York

Re: [O] Using #+INCLUDE for a .tex file

On Thursday, 3 Mar 2016 at 17:13, Nooreen Dabbish wrote: [...] > I am now resorting to > > #BEGIN_LATEX > \include{file} > #+END_LATEX > > But I am unhappy with this solution because I would like to generate the > include line as the raw results of a code block. You could ":wrap export latex"

[O] Using #+INCLUDE for a .tex file

Hi, I would like to include some latex files in my latex export exactly where I place them in the flow. I am trying to do this with #+INCLUDE: file.tex But this places them at the top of the document above the title. I have also tried #+INCLUDE: file.tex src latex #+INCLUDE: file.tex src LaTeX

Re: [O] Using #+INCLUDE for a .tex file

Hello Nooreen, > I am now resorting to > > #BEGIN_LATEX > \include{file} > #+END_LATEX > > But I am unhappy with this solution because I would like to generate the > include line as the raw results of a code block. I don't know anything about code block results, but would

Re: [O] Add caching to org-buffer-property-keys

Hello, Thierry Banel writes: > Maybe a rewrite of (org-read-property-name) calling > (org-entry-properties) could speed up things. > (org-entry-properties) returns an assoc list of the local header > properties. I agree. The OP should use `org-entry-properties' instead of

Re: [O] complex dates (ie schedule a class in a time range)

* Xebar Saram wrote: > > hi all > > im having difficulty understanding how the complex date input works and > would appreciate any help. > What i want is to schedule a class i teach on a sunday from 09:00 to 11:00 > between 3/6/2016 to 1/7/2016 > > from what i can understand i

Re: [O] Bug: Documentation of the html-export of links across files [8.2.10 (release_8.2.10 @ /usr/share/emacs/24.5/lisp/org/)]

Hello, Tobias Zawada writes: > This documentation bug exists also in org-mode 8.3.2 and the current > online org-mode manual. > > The export of links like [[file:a.org::#my-custom-id][Some link]] and > [[file:a.org::*Section header][Some link to a section header]] is not >

Re: [O] Babel code indentation problem

On Thursday, 3 Mar 2016 at 10:01, Jarmo Hurri wrote: [...] > So the problem is not in indentation in Processing mode itself, but the > error appears upon return from editing. This suggests that the issue > is in the communication between the editing mode and Org mode. As you > can see, I have

Re: [O] Mark subtrees for export?

Hi, I have (setq org-export-exclude-tags '("internal" "noexport")) i.e. I mark those I don't want to export. Then you export the buffer or the subtree above all of them. HTH, Simon On 03/03/2016 10:53 AM, Martin wrote: Hi there, Can I mark some subtrees (its ok with tags if that is

[O] org-time-stamp-custom-formats: change the default <> not suited for LaTeX export

Hi A week ago I asked how to change the format of org-time-stamp since the default format is not suited when exporting to LaTeX, the problem are the <> I'd prefer the format - «24-02-2016 Wed» I set org-display-custom-times to t and then did (customize-option (quote

[O] Mark subtrees for export?

Hi there, Can I mark some subtrees (its ok with tags if that is easyer) for export? I found just to export a subtree or the whole buffer. But what I want is to mark (in my case 3 out of 7) headers for export. How can I do that? Thanks, Martin -- Lösungen statt Diagnosen

[O] EXPORT_LATEX_HEADER property

Hi, I need some help here. I'm using org 8.3.4. I am exporting subtrees to LaTeX. So I configure as much as possible per subtree. First, I can't find where is documented the difference between :EXPORT_LATEX_HEADER: and :EXPORT_LATEX_HEADER+: Clearly, I need to use the latter form with my

Re: [O] org-collector - propview display problems

Hello, dche writes: > This function interested me in order to produce subset of data in tabular > with search criteria included in properties field. I hoped to > use this kind of approach as a kind of database and possibly use one of > property field to include an

Re: [O] org-time-stamp-custom-formats: change the default <> not suited for LaTeX export

Hello, Uwe Brauer writes: > A week ago I asked how to change the format of org-time-stamp since the > default format is not suited when exporting to LaTeX, the problem are > the <> > > I'd prefer the format > > - «24-02-2016 Wed» > > I set org-display-custom-times to t >

[O] Babel code indentation problem

Greetings. I would appreciate help in fixing a Babel indentation problem. I recently added support for Processing programming language in Babel. It is working very nicely except for an indentation problem I ran into. The Org snippet below shows two basically indentical code blocks, one in C

Re: [O] Babel code indentation problem

Eric S Fraga writes: > On Thursday, 3 Mar 2016 at 10:01, Jarmo Hurri wrote: > > [...] > >> So the problem is not in indentation in Processing mode itself, but the >> error appears upon return from editing. This suggests that the issue >> is in the communication between the

Re: [O] EXPORT_LATEX_HEADER property

Hello, Fabrice Popineau writes: > First, I can't find where is documented the difference between > :EXPORT_LATEX_HEADER: > and > :EXPORT_LATEX_HEADER+: See (info "(org) Property syntax"). > Second, when I use several lines with > :EXPORT_LATEX_HEADER+: > they are

Re: [O] EXPORT_LATEX_HEADER property

Fabrice Popineau writes: > In org reference, 12.7.2, it is said that: > > ‘LATEX_HEADER’ > Arbitrary lines added to the preamble of the document, before the ‘hyperref’ > settings. The location can be controlled via org-latex-classes. > > Note the plural to lines. How

Re: [O] Mark subtrees for export?

Hi there, This is a good start, but I want to export different things at different times, so this would need big rewrites in my file every time... Martin Simon Thum writes: > Hi, > > I have > > (setq org-export-exclude-tags '("internal" "noexport")) > > i.e. I mark those I don't want to

Re: [O] EXPORT_LATEX_HEADER property

On Thursday, 3 Mar 2016 at 12:58, Fabrice Popineau wrote: [...] > Note the plural to lines. How can several lines be specified? AFAICS, if I > do : > > :EXPORT_LATEX_HEADER: \usepackage{mathptmx} % rm & math > :EXPORT_LATEX_HEADER: \usepackage[scaled=0.90]{helvet} % ss > > The second line will

Re: [O] Mark subtrees for export?

Does "visible-only" (see export dialog) do what you want? Cheers, Simon On 03/03/2016 12:13 PM, Martin wrote: Hi there, This is a good start, but I want to export different things at different times, so this would need big rewrites in my file every time... Martin Simon Thum writes:

Re: [O] org-time-stamp-custom-formats: change the default <> not suited for LaTeX export

> Hello, > Uwe Brauer writes: > I cannot reproduce it. I get > \textit{\$«03-03-2016 jeu.»\$}. > The "\\textit{%s}" comes from `org-latex-active-timestamp-format'. You are right, I was in a latex file, using orgtbl-insert-table-or-matrix and did not

Re: [O] EXPORT_LATEX_HEADER property

2016-03-03 12:26 GMT+01:00 Nicolas Goaziou : > Hello, > > Hi Nicolas, > Fabrice Popineau writes: > > > First, I can't find where is documented the difference between > > :EXPORT_LATEX_HEADER: > > and > > :EXPORT_LATEX_HEADER+: > > See (info

Re: [O] org-collector - propview display problems

Thank you. In the first post I used the example proposed in the description of org-collector that is accessible at this link. http://orgmode.org/worg/sources/org-contrib/org-collector-example.org With this example org-collector is able to gather in a table with the use of propview in a

Re: [O] EXPORT_LATEX_HEADER property

On Thursday, 3 Mar 2016 at 16:49, Nicolas Goaziou wrote: [...] > The manual reference is about keywords, i.e, #+LATEX_HEADER:. You are > using properties. The two are slightly different. Ah, true. Please ignore my other email on this topic. -- : Eric S Fraga (0xFFFCF67D), Emacs

Re: [O] EXPORT_LATEX_HEADER property

2016-03-03 16:49 GMT+01:00 Nicolas Goaziou : > Fabrice Popineau writes: > > > In org reference, 12.7.2, it is said that: > > > > ‘LATEX_HEADER’ > > Arbitrary lines added to the preamble of the document, before the > ‘hyperref’ > > settings. The

[O] [PATCH] (fixed) ox-confluence.el: Do not generate filled paragraphs

* contrib/lisp/ox-confluence.el: Do not generate filled paragraphs ox-confluence was generating filled paragraphs. Since Confluence treats each newline as a line break, this caused unexpected formatting. Added a paragraph function to generate unfilled paragraphs (taken from ox-md.el). ---

[O] Batch org-icalendar-export-to-ics causes 'Variable binding depth exceeds max-specpdl-size'

Hi, This is perhaps more of an Emacs issue than a problem with Org. When trying to export my Org calendar in batch mode, I get the following: $ emacs /home/loris/org/gtd.org -batch -eval '(progn (package-initialize) (org-icalendar-export-to-ics))' --kill Loading 00debian-vars... Loading

Re: [O] EXPORT_LATEX_HEADER property

On Thursday, 3 Mar 2016 at 20:17, Fabrice Popineau wrote: [...] > I don't know what it could look like, but rare ... Am I the only one > who has a setup to export different subtrees from the same Org file? I used to try to do this but eventually realised it was easier to have separate files

[O] Checkbox cookies not shown anymore when refiling

With Org-mode version 8.3.4 (8.3.4-5-gdc68d2-elpa), it seems the checkbox cookies are not shown in the possible refile locations anymore when calling org-agenda-refile. How can I have them appear again? Besides, is there a way to have the TODO state be shown as well?

[O] [PATCH] ox-confluence.el: Do not generate filled paragraphs

* contrib/lisp/ox-confluence.el: Do not generate filled paragraphs ox-confluence was generating filled paragraphs. Since Confluence treats each newline as a line break, this caused unexpected formatting. Added a paragraph function to generate unfilled paragraphs (taken from ox-md.el). ---