Re: [O] render "->" as "&rarr" on html export?

[Xavier Maillard]

Sebastien Vauban  writes:

> Rasmus wrote:
>> Sebastien Vauban  writes:
>>> Rasmus wrote:
 Matt Price  writes:

> I feel like I've seen the answer to this somewhere but I can't find it --
> is it possible for me to get "->" and "=>" to render as rightarrows (→, 
> ⇒)?

 Do you want to render it in the buffer or on export?  For the buffer you
 could use prettify-symbols-mode.
>>>
>>> ... by adding the following into your .emacs:
>>>
>>>   ;; Show entities as UTF8 characters.
>>>   (setq org-pretty-entities t)  ; emsp, etc.
>>
>> This would work for "\rightarrow" but I don't think you can configure it
>> to support "->".  For that you'd need prettify-symbols-mode, I think.
>
> I think you're right, indeed!

So we need both if we want to display all these characters, right ?

Regards
-- Xavier.

Re: [O] [PATCH] Fix massive slowdown in org-id-find

[Florian Beck]

>> Could you profile it?

Here are the results:

With my setup and the patch I get, using

(let ((time (current-time)))
  (org-id-find "zangwill.nick_2014:aesthetic.judgment")
  (format "%ss" (time-to-seconds (time-subtract (current-time) time

--> "0.027756516s"

Without my patch, the result is

--> "16.104403749s"

profile-report returns:

- command-execute   16095  99%
 - call-interactively   16095  99%
  - funcall-interactively   15905  98%
   - eval-last-sexp 15879  98%
- elisp--eval-last-sexp 15879  98%
 - eval 15879  98%
  - let 15879  98%
   - org-id-find15879  98%
- org-id-find-id-in-file15879  98%
 - org-find-entry-with-id   15879  98%
  - org-find-property   15879  98%
   - save-excursion 15879  98%
- let   15879  98%
 - catch15879  98%
  - while   15879  98%
   - if 13311  82%
- if13311  82%
 - equal13311  82%
  - org-entry-get   11955  74%
   - org-get-property-block  8876  55%
- org-inlinetask-in-task-p   3329  20%
   org-inlinetask-outline-regexp 12   0%
- org-back-to-heading3009  18%
 - outline-back-to-heading   2000  12%
outline-on-heading-p4   0%
  org-before-first-heading-p  880   5%
  org-get-limited-outline-regexp 24   0%
   - #939   5%
  match-string-no-properties   44   0%
   - execute-extended-command  20   0%
- sit-for  16   0%
   redisplay   16   0%
+ command-execute   4   0%
   + previous-line  6   0%
  + byte-code 190   1%
+ timer-event-handler  15   0%
+ ...   0   0%



-- 
Florian Beck

Re: [O] [bug] orgstruct++-mode breaks backward-sentence

[Rasmus]

Hi,

Nicolas Goaziou  writes:

>>> Consider the following test file in text-mode where "|" is the cursor.
>>>
>>>1.  Foo bar
>>>baz|
>>>
>>> Before turning on orgstruct++-mode backward-sentence will correctly go to
>>> "|Foo".  When turning on orgstruct-mode, backward-sentence will also work
>>> correctly.  So somehow orgstruct++ does something that ruins
>>> backward-sentence.  Note that (sentence-end) does not seem to be affected
>>> by orgstruct++-mode.
>>
>> This is actually not particular to orgstruct++-mode.  It also happens in
>> org-mode.  With orgstruct-mode fill-paragraph does not work on lists.
>> Maybe you can't have both?
>
> I'm confused. Your first message talks about `backward-sentence' and the
> second one about `fill-paragraph'. Could you explain what the bug is?

Forget about fill-paragraph.  Try this with test-org as nil and non-nil:

(let ((test-org nil))
  (switch-to-buffer "test.org")
  (if test-org (org-mode) (text-mode))
  (erase-buffer)
  (insert "1. foo bar\n   baz")
  (backward-sentence))

When the buffer is in org-mode backward sentence behaves differently from
when it's in text-mode.  I think text-mode behaves correctly.

[The aside was that this does not happen in orgstruct-mode, but in
 orgstruct-mode fill-paragraph does not work.]

Thanks,
Rasmus

-- 
And I faced endless streams of vendor-approved Ikea furniture. . .

[O] completing-read for org-clock-select-task: It works!

[Tory S. Anderson]

In my first attempt at actually adding functionality to an existing emacs 
library, I've written some code to make `org-clock-select-task' use 
completing-read instead of the built-in org menu if you set 
`org-select-task-completing', for those who would find this useful (it now 
works with Helm). It seems like my functions, which are backed by a hash table, 
ought to be more capable of removing (non-adjacent) duplicates from the list 
since the table keys are the strings themselves, but I still see them 
appearing. Why doesn't the hash table merge the entries (they seem to have 
identical keys)?

Should this adjustment be useful to anyone else, what would I do next to 
contribute? As this is a first forray into more public-use elisp, I'm also open 
to any other suggestions or tips. 

Code at: 
http://www.toryanderson.com/files/helm-org-clock.el

Re: [O] [BUG?] wrong docstring for `org-reverse-note-order'

[Xavier Maillard]

Nicolas Goaziou  writes:

> Hello,
>
> Xavier  writes:
>
>> org-reverse-note-order's value is nil
>>
>> As far as I understand, the DONE state should be downside, right ?
>> Is this the correct understanding then ?
>
> AFAIU, `org-reverse-note-order' is about refiling and capturing. You
> want to use `org-log-states-order-reversed'.

I will try and compare both.

Regards
-- Xavier.

Re: [O] [BUG?] wrong docstring for `org-reverse-note-order'

[Nicolas Goaziou]

Hello,

Xavier  writes:

> org-reverse-note-order's value is nil
>
> Documentation:
> Non-nil means store new notes at the beginning of a file or entry.
> When nil, new notes will be filed to the end of a file or entry.
> This can also be a list with cons cells of regular expressions that
> are matched against file names, and values.
>
> You can customize this variable.
>
> I have it set to `nil' but I got the behaviour of the `non-nil' part.
> Here is my example:
>
> *** DONE Enregistrer résultats athlètes ASPTT
> :@computer:@online:
> - State "DONE"   from "DEMA"   [2015-03-24 Tue 07:14]
> - Note taken on [2015-03-24 Tue 07:12] \\
>   Il faut bien la neutraliser au niveau du challenge kilo
> - State "DEMA"   from "W4" [2015-03-24 Tue 07:12]
> CLOCK: [2015-03-24 Tue 06:50]--[2015-03-24 Tue 07:14] =>  0:24
> - State "WAIT"   from "DEMA"[2015-03-23 Mon 06:30] \\
>   En attente du retour du bureau concernant le traitement des
>   résultats.
>   Dois-je la neutraliser ?
> CLOCK: [2015-03-23 Mon 06:28]--[2015-03-23 Mon 06:29] =>  0:01
> :PROPERTIES:
> :Effort:   0:45
> :END:
>
> As far as I understand, the DONE state should be downside, right ?
> Is this the correct understanding then ?

AFAIU, `org-reverse-note-order' is about refiling and capturing. You
want to use `org-log-states-order-reversed'.

Regards,

-- 
Nicolas Goaziou

Re: [O] [Beamer] Combining blocks, columns, and column(s) options

[Nicolas Goaziou]

Matthew Gidden  writes:

> I just wanted to report back that this worked out perfectly. Thanks! I'd be
> happy to add documentation somewhere if it is desired.

This is already documented:

 Moreover, headlines handle the ‘BEAMER_COL’ property.  Its value
  should be a decimal number representing the width of the column as a
  fraction of the total text width.  If the headline has no specific
  environment, its title will be ignored and its contents will fill the
  column created.  Otherwise, the block will fill the whole column and the
  title will be preserved.  Two contiguous headlines with a non-‘nil’
  ‘BEAMER_COL’ value share the same ‘columns’ LaTeX environment.  It will
  end before the next headline without such a property.  This environment
  is generated automatically.  Although, it can also be explicitly
  created, with a special ‘columns’ value for ‘BEAMER_ENV’ property (if it
  needs to be set up with some specific options, for example).

in particular the last sentence.

However, feel free to improve it, or suggest an example, if you think
this is not clear.


Regards,

Re: [O] [bug] orgstruct++-mode breaks backward-sentence

[Nicolas Goaziou]

Hello,

Rasmus  writes:

> Rasmus  writes:
>
>> Hi,
>>
>> Consider the following test file in text-mode where "|" is the cursor.
>>
>>1.  Foo bar
>>baz|
>>
>> Before turning on orgstruct++-mode backward-sentence will correctly go to
>> "|Foo".  When turning on orgstruct-mode, backward-sentence will also work
>> correctly.  So somehow orgstruct++ does something that ruins
>> backward-sentence.  Note that (sentence-end) does not seem to be affected
>> by orgstruct++-mode.
>
> This is actually not particular to orgstruct++-mode.  It also happens in
> org-mode.  With orgstruct-mode fill-paragraph does not work on lists.
> Maybe you can't have both?

I'm confused. Your first message talks about `backward-sentence' and the
second one about `fill-paragraph'. Could you explain what the bug is?

Regards,

-- 
Nicolas Goaziou

Re: [O] [bug] orgstruct++-mode breaks backward-sentence

[Rasmus]

Rasmus  writes:

> Hi,
>
> Consider the following test file in text-mode where "|" is the cursor.
>
>1.  Foo bar
>baz|
>
> Before turning on orgstruct++-mode backward-sentence will correctly go to
> "|Foo".  When turning on orgstruct-mode, backward-sentence will also work
> correctly.  So somehow orgstruct++ does something that ruins
> backward-sentence.  Note that (sentence-end) does not seem to be affected
> by orgstruct++-mode.

This is actually not particular to orgstruct++-mode.  It also happens in
org-mode.  With orgstruct-mode fill-paragraph does not work on lists.
Maybe you can't have both?

Thanks,
Rasmus

-- 
In theory, practice and theory are the same. In practice they are not

[O] [bug] orgstruct++-mode breaks backward-sentence

[Rasmus]

Hi,

Consider the following test file in text-mode where "|" is the cursor.

   1.  Foo bar
   baz|

Before turning on orgstruct++-mode backward-sentence will correctly go to
"|Foo".  When turning on orgstruct-mode, backward-sentence will also work
correctly.  So somehow orgstruct++ does something that ruins
backward-sentence.  Note that (sentence-end) does not seem to be affected
by orgstruct++-mode.

I'm not really sure how to debug this further.

Thanks,
Rasmus

-- 
Spil noget med Slayer!

[O] [BUG?] wrong docstring for `org-reverse-note-order'

[Xavier]

Hello,

C-h v org-reverse-node-order goes like this:

org-reverse-note-order's value is nil

Documentation:
Non-nil means store new notes at the beginning of a file or entry.
When nil, new notes will be filed to the end of a file or entry.
This can also be a list with cons cells of regular expressions that
are matched against file names, and values.

You can customize this variable.

I have it set to `nil' but I got the behaviour of the `non-nil' part.
Here is my example:

*** DONE Enregistrer résultats athlètes ASPTT
:@computer:@online:
- State "DONE"   from "DEMA"   [2015-03-24 Tue 07:14]
- Note taken on [2015-03-24 Tue 07:12] \\
  Il faut bien la neutraliser au niveau du challenge kilo
- State "DEMA"   from "W4" [2015-03-24 Tue 07:12]
CLOCK: [2015-03-24 Tue 06:50]--[2015-03-24 Tue 07:14] =>  0:24
- State "WAIT"   from "DEMA"[2015-03-23 Mon 06:30] \\
  En attente du retour du bureau concernant le traitement des
  résultats.
  Dois-je la neutraliser ?
CLOCK: [2015-03-23 Mon 06:28]--[2015-03-23 Mon 06:29] =>  0:01
:PROPERTIES:
:Effort:   0:45
:END:

As far as I understand, the DONE state should be downside, right ?
Is this the correct understanding then ?

Regards
-- 
  Xavier
  xav...@maillard.im

[O] Problem: clock-in:t not respected in the org-capture-templates ?

[Xavier]

Hi,

I have several org-capture-templates with the clock-in property set to t
but, either I do not understand how it works either there is a bug but,
AFAICS, I do not see the clock-in when triggering the template.

How is it supposed to be working ? When does it appear in the capture
workflow ?

Regards

-- 
  Xavier
  xav...@maillard.im

Re: [O] [Beamer] Combining blocks, columns, and column(s) options

[Matthew Gidden]

Hi Nicolas,

I just wanted to report back that this worked out perfectly. Thanks! I'd be
happy to add documentation somewhere if it is desired.

Cheers,

On Mon, Mar 23, 2015 at 5:50 PM, Nicolas Goaziou 
wrote:

> Hello
>
> Matthew Gidden  writes:
>
> > I've found a number of references to the problem of aligning columns,
> > especially using the block environment [1, 2, 3]. Specifically, I would
> > like to supply option arguments to either the `columns` or `column` latex
> > environment directive. As written, it appears that only the `block`
> > environment can be supplied options. I have also tried the BEAMER_envarg
> > suggestion on the website 
> to
> > no avail.
>
> "BEAMER_envarg" no longer exists. Using "columns", as suggested in the
> manual, should work however:
>
> * Foo
> ** Columns
>  :B_columns:
>:PROPERTIES:
>:BEAMER_env: columns
>:BEAMER_opt: t
>:END:
> *** Bar
> :B_block:BMCOL:
> :PROPERTIES:
> :BEAMER_col: 0.45
> :BEAMER_env: block
> :END:
>  foo
>
> *** Baz
> :B_block:BMCOL:
> :PROPERTIES:
> :BEAMER_col: 0.45
> :BEAMER_env: block
> :END:
>  foo
>
>
> Regards,
>
> --
> Nicolas Goaziou
>



-- 
Matthew Gidden
Ph.D. Candidate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph. 225.892.3192

Re: [O] [OT] A short (less than a minute), informal survey about LaTeX

[Richard Lawrence]

Marcin Borkowski  writes:

> 1. Did you know about the savetrees package by Scott Pakin
> (http://www.ctan.org/pkg/savetrees)?  From the description:

Only vaguely.

> 2. Would you find it useful when producing PDF files other that
> scientific articles (using Org-mode or not)?

Yes.  I often produce PDFs from Org of things like lecture notes,
handouts, etc. where it is more important to get more infomation onto
fewer pages than to have publication-quality output.  (Normally, I do
this with \usepackage[margin=1in]{geometry}.)  

(However, I just tried to build one of my handouts with the savetrees
package, and was unsuccessful.  I didn't do anything besides loading
savetrees instead of geometry.  Is savetrees incompatible with other
packages Org loads by default?)

Best,
Richard

Re: [O] html preamble

[Scott Randby]

On 03/23/2015 04:12 PM, hymie! wrote:

So my next task is to learn about the HTML preamble.


From reading the docs, it looks like all of my org files have to share a

single HTML preamble, which is set in my .emacs file through either the
org-html-preamble variable, the org-html-preamble-format variable, or the
org-publish-project-alist variable.  There is no way to tell a specific Org
file "This is your HTML preamble."  Is that correct?

Why are there two different variables org-html-preamble-format and
org-html-preamble if the org-html-preamble variable can perform all of the
tasks of org-html-preamble-format and more?

Finally, how do I get the current date into the preamble?  I see that I can
specifically set a date, and I see the current date in a comment at the top
of my exported HTML, but I can't figure out how to get the current date out
of the comment and into my preamble.



I don't know if this helps, but I have postamble requirements in each 
file that I export. I believe you can do the same for the preamble. 
Below is an example from one of my files.



* COMMENT Postamble Settings

#+BEGIN_SRC emacs-lisp

;; Turn off postamble creation
(setq org-html-postamble nil)

;; Turn on postamble creation (default)
(setq org-html-postamble t)

;; Postamble format for lessons
(setq org-html-postamble-format (quote (("en" "class=\"author\">Author: %a 

Email: %e
%c"

;; Postamble format for non-lesson pages (default)
(setq org-html-postamble-format (quote (("en" "class=\"author\">Author: %a 

Email: %e
Date: %T
%c"

#+END_SRC


Scott Randby

Re: [O] org-insert-subheading doesn't work well with colons

[Leo Ufimtsev]

Thank you for fix.

Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

- Original Message -
From: "Nicolas Goaziou" 
To: "Leo Ufimtsev" 
Cc: emacs-orgmode@gnu.org
Sent: Monday, March 23, 2015 6:41:04 PM
Subject: Re: [O] org-insert-subheading doesn't work well with colons

Hello,

Leo Ufimtsev  writes:

> When I have a plain list entry like this and issue org-insert-heading:
>
> - Meaning of life ::
>
> I expect something like this:
>
> - Meaning of life ::
> - 

It depends on where point is. It should be so past the colons, indeed.
Before them, it is

  - |:: 
  - Meaning of life ::

where "|" is the point.

This should be fixed in 5a550938ce806ee88f62e6df774af47df83312a4. Thank
you


Regards,

-- 
Nicolas Goaziou

Re: [O] org-mode timestamp and calendar questions

[Nick Dokos]

Randomcoder  writes:

> Is it possible to make org-mode timestamps inactive? (I mean, the
> calendar(Google calendar) and the org-agenda would ignore them)
>

I am (as usual) confused: is the part above related to the part below?
As Seb says, <...> are active timestamps, [...] are inactive ones and
the agenda does not pay any attention to the latter. No idea what
happens with Google calendar, or any other for that matter.

> I tried specifying that I should be notified 1h in advance for an
> event like this :  <2015-03-24 Mon 07:30 -1h> but apparently this is
> not the way to do it.
> Is it currently possible to do this and if so, what is the correct
> org-mode timestamp markup for this ?
>

What notification system are you using? The stuff in appt.el perhaps?
If so, see the docstring of org-agenda-to-appt, in particular the
APPT_WARNTIME property. But in general, the notification settings are
appt-related ones: afaik, you cannot use things like -1h in the
timestamp and have it carry over to the appt settings, although that
might be possible "with a small amount of coding".

-- 
Nick

Re: [O] [PATCH] Fix massive slowdown in org-id-find

[Florian Beck]

> Would you mind elaborating a bit? Slow down doing what? In which cases?

A fraction of a second vs 10 seconds when executing a function that
calls org-id-find. The slowdowwn is not quite as massive since I
cleaned up org-id-files a bit, however.

> Could you profile it?

I'll look into it.

> Here, it catches false positives, e.g., lines looking like properties in
> example blocks. It also overlooks accumulated values.

This is true. However that is not really relevant for id searches, is
it? In the worst case, you'll find ids in example, etc blocks when you
SEARCH for them.

I guess, you want to use org-find-property in other places as well. In
that case org-id-find could maybe use a faster, simplified version? Let
me see, if I can do some profiling tonight.

> It should fail with "make test".

Doesn't work for me (it hangs).

-- 
Florian Beck

Re: [O] render "->" as "&rarr" on html export?

[Sebastien Vauban]

Rasmus wrote:
> Sebastien Vauban  writes:
>> Rasmus wrote:
>>> Matt Price  writes:
>>>
 I feel like I've seen the answer to this somewhere but I can't find it --
 is it possible for me to get "->" and "=>" to render as rightarrows (→, ⇒)?
>>>
>>> Do you want to render it in the buffer or on export?  For the buffer you
>>> could use prettify-symbols-mode.
>>
>> ... by adding the following into your .emacs:
>>
>>   ;; Show entities as UTF8 characters.
>>   (setq org-pretty-entities t)  ; emsp, etc.
>
> This would work for "\rightarrow" but I don't think you can configure it
> to support "->".  For that you'd need prettify-symbols-mode, I think.

I think you're right, indeed!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] org-mobile-copy-agenda-files: Truncating output file

[Guido Van Hoecke]

On 24 February 2015 at 13:10, Guido Van Hoecke  wrote:

> Hi,
>
> org-mobile-push frequently fails to copy my org files to the staging
> directory with following output:
>
> Copying files...
> org-mobile-copy-agenda-files: Truncating output file: interrupted
> system call, /Volumes/guivho/org/z.org
>
> This error is not consistent. Just call it again, sometimes again and
> again, and eventually the copy succeeds.
>
> Any ideas?
>
>
​Any one any ideas?

Suggestions to pinpoint this problem would be utterly appreciated!

TIA,

Guido

[O] Space at end of monospace string?

[Loris Bennett]

Hi,

I'm writing a beamer presentation and have the followoing

   - =--nodes=2=  $\Rightarrow$ 2 /or more/ nodes
   - =--nodes=2-4=  $\Rightarrow$ 2 to 4 nodes

It would be nice to have the arrows line up, but doing =--nodes=2  =
obviously doesn't work.

Is there a simple solution to this problem?

Cheers,

Loris

-- 
This signature is currently under construction.

Re: [O] render "->" as "&rarr" on html export?

[Rasmus]

Sebastien Vauban 
writes:

> Rasmus wrote:
>> Matt Price  writes:
>>
>>> I feel like I've seen the answer to this somewhere but I can't find it --
>>> is it possible for me to get "->" and "=>" to render as rightarrows (→, ⇒)?
>>
>> Do you want to render it in the buffer or on export?  For the buffer you
>> could use prettify-symbols-mode.
>
> ... by adding the following into your .emacs:
>
>   ;; Show entities as UTF8 characters.
>   (setq org-pretty-entities t)  ; emsp, etc.

This would work for "\rightarrow" but I don't think you can configure it
to support "->".  For that you'd need prettify-symbols-mode, I think.

—Rasmus

-- 
Dung makes an excellent fertilizer

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

[Rasmus]

Nicolas Goaziou  writes:

> E.g., when creating a new export back-end, it is quite obvious that one
> will need to handle TITLE, DATE, AUTHOR and EMAIL somehow. Now, if you
> request handlers for SUBTITLE, KEYWORDS and DESCRIPTION, it becomes more
> tedious to achieve the task.

Isn't the point that you don't have to support those (e.g. markddown).
The current documentation is pretty specific about not having expectations
about KEYWORDS and DESCRIPTION working.  It would be the same for
SUBTITLE.

> This is not really about SUBTITLE, but, sooner or later, we will have to
> draw a line between common features ensuring compatibility between
> back-ends and specific ones. The cost of the former is some orders of
> magnitude higher.

This is why I proposed SUBTITLE as a feature of a few backends: ox-ascii,
ox-html, ox-odt, and ox-latex (and some derived backends).

>> Yeah, I still have a patch for that...  I still have to do the
>> documentation changes.
>
> Unless we decide that KEYWORD and DESCRIPTION should move to the "common
> features" discussed above. In this case, they stay in "ox.el" and all
> major back-ends are expected to handle them. WDYT?

I think it is fine either way.  But I have never used DESCRIPTION and I
don't use KEYWORDS regularly.

>>> Now, if SUBTITLE is a feature desperately needed everywhere, which can
>>> be discussed, it should be moved to "ox.el" and probably
>>> `org-element-document-keywords'. IMO, this is not necessary. SUBTITLE
>>> should be kept for back-ends that can handle it.
>>
>> IMO it is.
>
> See above. I don't mind much, as long as we eventually stop
> compatibility hell at some point.

I think I didn't understand the first quote above (prefixed with ">>>").
It should *not* be a common feature.  It should be a feature of the
backend where it makes sense, namely backends for text documents at large.

—Rasmus

-- 
Together we'll stand, divided we'll fall

Re: [O] org-mode timestamp and calendar questions

[Sebastien Vauban]

Randomcoder wrote:
> Hi,
>
> Is it possible to make org-mode timestamps inactive? (I mean, the
> calendar(Google calendar) and the org-agenda would ignore them)
>
> I tried specifying that I should be notified 1h in advance for an
> event like this :  <2015-03-24 Mon 07:30 -1h> but apparently this is
> not the way to do it.
> Is it currently possible to do this and if so, what is the correct
> org-mode timestamp markup for this ?

As written in the docs, inactive timestamps have `[' brackets instead of
`<'.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] comment section with latex_header

[Sebastien Vauban]

Nicolas Goaziou wrote:
> Robert Klein  writes:
>
>> this patch also breaks this kind of construct where not the table is
>> exported, but the one created from the booktabs() call:
>>
>>
>> ---> begin example <---
>>   * Grundlagen
>>   *** COMMENT unexported subtree with table source
>>   #+tblname: masse
>
> This is deprecated. Use #+name: instead.
>
>>   | 1 gestr. Teelffel   | 1 gestr. Elffel   | 1 Tasse |
>>   | ca. 5 ccm   | ca 15 ccm | ca 120 ccm  |
>>   |-+---+-|
>>   | Zimt 2 g| Haferflocken 8 g  | Mehl 80 g   |
>>   | Paprika 2 g | Speisestärke 9 g  | Grieß 96 g  |
>>   | Speisestärke 2--3 g | Mehl, Semmelmehl 10 g | Zucker 90 g |
>>   | Zucker 4 g  | Salz, Zucker, Öl 15 g | |
>>   | Salz 5 g| Reis, Butter 15 g | |
>>
>>   ** Maße und Gewichte
>>
>>   #+call: booktabs(table=masse, align="lll") :results latex :exports results
>> ---> end example <---
>
> Good catch. The line between data that can be accessed and data that
> cannot in a commented subtree is blurry.

Can't we say that a COMMENT'ed subtree is like having all of its
contents commented, line by line?  IOW, nothing "accessible"?

Best regards,
  Seb

-- 
Sebastien Vauban

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

[Nicolas Goaziou]

Rasmus  writes:

> Nicolas Goaziou  writes:
>
>> However, I think porting this feature to back-ends that do not support
>> it out of the box is pushing too hard. 
>
> In the patch there's ox-latex where e.g. KOMA-Script has as
> subtitle-macro.  ox-html, ox-ascii, ox-odt all are pretty liberate formats
> in terms of what elements are supported.

My concern is not technical. You can indeed tweak "ox-html", "ox-ascii"
and "ox-odt" to support many things.

I just don't want to make it too difficult for back-end developers, and
maintainers, to keep up with compatibility with other back-ends, while
still allowing existing back-ends to extend (almost) freely.

E.g., when creating a new export back-end, it is quite obvious that one
will need to handle TITLE, DATE, AUTHOR and EMAIL somehow. Now, if you
request handlers for SUBTITLE, KEYWORDS and DESCRIPTION, it becomes more
tedious to achieve the task.

This is not really about SUBTITLE, but, sooner or later, we will have to
draw a line between common features ensuring compatibility between
back-ends and specific ones. The cost of the former is some orders of
magnitude higher.

>> This is why I suggested to move KEYWORD and DESCRIPTION outside of
>> "ox.el", as they cannot be ported to all back-ends without relying on
>> dubious markup.
>
> Yeah, I still have a patch for that...  I still have to do the
> documentation changes.

Unless we decide that KEYWORD and DESCRIPTION should move to the "common
features" discussed above. In this case, they stay in "ox.el" and all
major back-ends are expected to handle them. WDYT?

>> Now, if SUBTITLE is a feature desperately needed everywhere, which can
>> be discussed, it should be moved to "ox.el" and probably
>> `org-element-document-keywords'. IMO, this is not necessary. SUBTITLE
>> should be kept for back-ends that can handle it.
>
> IMO it is.

See above. I don't mind much, as long as we eventually stop
compatibility hell at some point.

If you think it's important, then go ahead.

> The only place where there's a "hack" is in ox-latex and
> that's cause article is the default class.  If you prefer, it can just
> output to the \subtitle{·} by default and say it's KOMA-script only.  That
> seems harsh, though.

I agree it would be harsh.

>> As a side note, "ox-texinfo" doesn't parse SUBTITLE. You might want to
>> change it and update manual accordingly.
>
> The patch doesn't touch ox-texinfo.  I don't mind fixing that bug,
> though.

It isn't a bug at the moment, since that feature is documented in the
manual. However, it will become inconsistent if other back-ends parse
SUBTITLE.


Regards,

Re: [O] [PATCH] Fix massive slowdown in org-id-find

[Sebastien Vauban]

Nicolas Goaziou wrote:
> Florian Beck  writes:
>
>> the recent changes in org-id (presumably
>> 8cdb2eef0f9f98f9e00a5e689decfe341fe0c6ec) lead to a massive slowdown.
>
> Would you mind elaborating a bit? Slow down doing what? In which cases?
> Could you profile it?
>
>> org-id-find is slow as it is, now I find it almost unusable.
>>
>> Attached patch provides a fix.
>
> Thanks. However, your patch is (partly) wrong.
>
>> -  (re (org-re-property property nil (not value
>> -  (catch 'exit
>> -(while (re-search-forward re nil t)
>> -  (when (if value (equal value (org-entry-get (point) property nil t))
>> -  (org-entry-get (point) property nil t))
>> -(throw 'exit (progn (org-back-to-heading t) (point)
>> +  (re (org-re-property property nil (not value) value)))
>> +  (when (re-search-forward re nil t)
>> +(org-back-to-heading t)
>> +(point)
>
> Here, it catches false positives, e.g., lines looking like properties in
> example blocks. It also overlooks accumulated values. It should fail
> with "make test".
>
> However, the optional VALUE argument is nice (I think some profiling
> would still be welcome, tho).

For my own information, does one know if it's possible to integrate
profiling tests in ERT?  So that one could write that if test X takes
more than 2 s (for example), the test would fail?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] render "->" as "&rarr" on html export?

[Sebastien Vauban]

Rasmus wrote:
> Matt Price  writes:
>
>> I feel like I've seen the answer to this somewhere but I can't find it --
>> is it possible for me to get "->" and "=>" to render as rightarrows (→, ⇒)?
>
> Do you want to render it in the buffer or on export?  For the buffer you
> could use prettify-symbols-mode.

... by adding the following into your .emacs:

--8<---cut here---start->8---
  ;; Show entities as UTF8 characters.
  (setq org-pretty-entities t)  ; emsp, etc.
--8<---cut here---end--->8---

>> \rightarrow will work, but doesn't give me the visual cue I want when
>> working in org.
>
> With org-entities you can have it displayed as the equivalent unicode
> characters of e.g. \rightarrow.  With cdlatex you can insert \rightarrow
> quickly (on my keyboard: "¨>").

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] comment section with latex_header

[Nicolas Goaziou]

Hello,

Robert Klein  writes:

> this patch also breaks this kind of construct where not the table is
> exported, but the one created from the booktabs() call:
>
>
> ---> begin example <---
>   * Grundlagen
>   *** COMMENT unexported subtree with table source
>   #+tblname: masse

This is deprecated. Use #+name: instead.

>   | 1 gestr. Teelffel   | 1 gestr. Elffel   | 1 Tasse |
>   | ca. 5 ccm   | ca 15 ccm | ca 120 ccm  |
>   |-+---+-|
>   | Zimt 2 g| Haferflocken 8 g  | Mehl 80 g   |
>   | Paprika 2 g | Speisestärke 9 g  | Grieß 96 g  |
>   | Speisestärke 2--3 g | Mehl, Semmelmehl 10 g | Zucker 90 g |
>   | Zucker 4 g  | Salz, Zucker, Öl 15 g | |
>   | Salz 5 g| Reis, Butter 15 g | |
>
>   ** Maße und Gewichte
>
>   #+call: booktabs(table=masse, align="lll") :results latex :exports results
> ---> end example <---

Good catch. The line between data that can be accessed and data that
cannot in a commented subtree is blurry.

Anyway, this should be fixed in
359572d37eb3131d934fbfaeffdee0c2a1abc7cc. Thank you.


Regards,

-- 
Nicolas Goaziou

[O] org-mode timestamp and calendar questions

[Randomcoder]

Hi,

Is it possible to make org-mode timestamps inactive? (I mean, the
calendar(Google calendar) and the org-agenda would ignore them)

I tried specifying that I should be notified 1h in advance for an
event like this :  <2015-03-24 Mon 07:30 -1h> but apparently this is
not the way to do it.
Is it currently possible to do this and if so, what is the correct
org-mode timestamp markup for this ?


Best regards,
Stefan

Re: [O] [ox-beamer] overlay specification for bold markup ignored in list labels

[Andreas Leha]

Hi Nicolas,

Nicolas Goaziou  writes:
> Hello,
>
> Andreas Leha  writes:
>
>> The overlay specification for bold markup (as in
>> *@@beamer:<2->@@useful*) is ignored when used in the label of a
>> description list.  Is this a bug?
>>
>> Regards,
>> Andreas
>>
>> PS: ECM:
>>
>> #+TITLE: Example Presentation
>> #+OPTIONS: H:2
>> #+LATEX_CLASS: beamer
>> #+LATEX_CLASS_OPTIONS: [presentation]
>> #+BEAMER_THEME: Madrid
>>
>> * This is the first structural section
>> ** Frame
>> *** Request
>> - Test :: of a *@@beamer:<2->@@useful* feature! 
>> - *@@beamer:<2->@@Test 2* :: of the same feature
>
> This is fixed in ec54a5852d8da476b9b8381653af6ca72cf26a18. Thank you.
>
>

Thank you!

Regards,
Andreas

Re: [O] [ox-beamer] overlay specification for bold markup ignored in list labels

[Nicolas Goaziou]

Hello,

Andreas Leha  writes:

> The overlay specification for bold markup (as in
> *@@beamer:<2->@@useful*) is ignored when used in the label of a
> description list.  Is this a bug?
>
> Regards,
> Andreas
>
> PS: ECM:
>
> #+TITLE: Example Presentation
> #+OPTIONS: H:2
> #+LATEX_CLASS: beamer
> #+LATEX_CLASS_OPTIONS: [presentation]
> #+BEAMER_THEME: Madrid
>
> * This is the first structural section
> ** Frame
> *** Request
> - Test :: of a *@@beamer:<2->@@useful* feature! 
> - *@@beamer:<2->@@Test 2* :: of the same feature

This is fixed in ec54a5852d8da476b9b8381653af6ca72cf26a18. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] comment section with latex_header

[Robert Klein]

On 03/24/2015 12:36 AM, Nicolas Goaziou wrote:
> Hello,
> 
> Andreas Leha  writes:
> 
>> If there are `#+latex_header:' entries in a section and that section is
>> `COMMENT'ed out, I'd expect the #+latex_header entries to be
>> uneffective.  As they are when I comment them out one by one as in
>> `# #+latex_header:'.
>>
>> Is this a bug? (I'd say, yes)
> 
> This is fixed in c9a52787c14c3a7429bcd3c8975350525e0baa04. Thank you.
> 
> Regards,
> 


Hello,

this patch also breaks this kind of construct where not the table is
exported, but the one created from the booktabs() call:


---> begin example <---
  * Grundlagen
  *** COMMENT unexported subtree with table source
  #+tblname: masse
  | 1 gestr. Teelöffel  | 1 gestr. Eßlöffel | 1 Tasse |
  | ca. 5 ccm   | ca 15 ccm | ca 120 ccm  |
  |-+---+-|
  | Zimt 2 g| Haferflocken 8 g  | Mehl 80 g   |
  | Paprika 2 g | Speisestärke 9 g  | Grieß 96 g  |
  | Speisestärke 2--3 g | Mehl, Semmelmehl 10 g | Zucker 90 g |
  | Zucker 4 g  | Salz, Zucker, Öl 15 g | |
  | Salz 5 g| Reis, Butter 15 g | |

  ** Maße und Gewichte

  #+call: booktabs(table=masse, align="lll") :results latex :exports results
---> end example <---


booktabs() code is from library-of-babel.org (currently residing in the
doc directory).  Also cf.
http://orgmode.org/tmp/worg/org-contrib/babel/languages/ob-doc-LaTeX.html.



However, in this org version (8.3 beta+) you get the same / similar
results using

---> begin example <---
  ** Maße und Gewichte
  #+tblname: masse
  #+attr_latex: :align lll :booktabs t
  | 1 gestr. Teelöffel  | 1 gestr. Eßlöffel | 1 Tasse |
  | ca. 5 ccm   | ca 15 ccm | ca 120 ccm  |
  |-+---+-|
  | Zimt 2 g| Haferflocken 8 g  | Mehl 80 g   |
  | Paprika 2 g | Speisestärke 9 g  | Grieß 96 g  |
  | Speisestärke 2--3 g | Mehl, Semmelmehl 10 g | Zucker 90 g |
  | Zucker 4 g  | Salz, Zucker, Öl 15 g | |
  | Salz 5 g| Reis, Butter 15 g | |
---> end example <---


This change probably ought to be mentioned in the Changes for a 8.3 release.

Best regards,
Robert

Re: [O] Org-Timer has nice popups; how can I use them elsewhere?

[Bernhard Pröll]

This blogpost demonstrates the usage of org-agenda-to-appt:

http://emacs-fu.blogspot.co.at/2009/11/showing-pop-ups.html

Instead of a sound I call notify-send for example.

"Tory S. Anderson"  schrieb am Mon, 23. Mar 15:36:

So, orgmode timers have a nice popup when they run out; on my KDE, it's gentle 
GUI-box (not emacs) that nicely rises and falls. I would love to have this as 
how my appt reminders work, instead of the ugly minibuffer screeching; but 
looking through the org-timer code didn't give me any ideas. How can I achieve 
this?