Re: [O] [DEV] Bump Emacs requirement to 24.4?

Hi, Two reasons to at least jump to 24.4: - nadvice.el: we can clean up all the advising in the code and advocate add-function. This is already employed in upstream Emacs. - prettify-symbols-mode: Perhaps some entity display code can be dropped in favor of

Re: [O] failed tests

On 2015-09-10 21:40, Nicolas Goaziou writes: > Alan Schmitt writes: > >> Should I try to run it interactively? If so, are there instructions on >> how to do it? > > The test is self contained, i.e., no `org-test-at-id' insanity. You can >

Re: [O] Displaying SVG inline in org-mode

Hi Rasmus. >> [...] OTOH I have some svg icons that are shown perfectly in their >> own buffers, but when included inline -just like the pngs- are shown >> only as a reference like "/home/edumerco/whatever.svg" instead of the >> icon. iimage mode is on. > It works for me. > This is my test file

Re: [O] Org-lint error

Hello, Thomas S. Dye writes: >> In the process of tracking down misbehavior during export, I ran >> org-lint, which failed with this error: >> >> Debugger entered--Lisp error: (wrong-number-of-arguments max 0) >> max() >> apply(max nil) >> >> I suspect I have some error in

[O] Agenda Tag filtering - has the behaviour changed?

Hi, I am a long-time user of org-mode and am currently using the maintenance release 8.3.1 I noticed that in the agenda the '//' key to filter by tag now adds tags when used multiple times. This breaks my normal workflow for quickly filtering by a specific tag. In the past I would do: / P to

Re: [O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

Denis Bitouzé writes: > Well, please, don't trust me too quickly :) I must admit I'm very far > from a mardown expert: I'm only a very occasional user. I never use markdown myself. Between the two of us, you are de facto the expert. > In

[O] Bug: babel python indentations fail in sessions [8.3.1]

Dear All, The following code block fails: #+BEGIN_SRC python :results output :session for i in (1, 2): pass print "hey" #+END_SRC #+RESULTS: : : ... ... File "", line 3 : print "hey" : ^ : SyntaxError: invalid syntax but this works:

Re: [O] inter-word space in org -> latex

On Mon, Sep 14, 2015 at 12:54 PM, Suvayu Ali wrote: > You can use entities. Maybe something like this: > > (setq org-entities-user ; can also use "\ " > '(("space" "~" nil "" " " " " " "))) > > Then the following: > > Mr.\space{}Henry Higgins. > That's

Re: [O] obtain ob-template.el for Babel language extension

On Mon, 14 Sep 2015 16:37:04 -1000 Thomas S. Dye wrote: > Aloha all, > > I took the liberty of forwarding Marco's queries to Eric Schulte, the > author of ob-template.el. Eric no longer maintains Babel or reads the > mailing list, but he replied to the queries as follows: > >

Re: [O] remote plot with local output?

Hi Suvayu, Suvayu Ali writes: > Maybe, you could do all that in your python source block? You could use > the :file header to specify where the plot gets copied to on the local > filesystem. > > WDYT? I did think of putting the logic into python source block. As

[O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list.

Re: [O] inter-word space in org -> latex

On Mon, Sep 14, 2015 at 12:50 PM, Rasmus wrote: > > How should I mark in org mode that I want a space following a period > > concluding an abbreviation to be seen by LaTeX as an interword space? > > .@@latex:\ @@ Pretty neat. Thanks.

Re: [O] Bug: babel python indentations fail in sessions [8.3.1]

Hello, Benda Xu writes: > Dear All, > > The following code block fails: > >#+BEGIN_SRC python :results output :session > for i in (1, 2): > pass > print "hey" >#+END_SRC > > >#+RESULTS: >: >: ... ... File "", line 3 >: print

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Thanks for getting back to me. Unfortunately this is not the issue I am reporting. The problem is that the #+NAME that produces the label is incorrectly exported to the LaTeX document. That is it is the weird \label{fig:orgparagraph1} which is not what I am trying to label the figure as. You are

Re: [O] Org-lint error

Nicolas Goaziou writes: > Hello, > > Thomas S. Dye writes: > >>> In the process of tracking down misbehavior during export, I ran >>> org-lint, which failed with this error: >>> >>> Debugger entered--Lisp error: (wrong-number-of-arguments max 0) >>>

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Hello, Andrew Davis writes: > #+CAPTION: Plot of something interesting. > #+ATTR_LaTeX: :width \textwidth > #+NAME: fig:result_plot > file:./img/plot.pdf > > This method of placing plots into an org document no longer > works. Previously, this would correctly produce the

Re: [O] Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]

Le 16/09/15 à 14h51, Nicolas Goaziou a écrit : > Denis Bitouzé writes: > >> Well, please, don't trust me too quickly :) I must admit I'm very far >> from a mardown expert: I'm only a very occasional user. > > I never

[O] Beamer export: no alert command

Eric S. Frage explained that an @alert@ could be used in order to highlight specific parts of the text (http://orgmode.org/worg/exporters/beamer/tutorial.html ). However, exporting it to a PDF doesn’t convert the @alert@ to a highlight.

[O] Another babel scheme issue

The patch to ob-scheme.el that Nick Dokos provided is working well. But another ob-scheme/geiser problem has come up. The code below #+name: letter #+header: #+begin_src scheme :exports both :session ch1 (require 2htdp/batch-io) (define (letter fst lst signature-name) (string-append (opening

Re: [O] Another babel scheme issue

Lawrence Bottorff writes: > ... > However C- C-c-ing > > #+BEGIN_SRC scheme :session ch1 > (write-file 'stdout (letter "Matthew" "Fisler" "Felleisen")) > #+END_SRC > > produces  > > #+RESULTS: > : stdout > I presume write-file returns stdout as its value (?). Does

Re: [O] Another babel scheme issue

Lawrence Bottorff writes: > Sort of. It doesn't give me a geiser dbg buffer, rather > > #+RESULTS: > : "Dear Matthew,\n\nWe have discovered that all people with the last name > \nFisler have won our lottery. > So, Matthew, \nhurry and pick up your

[O] DONE repeating events become TODO, not OTHER

I have repeating events of type OTHER, as in: * OTHER Foo <2015-09-16 +1w> When I have finished the task for today, I mark it done. Because it is a repeating event, it doesn't actually change to DONE, instead it changes to TODO and adds a :LAST_REPEAT: item in the :PROPERTIES: drawer. How

Re: [O] Beamer export: no alert command

Tobias Frischholz writes: > Eric S. Frage explained that an @alert@ could be used in order to > highlight specific parts of the text > (http://orgmode.org/worg/exporters/beamer/tutorial.html > ). > > However, exporting it

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Nicolas, Thanks for following up on this with me. I now understand that this is intentional. Could you just briefly let me know why this is a feature? I am assuming that this is so that org references are unique should you accidentally reuse a label? Best, Andrew On Wed, Sep 16, 2015 at 11:26

[O] [patch] Add footnote when exporting links in LaTeX

Hi! When exporting to LaTeX, links are exported using \href. These are completely invisible if the document is printed out. I consider this a problem. I think a good solution is to add a footnote with the link, in addition to the \href. I've added a patch with this (tiny) change. - Lars >From

Re: [O] DONE repeating events become TODO, not OTHER

On 2015-09-16 at 17:37, Nick Dokos wrote: > Ken Mankoff writes: > >> I have repeating events of type OTHER, as in: >> >> * OTHER Foo >> <2015-09-16 +1w> >> >> When I have finished the task for today, I mark it done. Because it is >> a repeating event, it

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Andrew Davis writes: > You are getting the same results I am. What is concerning me is the fact > that the label you are applying in the document: > > #+NAME: fig:result_plot > > is not the label that is being applied to the the exported tex document, > i.e. > >

Re: [O] Another babel scheme issue

Sort of. It doesn't give me a geiser dbg buffer, rather #+RESULTS: : "Dear Matthew,\n\nWe have discovered that all people with the last name \nFisler have won our lottery. So, Matthew, \nhurry and pick up your prize.\n\nSincerely,\n\nFelleisen\n" Tthat is, it puts it in my org buffer, but it

Re: [O] DONE repeating events become TODO, not OTHER

Ken Mankoff writes: > I have repeating events of type OTHER, as in: > > * OTHER Foo > <2015-09-16 +1w> > > When I have finished the task for today, I mark it done. Because it is > a repeating event, it doesn't actually change to DONE, instead it > changes to TODO and adds a

Re: [O] [patch] Add footnote when exporting links in LaTeX

Hej Lars, Thanks for your patch. Lars Tveito writes: > When exporting to LaTeX, links are exported using \href. These are > completely invisible if the document is printed out. I consider this a > problem. It's easy enough to fix in latex. Here's a not quite trivial

Re: [O] Another babel scheme issue

I appreciate your efforts, ND. No silver bullet is just lying around, so I think I can live with this for the time being. Must learn elisp I. LB On Wed, Sep 16, 2015 at 9:56 PM, Nick Dokos wrote: > Lawrence Bottorff writes: > > > Sort of. It doesn't give

Re: [O] DONE repeating events become TODO, not OTHER

Ken Mankoff writes: > On 2015-09-16 at 17:37, Nick Dokos wrote: >> Ken Mankoff writes: >> >>> I have repeating events of type OTHER, as in: >>> >>> * OTHER Foo >>> <2015-09-16 +1w> >>> >>> When I have finished the task for today, I mark

[O] Babel python regression org-mode-8 (Was: Bug: babel python indentations fail in sessions [8.3.1])

Hi Kyle, Kyle Meyer writes: > Benda Xu writes: >> >> The following code block fails: >> >>#+BEGIN_SRC python :results output :session >> for i in (1, 2): >> pass >> print "hey" >>#+END_SRC >> >> >>#+RESULTS: >>: >>:

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Hi Andrew, Andrew Davis writes: > Thanks for following up on this with me. I now understand that this is > intentional. Could you just briefly let me know why this is a feature? > I am assuming that this is so that org references are unique should > you accidentally reuse

[O] feature request: simulate agenda view as if another day

Hello, For some reason, thought crossed my mind to use this in trying out agenda views. And I thought for some reason this functionality existed, though I was probably thinking of something else I had seen about a year ago. But so, ideas are ideas, so I offer it here. So the feature I am

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

Andrew Davis writes: > Thanks for getting back to me. Unfortunately this is not the issue I am > reporting. The problem is that the #+NAME that produces the label is > incorrectly exported to the LaTeX document. That is it is the weird > \label{fig:orgparagraph1} which is

[O] Using the file as 1st level headline

Hi all Is it possible to have a file header which is counted as a first level headline? If that sounds weird, this is what I like to do: I'm using Bernt Hansen's setup of orgmode for GTD (http://doc.norang.ca/org-mode.html). In this setup a project is defined as each headline which has a TODO

Re: [O] Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]

You are getting the same results I am. What is concerning me is the fact that the label you are applying in the document: #+NAME: fig:result_plot is not the label that is being applied to the the exported tex document, i.e. \label{fig:orgparagraph1} \ref{fig:orgparagraph1} This is rather