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

[Andreas Leha]

Hi,

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:

--8<---cut here---start->8---
#+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
--8<---cut here---end--->8---

Re: [O] [patch] ob-latex: htlatex and imagemagick

[Andreas Leha]

Nicolas Goaziou  writes:
> Hello,
>
> Andreas Leha  writes:
>
>> please find attached a small patch that fixes a problem discussed
>> in [1].
>>
>> In short, when executing a latex src block and htlatex is a valid
>> option, it should be used even if imagemagick is part of the headers.
>
> Applied. Thank you.
>

Thanks,
Andreas

Re: [O] comment section with latex_header

[Andreas Leha]

Nicolas Goaziou  writes:
> 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.
>

Thanks.  Confirmed.

Andreas

Re: [O] [patch] ob-latex: htlatex and imagemagick

[Nicolas Goaziou]

Hello,

Andreas Leha  writes:

> please find attached a small patch that fixes a problem discussed
> in [1].
>
> In short, when executing a latex src block and htlatex is a valid
> option, it should be used even if imagemagick is part of the headers.

Applied. Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] comment section with latex_header

[Nicolas Goaziou]

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,

-- 
Nicolas Goaziou

Re: [O] fontenc makes pdf non-searchable

[Martin Leduc]

You're right, I customized org-latex-pdf-process, which now call a script that 
basically does latex/dvips/ps2pdf. 
I cannot use pdflatex since my figures are from eps images.

Martin


dboyd2  mmm.com (J. David Boyd) writes:

> And how did you determine that please?

I assume you mean how I determined that the PDF has been produced by
dvips and Ghostscript. In this case: I've just looked into the
document information of the PDF file. For example with Acrobat Reader
I just press CMD+D, with Apple Preview its CMD+I (look out in the
menus for document information or properties).

In this document information there is somewhere a line like "PDF
creator". If the PDF is created with pdftex or pdflatex, this line
should read something like "pdfTeX-1.40.15".

Each PDF viewer shows a different degree of details about the file.
For example with Apple Preview I do not see the used fonts, these are
only shown by Acrobat Reader (or command line tools like pdffonts from
xpdf).

> And how would it be switched?

The default settings of org-mode uses pdflatex. The compilation
process is configurable via the variable org-latex-pdf-process.

I don't know why and how Martin used dvips+gs. Maybe he just generated
the tex file with org and used another tool for generating PDF. Or
maybe he customized org-latex-pdf-process.

-- 
Until the next mail...,
Stefan.   

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

[Nicolas Goaziou]

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

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

[Nicolas Goaziou]

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] [PATCH] Fix massive slowdown in org-id-find

[Nicolas Goaziou]

Hello,

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).


Regards,

-- 
Nicolas Goaziou

Re: [O] refile error with org-inlinetask: The kill is not a set of trees

[Barrett Kirwan]

On Sun, Mar 15 2015 at 03:31:19 PM, Damien Couroussé
 wrote:
> I cannot refile inline tasks when using the package org-inlinetask.
>
> In the example below, I try to refile the TODO task to another heading.
> I get the error message "The kill is not a (set of) tree(s) - please use
>  to yank anyway".
>
> This looks like a problem of bad configuration, but after having read
> the file org-inlinetask.el, I don't have a clue what is the problem
> here. Any help will be greatly appreciated  :)

Has this been resolved? I'm having the same problem.

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

[Kyle Meyer]

torys.ander...@gmail.com (Tory S. Anderson) wrote:
> 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?

org-timer uses org-notify for this (which is in org-clock.el).  It seems
that appointments, on the other hand, use appt.el.  Specifically,
appt-display-message is used to show the message.  Perhaps you could set
appt-disp-window-function to a function that uses org-notify.

#+begin_src elisp
  (defun org-notify-display-appt (min-to-app new-time appt-msg)
"Use `org-notify' to display an appointment.
  You can use this for `appt-disp-window-function'.
  `appt-display-format' should be set to 'window, and
  `appt-delete-window-function' should be a function that does
  nothing."
;; FIXME: Update the message to incorporate MIN-TO-APP.  See
;; `appt-disp-window'.
(org-notify appt-msg))

  (setq appt-disp-window-function #'org-notify-display-appt)
  (setq appt-delete-window-function (lambda nil))
#+end_src

This seems to work when using appt-display-message directly.

#+begin_src elisp
  (appt-display-message "test" 1)
#+end_src

I think this should work with Org appointments, but I haven't tested it
(and I don't use appointment reminders myself, so perhaps I'm missing
something).  In any case, hopefully that gives you somewhere to start.

--
Kyle

Re: [O] html preamble

[Rasmus]

hymie!  writes:

> 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?

That is incorrect (IMO).  On a file basis you can turn off most preamble
things via the relevant OPTIONS keyword.

On a project basis you could set the relevant variable.  See
org-publish-project-alist.

I guess you could make a clever function that sets the org-html-preamble
based on some heuristics and add it to one of hooks that are run before
parsing.  See e.g. org-export-before-parsing-hook.

> 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?

org-html-preamble-format is a template, it seems, that is used by
org-html-preamble, which can also take a string or a function.  In
practice I always use org-html-preamble in ox-html projects.

> 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.

Hmm.  Does %d or %C work? See org-html-postamble-format.

Hope it helps,
Rasmus

-- 
I almost cut my hair, it happened just the other day

[O] Bug: reftex breaking after org-mode export [8.2.10 (8.2.10-35-g19a7d6-elpa @ /Users/adamjackson/.emacs.d/elpa/org-20150323/)]

[Adam Jackson]

Hi,

I've been struggling with Reftex in org-mode. Initially things are fine,
then after exporting the document to LaTeX and continuing to work with
org-mode, using most of the reftex features (e.g. reftex-toc or trying to
insert a reference) produces a "Wrong type argument: stringp, nil" error
message.

The code in my init file to set up reftex:

;; Reftex
(require 'reftex)
(defun org-mode-reftex-setup ()
  (load-library "reftex")
  (and (buffer-file-name) (file-exists-p (buffer-file-name))
 ;enable auto-revert-mode to update reftex when bibtex file changes on 
disk
 (global-auto-revert-mode t)
 (reftex-parse-all)
  (define-key org-mode-map (kbd "C-c [") 'reftex-citation)
 ;add a custom reftex cite format to insert links
 ;; (reftex-set-cite-format "** [[papers:%l][%l]]: %t \n")
 )
) 

(add-hook 'org-mode-hook 'org-mode-reftex-setup) 

At the moment I still enter reftex-mode on demand with "M-x reftex-mode".
Here is the backtrace for the error:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  re-search-forward(nil 10001 t)
  tex-main-file()
  reftex-TeX-master-file()
  reftex-insert-docstruct(# t "e" nil nil t nil nil 
("SEC:lagrange_gibbs_proof" "s" "We define the molar Gibbs free energy in a 
molecular gas mixture as \\begin{align} \\h" "/my/path/to/the/paper.org" nil) 
"" nil)
  byte-code("\306 \307\216\310 \210\311 \f\203\312rq\210\313
!)!\210\202&\312\314!\210\315 \210@\316=\2040\316 
\210\317\320p\"\210\321A\322\323\324\325\326B\327\330\331\332\333\257C\334 
\335U\203v\336D\337\340!\210\341  E
\336FGHIJ\206kKL\336&K)\202\211J\203\206\342   J
#K\202\211\321K\321DK\206\222\321K\336J\343MNOK\344P&\211Q@RQA@S\345Q8T\321KR\204\304\346\347\336\"\210R\350=\203\321\315
 \210\202 R\351=\204\337R\352=\203\365U\203\347\352R\315 \210\353 
TR#\210\202 R\354=\203
\315 \210G?G\202 R\355=\203
VJ\356 \202 
R\357=\2038
\315 \210U\2030
\360U!W\202 E?E\202 R\361=\203J
\315 
\210F?F\202 R\362=\203\\
\315 \210H?H\202 R\363=\203n
\315 
\210I?I\202 R\364=\203\201
XY\346\347\321\"\210\202 
R\365=\203\264
\366Z[\"[\367[Z8A!\206\236
\370\371![Z8@\206\251
\372L
q\210\373 \210\202 R;\203\324
\374R\\J\"\206\310
R
DCCY\346\347\321\"\210\202 
R\375>\203]\203\350
]\237Y\202\371
S\203\366
SCCY\202\371
\336YY\203R\376\232\203\377YBYYX
 q\210\346\347\321\"\210\202 \370\201^!\210*\202" [wconfig buf 
reftex-call-back-to-this-buffer reftex-latex-syntax-table 
reftex-use-multiple-selection-buffers typekey current-window-configuration 
((set-window-configuration wconfig)) delete-other-windows syntax-table 
switch-to-buffer-other-window reftex-make-selection-buffer-name "*RefTeX 
Select*" reftex-erase-buffer reftex-select-label-mode add-to-list 
selection-buffers t "  " mode-line-buffer-identification "  " 
global-mode-string "   (" ")" "  S<" reftex-refstyle ">" " -%-" buffer-size 0 
nil message "Creating Selection Buffer..." reftex-insert-docstruct 
reftex-get-offset reftex-select-item reftex-show-label-location 2 throw exit 
103 114 82 reftex-reparse-document 99 115 reftex-query-label-type 116 
prefix-numeric-value 70 ...] 13)
  reftex-offer-label-menu("e")
  reftex-reference()
  call-interactively(reftex-reference nil nil)

Many thanks,
Adam



Emacs  : GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36)
 of 2013-03-13 on bob.porkrind.org
Package: Org-mode version 8.2.10 (8.2.10-35-g19a7d6-elpa @ 
/Users/adamjackson/.emacs.d/elpa/org-20150323/)

current state:
==
(setq
 org-export-backends '(latex md ascii html icalendar beamer)
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-latex-classes '(("beamer" "\\documentclass[presentation]{beamer}" 
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("article" "\\documentclass[11pt]{article}" 
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}") 
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
  ("\\paragraph{%s}" . "\\paragraph*{%s}") 
("\\subparagraph{%s}" . "\\su

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

[Matthew Gidden]

Hi everyone,

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.

To clarify, I would like to inject an option `[t]` such that a .org file
that looks like
```
*** Foo

 Bar
:PROPERTIES:
:BEAMER_col: 0.45
:BEAMER_env: block
:END:
foo

 Baz
:PROPERTIES:
:BEAMER_col: 0.45
:BEAMER_env: block
:END:
foo
```

gets translated into tex that looks like
```
\begin{frame}[label=sec-x-y-z]{Foo}
\begin{columns}*[t]*
\begin{column}{0.45\columnwidth}
\begin{block}{Bar}
foo
\end{block}
\end{column}

\begin{column}{0.45\columnwidth}
\begin{block}{Baz}
foo
\end{block}
\end{column}
\end{columns}
\end{frame}
```

Note that an alternative of placing `[t]` after each `column` environment
would also work.

Has anyone gotten these environments to work nicely together?

Cheers,
Matt

[1] http://comments.gmane.org/gmane.emacs.orgmode/67508
[2] http://osdir.com/ml/emacs-orgmode-gnu/2009-12/msg00238.html
[3] http://osdir.com/ml/emacs-orgmode-gnu/2014-05/msg00980.html

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

[O] html preamble

[hymie!]

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.

Thanks.

--hymie!

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

[Leo Ufimtsev]

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 ::
- 

Instead, it is inserted above the current item, like:

- :: 
- Meaning of life

I'm running emacs 25.0.50.3

Thoughts?

Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

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

[Marcin Borkowski]

On 2015-03-23, at 17:48, Ista Zahn  wrote:

> Not an answer to your question, but alternative: the company-math[1]
> package makes it really easy to insert unicode.

Also, TeX input method.  Also, C-x 8 RET 2192 RET.  Also, filters.

> Best,
> Ista

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

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

[Tory S. Anderson]

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? 

Re: [O] fontenc makes pdf non-searchable

[Stefan Nobis]

dbo...@mmm.com (J. David Boyd) writes:

> And how did you determine that please?

I assume you mean how I determined that the PDF has been produced by
dvips and Ghostscript. In this case: I've just looked into the
document information of the PDF file. For example with Acrobat Reader
I just press CMD+D, with Apple Preview its CMD+I (look out in the
menus for document information or properties).

In this document information there is somewhere a line like "PDF
creator". If the PDF is created with pdftex or pdflatex, this line
should read something like "pdfTeX-1.40.15".

Each PDF viewer shows a different degree of details about the file.
For example with Apple Preview I do not see the used fonts, these are
only shown by Acrobat Reader (or command line tools like pdffonts from
xpdf).

> And how would it be switched?

The default settings of org-mode uses pdflatex. The compilation
process is configurable via the variable org-latex-pdf-process.

I don't know why and how Martin used dvips+gs. Maybe he just generated
the tex file with org and used another tool for generating PDF. Or
maybe he customized org-latex-pdf-process.

-- 
Until the next mail...,
Stefan.

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

[Rasmus]

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.

> \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: "¨>").

—Rasmus

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

Re: [O] Possible bug: Can not search for text in links - only description

[Rainer M Krug]

Achim Gratz  writes:

> Rainer M Krug  krugs.de> writes:
>> > M-x occur RET Exa RET
>> 
>> Ah - occur is nice - very nice. I like the output and also that it shows
>> me all hits - I'll use this more often!
>
> It even has a key binding: "M-s o".  If you like a function and wonder if it
> has a key binding: "C-h w  RET" will tell you (use it in the
> mode you'll want to use that function in, it may not have a key binding in
> other modes).

Very nice - learning each day something new.

Thanks,

Rainer

>
>
> Regards,
> Achim
>
>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

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

[Ista Zahn]

Not an answer to your question, but alternative: the company-math[1]
package makes it really easy to insert unicode.

Best,
Ista

[1] https://github.com/vspinu/company-math

On Mon, Mar 23, 2015 at 12:23 PM, Matt Price  wrote:
> 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 (→, ⇒)?
>
> \rightarrow will work, but doesn't give me the visual cue I want when
> working in org. And entering unicode directly in org is pretty distracting
> for me, as the gnome unicode shortcuts seem to turn themselves on and off
> whenever I upgrade.
>
> thanks!
> m
>

Re: [O] bug#18870: bug#18870: \emsp and alignment in org clock report

[J. David Boyd]

Nicolas Goaziou  writes:

> Nicolas Goaziou  writes:
>
>> The trick could be to use an Org entity which is as large as its
>> overlay. Even better if that entity is readable without that overlay.
>> I'll look into it soon.
>
> This should now be fixed. The markup used is more readable and doesn't
> alter table alignment.

Thanks very much, I feel this is much better.  I can read the columns ok, and
they export fine too.

Thanks for all your efforts in Org-mode!

Dave in Hudson, FL

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

[Matt Price]

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 (→, ⇒)?

\rightarrow will work, but doesn't give me the visual cue I want when
working in org. And entering unicode directly in org is pretty distracting
for me, as the gnome unicode shortcuts seem to turn themselves on and off
whenever I upgrade.

thanks!
m

Re: [O] fontenc makes pdf non-searchable

[J. David Boyd]

Stefan Nobis  writes:

> Martin Leduc  writes:
>
>> You can find a minimal example here[1], with the org file, and the
>> tex and pdf files generated from it. Firts try to search within the
>> pdf. It does not work (at least on my side) To solve the problem,
>> remove the line with \usepackage[T1]{fontenc}
>
> Your PDF is not generated with pdflatex (or a newer engine like
> lualatex), but with dvips and Ghostscript. Thus the fonts are not PS
> Type 1 fonts, but Type 3 fonts (bitmap instead of vector; therefore
> scaling/zooming will result in bad quality).
>
> I'm not quite sure if this is also the root cause of the inability to
> search. But if i recompile your tex-file (from [1]) with pdflatex, I
> get Type 1 fonts and have no problems with searching.
>
> Therefore I would suggest to switch the engine to pdflatex.
>
> Another hint: You should try the Latin Modern font (put a
> "\usepackage{lmodern}" after loading fontenc) -- it's the
> (technically) modern variant of Computer Modern (the old TeX default
> font). Lati Modern is available as OpenType font and has less problems
> with Unicode and special characters like german umlauts (ä, ü,...) or
> other non-ASCII letters.
>
> And maybe you should also have a look at biblatex[2] (as a much more
> flexible alternative to natbib).
>
> [1] https://www.dropbox.com/sh/7s6di4en5ljbkcq/AAAzyQeg6VkMHnC1X9dQTg6ua?dl=0
> [2] http://ctan.org/pkg/biblatex

And how did you determine that please?   And how would it be switched?

Dave

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

[hymie!]

In our last episode, the evil Dr. Lacto had captured our hero,
  hy...@lactose.homelinux.net (hymie!), who said:
>In our last episode, the evil Dr. Lacto had captured our hero,
>  Marcin Borkowski , who said:
>>,
>>| The goal of the savetrees package is to pack as much text as
>>| possible onto each page of a LaTeX document. Admittedly, this
>>| makes the document far less attractive. Nevertheless,
>>| savetrees is a simple way to save paper when printing draft copies
>>| of a document.
>>`
>
>I typically want my draft to look like my finished copy will look, so

I just realized that I mis-read the original question, so I will just
echo what somebody else said.

I use Org for writing and maintaining documentation, and my documentation
has to be readable to be usable.

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

Still no.

--hymie!http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net
My fitbit says I've walked 3381 steps today (as of 10:58).

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

[hymie!]

In our last episode, the evil Dr. Lacto had captured our hero,
  Marcin Borkowski , who said:
>,
>| The goal of the savetrees package is to pack as much text as
>| possible onto each page of a LaTeX document. Admittedly, this
>| makes the document far less attractive. Nevertheless,
>| savetrees is a simple way to save paper when printing draft copies
>| of a document.
>`

I typically want my draft to look like my finished copy will look, so

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

No.

--hymie!http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net
My fitbit says I've walked 3381 steps today (as of 10:58).

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

[Grant Rettke]

No. Yes.

On Sun, Mar 22, 2015 at 4:04 PM, Marcin Borkowski  wrote:
> Hi there,
>
> two questions for people using LaTeX (possibly only as Org-mode
> backend).
>
> 1. Did you know about the savetrees package by Scott Pakin
> (http://www.ctan.org/pkg/savetrees)?  From the description:
>
> ,
> | The goal of the savetrees package is to pack as much text as
> | possible onto each page of a LaTeX document. Admittedly, this
> | makes the document far less attractive. Nevertheless,
> | savetrees is a simple way to save paper when printing draft copies
> | of a document.
> `
>
> 2. Would you find it useful when producing PDF files other that
> scientific articles (using Org-mode or not)?
>
> (Note: I explained the rationale behind this survey in another post
> I sent to the list a few minutes ago in the thread about the #+SUBTITLE
> keyword.)
>
> Best,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Faculty of Mathematics and Computer Science
> Adam Mickiewicz University
>



-- 
Grant Rettke
g...@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson

Re: [O] Possible bug: Can not search for text in links - only description

[Achim Gratz]

Rainer M Krug  krugs.de> writes:
> > M-x occur RET Exa RET
> 
> Ah - occur is nice - very nice. I like the output and also that it shows
> me all hits - I'll use this more often!

It even has a key binding: "M-s o".  If you like a function and wonder if it
has a key binding: "C-h w  RET" will tell you (use it in the
mode you'll want to use that function in, it may not have a key binding in
other modes).


Regards,
Achim

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

[Florian Beck]

Hi,

the recent changes in org-id (presumably
8cdb2eef0f9f98f9e00a5e689decfe341fe0c6ec) lead to a massive slowdown.
org-id-find is slow as it is, now I find it almost unusable.

Attached patch provides a fix.
-- 
Florian Beck


>From 9867f0f45befc26854920d759a2505adba5d486b Mon Sep 17 00:00:00 2001
From: Florian Beck 
Date: Mon, 23 Mar 2015 11:35:09 +0100
Subject: [PATCH 362/362] org.el: Improve speed of org-find-property

* lisp/org.el (org-re-property): New optional argument.
(org-find-property): Simplify value search.
---
 lisp/org.el | 28 +---
 1 file changed, 17 insertions(+), 11 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index 85a8048..71c5e6e 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -6268,7 +6268,7 @@ takes into consideration inlinetasks."
 
 (defvar org-font-lock-keywords nil)
 
-(defsubst org-re-property (property &optional literal allow-null)
+(defsubst org-re-property (property &optional literal allow-null value)
   "Return a regexp matching a PROPERTY line.
 
 When optional argument LITERAL is non-nil, do not quote PROPERTY.
@@ -6276,14 +6276,22 @@ This is useful when PROPERTY is a regexp.  When ALLOW-NULL is
 non-nil, match properties even without a value.
 
 Match group 3 is set to the value when it exists.  If there is no
-value and ALLOW-NULL is non-nil, it is set to the empty string."
+value and ALLOW-NULL is non-nil, it is set to the empty string.
+
+With optional argument VALUE, match only property lines with
+that value; in this case, ALLOW-NULL is ignored.  VALUE is quoted
+unless LITERAL is non-nil."
   (concat
"^\\(?4:[ \t]*\\)"
(format "\\(?1::\\(?2:%s\\):\\)"
 	   (if literal property (regexp-quote property)))
-   (if allow-null
-   "\\(?:\\(?3:$\\)\\|[ \t]+\\(?3:.*?\\)\\)\\(?5:[ \t]*\\)$"
- "[ \t]+\\(?3:[^ \r\t\n]+.*?\\)\\(?5:[ \t]*\\)$")))
+   (cond (value
+	  (format "[ \t]+\\(?3:%s\\)\\(?5:[ \t]*\\)$"
+		  (if literal value (regexp-quote value
+	 (allow-null
+	  "\\(?:\\(?3:$\\)\\|[ \t]+\\(?3:.*?\\)\\)\\(?5:[ \t]*\\)$")
+	 (t
+	  "[ \t]+\\(?3:[^ \r\t\n]+.*?\\)\\(?5:[ \t]*\\)$"
 
 (defconst org-property-re
   (org-re-property "\\S-+" 'literal t)
@@ -16331,12 +16339,10 @@ part of the buffer."
   (save-excursion
 (goto-char (point-min))
 (let ((case-fold-search t)
-	  (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)
 
 (defun org-delete-property (property)
   "In the current entry, delete PROPERTY."
-- 
2.1.0

Re: [O] Possible bug: Can not search for text in links - only description

[Jacob Gerlach]

On Mon, Mar 23, 2015 at 8:45 AM, Rainer M Krug  wrote:
> First I must say it makes sense to give the error message, although I
> was quite surprised.
>
> But the message should contain a string one can easily search for. And I
> guess the most used search function is C-s I think the message should be
> changes to the description of the link and the target in brackets. This
> would make searching easier.

FWIW, I completely agree. I would be happy to provide a patch for
this, but I'm not sure how to get the link's description inside
org-export-resolve-fuzzy-link. AFAICT, the `link' object passed to
this function has properties as determined by
`org-element-link-parser'. The properties listed in the docstring
don't include the description.

Could anyone provide a hint on how to get the link's description?

Regards,
Jake

Re: [O] Possible bug: Can not search for text in links - only description

[Rainer M Krug]

Thanks everybody - many useful comments and ideas.

First I must say it makes sense to give the error message, although I
was quite surprised.

But the message should contain a string one can easily search for. And I
guess the most used search function is C-s I think the message should be
changes to the description of the link and the target in brackets. This
would make searching easier.

Thanks,

Rainer


Rainer M Krug  writes:

> Hi
>
> I got an error as follow when I tried to export:
>
> ,
> | org-babel-exp process R at line 5495...
> | Evaluation of this R code-block is disabled.
> | user-error: Unable to resolve link "*uLELFit"
> `
>
> I thought "OK - I'll search for uLELFit and just fix this link - but I
> could do what I wanted, I did not manage to find the link.
>
> I figured out that I can not search for text in the link.
>
> Thins is quite annoying, especially as I even thought of opening the
> file in another texteditor, search for the string, and save it again.
>
> As an example: if this link is in an org-mode file, A search for "exa"
> does not return any results.
>
> [[*Examples][Link to exp]]
>
> Is this a problem on my side?
> ,
> | Org-mode version 8.3beta (release_8.3beta-927-ge0b19d @ 
> /Users/rainerkrug/.emacs.d/org-mode/lisp/)
> | GNU Emacs 24.4.1 (x86_64-apple-darwin14.0.0, Carbon Version 157
> | AppKit 1343.16) of 2015-02-02 on Rainers-MacBook-Pro-4.local
> `
>
> Thanks,
>
> Rainer

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Possible bug: Can not search for text in links - only description

[Rainer M Krug]

"Charles C. Berry"  writes:

> On Fri, 20 Mar 2015, Ken Mankoff wrote:
>
>> It would be nice to be able to search in links without extra work to
>> change modes. Without this, you cannot even search for a cite key!
>
> You *can* search in links without changing modes.
>
> Exa RET
>
> runs nonincremental-search-forward on "Exa" and  finds Rainier's
> `*Example' if point preceeds it.
>
> M-x occur RET Exa RET

Ah - occur is nice - very nice. I like the output and also that it shows
me all hits - I'll use this more often!

Rainer

>
> finds the link, too.
>
> Chuck
>
>>
>>  -k.
>>
>> Please excuse brevity. Sent from pocket computer with tiny non-haptic 
>> feedback keyboard.
>>
>>> On Mar 20, 2015, at 11:38, Jacob Gerlach  wrote:
>>>
 On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug  wrote:
 Hi

 I got an error as follow when I tried to export:

 ,
 | org-babel-exp process R at line 5495...
 | Evaluation of this R code-block is disabled.
 | user-error: Unable to resolve link "*uLELFit"
 `

 I thought "OK - I'll search for uLELFit and just fix this link - but I
 could do what I wanted, I did not manage to find the link.

 I figured out that I can not search for text in the link.
>>>
>>> `org-toggle-link-display' is very helpful here. See [1] for a
>>> discussion of the patch and new behavior.
>>>
>>> It is perhaps worth considering to change the error message to show
>>> the link description (when it exists) rather than the link itself to
>>> make it easier to find the bad link.
>>>
>>> Regards,
>>> Jake
>>>
>>> [1] http://comments.gmane.org/gmane.emacs.orgmode/90891
>>>
>>
>>
>
> Charles C. Berry Dept of Family Medicine & Public Health
> cberry at ucsd edu   UC San Diego / La Jolla, CA 92093-0901
> http://famprevmed.ucsd.edu/faculty/cberry/
>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Possible bug: Can not search for text in links - only description

[Rainer M Krug]

Jacob Gerlach  writes:

> On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug  wrote:
>> Hi
>>
>> I got an error as follow when I tried to export:
>>
>> ,
>> | org-babel-exp process R at line 5495...
>> | Evaluation of this R code-block is disabled.
>> | user-error: Unable to resolve link "*uLELFit"
>> `
>>
>> I thought "OK - I'll search for uLELFit and just fix this link - but I
>> could do what I wanted, I did not manage to find the link.
>>
>> I figured out that I can not search for text in the link.
>
> `org-toggle-link-display' is very helpful here. See [1] for a
> discussion of the patch and new behavior.
>
> It is perhaps worth considering to change the error message to show
> the link description (when it exists) rather than the link itself to
> make it easier to find the bad link.

Agreed. But I think that showing both would be the d=best solution here.

>
> Regards,
> Jake
>
> [1] http://comments.gmane.org/gmane.emacs.orgmode/90891
>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] [proposal] timezone-aware timestamps enhancement

[e.fraga]

On Friday, 20 Mar 2015 at 11:29, Randomcoder wrote:

[...]

> So would your computer find out the timezone and switch it
> automatically ?
> (IIRC Ubuntu does that by default)

No, I would change the time zone manually.

>
> On Wed, Mar 18, 2015 at 04:33:44PM +, Eric S Fraga wrote:
>> org data were "local" time with a fluid definition of "local".
>
> I'd be interested in knowing a bit more about the "fluid definition".

Simply that I would put in the time that would be appropriate for where
I expected to be when the particular event were to take place.

Sometimes it's easier to not let the computers do everything!

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-790-gb719c1.dirty

Re: [O] [proposal] timezone-aware timestamps enhancement

[e.fraga]

On Friday, 20 Mar 2015 at 11:40, Randomcoder wrote:

[...]

> At this point in time I'm using Org-Mode's agenda to view events.
> Should I try to sync them up with my phone and if so what is the recommended
> way to go ?

I use MobileOrg on Android to sync between org and Google's calendar.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-790-gb719c1.dirty

Re: [O] comment section with latex_header

[Andreas Leha]

Hi Rasmus,

Rasmus  writes:
> Andreas Leha  writes:
>
>> Hi Rasmus,
>>
>> Rasmus  writes:
>>> Andreas Leha  writes:
>>>
 Hi all,

 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)
>>>
>>> Why?  I guess you can still archive 
>>
>> Could you expand on that?
>
> Sorry, I must have clicked C-c C-c by accident.
>
> #+LATEX_HEADERs in :noexport: sections are included.  I guess that code in
> COMMENT sections aren't included.  So I guess keywords could also be
> excluded.  I don't know.
>
> —Rasmus

Thanks,
Andreas

Re: [O] comment section with latex_header

[Rasmus]

Andreas Leha  writes:

> Hi Rasmus,
>
> Rasmus  writes:
>> Andreas Leha  writes:
>>
>>> Hi all,
>>>
>>> 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)
>>
>> Why?  I guess you can still archive 
>
> Could you expand on that?

Sorry, I must have clicked C-c C-c by accident.

#+LATEX_HEADERs in :noexport: sections are included.  I guess that code in
COMMENT sections aren't included.  So I guess keywords could also be
excluded.  I don't know.

—Rasmus

-- 
⠠⠵

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

[Sebastien Vauban]

Marcin Borkowski wrote:
> Hi there,
>
> two questions for people using LaTeX (possibly only as Org-mode
> backend).
>
> 1. Did you know about the savetrees package by Scott Pakin
> (http://www.ctan.org/pkg/savetrees)?  From the description:
>
> ,
> | The goal of the savetrees package is to pack as much text as
> | possible onto each page of a LaTeX document. Admittedly, this
> | makes the document far less attractive. Nevertheless,
> | savetrees is a simple way to save paper when printing draft copies
> | of a document.
> `

Yes.

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

Not sure about that. All my work reports are made in Org mode and
exported to PDF. They never are "scientific" reports (they're discussion
notes with TODO items, etc.), and I must adhere to the format others use
when writing in Word.

Best regards,
  Seb

-- 
Sebastien Vauban

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

[Sebastien Vauban]

Marcin Borkowski wrote:
> On 2015-03-22, at 16:29, Rasmus  wrote:
>
>> IMO it is.  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.
>
> Hi there,
>
> being like a Pavlov's dog trained to dribble on seeing the word
> LaTeX;-), let me add my 2 cents here.
>
> [TL;DR: imho, the right way to do LaTeX export is to prepare a dedicated
> package for Org-mode generated files (easy/medium), arrange for it to be
> included in all major TeX distros (easy) and simplify the LaTeX exporter
> to comply with it (easy).  This could greatly enhance the quality of
> PDFs produced by Org-mode and make modifying their look easier on the
> Org side.  I could do the LaTeX side of the work.  Now the question is:
> does the community /want/ it.]
>
> The (default) LaTeX markup sucks.  (It’s not about Org-mode-produced
> LaTeX files, it’s about LaTeX itself.)  And I'm telling that as
> a long-time TeX and LaTeX user and fan.  I would strongly suggest not
> caring too much about “what does LaTeX support out-of-the-box” – in
> fact, it supports almost nothing without a heap of packages.
>
> What I really think Org-mode community should do is the following.
>
> We (if I may use that pronoun here) should prepare a dedicated Org LaTeX
> package, properly supporting all Org’s fancy stuff like tags,
> timestamps, todo keywords etc., and allowing for parametrizing their
> look-and-feel through a reasonable LaTeX interface.  I think it should
> /not/ be a class, since then people would be free to use it with
> article/amsart/koma-script/memoir/whatever.  This is not very difficult
> nor time-consuming, and in fact I might be tempted to do it (more on
> that below).  This would require (simple) changes in the LaTeX exporter
> (generally, simplifying it); this I cannot do, since I don’t have the
> FSF papers signed (and I don’t want to sign them).  OTOH, the package
> does not have this problem, since LaTeX licensing is much more sane than
> Emacs’; this package should be imho part of every TeX distro (which is
> important, and in fact easy to arrange), so that we could send an
> Org-generated LaTeX file to any TeX user.
>
> The biggest advantage would be the possibility of exporting e.g. TODO
> lists or agendas to LaTeX, and have them formatted as TODO lists and
> agendas and not as “articles”.  Currently, LaTeX export is more or less
> limited to scientific articles (unless you want to tweak it /a lot/ so
> that it looks even remotely reasonable), where you don’t really care
> about layout and design, since they are going to be changed by the
> journal anyway.
>
> Just think about the possibilities.  We could make a TODO list in Org,
> and send it (as a pdf file) for non-Org-users to print, and it could
> look like a TODO-list.  (I guess there are still lots of people who
> depend on paper todo lists; I do, for sure, though I make them
> manually.)  We could have an option (on Org side, which would translate
> to a LaTeX one) to have more Word-like layout.  (You can say what you
> want about Word – my personal opinion is that it is unsuitable for
> documents larger/more complex than a piece of paper with an arrow
> showing the direction to the restroom – but sometimes, especially for
> short memos/notes, LaTeX’s extremely generic spacing can be annoying.
> Of course, you could just load the savetrees package – but let me make
> a short, informal and unscientific survey here: how many of you would
> find it useful, but never thought that something like that exists?  If,
> OTOH, there would be such option for the LaTeX exporter, it would be
> right there, in Org-mode manual.  In fact, since not everyone might
> follow this thread, let me start another one, with this very question in
> a minute;-).)
>
> The added benefit would be much cleaner structure of Org-generated LaTeX
> files.  Currently, they have a huge preamble and a few hard-wired
> things.
>
> Summing up: as we know, there are many ways people use Org-mode, but the
> current PDF exporter (through LaTeX’s article class, heavily biased
> toward scientific material) is suboptimal for all but one of these ways.
>
> As I said, if there is some consensus on whether something like that is
> needed, I can start working on it.  (In fact, it might be a fun
> side-project.)  I would estimate that I’d need a week or two to come up
> with a proof-of-concept, sort-of-working thing, and something like two
> months with a first production version.  (Though I don’t have time for
> a project like this now, realistically I could start in August.)  (Let
> me thank here for Org-mode clocking feature – the above estimate is due
> to the fact that I did some work on coding a dedicated, quite complex
> LaTeX class for a journal, and I know that it has taken me about 32
> hours as of now.  Assuming an average pace of 2-4 hours

Re: [O] comment section with latex_header

[Sebastien Vauban]

Rasmus wrote:
> 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)
>
> Why?  I guess you can still archive 

I'd also say that this is a bug, as -- in my understanding --
COMMENT'ing a subtree is exactly equivalent to commenting every line of
it, that is:

--8<---cut here---start->8---
* COMMENT Section
Some text
Some code
Some text
--8<---cut here---end--->8---

should be equivalent to:

--8<---cut here---start->8---
# * Section
# Some text
# Some code
# Some text
--8<---cut here---end--->8---

Best regards,
  Seb

-- 
Sebastien Vauban

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

[Stefan Nobis]

Marcin Borkowski  writes:

> 1. Did you know about the savetrees package by Scott Pakin

Yes.

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

No. I use org-mode mostly for documentation and even documentation
should look nice (the whitespace in a document is there for a reason;
IIRC in the documentation of koma-script there is some rationale for
the layout).

There are many other ways to influence the layout and save
whitespace on paper. Personally, I use the koma-script classes and
playing with parameters like DIV IMHO give more appealing results. For
controlling the body there are also quite some good packages (like
enumitem), that allow more fine grained control.

With a simple "#+LATEX_HEADER_EXTRA: \usepackage[extreme]{savetrees}"
it's very easy to get this special effect. But maybe we should make
this easier with a special option like "uglyandcompressed:t" (pun
intended)?

I'm not against a more compact and cleaned up preamble and maybe a
special orgmode package for LaTeX may be a good idea. But fiddling
with the layout of a document should never be the default and only be
enabled via explicit options, as quite some classes out there do a
really good job.

BTW: If producing PDF for screenreading is important, we should think
about an easy option to switch to A5 with a sane layout. A5 is much
better for screenreading than A4 and even 2 pages A5 printed on a
single A4 looks quite good and readable. The main benefit: With A5
there is much less whitespace (see documentation of koma-script for an
example). Maybe A5 output should be the default setting?

-- 
Until the next mail...,
Stefan.

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

[Michael Strey]

Hi Marcin,

On So, 2015-03-22, Marcin Borkowski wrote:

[...]

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

I've heard about it but never used it.


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

Yes.  I'm currently using Orgmode LaTeX export for sales activity
reports, letters, Beamer presentations, minutes, and check lists.  In
the past I've been using LaTeX (without Orgmode) for manuals and even
for data sheets.

Best regards
Michael

-- 
Michael Strey
http://www.strey.biz * https://twitter.com/michaelstrey

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

[Marcin Borkowski]

On 2015-03-23, at 01:05, Rasmus  wrote:

> Hi,
>
> First: Please don't take me being critical as meaning I'm necessarily
> negative about.  I'm just minimizing risk over the expectation.

Of course, fine with me.  It’s the criticism which can make this project
better (or help decide it’s unnecessary, which would spare the unneeded
work;-)).  Also, you make me think more and refine my idea, so thanks
for the criticism!

> Marcin Borkowski  writes:
>
>>> - What happens when you cannot maintain it any longer?  Note also that the
>>
>> Either the project dies, or someone takes it over.  The latter seems to
>> be quite common in the LaTeX community, so I wouldn't be very worried.
>
> That does not seem like something you'd want to base Org on...

You might have misunderstood me.  I did not claim that it's often in the
TeX world that people abandon projects, but /if/ they do, it's common
that someone takes over the package.  (Though I don’t have any real
data, just my gut feeling.)

>>>   scope is somewhat different as a typical latex package solves a problem
>>>   like "provide good tables" or "enhance itemize 2e" (ei2e).  Such
>>>   packages are fairly easy to replace (e.g. sugfigure → subcaption).
>>
>> Fair enough.  Not a problem imho, though.  A “package” has a very wide
>> definition in the LaTeX world, and I explained why a package would be
>> better than a class (even though doing it as a package would be a bit
>> more work with ensuring that it works with wide range of classes).
>
> I am talking about latex packages and the example mentions real latex
> packages.  A class would be a sure route to failure.  A packages is fine.
> But it's beside the point.  You argue, if I understand correctly, for
> amending ox-latex to rely on a very specialized package, which we may or
> may not easily be able to replace should it come to that.

Well, currently it relies on 15 packages anyway, including marvosym and
wasysym which might not be present in every TeX installation, btw.
(They should /really/ be only included when actually needed!)  I don't
see much difference.

Besides, I'm not telling about /replacing/ the current exporter.  The
behavior I'm talking about could be optional, and turned on by an
option.  It would require changes to, say, maybe half of the transcoders
in ox-latex, and a new preamble – and that would be probably it.
Instead of replacing them, they might behave in two ways (“old” one and
“new” one) based on some option.

Finally, assuming that it gets stable after a few months, I don’t see
the need for “replacing” it.  I don’t think Org syntax is about to
change drastically.

I can see your concern, though.  If my proposal gets some traction, then
Org would indeed depend on something which is not under its control, and
it might be a real concern for some people.  OTOH, it /does/ depend on
a few third-party tools anyway – some LaTeX packages, too.  (Though they
are stable, and not tightly coupled with Org itself.)

But take, for instance, the current discussion about Org and
bibliographies (which I’m only aware of, I don’t follow it).  Assuming
Org gets some standard syntax for citations, there will be a need for
properly exporting them to LaTeX (probably using biblatex or optionally
amsrefs).  But these packages already exists, and are stable and
well-known, and it’s fine to call them, so it doesn’t seem a problem for
me.  Assuming we don’t want to clutter the exported file with
\usepackage’s, this would require adding /a few lines/ to the proposed
package (\RequirePackage{biblatex} and possibly some simple default
setup).

OTOH, the change in the proposed package /would/ be needed if something
is added to Org core (like TODO keywords, tags or timestamps), which is
not directly supported by LaTeX.  I wouldn’t expect that to happen very
often.

>>> - I don't want latex code generated by org to a "special flavor" like with
>>>   LyX.
>
>> In my vision, the huge preamble is replaced by \usepackage{orglatex} or
>> something like this, and instead of, say,
>
> OK.
>
>> : \section{{\bfseries\sffamily TODO} hello\hfill{}\textsc{world}}
>>
>> (how is that not a “special flavor”?) you would have
>>
>> : \section{\orgtodo{TODO}hello\orgtags{world}}
>>
>> or, if we decide to do a major surgery on LaTeX’s sectioning mechanism
>> (which is debatable), even
>>
>> : \section[orgtodo=TODO,orgtags=world]{hello}
>
> Both are appealing.
>
>>> - Why can the issues you have in mind not be solved by a specialized
>>>   derived backend?  Such as ox-beamer or ox-koma-letter.
>>
>> This seems to bug you enough that you basically asked twice;-).
>
> No.  Here is ask why you can't settle for another Org-mode backend, rather
> than a new latex package.  This can even live in contrib without signing
> the copyright agreement with FSF.

If it lives in contrib – which is fine for me personally – it would be
used by a lot less people.  If it’s official, Org would have better PDF
support /by default/.

Notice that there might

Re: [O] comment section with latex_header

[Andreas Leha]

Hi Rasmus,

Rasmus  writes:
> Andreas Leha  writes:
>
>> Hi all,
>>
>> 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)
>
> Why?  I guess you can still archive 

Could you expand on that?

Best,
Andreas

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

[Samuel Loury]

Marcin Borkowski  writes:

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

No.

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

Yes
-- 
Konubinix
GPG Key: 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A


signature.asc
Description: PGP signature

[O] signing of FSF papers needed for documentation changes? (was: Re: PATCH: Document how to scroll calendar by one year at date prompt.)

[Gregor Zattler]

Hi Nicolas,
* Nicolas Goaziou  [23. Mar. 2015]:
> I added TINYCHANGE at the end of the commit message, since you don't
> seem to have signed FSF papers. Please correct me if I'm wrong.

You are right.  Thanks.

Do these copyright/assigment issues also apply to documentation
chenges?  One would only be allowed to do max n lines of
documentation changes without legal paperwork with the FSF?

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: [O] fontenc makes pdf non-searchable

[Stefan Nobis]

Martin Leduc  writes:

> You can find a minimal example here[1], with the org file, and the
> tex and pdf files generated from it. Firts try to search within the
> pdf. It does not work (at least on my side) To solve the problem,
> remove the line with \usepackage[T1]{fontenc}

Your PDF is not generated with pdflatex (or a newer engine like
lualatex), but with dvips and Ghostscript. Thus the fonts are not PS
Type 1 fonts, but Type 3 fonts (bitmap instead of vector; therefore
scaling/zooming will result in bad quality).

I'm not quite sure if this is also the root cause of the inability to
search. But if i recompile your tex-file (from [1]) with pdflatex, I
get Type 1 fonts and have no problems with searching.

Therefore I would suggest to switch the engine to pdflatex.

Another hint: You should try the Latin Modern font (put a
"\usepackage{lmodern}" after loading fontenc) -- it's the
(technically) modern variant of Computer Modern (the old TeX default
font). Lati Modern is available as OpenType font and has less problems
with Unicode and special characters like german umlauts (ä, ü,...) or
other non-ASCII letters.

And maybe you should also have a look at biblatex[2] (as a much more
flexible alternative to natbib).

[1] https://www.dropbox.com/sh/7s6di4en5ljbkcq/AAAzyQeg6VkMHnC1X9dQTg6ua?dl=0
[2] http://ctan.org/pkg/biblatex
-- 
Until the next mail...,
Stefan.