Re: [O] no fontification of #+BEGIN_LaTeX blocks

[Sebastien Vauban]

Hi Julien,

Julien Cubizolles wrote:
>> But I'm not really sure to understand what you try to achieve. Could you be
>> more explicit? Could you give a minimal example file?
>
> In the following, begin, center, and braces get different colors
> #+BEGIN_SRC latex
>  \begin{center}
> \includegraphics[width=0.5\textwidth]{figures/fresnel}
>   \end{center}
> #+END_SRC
>
> Here everything is the same color, not very good for readability.
> #+BEGIN_LaTeX
>   \begin{center}
> \includegraphics[width=0.5\textwidth]{figures/fresnel}
>   \end{center}
> #+END_LaTeX
>
> Since I use them for pieces of code to be exported to Beamer, the latex
> block is easier to use (no export options to take care of) but less
> readable. Anyway I can edit both with org-edit-src-code, with
> fontification, and I'm happy with that so far.

I perfectly understand your need, now: to have *syntax highlighting* of
everything in a #+BEGIN/END_LaTeX block (the same would be true for HTML or
...).

This is something I'd like to get as well, in fact!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] no fontification of #+BEGIN_LaTeX blocks

[Julien Cubizolles]

"Sebastien Vauban" 
writes:


> I perfectly understand your need, now: to have *syntax highlighting* of
> everything in a #+BEGIN/END_LaTeX block (the same would be true for HTML or

I guess I mixed the concepts of fontification/highlighting up :-)

Julien.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Carsten Dominik]

On 17.9.2013, at 08:01, Matt Price  wrote:

> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price  wrote:
>> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz  wrote:
>>> 
>>> Or you could leave it in and see who complains.  The instances where
>>> xdg-open doesn't work or is not correctly configured will probably be in
>>> multi-user / corporate environments where it is unlikely that the newest Org
>>> or Emacs is installed anyway.
>> 
>> Hi,
>> 
>> I'm running today's org with a recent emacs-snapshot in a single-user
>> linux environment (ubuntu 13.04).
>> 
>> xdg-open xxx.html works fine when run from the command line, but from
>> inside org-mode it seems to fail to run  In particular, html, odt and
>> pdf documents no longer seem to open from the export menu, even though
>> the log in *Messages* reports that the relevant command
>> ("xdg-open-my-org-file.html") has been run.

Is there anyone else who has tried the xgd-open way to follow links with Org?

Cheers

- Carsten

>> 
>> Can I help diagnose this?  toggle-debug-on-error doesn't give me any extra 
>> info.
>> 
> 
> 
> hmm, it looks like xdg-open isn't the culprit -- no matter what I set
> in org-file-apps, the command doesn't seem to run.
>> Thanks!
>> Matt
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

[O] Error when recomputing the line of a table

[Alan Schmitt]

Hello,

I have a problem when recomputing the last line of a table. If I hit
"C-c *", I get the following (in the debugger):

--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("^ *" nil)
  org-table-align()
  org-table-recalculate(nil)
  call-interactively(org-table-recalculate)
  org-ctrl-c-star()
  call-interactively(org-ctrl-c-star nil nil)
--8<---cut here---end--->8---

What is really strange is that if I copy the file to another location on
the disk and try to recompute the line, I don't get this error, so it's
quite difficult to provide a minimal example with the problem.

I looked at a little at the code, and the problem comes from here:

--8<---cut here---start->8---
;; Get the rows
(setq lines (org-split-string
 (buffer-substring beg end) "\n"))
;; Store the indentation of the first line
(if (string-match "^ *" (car lines))
--8<---cut here---end--->8---

for some reason `lines' is nil, which causes the problem. The table is
far from empty (it has more than 500 lines).

I tried to get a little more information from the backtrace evaluating
expressions, and it seems that `beg' is bound to 42, and `end' to
"#"

One strange thing is that position 42 is not in the table at all, it's
in a code block right before it (42 is right before the reset). This is
what the beginning of my file looks like:

--8<---cut here---start->8---
#+begin_src gnuplot :var data=data-table
reset

set title "PW"
set size ratio square

set xlabel "Date"
set xdata time
set timefmt "%Y-%m-%d"
set format x "%Y-%m"
set xtics nomirror

plot data using 1:4 with lines axis x1y1 title 'Week',
 data using 1:5 with lines axis x1y1 title 'Month'
#+end_src

#+tblname: data-table
| Date |   Q |  Cumul | 7 days | 30 days | Global |
|--+-+++-+|
| [2012-03-19 Mon] |   0 |  0 | NA |  NA |   0.00 |
| [2012-03-20 Tue] |   4 |  4 | NA |  NA |   2.00 |
| [2012-03-21 Wed] |   8 | 12 | NA |  NA |   4.00 |
| [2012-03-22 Thu] |   7 | 19 | NA |  NA |   4.75 |
...
--8<---cut here---end--->8---

I'd gladly provide more information, but I don't really know how to do
it. (Of course, if I debug "org-table-begin", everything works as
expected.)

Any suggestion as how to try to track this down?

Thanks,

Alan

[O] some movement on zotero!

[Matt Price]

hi,

Just found this:

http://zotero-odf-scan.github.io/zotero-odf-scan/

don't havetime to look thorugh it yet, but it looks like a way to
write in org-mode and still use a zotero bibliography.  It wil mean
that odt is the only really usable export, though.

I'd be interested to hear what other people think -- as I say, rushing
to get some work done right now!

Matt

[O] #+BEAMER_THEME fails

[Loris Bennett]

Hi,

Using Emacs 24.2.1 (Org mode 8.1.1) and having read the page

  http://orgmode.org/worg/exporters/beamer/ox-beamer.html

I assumed I would be able to set the Beamer theme using

  #+BEAMER_THEME: Madrid

However, this did not work and I just got the default theme.  However,
looking at 

  http://orgmode.org/worg/exporters/beamer/presentation.org.html

I found the more cryptic

  #+latex_header: \mode{\usetheme{Madrid}}

which did work.

Am I missing something here?

Cheers,

Loris

-- 
This signature is currently under construction.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Glyn Millington]

Carsten Dominik  writes:

> On 17.9.2013, at 08:01, Matt Price  wrote:
>
>> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
>> wrote:
>>> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz 
>>> wrote:
  Or you could leave it in and see who complains.  The instances
 where xdg-open doesn't work or is not correctly configured will
 probably be in multi-user / corporate environments where it is
 unlikely that the newest Org or Emacs is installed anyway.
>>>  Hi,
>>> 
>>> I'm running today's org with a recent emacs-snapshot in a
>>> single-user linux environment (ubuntu 13.04).
>>> 
>>> xdg-open xxx.html works fine when run from the command line, but
>>> from inside org-mode it seems to fail to run In particular, html,
>>> odt and pdf documents no longer seem to open from the export menu,
>>> even though the log in *Messages* reports that the relevant command
>>> ("xdg-open-my-org-file.html") has been run.
>
> Is there anyone else who has tried the xgd-open way to follow links
> with Org?
>

Yes, I have the same symptoms as Matt.

GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
Org-mode 8.1.1  (the latest ELPA package fails in the same way)

xdg-open works on the command line but not through the org-export menu -
pdfs and html files don't open automatically.  There are no error messages.

atb




Glyn

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Eric S Fraga]

Carsten Dominik  writes:

> On 11.9.2013, at 13:05, Eric S Fraga  wrote:
>
>> Hi,
>> 
>> A minor feature request.  Feel free to ignore!
>> 
>> Using the sidewaystable :float option for table exports to LaTeX
>> requires one to manually add a 
>> 
>>  #+LaTeX_header: \usepackage{rotating}
>> 
>> line to the org file.  Could this package be added automatically by the
>> exporter if the sidewaystable option is present?
>
> After a long discussion:  Yes, rotating has been added to the default 
> packages.
> Tabu has not been added, but this is now documented in the manual.

Thanks for both of these changes.

> Thanks to everyone who contributed to this discussion.

I've enjoyed the discussion.  Some very well reasoned arguments on both
sides.  This has been an example of the Internet (I almost wrote USENET
;-) at its best!

Thanks again,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.1.1-7-gaecdf5

[O] create a sparse tree by TODO and property? possible?

[Xebar Saram]

Hi all

can one create a sparse tree using 2 queries, In particular i want to
create a sparse tree that has all heading marked TODO and that have a
specific property i set IE:
:PROPERTIES:
:food_type: indian
:END:

so i would like sparse tree for example to show 'indian' property but also
TODO state

thx in advancce!

z.

[O] export error "unknown marker at"

[Xebar Saram]

Hi all

i tried this with various org mode files i have and its always the same.
whenever i go to export an org mode file via C-c C-e i get the following
error:

"unknown marker at X" where X is different from file to file. i go to line
X in each file and take a look but nothing seems out of the ordinary. i
even delete that file but nothing helps. i habe yet to be able to export
orgmode files.

Im using latest org from MELPA (0.8.1) and latest emacs.

any help/ideas to solve this would be greatly appreciated

Z.

Re: [O] #+BEAMER_THEME fails

[Suvayu Ali]

Hi Loris,

On Tue, Sep 17, 2013 at 10:22:40AM +0200, Loris Bennett wrote:
> Hi,
> 
> Using Emacs 24.2.1 (Org mode 8.1.1) and having read the page
> 
>   http://orgmode.org/worg/exporters/beamer/ox-beamer.html
> 
> I assumed I would be able to set the Beamer theme using
> 
>   #+BEAMER_THEME: Madrid
> 
> However, this did not work and I just got the default theme.  However,
> looking at 

Can you provide a minimal working example[1] with a sample of the exported
LaTeX code for you?

>   http://orgmode.org/worg/exporters/beamer/presentation.org.html
> 
> I found the more cryptic
> 
>   #+latex_header: \mode{\usetheme{Madrid}}
> 
> which did work.

Well, this inserts raw LaTeX in the exported file.  So yes, that should
always work.


Footnotes:

[1] 

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [PATCH] Added language support for et

[mihkel]

Hi Carsten and thanks for replying. I made suggested modifications and
here is v2:

From 3081cd92a2f5868d5c52e70d2eff4ecff95566d7 Mon Sep 17 00:00:00 2001
From: mihkel 
Date: Tue, 17 Sep 2013 15:33:54 +0300
Subject: [PATCH] Added proper language support for et (Estonian)

---
 lisp/ox.el | 14 ++
 1 file changed, 14 insertions(+)

diff --git a/lisp/ox.el b/lisp/ox.el
index 07239a0..10354b2 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -5218,6 +5218,7 @@ them."
  ("de" :default "Autor")
  ("eo" :html "Aŭtoro")
  ("es" :default "Autor")
+ ("et" :default "Autor")
  ("fi" :html "Tekijä")
  ("fr" :default "Auteur")
  ("hu" :default "Szerzõ")
@@ -5241,6 +5242,7 @@ them."
  ("de" :default "Datum")
  ("eo" :default "Dato")
  ("es" :default "Fecha")
+ ("et" :html "Kuupäev" :utf-8 "Kuupäev")
  ("fi" :html "Päivämäärä")
  ("hu" :html "Dátum")
  ("is" :default "Dagsetning")
@@ -5260,6 +5262,7 @@ them."
  ("da" :default "Ligning")
  ("de" :default "Gleichung")
  ("es" :html "Ecuación" :default "Ecuación")
+ ("et" :html "Võrrand" :utf-8 "Võrrand")
  ("fr" :ascii "Equation" :default "Équation")
  ("no" :default "Ligning")
  ("nb" :default "Ligning")
@@ -5270,6 +5273,7 @@ them."
  ("da" :default "Figur")
  ("de" :default "Abbildung")
  ("es" :default "Figura")
+ ("et" :default "Joonis")
  ("ja" :html "図" :utf-8 "図")
  ("no" :default "Illustrasjon")
  ("nb" :default "Illustrasjon")
@@ -5280,6 +5284,7 @@ them."
  ("da" :default "Figur %d")
  ("de" :default "Abbildung %d:")
  ("es" :default "Figura %d:")
+ ("et" :default "Joonis %d:")
  ("fr" :default "Figure %d :" :html "Figure %d :")
  ("ja" :html "図%d: " :utf-8 "図%d: ")
  ("no" :default "Illustrasjon %d")
@@ -5294,6 +5299,7 @@ them."
  ("de" :html "Fußnoten" :default "Fußnoten")
  ("eo" :default "Piednotoj")
  ("es" :html "Nota al pie de página" :default "Nota al pie de página")
+ ("et" :html "Allmärkused" :utf-8 "Allmärkused")
  ("fi" :default "Alaviitteet")
  ("fr" :default "Notes de bas de page")
  ("hu" :html "Lábjegyzet")
@@ -5315,6 +5321,7 @@ them."
  ("da" :default "Programmer")
  ("de" :default "Programmauflistungsverzeichnis")
  ("es" :default "Indice de Listados de programas")
+ ("et" :default "Loendite nimekiri")
  ("fr" :default "Liste des programmes")
  ("no" :default "Dataprogrammer")
  ("nb" :default "Dataprogrammer")
@@ -5323,6 +5330,7 @@ them."
  ("da" :default "Tabeller")
  ("de" :default "Tabellenverzeichnis")
  ("es" :default "Indice de tablas")
+ ("et" :default "Tabelite nimekiri")
  ("fr" :default "Liste des tableaux")
  ("no" :default "Tabeller")
  ("nb" :default "Tabeller")
@@ -5333,6 +5341,7 @@ them."
  ("da" :default "Program %d")
  ("de" :default "Programmlisting %d")
  ("es" :default "Listado de programa %d")
+ ("et" :default "Loend %d")
  ("fr" :default "Programme %d :" :html "Programme %d :")
  ("no" :default "Dataprogram")
  ("nb" :default "Dataprogram")
@@ -5341,11 +5350,13 @@ them."
  ("da" :default "jævnfør afsnit %s")
  ("de" :default "siehe Abschnitt %s")
  ("es" :default "vea seccion %s")
+ ("et" :html "Vaata peatükki %s" :utf-8 "Vaata peatükki %s")
  ("fr" :default "cf. section %s")
  ("zh-CN" :html "参见第%d节" :utf-8 "参见第%s节"))
 ("Table"
  ("de" :default "Tabelle")
  ("es" :default "Tabla")
+ ("et" :default "Tabel")
  ("fr" :default "Tableau")
  ("ja" :html "表" :utf-8 "表")
  ("zh-CN" :html "表" :utf-8 "表"))
@@ -5353,6 +5364,7 @@ them."
  ("da" :default "Tabel %d")
  ("de" :default "Tabelle %d")
  ("es" :default "Tabla %d")
+ ("et" :default "Tabel %d")
  ("fr" :default "Tableau %d :")
  ("ja" :html "表%d:" :utf-8 "表%d:")
  ("no" :default "Tabell %d")
@@ -5367,6 +5379,7 @@ them."
  ("de" :default "Inhaltsverzeichnis")
  ("eo" :default "Enhavo")
  ("es" :html "Índice")
+ ("et" :default "Sisukord")
  ("fi" :html "Sisällysluettelo")
  ("fr" :ascii "Sommaire" :default "Table des matières")
  ("hu" :html "Tartalomjegyzék")
@@ -5388,6 +5401,7 @@ them."
  ("da" :default "ukendt reference")
  ("de" :default "Unbekannter Verweis")
  ("es" :default "referencia desconocida")
+ ("et" :default "Tundmatu viide")
  ("fr" :ascii "Destination inconnue" :default "Référence inconnue")
  ("zh-CN" :html "未知引用" :utf-8 "未知引用")))
   "Dictionary for export engine.
-- 
1.8.3.1



Mihkel Vain

Carsten Dominik  writes:

> Hi Mihkel,
>
> thank you for the patch.  It is in principle already too long for a
> contributor without signed papers, but I am going to interpret it as
> "just" a translation table.
>
> If you look at how other languages are done - people have used HTML
> entities like а in order to be independent of the charset of the
> file.  Could you please resubmit and chang

Re: [O] #+BEAMER_THEME fails

[Loris Bennett]

Hi Suvayu,

Suvayu Ali  writes:

> Hi Loris,
>
> On Tue, Sep 17, 2013 at 10:22:40AM +0200, Loris Bennett wrote:
>> Hi,
>> 
>> Using Emacs 24.2.1 (Org mode 8.1.1) and having read the page
>> 
>>   http://orgmode.org/worg/exporters/beamer/ox-beamer.html
>> 
>> I assumed I would be able to set the Beamer theme using
>> 
>>   #+BEAMER_THEME: Madrid
>> 
>> However, this did not work and I just got the default theme.  However,
>> looking at 
>
> Can you provide a minimal working example[1] with a sample of the exported
> LaTeX code for you?

That was a good suggestion, as it helped me to find the problem.  My
mistake was exporting to LaTeX

  As PDF file

instead of 

  As PDF file (Beamer)

In principle it is clear when you do 'C-x C-e' that you should choose
the latter option if you are using Beamer.  However, I didn't come
across any mention of export to Beamer being different from export to
non-beamer PDF in the documentation.  So maybe it would be an idea to
add a section about exporting to the tutorial

  http://orgmode.org/worg/exporters/beamer/tutorial.html

to help the easily-confused, like myself.

As a matter of interest, has the new exporter always behaved like that?
And what is the rationale behind the distinction?

>>   http://orgmode.org/worg/exporters/beamer/presentation.org.html
>> 
>> I found the more cryptic
>> 
>>   #+latex_header: \mode{\usetheme{Madrid}}
>> 
>> which did work.
>
> Well, this inserts raw LaTeX in the exported file.  So yes, that should
> always work.
>
>
> Footnotes:
>
> [1] 

Cheers,

Loris

-- 
This signature is currently under construction.

Re: [O] #+BEAMER_THEME fails

[Suvayu Ali]

Hi Loris,

On Tue, Sep 17, 2013 at 02:51:36PM +0200, Loris Bennett wrote:
> Hi Suvayu,
> 
> Suvayu Ali  writes:
> 
> > Hi Loris,
> >
> > On Tue, Sep 17, 2013 at 10:22:40AM +0200, Loris Bennett wrote:
> >> Hi,
> >> 
> >> Using Emacs 24.2.1 (Org mode 8.1.1) and having read the page
> >> 
> >>   http://orgmode.org/worg/exporters/beamer/ox-beamer.html
> >> 
> >> I assumed I would be able to set the Beamer theme using
> >> 
> >>   #+BEAMER_THEME: Madrid
> >> 
> >> However, this did not work and I just got the default theme.  However,
> >> looking at 
> >
> > Can you provide a minimal working example[1] with a sample of the exported
> > LaTeX code for you?
> 
> That was a good suggestion, as it helped me to find the problem.  My
> mistake was exporting to LaTeX
> 
>   As PDF file
> 
> instead of 
> 
>   As PDF file (Beamer)
> 
> In principle it is clear when you do 'C-x C-e' that you should choose
> the latter option if you are using Beamer.  However, I didn't come
> across any mention of export to Beamer being different from export to
> non-beamer PDF in the documentation.  So maybe it would be an idea to
> add a section about exporting to the tutorial
> 
>   http://orgmode.org/worg/exporters/beamer/tutorial.html
> 
> to help the easily-confused, like myself.
> 
> As a matter of interest, has the new exporter always behaved like that?
> And what is the rationale behind the distinction?
> 

The answer is: it is a feature.  Documenting it is actually among my
TODOs[1].  If you would like to add something to any of the articles,
please feel free to contribute.

  

In case sending SSH keys is not possible or complicated for you, you can
send a patch, I can commit it for you.  In any case, I will try to
update the articles when I can find the time.

Cheers,


Footnotes:

[1] 

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Rasmus]

Hi Carsten,

Carsten Dominik  writes:

> I'd be interested to see a patch to this effect.

For now here's the filter I use and a add-to-list that hopefully
works.  It could be turned into a general function such that

   - Certain packages are only required with certain flavors of TeX
 (curtsy of iftex).
   - It only applies to the preamble (e.g. I don't want it in my
 code-blocks).

For me it works great because I can quickly check drafts with pdftex
(which is substantially faster on my system) and switch to xelatex or
lualatex for more serious drafts.

  (setq rasmus/org-protected-packages '(inputenc fontenc))
  (add-to-list 'org-latex-default-packages-alist '("" "iftex" nil))

  (defun rasmus/org-latex-filter-protect-inputenc (text backend info)
"Make inputenc and fontenc only load when using pdflatex"
(when (org-export-derived-backend-p backend 'latex 'beamer)
  (replace-regexp-in-string
   (format  "\\(usepackage\\[.*\\]{\\(%s\\)}\\)"
(mapconcat 'symbol-name pank/org-protected-packages "\\|"))
   "ifPDFTeX\\1elsefi"
   text)))

  (add-to-list 'org-export-filter-final-output-functions
   'rasmus/org-latex-filter-protect-inputenc)


The output tex file looks something like this:

  \ifPDFTeX\usepackage[utf8]{inputenc}\else\fi
  \ifPDFTeX\usepackage[T1]{fontenc}\else\fi

BTW: I think the \else is redundant.

–Rasmus

--
There are known knowns; there are things we know that we know.

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Rasmus]

Hi Eric,

>> While automatic package handling is very exciting it could go awry.
>
> I'm not too in favor of automatic package detection. Unless it works
> nearly perfectly, it just seems like trading one kind of user irritation
> for another.

Yeah.

> Personally, I _always_ blast the default packages and load my own stuff.
>
> One potential middle ground would be providing defaults "sets": for
> instance LATEX_MATH_DEFAULTS (or whatever), that provided a couple
> choices for math-related package suites that are known to work well
> together.
>
> Meh, maybe not.

It's just not much different from org-latex-classes. . .  Perhaps it
would be nice for reproducibility between documents.  But, yeah. . .

>> Fixes are usually available.  For instance, I use a filter to disable
>> fontenc/inputenc if pdflatex is not used (it breaks xelatex for me).
>
> If anything was going to be automatically detected and handled, it seems
> like it should be this. This is one of the main reasons I gave up trying
> to use the defaults at all.

The nice thing is that such stuff can be handled pretty conveniently
on the TeX side so that documents can be used for different engines
cf. my other post.  I also use this for e.g. fonts; I like Linux
Libertine for the final version, but usually don't want to deal with
the slowdown of xelatex.

–Rasmus

-- 
The Kids call him Billy the Saint

Re: [O] Customizing TOCs in Derived Exporters

[Rasmus]

Hi Josiah,

Josiah Schwab  writes:

> How does one go about overriding org-html-toc, which unlike something
> like org-html-bold, does not appear in org-export-define-backend?  I
> don't want the TOC not to appear, rather want it to be generated by
> another function, org-md-toc or what have you.

I'm not sure whether this would work with md simply 'cause I haven't
worked with the html+friends exporter(s), but perhaps you could
replace the inner-template, i.e. write a replacement for
org-html-inner-template.

–Rasmus

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

Re: [O] create a sparse tree by TODO and property? possible?

[Suvayu Ali]

On Tue, Sep 17, 2013 at 01:48:59PM +0200, Xebar Saram wrote:
> Hi all
> 
> can one create a sparse tree using 2 queries, In particular i want to
> create a sparse tree that has all heading marked TODO and that have a
> specific property i set IE:
> :PROPERTIES:
> :food_type: indian
> :END:
> 
> so i would like sparse tree for example to show 'indian' property but also
> TODO state

I don't think this is possible.  But I think you can do an agenda search
restricted to the current buffer, `C-c a < m  RET'.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Suvayu Ali]

On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
> Carsten Dominik  writes:
> 
> > On 17.9.2013, at 08:01, Matt Price  wrote:
> >
> >> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
> >> wrote:
> >>> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz 
> >>> wrote:
>   Or you could leave it in and see who complains.  The instances
>  where xdg-open doesn't work or is not correctly configured will
>  probably be in multi-user / corporate environments where it is
>  unlikely that the newest Org or Emacs is installed anyway.
> >>>  Hi,
> >>> 
> >>> I'm running today's org with a recent emacs-snapshot in a
> >>> single-user linux environment (ubuntu 13.04).
> >>> 
> >>> xdg-open xxx.html works fine when run from the command line, but
> >>> from inside org-mode it seems to fail to run In particular, html,
> >>> odt and pdf documents no longer seem to open from the export menu,
> >>> even though the log in *Messages* reports that the relevant command
> >>> ("xdg-open-my-org-file.html") has been run.
> >
> > Is there anyone else who has tried the xgd-open way to follow links
> > with Org?
> >
> 
> Yes, I have the same symptoms as Matt.
> 
> GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
> Org-mode 8.1.1  (the latest ELPA package fails in the same way)
> 
> xdg-open works on the command line but not through the org-export menu -
> pdfs and html files don't open automatically.  There are no error messages.

I see the same problem.  But I think this might be an Emacs issue; I
can't open a pdf from dired either (with & on a pdf file).  However I
can open it if I execute a shell command: M-! xdg-open file.pdf RET.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] error message at line break

[henry atting]

henry atting  writes:

> Nicolas Goaziou  writes:
>
>> Hello,
>>
>> henry atting  writes:
>>
>>> Okay, say I have an org file with two lines in it (fill-column is set to
>>> 70). Here you go:
>>>
>>>
>>> Jemand mußte Josef K. verleumdet haben, denn ohne daß er etwas Boeses
>>> getan haette, wurde er eines Morgens verhaftet. Die Koechin der Frau
>>>
>>>
>>> Then you go on with the text, which is:
>>>
>>> Grubach, seiner Zimmervermieterin, die ihm jeden Tag gegen acht Uhr frueh
>>> das Fruehstueck brachte,...
>>>
>>> At each automatic line skip I get the mentioned error message. But if
>>> you indent these two lines one space everything works fine.
>>
>> Strange, I still cannot reproduce it.
>>
> Strange, in deed. I can reproduce it even this way:
>
> 1. Start emacs with `emacs -Q'
> 2. Add my org directory to the load path 
> 3. Load org-mode
> 4. Then type the above quoted beginning of Kafka's Prozess
>

Finally... the culprit was:

(setq-default auto-fill-function 'do-auto-fill) 

A very old setting in my ~/.emacs. Now that I start auto-fill with the
appropriate hook everythings works fine.

henry

Re: [O] #+TAGS has some groups with many entries, suppress hotkey assignment

[Jeff Kowalczyk]

Carsten Dominik writes:
> Please take a look at the variable org-use-fast-tag-selection
> and see if there is a setting that you find useful.

Thanks Carsten, 'auto is the behaviour I am seeking.

Is org-use-fast-tag-selection 'auto working as intended? It seems to
be acting like value t as described in the function doc string.

My Emacs 24 with org-mode git master has the default value:

: org-use-fast-tag-selection
: auto

I can reproduce a minimal test file:


#+TAGS: { admin(a) reporting(r) util(u) foo }
#+TAGS: { projecta projectb projectc(c) }
#+TAGS: { billable(b) nonbillable(e) unknown(k) }

* headline


Where C-c C-c on headline gives the selector:


Inherited:
Current:

{ [a] admin [r] reporting [u] util  [f] foo}
{ [p] projecta  [d] projectb  [c] projectc  }
{ [b] billable  [e] nonbillable   [k] unknown   }


I would have anticipated only explicit single key selectors, e.g.:


Inherited:
Current:

{ [a] admin [r] reporting [u] util  foo}
{ projecta  projectb  [c] projectc  }
{ [b] billable  [e] nonbillable   [k] unknown   }


Thanks,
Jeff

[O] configuration's issues for publishing

[pw]

Hi,

I'm a new user of org-mode and I'm a little bit confused with 
configuration's issues.


My purpose is to use org-mode in order to publish a website (and spare 
me the time needed by html editing). I'm not use to org-mode but I do 
know emacs.


At the bottom of this email is my configuration for org-publishing. I 
putted it into my .emacs. I don't know if it is the right thing to do ?


These settings works (html files are created) but the propriety values 
are not working. For example, I do not want section numbering 
(:section-numbers nil) or toc (:with-toc nil) but I have both in my html 
result.


I'm wonder why these settings are not working. Moreover, I do not know 
where is the right place to put this kind of information : into .emacs 
or inside .org files with #+... format.


My last question is the following : where are the documentation string 
for publishing options ? On the manual it's written : "See the 
documentation string of these options for details." 
(http://orgmode.org/manual/Publishing-options.html#Publishing-options) 
but I cannot find it. I'm looking for a reference with the description 
of every possible string.


Thanks for taking the time to read my newbie questions.

pw


---
;; org-mode publishing
(setq org-publish-project-alist
  '(("org-notes"
 :base-directory "~/site/org/"
 :base-extension "org"
 :publishing-directory "~/site/public_html/"
 :recursive t
 :publishing-function org-html-publish-to-html
 :section-numbers nil
 :with-toc nil
 :author nil
 :creator-info nil
 :export-creator-info nil
 :export-author-info nil
 )
("org-static"
 :base-directory "~/site/org/"
 :base-extension "css\\|js\\|png\\|jpg\\|pdf\\|mp3\\|ogg"
 :publishing-directory "~/site/public_html/"
 :recursive t
 :publishing-function org-publish-attachment
 )
("site" :components ("org-notes" "org-static"
--

Re: [O] #+BEAMER_THEME fails

[Eric S Fraga]

Loris Bennett  writes:

[...]

> However, this did not work and I just got the default theme.  However,
> looking at 
>
>   http://orgmode.org/worg/exporters/beamer/presentation.org.html
>
> I found the more cryptic
>
>   #+latex_header: \mode{\usetheme{Madrid}}
>
> which did work.
>
> Am I missing something here?

I see you have already solved your problem (export to beamer, not
LaTeX).  FYI, the line you found was for the previous exporter which did
not have a separate export to beamer.  This will still work but the new
BEAMER_THEME directive is more friendly!

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.1.1-7-gaecdf5

[O] css stylesheet

[pw]

Hi,

I want to define the layout of one html file exported from org-mode. I 
have putted into the org file this lign to appeal the stylesheet :





It's works ! But when I look at the html code generated, I can see a bunch of 
css which I do not want (see below).


Why this css code is here and how can I remove it ?

pw



 

[O] [PATCH] Columnview: Fix the case of #+ content present

[Benjamin Beckwith]

* lisp/org-colview.el (org-dblock-write:columnview): Change the
  capture of pos to after inserting the original content

The problem is with a block that has content preceding the table.
Upon recreating the content, the `pos' gets set to the beginning of
this content instead of the table.  Later calls to
`org-table-recalculate' or `org-table-align' will fail because the
point is not at a table.

This patch moves the capture of `pos' to right before the insertion of
the table.

TINYCHANGE
---
 lisp/org-colview.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-colview.el b/lisp/org-colview.el
index f3b8e42..8790ad4 100644
--- a/lisp/org-colview.el
+++ b/lisp/org-colview.el
@@ -1306,10 +1306,10 @@ PARAMS is a property list of parameters:
(if (eq 'hline x) x (cons "" x)))
  tbl))
(setq tbl (append tbl (list (cons "/" (make-list nfields "<>"))
-  (setq pos (point))
   (when content-lines
(while (string-match "^#" (car content-lines))
  (insert (pop content-lines) "\n")))
+  (setq pos (point))
   (insert (org-listtable-to-string tbl))
   (when (plist-get params :width)
(insert "\n|" (mapconcat (lambda (x) (format "<%d>" (max 3 x)))
--
1.8.1.2

Re: [O] create a sparse tree by TODO and property? possible?

[Carsten Dominik]

On 17.9.2013, at 13:48, Xebar Saram  wrote:

> Hi all
> 
> can one create a sparse tree using 2 queries, In particular i want to create 
> a sparse tree that has all heading marked TODO and that have a specific 
> property i set IE:
> :PROPERTIES:
> :food_type: indian
> :END:
> 
> so i would like sparse tree for example to show 'indian' property but also 
> TODO state

Yes, this is possible.

C-c / m food_type="indian"/TODO  RET


The match syntax is described here:

http://orgmode.org/manual/Matching-tags-and-properties.html#Matching-tags-and-properties

- Carsten

> 
> thx in advancce!
> 
> z. 
>  



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] Connect to the ssh and execute any command

[Andrey Tykhonov]

On Tue, Sep 17, 2013 at 08:54:51AM +0200, Michael Albinus wrote:
> Andrey Tykhonov  writes:
> 
> Hi Andrey,

Hi Michael!

> 
> >> Tramp does not use FUSE for ssh connections. Please show an example
> >> connection to the remote host, and how it fails.
> 
> > Here I try to "ls -la" and get the following error:
> >
> > Couldn't find a POSIX `id' command
> 
> Your remote host does not find a proper "id" command. What happens, if
> you call the following commands in a shell on that remote host:
> 
> # id -u

id: Command not found.

> # id --version

id: Command not found.

> # which id

id: Command not found.

> # whereis id

whereis: Command not found.

I also didn't find 'id' by means of

find / -name id

As I understand TRAMP is not able to work without 'id'. Therefore TRAMP is
not suitable for me...

> # uname -a

FreeBSD {hostname} 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Sep 13
21:22:42 PDT 2013 auto-build@{hostname}:{some/path/} amd64

Here I replaced real hostname by {hostname}.



Best regards,
Andrey


> 
> > Best regards,
> > Andrey.
> 
> Best regards, Michael.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Suvayu Ali]

On Tue, Sep 17, 2013 at 09:34:34PM +0200, Carsten Dominik wrote:
> 
> On 17.9.2013, at 15:56, Suvayu Ali  wrote:
> 
> > On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
> >> Carsten Dominik  writes:
> >> 
> >>> On 17.9.2013, at 08:01, Matt Price  wrote:
> >>> 
>  On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
>  wrote:
> > 
> > xdg-open xxx.html works fine when run from the command line, but
> > from inside org-mode it seems to fail to run In particular, html,
> > odt and pdf documents no longer seem to open from the export menu,
> > even though the log in *Messages* reports that the relevant command
> > ("xdg-open-my-org-file.html") has been run.
> >>> 
> >>> Is there anyone else who has tried the xgd-open way to follow links
> >>> with Org?
> >>> 
> >> 
> >> Yes, I have the same symptoms as Matt.
> >> 
> >> GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
> >> Org-mode 8.1.1  (the latest ELPA package fails in the same way)
> >> 
> >> xdg-open works on the command line but not through the org-export menu -
> >> pdfs and html files don't open automatically.  There are no error messages.
> > 
> > I see the same problem.  But I think this might be an Emacs issue; I
> > can't open a pdf from dired either (with & on a pdf file).  However I
> > can open it if I execute a shell command: M-! xdg-open file.pdf RET.
> 
> Do I need to conclude that, for the time being, xdg-open has to be removed 
> from the default value of org-file-apps?

Yes, I think so.  The problem is consistently repeatable.

It's strange though.  I'll try to investigate.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Carsten Dominik]

On 17.9.2013, at 21:42, Suvayu Ali  wrote:

> On Tue, Sep 17, 2013 at 09:34:34PM +0200, Carsten Dominik wrote:
>> 
>> On 17.9.2013, at 15:56, Suvayu Ali  wrote:
>> 
>>> On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
 Carsten Dominik  writes:
 
> On 17.9.2013, at 08:01, Matt Price  wrote:
> 
>> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
>> wrote:
>>> 
>>> xdg-open xxx.html works fine when run from the command line, but
>>> from inside org-mode it seems to fail to run In particular, html,
>>> odt and pdf documents no longer seem to open from the export menu,
>>> even though the log in *Messages* reports that the relevant command
>>> ("xdg-open-my-org-file.html") has been run.
> 
> Is there anyone else who has tried the xgd-open way to follow links
> with Org?
> 
 
 Yes, I have the same symptoms as Matt.
 
 GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
 Org-mode 8.1.1  (the latest ELPA package fails in the same way)
 
 xdg-open works on the command line but not through the org-export menu -
 pdfs and html files don't open automatically.  There are no error messages.
>>> 
>>> I see the same problem.  But I think this might be an Emacs issue; I
>>> can't open a pdf from dired either (with & on a pdf file).  However I
>>> can open it if I execute a shell command: M-! xdg-open file.pdf RET.
>> 
>> Do I need to conclude that, for the time being, xdg-open has to be removed 
>> from the default value of org-file-apps?
> 
> Yes, I think so.  The problem is consistently repeatable.
> 
> It's strange though.  I'll try to investigate.

Hi Suvayu,

Thank you!

- Carsten

> 
> Cheers,
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] [export] Easy way to make children of Beamer frames generate list items?

[Christoph LANGE]

Hi Suvayu,

2013-09-15 14:42 Suvayu Ali:
> I added these entries on Worg.  Do you think this helps future users
> with similar questions?
>
> 
> 

Thanks for writing up these FAQ.  They look very helpful to me.

Cheers,

Christoph

-- 
Christoph Lange, School of Computer Science, University of Birmingham
http://cs.bham.ac.uk/~langec/, Skype duke4701

→ Mathematics in Computer Science Special Issue on “Enabling Domain
  Experts to use Formalised Reasoning”; submission until 31 October.
  http://cs.bham.ac.uk/research/projects/formare/pubs/mcs-doform/

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Carsten Dominik]

On 17.9.2013, at 15:56, Suvayu Ali  wrote:

> On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
>> Carsten Dominik  writes:
>> 
>>> On 17.9.2013, at 08:01, Matt Price  wrote:
>>> 
 On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
 wrote:
> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz 
> wrote:
>> Or you could leave it in and see who complains.  The instances
>> where xdg-open doesn't work or is not correctly configured will
>> probably be in multi-user / corporate environments where it is
>> unlikely that the newest Org or Emacs is installed anyway.
> Hi,
> 
> I'm running today's org with a recent emacs-snapshot in a
> single-user linux environment (ubuntu 13.04).
> 
> xdg-open xxx.html works fine when run from the command line, but
> from inside org-mode it seems to fail to run In particular, html,
> odt and pdf documents no longer seem to open from the export menu,
> even though the log in *Messages* reports that the relevant command
> ("xdg-open-my-org-file.html") has been run.
>>> 
>>> Is there anyone else who has tried the xgd-open way to follow links
>>> with Org?
>>> 
>> 
>> Yes, I have the same symptoms as Matt.
>> 
>> GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
>> Org-mode 8.1.1  (the latest ELPA package fails in the same way)
>> 
>> xdg-open works on the command line but not through the org-export menu -
>> pdfs and html files don't open automatically.  There are no error messages.
> 
> I see the same problem.  But I think this might be an Emacs issue; I
> can't open a pdf from dired either (with & on a pdf file).  However I
> can open it if I execute a shell command: M-! xdg-open file.pdf RET.

Do I need to conclude that, for the time being, xdg-open has to be removed from 
the default value of org-file-apps?

- Carsten

> 
> Cheers,
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Suvayu Ali]

Hi,

Some comments and a question.

On Tue, Sep 17, 2013 at 09:42:50PM +0200, Suvayu Ali wrote:
> On Tue, Sep 17, 2013 at 09:34:34PM +0200, Carsten Dominik wrote:
> > 
> > On 17.9.2013, at 15:56, Suvayu Ali  wrote:
> > 
> > > I see the same problem.  But I think this might be an Emacs issue; I
> > > can't open a pdf from dired either (with & on a pdf file).  However I
> > > can open it if I execute a shell command: M-! xdg-open file.pdf RET.
> 
> It's strange though.  I'll try to investigate.

I can consistently repeat this outside of Org.  I am trying with
`dired-do-shell-command'.

Steps:
1) (dired-do-shell-command "xdg-open" nil '("file.pdf")), the script
   runs and opens the pdf file.
2) (dired-do-shell-command "xdg-open &" nil '("file.pdf")), this runs
   the script too but the pdf is not opened.

(I know the scripts run because I turned on debugging in the scripts)

I'm assuming Org opens it asynchronously.  What lisp function does Org
use?  A weekly related issue: when following links to pdf files, I have
the same problem.  When following https links I have no issues, they
open in my web browser as expected.  Does org use a similar mechanism
when following links?

Any thoughts?

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Carsten Dominik]

On 17.9.2013, at 22:21, Suvayu Ali  wrote:

> Hi,
> 
> Some comments and a question.
> 
> On Tue, Sep 17, 2013 at 09:42:50PM +0200, Suvayu Ali wrote:
>> On Tue, Sep 17, 2013 at 09:34:34PM +0200, Carsten Dominik wrote:
>>> 
>>> On 17.9.2013, at 15:56, Suvayu Ali  wrote:
>>> 
 I see the same problem.  But I think this might be an Emacs issue; I
 can't open a pdf from dired either (with & on a pdf file).  However I
 can open it if I execute a shell command: M-! xdg-open file.pdf RET.
>> 
>> It's strange though.  I'll try to investigate.
> 
> I can consistently repeat this outside of Org.  I am trying with
> `dired-do-shell-command'.
> 
> Steps:
> 1) (dired-do-shell-command "xdg-open" nil '("file.pdf")), the script
>   runs and opens the pdf file.
> 2) (dired-do-shell-command "xdg-open &" nil '("file.pdf")), this runs
>   the script too but the pdf is not opened.
> 
> (I know the scripts run because I turned on debugging in the scripts)
> 
> I'm assuming Org opens it asynchronously.  What lisp function does Org
> use?

Org used start-process-shell-command, and this happens in
org-open-file, which is called for links to a file in org-open-at-point.


>  A weekly related issue: when following links to pdf files, I have
> the same problem.  When following https links I have no issues, they
> open in my web browser as expected.  Does org use a similar mechanism
> when following links?

http and https links are followed using browse-url.

- Carsten

> 
> Any thoughts?
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.



signature.asc
Description: Message signed with OpenPGP using GPGMail

[O] Spaces in HTML export

[Simon W. Jones]

Hello,

A few days ago I raised a problem with HTML export I was having and was advised 
to upgrade to Orgmode 8.1. I have now done so but the problem persists. The 
problem significantly effects my workflow and I would be very grateful for a 
solution.

If I add a link in my document to an external website that has spaces in the 
URL, for example www.example.com/useful%20document.pdf, then export as HTML, 
the URL appears in the HTML output as www.example.com/useful%2520document.pdf. 
The link obviously then returns an error when one clicks on it.

Is there any way round this issue, can anyone else replicate the problem?

Many thanks,

Simon.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Glyn Millington]

Carsten Dominik  writes:

> On 17.9.2013, at 15:56, Suvayu Ali 
> wrote:
>
>> On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
>>> Carsten Dominik  writes:
>>> 
 On 17.9.2013, at 08:01, Matt Price  wrote:
 
> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
> wrote:
>> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz 
>> wrote:
>>> Or you could leave it in and see who complains.  The instances
>>> where xdg-open doesn't work or is not correctly configured will
>>> probably be in multi-user / corporate environments where it is
>>> unlikely that the newest Org or Emacs is installed anyway.
>> Hi,
>> 
>> I'm running today's org with a recent emacs-snapshot in a
>> single-user linux environment (ubuntu 13.04).
>> 
>> xdg-open xxx.html works fine when run from the command line, but
>> from inside org-mode it seems to fail to run In particular,
>> html, odt and pdf documents no longer seem to open from the
>> export menu, even though the log in *Messages* reports that the
>> relevant command ("xdg-open-my-org-file.html") has been run.
  Is there anyone else who has tried the xgd-open way to follow
 links with Org?
 
>>>  Yes, I have the same symptoms as Matt.
>>> 
>>> GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
>>> Org-mode 8.1.1 (the latest ELPA package fails in the same way)
>>> 
>>> xdg-open works on the command line but not through the org-export
>>> menu - pdfs and html files don't open automatically.  There are no
>>> error messages.
>>  I see the same problem.  But I think this might be an Emacs issue;
>> I can't open a pdf from dired either (with & on a pdf file).
>> However I can open it if I execute a shell command: M-! xdg-open
>> file.pdf RET.
>
> Do I need to conclude that, for the time being, xdg-open has to be
> removed from the default value of org-file-apps?

That did the trick - pdf files now open as before, as do html exports.

Many thanks.

atb




Glyn

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Suvayu Ali]

Hi,

On Tue, Sep 17, 2013 at 10:31:41PM +0200, Carsten Dominik wrote:
> 
> On 17.9.2013, at 22:21, Suvayu Ali  wrote:
> > 
> > I can consistently repeat this outside of Org.  I am trying with
> > `dired-do-shell-command'.
> > 
> > Steps:
> > 1) (dired-do-shell-command "xdg-open" nil '("file.pdf")), the script
> >   runs and opens the pdf file.
> > 2) (dired-do-shell-command "xdg-open &" nil '("file.pdf")), this runs
> >   the script too but the pdf is not opened.
> > 
> > (I know the scripts run because I turned on debugging in the scripts)
> > 
> > I'm assuming Org opens it asynchronously.  What lisp function does Org
> > use?
> 
> Org used start-process-shell-command, and this happens in
> org-open-file, which is called for links to a file in org-open-at-point.

I need some feedback from users using different desktop environments.
What DEs do you use, Matt, Glyn?

I am on XFCE.  For me xdg-open calls the internal function (defined in
the script), open_xfce.  Inside that function, exo-open is called.  This
is XFCE specific.  When I replace exo-open with say, evince, and open a
pdf file; start-process-shell-command works; with exo-open it doesn't.
I can repeat this for html files with Firefox.

I would like to know if other desktop environments has the same issue:
kde-open (KDE) and gvfs-open (Gnome, Mate, etc).  So to test, just open
a directory with pdf/odt/html files in dired and run either of them
asynchronously with &.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Matt Price]

On Tue, Sep 17, 2013 at 5:25 PM, Suvayu Ali  wrote:
> Hi,
>
> On Tue, Sep 17, 2013 at 10:31:41PM +0200, Carsten Dominik wrote:
>>
>> On 17.9.2013, at 22:21, Suvayu Ali  wrote:
>> >
>> > I can consistently repeat this outside of Org.  I am trying with
>> > `dired-do-shell-command'.
>> >
>> > Steps:
>> > 1) (dired-do-shell-command "xdg-open" nil '("file.pdf")), the script
>> >   runs and opens the pdf file.
>> > 2) (dired-do-shell-command "xdg-open &" nil '("file.pdf")), this runs
>> >   the script too but the pdf is not opened.
>> >
>> > (I know the scripts run because I turned on debugging in the scripts)
>> >
>> > I'm assuming Org opens it asynchronously.  What lisp function does Org
>> > use?
>>
>> Org used start-process-shell-command, and this happens in
>> org-open-file, which is called for links to a file in org-open-at-point.
>
> I need some feedback from users using different desktop environments.
> What DEs do you use, Matt, Glyn?
>
> I am on XFCE.  For me xdg-open calls the internal function (defined in
> the script), open_xfce.  Inside that function, exo-open is called.  This
> is XFCE specific.  When I replace exo-open with say, evince, and open a
> pdf file; start-process-shell-command works; with exo-open it doesn't.
> I can repeat this for html files with Firefox.
>
> I would like to know if other desktop environments has the same issue:
> kde-open (KDE) and gvfs-open (Gnome, Mate, etc).  So to test, just open
> a directory with pdf/odt/html files in dired and run either of them
> asynchronously with &.


I'm running unity in Ubuntu 13.04, which still is sorta descended from
gnome.  Neither xdg-open nor gnome-open seems to work (if I'm doing
this right in dired: navigate to a pdf/html file, type &, enter
xdg-open).

I have the feeling the problem is in emacs, org-open-file, or their
interaction.  It's definitely not in xdg-open/gnome-open themselves,
as they work fine from the command-line with M-! .

thanks guys,
Matt

>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Matt Price]

On Tue, Sep 17, 2013 at 5:25 PM, Glyn Millington
 wrote:
> Carsten Dominik  writes:
>
>> On 17.9.2013, at 15:56, Suvayu Ali 
>> wrote:
>>
>>> On Tue, Sep 17, 2013 at 09:04:45AM +0100, Glyn Millington wrote:
 Carsten Dominik  writes:

> On 17.9.2013, at 08:01, Matt Price  wrote:
>
>> On Tue, Sep 17, 2013 at 12:42 AM, Matt Price 
>> wrote:
>>> On Tue, Sep 3, 2013 at 5:12 AM, Achim Gratz 
>>> wrote:
 Or you could leave it in and see who complains.  The instances
 where xdg-open doesn't work or is not correctly configured will
 probably be in multi-user / corporate environments where it is
 unlikely that the newest Org or Emacs is installed anyway.
>>> Hi,
>>>
>>> I'm running today's org with a recent emacs-snapshot in a
>>> single-user linux environment (ubuntu 13.04).
>>>
>>> xdg-open xxx.html works fine when run from the command line, but
>>> from inside org-mode it seems to fail to run In particular,
>>> html, odt and pdf documents no longer seem to open from the
>>> export menu, even though the log in *Messages* reports that the
>>> relevant command ("xdg-open-my-org-file.html") has been run.
>  Is there anyone else who has tried the xgd-open way to follow
> links with Org?
>
  Yes, I have the same symptoms as Matt.

 GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
 Org-mode 8.1.1 (the latest ELPA package fails in the same way)

 xdg-open works on the command line but not through the org-export
 menu - pdfs and html files don't open automatically.  There are no
 error messages.
>>>  I see the same problem.  But I think this might be an Emacs issue;
>>> I can't open a pdf from dired either (with & on a pdf file).
>>> However I can open it if I execute a shell command: M-! xdg-open
>>> file.pdf RET.
>>
>> Do I need to conclude that, for the time being, xdg-open has to be
>> removed from the default value of org-file-apps?
>
> That did the trick - pdf files now open as before, as do html exports.


Glyn, can you just tell me what you set org-file-apps to? I wasn't
able to find a value that worked.  Thank you!

Matt

Re: [O] create a sparse tree by TODO and property? possible?

[Suvayu Ali]

On Tue, Sep 17, 2013 at 09:15:14PM +0200, Carsten Dominik wrote:
> 
> On 17.9.2013, at 13:48, Xebar Saram  wrote:
> 
> > Hi all
> > 
> > can one create a sparse tree using 2 queries, In particular i want to 
> > create a sparse tree that has all heading marked TODO and that have a 
> > specific property i set IE:
> > :PROPERTIES:
> > :food_type: indian
> > :END:
> > 
> > so i would like sparse tree for example to show 'indian' property but also 
> > TODO state
> 
> Yes, this is possible.
> 
> C-c / m food_type="indian"/TODO  RET
> 
> 
> The match syntax is described here:
> 
> http://orgmode.org/manual/Matching-tags-and-properties.html#Matching-tags-and-properties

I didn't know this!  Althought now that I think, if the agenda can do
it, sparse tree should be too :-p.

Thanks :).

-- 
Suvayu

Open source is the future. It sets us free.

[O] [Babel] Buffer-wide properties ignored ...

[aditya siram]

Hi all,

It appears as though buffer wide properties are ignored when tangling
source blocks. This is easily reproducible by add a `#+PROPERTY: :padlines
no` to the top of the file and tangling something. The source has padlines.
I tried variations on including `#+PROPERTY: padlines no` and `#+PROPERTY:
header-args: padlines-no` with the same result.

-deech

[O] [Babel] Padlines

[aditya siram]

Hi all,
What's the rationale for having padlines by default in tangled source? It
generates wrong programs for languages where whitespace is significant
(Haskell) and, for me, doesn't noticeably improve the look of the tangled
file in cases where it isn't.
Thanks!
-deech

Re: [O] Change org-back-to-heading to use org's heading regex

[aditya siram]

Yes, you're right. And while I was looking for an alternate solution I
found `org-heading-components` which does everything I need and more!
Thanks!
-deech


On Sat, Sep 14, 2013 at 5:21 PM, Carsten Dominik
wrote:

> Hi Aditya,
>
> I do not support this idea.
>
> 1. sometimes Org functions are used in other modes, with a different value
> for the outline regexp.  WHile this will not work for many Org functions,
> it is useful to have it work for some.
>
> 2. For just searching headings, it is efficient to use a regexp that is as
> simple as possible and does not need to do any back tracking.
>
> 3. You can easily use the simple regexps to find a heading.  If you need
> detailed info, match again with looking-at and then use the match data.
>
> Regards
>
> - Carsten
>
> On 14.9.2013, at 23:30, aditya siram  wrote:
>
> > Hi all,
> > Org-mode uses two regex's to find headings, one from outline.el and one
> defined internally and captures more information. I propose we stop using
> the one from outline.el.
> >
> > org-mode uses `org-back-to-heading` a lot to navigate point back to the
> nearest heading.
> >
> > This just delegates to `outline-back-to-heading` from the outline.el
> package, which uses a regex for finding headlines: "[*\^L]+"
> >
> > Org also defines another heading regex which is more capable and
> captures more information: "^\\(\\*+\\)\\(?: +\\(.*?\\)\\)?[ \t]*$".
> >
> > I would propose changing org-back-to-heading to use that so that a user
> (like me :) ) can use `match-string` to grab the relevant parts of the
> string.
> >
> > Since this is a pretty simple, but sweeping change, I thought I'd bring
> it up here first before patching.
> >
> > Thanks!
> > -deech
> >
> >
> >
>
>

Re: [O] [Babel] Getting Info On Empty Source Block Fails

[aditya siram]

I believe this may have been an instance of the regex being too greedy
which is fixed by the patch I submitted.
-deech


On Fri, Sep 13, 2013 at 12:05 PM, Eric Schulte wrote:

> aditya siram  writes:
>
> > Hi all,
> > `org-babel-get-src-block-info` on an empty block fails.
> >
> > Given:
> > #+BEGIN_SRC c
> > #+END_SRC
> > #+BEGIN_SRC c
> > non-empty
> > #+END_SRC
> >
> > Running `org-babel-get-src-block-info` with point at the beginning of the
> > first line gives:
> > ("c" "#+END_SRC
> >
> > #+BEGIN_SRC c
> > non-empty" ((:colname-names) (:rowname-names) (:result-params "replace")
> > (:result-type . value) (:comments . "") (:shebang . "") (:cache . "no")
> > (:padline . "") (:noweb . "no") (:tangle . "no") (:exports . "code")
> > (:results . "replace") ...) "" nil 0 8)
> >
> > The problem is somewhere in `org-babel-src-block-regex` but I didn't want
> > to mess with it because it touches all parts of org-babel and I'm not
> sure
> > what else would break.
> >
> > Any advice on how to fix this is appreciated.
> > -deech
>
> This works for me.  With the point on the first "#" in
>
> > #+BEGIN_SRC c
> > #+END_SRC
>
>
> I get
>
> ,[C-c C-v I]
> | Lang: c
> | Header Arguments:
> |   :cache  no
> |   :exportscode
> |   :hlines no
> |   :noweb  yes
> |   :padnewline yes
> |   :resultsreplace
> |   :sessionnone
> |   :tangle no
> |
> | [back]
> `
>
> and
>
> ,[M-: (org-babel-get-src-block-info)]
> | ("c" "" ((:colname-names) (:rowname-names) (:result-params "replace")
> |  (:result-type . value) (:comments . "") (:shebang . "")
> |  (:cache . "no") (:padline . "") (:noweb . "yes") (:tangle .
> "no")
> |  (:exports . "code") (:results . "replace") ...) "" nil 0 882)
> `
>
> Cheers,
>
> --
> Eric Schulte
> https://cs.unm.edu/~eschulte
> PGP: 0x614CA05D
>

[O] M-x fill-region equivalent for lists?

[John Hendy]

Greetings,


When editing lists after deleting words (shortening lines) and/or
concatenating one line with the one that follows (to remedy a
shortened line), I end up with an "unfilled" list item. Is there an
Org equivalent to `M-x fill-region` on paragraphs to tidy up the Org
document list entries?

In other words, I'd like to cause the item to look equivalent to
typing it all at once and having the text flowed onto the next line
when I hit my setting for the fill width:

(setq-default fill-column 90)

Example:

- here's some
  text that should all be one bullet and not be on separate lines. I
deleted the stuff on the
  line above and now want all three of these lines to reflow nicely in
the same bullet. Is this
  possible?

If I put that all one one line, go to the end and press SPACE, I get
this (probably won't reflow right with the limits of email widths...):

- here's some text that should all be one bullet and not be on
separate lines. I deleted
  the stuff on the line above and now want all three of these lines to
reflow nicely in
  the same bullet. Is this possible?



Thanks,
John

Re: [O] Spaces in HTML export

[Nick Dokos]

"Simon W. Jones"  writes:

> Hello,
>
> A few days ago I raised a problem with HTML export I was having and
> was advised to upgrade to Orgmode 8.1. I have now done so but the
> problem persists. The problem significantly effects my workflow and I
> would be very grateful for a solution.
>
> If I add a link in my document to an external website that has spaces
> in the URL, for example www.example.com/useful%20document.pdf, then
> export as HTML, the URL appears in the HTML output as
> www.example.com/useful%2520document.pdf. The link obviously then
> returns an error when one clicks on it.
>
> Is there any way round this issue, can anyone else replicate the problem?
>

How do you add the link to your org document? If you cut-and-paste into
the document, there should be no double encoding. If OTOH you use C-C
C-l, that *always* url-encodes, so you end up encoding the % sign and
%20 becomes %2520 since there is no way for org to know whether
something is urlencoded already. There was a discussion about this not
too long ago that came to this conclusion IIRC[fn:1].

You can get around the problem by constructing such links manually -
paste the url-encoded URL as it comes from your browser directly into
your org file buffer:

http://hl.udogs.net/files/Gaming/%20Myth%20Series/Myth%20II%20-%20Soulblighter/

and then put the link decorations around it by hand - after all, org is
just plain text:

[[http://hl.udogs.net/files/Gaming/%20Myth%20Series/Myth%20II%20-%20Soulblighter/][my
 link]]

Exporting that to HTML works fine I believe.

Footnotes:

[fn:1] http://thread.gmane.org/gmane.emacs.orgmode/74983
   but I haven't gone back to reread it all.

-- 
Nick

[O] Assistance customizing org-format-latex-options

[John Hendy]

Hi,


I'm running into a similar issue as I once did before:
- http://comments.gmane.org/gmane.emacs.orgmode/50452

When I'm writing a paragraph and have a dollar currency amount, Org's
footnote functionality (e.g. =C-x f=) does not work in the region.

The suggestion was to remove "$" from org-format-latex-options.

I've not customized a variable with many "sub-options." Can someone
give me an example of how to directly customize just the :matchers
portion of that variable in .emacs? I prefer to set options directly
vs. having a jumbled list of customizations in custom-set-variables.

I searched around and found this:
- 
http://stackoverflow.com/questions/11272236/how-to-make-formule-bigger-in-org-mode-of-emacs

It gives instructions on setting the :scale portion, which I tried to
adapt to :matchers like this:

(setq org-format-latex-options (plist-put org-format-latex-options
:matchers ("begin" "$1" "$$" "\\(" "\\[")))

As well as this:

(setq org-format-latex-options (plist-put org-format-latex-options
:matchers "("begin" "$1" "$$" "\\(" "\\[")"))

Both of those aren't parsing correctly. Sorry for my elisp munging ignorance!


Thanks!
John

Re: [O] Assistance customizing org-format-latex-options

[Carsten Dominik]

Hi John,

don't be afraid of property lists - they are just ordinary
lists with alternating keys and values.

(setq org-format-latex-options
  '(:foreground default
:background default
:scale 1.0
:html-foreground "Black"
:html-background "Transparent"
:html-scale 1.0 
:matchers ("begin" "$1" "$$" "\\(" "\\[")))

HTH

- Carsten

On 18.9.2013, at 05:52, John Hendy  wrote:

> Hi,
> 
> 
> I'm running into a similar issue as I once did before:
> - http://comments.gmane.org/gmane.emacs.orgmode/50452
> 
> When I'm writing a paragraph and have a dollar currency amount, Org's
> footnote functionality (e.g. =C-x f=) does not work in the region.
> 
> The suggestion was to remove "$" from org-format-latex-options.
> 
> I've not customized a variable with many "sub-options." Can someone
> give me an example of how to directly customize just the :matchers
> portion of that variable in .emacs? I prefer to set options directly
> vs. having a jumbled list of customizations in custom-set-variables.
> 
> I searched around and found this:
> - 
> http://stackoverflow.com/questions/11272236/how-to-make-formule-bigger-in-org-mode-of-emacs
> 
> It gives instructions on setting the :scale portion, which I tried to
> adapt to :matchers like this:
> 
> (setq org-format-latex-options (plist-put org-format-latex-options
> :matchers ("begin" "$1" "$$" "\\(" "\\[")))
> 
> As well as this:
> 
> (setq org-format-latex-options (plist-put org-format-latex-options
> :matchers "("begin" "$1" "$$" "\\(" "\\[")"))
> 
> Both of those aren't parsing correctly. Sorry for my elisp munging ignorance!
> 
> 
> Thanks!
> John
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] Assistance customizing org-format-latex-options

[John Hendy]

On Tue, Sep 17, 2013 at 11:09 PM, Carsten Dominik
 wrote:
> Hi John,
>
> don't be afraid of property lists - they are just ordinary
> lists with alternating keys and values.
>
> (setq org-format-latex-options
>   '(:foreground default
> :background default
> :scale 1.0
> :html-foreground "Black"
> :html-background "Transparent"
> :html-scale 1.0
> :matchers ("begin" "$1" "$$" "\\(" "\\[")))
>

After sending the email, I remembered my typical hack of doing this
and set the value using `M-x customize-variable`, then examining what
it saved to .emacs. The above is, indeed, what it was. How might one
set it via the single property method in the StackOverflow post? I can
certainly do the above, though I only want to customize :matchers, so
perhaps it's a bit unnecessary?

I can't imagine the above biting me, but I could see that someone
might want to just target one property in the event that, say, they
want to override one of the above at buffer level and that somehow
conflicts with the whole set of properties existing in .emacs (just
brainstorming...)?


Thanks,
John


> HTH
>
> - Carsten
>
> On 18.9.2013, at 05:52, John Hendy  wrote:
>
>> Hi,
>>
>>
>> I'm running into a similar issue as I once did before:
>> - http://comments.gmane.org/gmane.emacs.orgmode/50452
>>
>> When I'm writing a paragraph and have a dollar currency amount, Org's
>> footnote functionality (e.g. =C-x f=) does not work in the region.
>>
>> The suggestion was to remove "$" from org-format-latex-options.
>>
>> I've not customized a variable with many "sub-options." Can someone
>> give me an example of how to directly customize just the :matchers
>> portion of that variable in .emacs? I prefer to set options directly
>> vs. having a jumbled list of customizations in custom-set-variables.
>>
>> I searched around and found this:
>> - 
>> http://stackoverflow.com/questions/11272236/how-to-make-formule-bigger-in-org-mode-of-emacs
>>
>> It gives instructions on setting the :scale portion, which I tried to
>> adapt to :matchers like this:
>>
>> (setq org-format-latex-options (plist-put org-format-latex-options
>> :matchers ("begin" "$1" "$$" "\\(" "\\[")))
>>
>> As well as this:
>>
>> (setq org-format-latex-options (plist-put org-format-latex-options
>> :matchers "("begin" "$1" "$$" "\\(" "\\[")"))
>>
>> Both of those aren't parsing correctly. Sorry for my elisp munging ignorance!
>>
>>
>> Thanks!
>> John
>>
>

Re: [O] Assistance customizing org-format-latex-options

[Carsten Dominik]

On 18.9.2013, at 05:52, John Hendy  wrote:

> Hi,
> 
> 
> I'm running into a similar issue as I once did before:
> - http://comments.gmane.org/gmane.emacs.orgmode/50452
> 
> When I'm writing a paragraph and have a dollar currency amount, Org's
> footnote functionality (e.g. =C-x f=) does not work in the region.
> 
> The suggestion was to remove "$" from org-format-latex-options.
> 
> I've not customized a variable with many "sub-options." Can someone
> give me an example of how to directly customize just the :matchers
> portion of that variable in .emacs? I prefer to set options directly
> vs. having a jumbled list of customizations in custom-set-variables.
> 
> I searched around and found this:
> - 
> http://stackoverflow.com/questions/11272236/how-to-make-formule-bigger-in-org-mode-of-emacs
> 
> It gives instructions on setting the :scale portion, which I tried to
> adapt to :matchers like this:
> 
> (setq org-format-latex-options (plist-put org-format-latex-options
> :matchers ("begin" "$1" "$$" "\\(" "\\[")))
> 
> As well as this:
> 
> (setq org-format-latex-options (plist-put org-format-latex-options
> :matchers "("begin" "$1" "$$" "\\(" "\\[")"))

Or, if you want to do it like this:

(setq org-format-latex-options
  (plist-put org-format-latex-options
   :matchers '("begin" "$1" "$$" "\\(" "\\[")))

Quoting a list is done with a single ' before the opening parenthesis.
Not by enclosing it in "...".

HTH

- Carsten


> 
> Both of those aren't parsing correctly. Sorry for my elisp munging ignorance!
> 
> 
> Thanks!
> John
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] create a sparse tree by TODO and property? possible?

[Carsten Dominik]

On 17.9.2013, at 23:33, Suvayu Ali  wrote:

> On Tue, Sep 17, 2013 at 09:15:14PM +0200, Carsten Dominik wrote:
>> 
>> On 17.9.2013, at 13:48, Xebar Saram  wrote:
>> 
>>> Hi all
>>> 
>>> can one create a sparse tree using 2 queries, In particular i want to 
>>> create a sparse tree that has all heading marked TODO and that have a 
>>> specific property i set IE:
>>> :PROPERTIES:
>>> :food_type: indian
>>> :END:
>>> 
>>> so i would like sparse tree for example to show 'indian' property but also 
>>> TODO state
>> 
>> Yes, this is possible.
>> 
>> C-c / m food_type="indian"/TODO  RET
>> 
>> 
>> The match syntax is described here:
>> 
>> http://orgmode.org/manual/Matching-tags-and-properties.html#Matching-tags-and-properties
> 
> I didn't know this!  Althought now that I think, if the agenda can do
> it, sparse tree should be too :-p.

Indeed, it is the same internal function that does the matching in both cases.

- Carsten

> 
> Thanks :).
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] #+TAGS has some groups with many entries, suppress hotkey assignment

[Carsten Dominik]

On 17.9.2013, at 17:56, Jeff Kowalczyk  wrote:

> Carsten Dominik writes:
>> Please take a look at the variable org-use-fast-tag-selection
>> and see if there is a setting that you find useful.
> 
> Thanks Carsten, 'auto is the behaviour I am seeking.
> 
> Is org-use-fast-tag-selection 'auto working as intended? It seems to
> be acting like value t as described in the function doc string.

Well, yes.  If you specify only a single selection character, Org thinks that 
you want selection characters and assigns random ones to the others as well.

I do now understand what you mean.

No, this is currently not possible.  I might take a look at this after the 8.2 
release.

- Carsten

> 
> My Emacs 24 with org-mode git master has the default value:
> 
> : org-use-fast-tag-selection
> : auto
> 
> I can reproduce a minimal test file:
> 
> 
> #+TAGS: { admin(a) reporting(r) util(u) foo }
> #+TAGS: { projecta projectb projectc(c) }
> #+TAGS: { billable(b) nonbillable(e) unknown(k) }
> 
> * headline
> 
> 
> Where C-c C-c on headline gives the selector:
> 
> 
> Inherited:
> Current:
> 
> { [a] admin [r] reporting [u] util  [f] foo}
> { [p] projecta  [d] projectb  [c] projectc  }
> { [b] billable  [e] nonbillable   [k] unknown   }
> 
> 
> I would have anticipated only explicit single key selectors, e.g.:
> 
> 
> Inherited:
> Current:
> 
> { [a] admin [r] reporting [u] util  foo}
> { projecta  projectb  [c] projectc  }
> { [b] billable  [e] nonbillable   [k] unknown   }
> 
> 
> Thanks,
> Jeff
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

[O] Wanted: Caretaker of the ODT backend

[Carsten Dominik]

Hi,

I am looking for someone who knows about the internals of the ODT file format, 
and who would have time to become the responsible person for ox-odt.el.  Since 
we cannot take patches from the original author (Jambunathan) anymore, this 
module is currently orphaned.

There are a few recent patches Jambunathan has made and published here:

 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15384

We cannot take them (due to FSF rules and for other reasons as well) - but the 
new maintainer can take a look at them and see if there is functionality or bug 
fixes we need and re-implment those.  For the rest I would hope that you can 
watch the mailing list and Emacs bug reports for issues related to this backend 
and try to fix them, obviously with support from the mailing list.  Also,maybe 
there are ideas for additional functionality?

Please write to me if you are interested.

Thank you.

- Carsten


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] Assistance customizing org-format-latex-options

[John Hendy]

On Tue, Sep 17, 2013 at 11:15 PM, Carsten Dominik
 wrote:
>
> On 18.9.2013, at 05:52, John Hendy  wrote:
>
>> Hi,
>>
>>
>> I'm running into a similar issue as I once did before:
>> - http://comments.gmane.org/gmane.emacs.orgmode/50452
>>
>> When I'm writing a paragraph and have a dollar currency amount, Org's
>> footnote functionality (e.g. =C-x f=) does not work in the region.
>>
>> The suggestion was to remove "$" from org-format-latex-options.
>>
>> I've not customized a variable with many "sub-options." Can someone
>> give me an example of how to directly customize just the :matchers
>> portion of that variable in .emacs? I prefer to set options directly
>> vs. having a jumbled list of customizations in custom-set-variables.
>>
>> I searched around and found this:
>> - 
>> http://stackoverflow.com/questions/11272236/how-to-make-formule-bigger-in-org-mode-of-emacs
>>
>> It gives instructions on setting the :scale portion, which I tried to
>> adapt to :matchers like this:
>>
>> (setq org-format-latex-options (plist-put org-format-latex-options
>> :matchers ("begin" "$1" "$$" "\\(" "\\[")))
>>
>> As well as this:
>>
>> (setq org-format-latex-options (plist-put org-format-latex-options
>> :matchers "("begin" "$1" "$$" "\\(" "\\[")"))
>
> Or, if you want to do it like this:
>
> (setq org-format-latex-options
>   (plist-put org-format-latex-options
>:matchers '("begin" "$1" "$$" "\\(" "\\[")))
>
> Quoting a list is done with a single ' before the opening parenthesis.
> Not by enclosing it in "...".
>

Fantastic and exactly what I was looking for! I realize I'm pretty
horrible at following through on my Worg aspirations... but perhaps I
can file this and some other things like this to help others with
customization of variables. Some of these syntax things seem to appear
with reasonable frequency and cause us non-elispers definite
confusion. I could see a page on setting .emacs options as helpful.
Come to think of it, I probably should have googled for more general
Emacs customization information.

Anyway, many thanks for the quick response and assistance!


John

> HTH
>
> - Carsten
>
>
>>
>> Both of those aren't parsing correctly. Sorry for my elisp munging ignorance!
>>
>>
>> Thanks!
>> John
>>
>

Re: [O] create a sparse tree by TODO and property? possible?

[Xebar Saram]

Thank you so much Carsten and Suvayu  (and let me take the opportunity to
thank you Carsten for orgmode in general which just makes my
academic/personal life so much more enjoyable :))

this works like a charm!

z.


On Wed, Sep 18, 2013 at 7:20 AM, Carsten Dominik
wrote:

>
> On 17.9.2013, at 23:33, Suvayu Ali  wrote:
>
> > On Tue, Sep 17, 2013 at 09:15:14PM +0200, Carsten Dominik wrote:
> >>
> >> On 17.9.2013, at 13:48, Xebar Saram  wrote:
> >>
> >>> Hi all
> >>>
> >>> can one create a sparse tree using 2 queries, In particular i want to
> create a sparse tree that has all heading marked TODO and that have a
> specific property i set IE:
> >>> :PROPERTIES:
> >>> :food_type: indian
> >>> :END:
> >>>
> >>> so i would like sparse tree for example to show 'indian' property but
> also TODO state
> >>
> >> Yes, this is possible.
> >>
> >> C-c / m food_type="indian"/TODO  RET
> >>
> >>
> >> The match syntax is described here:
> >>
> >>
> http://orgmode.org/manual/Matching-tags-and-properties.html#Matching-tags-and-properties
> >
> > I didn't know this!  Althought now that I think, if the agenda can do
> > it, sparse tree should be too :-p.
>
> Indeed, it is the same internal function that does the matching in both
> cases.
>
> - Carsten
>
> >
> > Thanks :).
> >
> > --
> > Suvayu
> >
> > Open source is the future. It sets us free.
> >
>
>

[O] Include files and exporter

[Fabrice Popineau]

Hi,

Is there anyway to know while exporting what is the relative path of the
current node?
Let's start with some master org file that includes some other org part
from another directory.
This org part references some image with a path relative to its own
directory.
I wonder if there is a way to keep track of the actual location of the
image file.

I know there is the FILE property, but does it take into account the
directory change induced by #include: ?

When exporting to latex, there is always the ability to use graphicspath,
but when exporting to html, it could be useful to collect all the files and
move them to the publish directory. I'm fiddling with o-blog which does
this, but does not address this include issue.

Thanks for any input / idea about this.

-- 
Fabrice

Re: [O] some movement on zotero!

[Erik Hetzner]

At Tue, 17 Sep 2013 03:59:36 -0400, Matt Price wrote:
> 
> hi,
> 
> Just found this:
> 
> http://zotero-odf-scan.github.io/zotero-odf-scan/
> 
> don't havetime to look thorugh it yet, but it looks like a way to
> write in org-mode and still use a zotero bibliography. It wil mean
> that odt is the only really usable export, though.
> 
> I'd be interested to hear what other people think -- as I say,
> rushing to get some work done right now!

You can also export to markdown, and use the extractcites.py script
included with the zotxt extension [1] to generate a JSON bib file,
then process via pandoc. A little complicated, but it works. Just use
citations in pandoc format.

best, Erik

1. https://bitbucket.org/egh/zotxt
Sent from my free software system .

Re: [O] Connect to the ssh and execute any command

[Michael Albinus]

Andrey Tykhonov  writes:

> Hi Michael!

Hi Andrey,

>> Your remote host does not find a proper "id" command. What happens, if
>> you call the following commands in a shell on that remote host:
>> 
>> # id -u
>
> id: Command not found.
>
>> # whereis id
>
> whereis: Command not found.
>
> I also didn't find 'id' by means of
>
> find / -name id
>
> As I understand TRAMP is not able to work without 'id'. Therefore TRAMP is
> not suitable for me...
>
>> # uname -a
>
> FreeBSD {hostname} 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Sep 13
> 21:22:42 PDT 2013 auto-build@{hostname}:{some/path/} amd64

Strange. `id' (and also `whereis') belong to FreeBSD proper. See for
example 

You might check with your remote host why it is not installed.

> Best regards,
> Andrey

Best regards, Michael.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Suvayu Ali]

Hi,

I think I have tracked down the issue.

On Tue, Sep 17, 2013 at 06:10:02PM -0400, Matt Price wrote:
> On Tue, Sep 17, 2013 at 5:25 PM, Suvayu Ali  
> wrote:
> >
> > I would like to know if other desktop environments has the same issue:
> > kde-open (KDE) and gvfs-open (Gnome, Mate, etc).  So to test, just open
> > a directory with pdf/odt/html files in dired and run either of them
> > asynchronously with &.
> 
> I'm running unity in Ubuntu 13.04, which still is sorta descended from
> gnome.  Neither xdg-open nor gnome-open seems to work (if I'm doing
> this right in dired: navigate to a pdf/html file, type &, enter
> xdg-open).
> 
> I have the feeling the problem is in emacs, org-open-file, or their
> interaction.  It's definitely not in xdg-open/gnome-open themselves,
> as they work fine from the command-line with M-! .

Unfortunately this is a problem with most of the desktop specific *-open
commands.  Take a look at this post from emacs-devel (thanks to Glenn
for pointing me to it):

  

Essentially, running xdg-open asynchronously will not work for Desktop
Environments that use gvfs-open (Gnome, Unity, Mate, etc).  From the
looks of it, exo-open (XFCE) also suffers from the same problem.

That said, it would be nice if Glyn could try it on KDE for the sake of
completeness.  As per the emacs-devel post, kde-open should work.

Conclusion: it would have been nice, but we can't use xdg-open.  This
feels somewhat like the texi2dvi issue.  :-/

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] bug#14605: Problem with export an .org file to .pdf does not open pdf file

[Carsten Dominik]

On 18.9.2013, at 08:51, Suvayu Ali  wrote:

> Hi,
> 
> I think I have tracked down the issue.
> 
> On Tue, Sep 17, 2013 at 06:10:02PM -0400, Matt Price wrote:
>> On Tue, Sep 17, 2013 at 5:25 PM, Suvayu Ali  
>> wrote:
>>> 
>>> I would like to know if other desktop environments has the same issue:
>>> kde-open (KDE) and gvfs-open (Gnome, Mate, etc).  So to test, just open
>>> a directory with pdf/odt/html files in dired and run either of them
>>> asynchronously with &.
>> 
>> I'm running unity in Ubuntu 13.04, which still is sorta descended from
>> gnome.  Neither xdg-open nor gnome-open seems to work (if I'm doing
>> this right in dired: navigate to a pdf/html file, type &, enter
>> xdg-open).
>> 
>> I have the feeling the problem is in emacs, org-open-file, or their
>> interaction.  It's definitely not in xdg-open/gnome-open themselves,
>> as they work fine from the command-line with M-! .
> 
> Unfortunately this is a problem with most of the desktop specific *-open
> commands.  Take a look at this post from emacs-devel (thanks to Glenn
> for pointing me to it):
> 
>  
> 
> Essentially, running xdg-open asynchronously will not work for Desktop
> Environments that use gvfs-open (Gnome, Unity, Mate, etc).  From the
> looks of it, exo-open (XFCE) also suffers from the same problem.
> 
> That said, it would be nice if Glyn could try it on KDE for the sake of
> completeness.  As per the emacs-devel post, kde-open should work.
> 
> Conclusion: it would have been nice, but we can't use xdg-open.  This
> feels somewhat like the texi2dvi issue.  :-/

Hi Suvayu,

thank you for spending the time to check this out.  This is too bad,
a general open command like we use it on Mac and Windows would have
been very nice.

- Carsten

> 
> Cheers,
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.



signature.asc
Description: Message signed with OpenPGP using GPGMail