On 19.9.2013, at 11:38, Nicolas Girard wrote:
> 2013/9/19 Carsten Dominik :
>>
>> On 19.9.2013, at 00:21, Rasmus wrote:
>>
>>> So what would the goal be? To make it compatible with XeLaTeX and
>>> LuaLaTeX out of the box?
>>
>> Yes, this is what I mean. I would be happy to have some clever
On 25.9.2013, at 08:53, Rainer M Krug wrote:
> "Sebastien Vauban"
> writes:
>
>> Hi Carsten,
>>
>> Carsten Dominik wrote:
>>> On 24.9.2013, at 18:17, Sebastien Vauban wrote:
Carsten Dominik wrote:
> On 23.9.2013, at 09:40, Rainer M Krug wrote:
>>
>> When starting to edit a
On 25.9.2013, at 08:48, Rainer M Krug wrote:
> Carsten Dominik writes:
>
>> Hi Rainer, hi Carsten,
>>
>> it does not get lost - it is in my queue. As are, unfortunately,
>> another 35 threads with possible bugs. Help is definitely wanted.
>
> That's what I was looking for - confirmation th
Hi,
I was going to ask about this.
The website actually does direct people to a collaborative issue tracker
on Worg:
http://orgmode.org/worg/org-issues.html
As outlined there, the idea was that the maintainer would add issues
from the mailing list, but others were welcome to modify the entries
"maybe just put a
,-
| #+OPTIONS toc:nil
`-
before the first headline of your org file?"
No, that did not help. In the html output there is a toc again.
Besides i have a lot export projects like pdf and odt and for that i want a toc.
Only the html output should b
Carsten Dominik writes:
> On 25.9.2013, at 08:48, Rainer M Krug wrote:
>
>> Carsten Dominik writes:
>>
>>> Hi Rainer, hi Carsten,
>>>
>>> it does not get lost - it is in my queue. As are, unfortunately,
>>> another 35 threads with possible bugs. Help is definitely wanted.
>>
>> That's what
On 25.9.2013, at 09:28, Christian Moe wrote:
>
> Hi,
>
> I was going to ask about this.
>
> The website actually does direct people to a collaborative issue tracker
> on Worg:
>
> http://orgmode.org/worg/org-issues.html
Ha, I completely forgot about this one, and it seems
to be entirely out
On 25.9.2013, at 09:25, Daniel Thom wrote:
> "maybe just put a
>
> ,-
> | #+OPTIONS toc:nil
> `-
Colon missing after OPTIONS.
- Carsten
>
> before the first headline of your org file?"
>
> No, that did not help. In the html output there is a toc again.
> Be
Hi François,
François Pinard wrote:
> This is an old annoyance of the Org exporter, yet I'm not sure what
> would be its best resolution.
>
> Whenever I use :export: tags on headers within an Org file, I expect
> only those headers and their contents to be exported (to HTML in my
> case), and almo
Carsten Dominik writes:
> On 25.9.2013, at 08:53, Rainer M Krug wrote:
>
>> "Sebastien Vauban"
>> writes:
>>
>>> Hi Carsten,
>>>
>>> Carsten Dominik wrote:
On 24.9.2013, at 18:17, Sebastien Vauban wrote:
> Carsten Dominik wrote:
>> On 23.9.2013, at 09:40, Rainer M Krug wrote:
>
2013/9/25 Carsten Dominik :
>
> On 19.9.2013, at 11:38, Nicolas Girard wrote:
>
>> I actually have some working code that does this. It lies in a file I
>> named 'minimal.tex', which I include into all my latex code using
>> \input{minimal}\makeatletter
>
> Hi Nicolas,
>
> of I were to include th
Hi Carsten,
Carsten Dominik wrote:
> we do not have an issue tracker for Org. However, if you
> have some time to help, the file with open issues that need
> attention can be found here:
>
> https://dl.dropboxusercontent.com/u/530458/org-tracker.html
>
> Note that I do not enter every issue into
On 25.9.2013, at 09:51, Sebastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>> we do not have an issue tracker for Org. However, if you
>> have some time to help, the file with open issues that need
>> attention can be found here:
>>
>> https://dl.dropboxusercontent.com/u/530458/
On Wed, Sep 25, 2013 at 09:51:20AM +0200, Sebastien Vauban wrote:
>
> The other solution that I'd see would be using Emacs' own bug tracker (the
> `org' package is already known to them), if that's possible. Anyway, having
> the
> bugs in an Org file seems natural too!
I think this is a great id
Excellent, I'll wait for your further input.
Thanks Nicolas!
- Carsten
On 25.9.2013, at 09:45, Nicolas Girard wrote:
> 2013/9/25 Carsten Dominik :
>>
>> On 19.9.2013, at 11:38, Nicolas Girard wrote:
>>
>>> I actually have some working code that does this. It lies in a file I
>>> named 'mini
On 25.9.2013, at 08:43, Carsten Dominik wrote:
> Hi everyone,
>
> we do not have an issue tracker for Org. However, if you
> have some time to help, the file with open issues that need
> attention can be found here:
>
> https://dl.dropboxusercontent.com/u/530458/org-tracker.html
I have moved
Carsten Dominik wrote:
> On 25.9.2013, at 09:51, Sebastien Vauban wrote:
>> Carsten Dominik wrote:
>>> we do not have an issue tracker for Org. However, if you
>>> have some time to help, the file with open issues that need
>>> attention can be found here:
>>>
>>> https://dl.dropboxusercontent.c
Nicolas Girard writes:
> 2013/9/25 Carsten Dominik :
> I came to think that, having a piece of code that brings
> cross-compatibility between the 3 engines would be of interest to
> people outside of the Org community. But this is not trivial,
> especially if the code has to work with older TeX
Hi Suvayu,
Suvayu Ali wrote:
> On Wed, Sep 25, 2013 at 09:51:20AM +0200, Sebastien Vauban wrote:
>>
>> The other solution that I'd see would be using Emacs' own bug tracker (the
>> `org' package is already known to them), if that's possible. Anyway, having
>> the
>> bugs in an Org file seems nat
Hi everyone,
I would like to come back to this issue.
While I can follow the argumentation that drawers are meta data and that it is
really hard for a backend to do something general and correct with them, I am
still wondering if it wouldn't be good to have some default way to export them
anyw
On 25.9.2013, at 11:31, Carsten Dominik wrote:
> Hi everyone,
>
> I would like to come back to this issue.
>
> While I can follow the argumentation that drawers are meta data and that it
> is really hard for a backend to do something general and correct with them, I
> am still wondering if i
Hi Sebastiaan,
I have added your issues.
(P.S. this sounds really funny and reminds me of Marvin from the
"Hitchhikers Guide to the Galaxy" does solve "all of the
major mathematical, physical, chemical, biological, sociological,
philosophical, etymological,meteorological and psychological
problem
"Sebastien Vauban"
writes:
> Hi Suvayu,
Hi,
>>> The other solution that I'd see would be using Emacs' own bug tracker (the
>>> `org' package is already known to them), if that's
>>> possible. Anyway, having the
>>> bugs in an Org file seems natural too!
>>
>> I think this is a great idea. A
OK,
now that I have made a fool out of myself, I think I understand now how
things work, and what I did not understand correctly in the
discussion so far.
1. I misunderstood that drawers could not be exported in
general with the new exporter. This is wrong, drawers are
exported just fine
Alexander Vorobiev writes:
> Hi Michael,
Hi Alex,
> The patch seems to be working, the only thing I noticed is having
> http://www.emacswiki.org/emacs/setup-cygwin.el loaded together with
> the patched ob-core.el makes tramp prepend "/cygwin" to /tmp/. When I
> disabled (require 'setup-cygwin)
Carsten Dominik writes:
> 3. The only exception to this rule are property drawers, which will
>currently not be exported by any of the backends. Nicolas
>proposed to define a derived backend that does export the property
>drawer, or he proposed to use macros to extract specific prope
On 25.9.2013, at 12:53, Thorsten Jolitz wrote:
> Carsten Dominik writes:
>
>> 3. The only exception to this rule are property drawers, which will
>> currently not be exported by any of the backends. Nicolas
>> proposed to define a derived backend that does export the property
>> drawer,
Hello,
Carsten Dominik writes:
> One possible remaining option would be to introduce user variables
> org-BACKEND-format-property-drawer-function in analogy
> org-BACKEND-format-drawer-function. This would provide an easy way
> to configure export of the property drawer as a whole, in a way
> t
On 25.9.2013, at 13:51, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> One possible remaining option would be to introduce user variables
>> org-BACKEND-format-property-drawer-function in analogy
>> org-BACKEND-format-drawer-function. This would provide an easy way
>> to co
Carsten Dominik writes:
> This sounds good to me. How about allowing also a function
> as a value and that function will receive the list of properties
> and do with it as it pleases.
At first I thought about it but I realized that was exactly what
a filter could do. Do we need to introduce red
Nicolas Goaziou writes:
Hello,
> There may be a slightly different option available: we can introduce
> a new defcustom, e.g., `org-export-with-node-properties' (what symbol to
> use for short item in OPTIONS?), which will trigger the following
> behaviour:
>
> - when t, export completely all
The footnote section in my HTML-export doc has the footnote number
separated from the footnote text by a blank line. See
http://www.commondraft.org for the document.
Here's an example of what it looks like:
==BEGIN EXAMPLE==
[TEXT:]
The term "Agreement-Related"[9] refers to something – for ex
On 25.9.2013, at 14:13, Nicolas Goaziou wrote:
> Carsten Dominik writes:
>
>> This sounds good to me. How about allowing also a function
>> as a value and that function will receive the list of properties
>> and do with it as it pleases.
>
> At first I thought about it but I realized that wa
For example:
* John MacColl's March to Kilbowie Cottage
#+begin_src abc :file john_maccol_kilbowie.svg :cmdline -g
T: John MacColl's March To Kilbowie Cottage
R: March
M: 4/4
L: 1/8
K: Amix
A>B|: c4 c>B A>c | e4 f>e cB cc A>B | cc B2 A>B |
c4 c>B A>c | e4 f>e ce f>c e>A BB :
Hi Simon,
Simon Thum writes:
> the attached patch solves the problem of having hexified strings in
> hte vCard export. It happens when you are entering tel: links and
> phone numbers that start with `+`. The plus sign causes the link
> insert helper to hexify the url.
>
> In tel: links the plus
Nick Dokos writes:
> "tuma...@gmail.com" writes:
>
>> How can i convert (1 2 3 5 7 8 9 10 11 12 13) to
>> ((1 2 3 ) (5) (7) (8 9) (10 11 12 13))?
>>
>
> Two problems:
>
> Wrong list: try comp.lang.lisp instead.
> Incomplete problem description: see "How to ask questions
> the smart way" at http:
Hi,
"D. C. Toedt" writes:
> The footnote section in my HTML-export doc has the footnote number
> separated from the footnote text by a blank line. See
> http://www.commondraft.org for the document.
What did you expect instead of this rendering?
Did you try to adapt the CSS to get what you nee
>> - when t, export completely all property drawers as examples;
>>
>> - when nil, do not export property drawers (default value);
>>
>> - when set to a list of strings, export property drawers as examples
>>but only include properties matching these strings;
+1
Christian
I thought the footnotes would come out as follows, which I believe is
the way it did before I upgraded from org version 7.9.3 (I think it
was):
==BEGIN EXAMPLE==
[FOOTNOTES:]
[9] Agreement-Related definition: This defined term is available for use
in, for example, attorneys' fees clauses, limit
Hi Michael,
Michael Albinus wrote:
> "Sebastien Vauban"
>
The other solution that I'd see would be using Emacs' own bug tracker (the
`org' package is already known to them), if that's
possible. Anyway, having the
bugs in an Org file seems natural too!
>>>
>>> I think this is a
Hi!
I wonder how Org-mode turned out as it is with regard to settings
that could be done in .emacs (user), as file-local ones (file), or
with properties (heading).
As an example:
[1] mentions:
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [bigger]
#+BEAMER_FR
>>>
>>> While we are at editing code blocks inline (I also do this quite often).
>>>
>>> This might have been asked before, but in code blocks we have
>>>
>>> - syntax highlighting
>>> - indenting using the code block language settings
>>>
>>> but would it be possible to have, when the cursor i
Eric Schulte writes:
While we are at editing code blocks inline (I also do this quite often).
This might have been asked before, but in code blocks we have
- syntax highlighting
- indenting using the code block language settings
but would it be pos
>> 1. M-: (setq org-agenda-window-frame-fractions '(1.0 . 1.0)) RET
>> 2. M-x org-agenda a
>>
>> Expected results: The *Org Agenda* buffer occupies the entire frame
>> Actual results: The *Org Agenda* buffer occupies the entire frame EXCEPT
>> for a five line window at the top of the frame
>
> Due
Karl Voit writes:
Hi,
> I wonder how Org-mode turned out as it is with regard to settings
> If not: why can't there be a general pattern where a user can assume
> that #+foo (file) can be applied as :FOO: (heading) as well?
and I wonder why
,--
| #+ATTR_HTML: :foo bar
`--
Hi all,
reading Sacha's post on blogging with Emacs* pushed me to write this
small tutorial on how to use ox-rss.el to write/publish a blog with
Emacs and Org:
http://bzg.fr/blogging-from-emacs.html
Enjoy!
*
http://sachachua.com/blog/2013/09/when-i-blog-with-emacs-and-when-i-blog-with-somethin
Hi everyone,
I guess it is appropriate to give a little shout-out to rackspace.com here,
because a few month back they have decided to sponsor the webhosting for
orgmode.org. Jason Dunsmore set us up with a rackspace account a few years ago
(2010 IIRC) and has done a great service to our commu
I started a post a bit ago and thought I had my R/Windows woes resolved:
- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg57170.html
I haven't change anything except for updating my path to the more
recent R version I now have installed (used to have 2.15, now have
3.0.1). I have the followi
"Sebastien Vauban"
writes:
> Hi François,
Hello, Sebastien! :-)
>> [...] if I have text and other contents prior to the first header of
>> a file, those contents are indeed exported, while I would prefer not.
>> [...] I have hundreds of Org files and for them all, have some
>> personal conventi
For the record I was mailed off-list and it was pointed out I had the
row/column order reversed in my formula.
#+TBLFM: $2@2='(length(org-lookup-all "F" '(remote(books,$3@2..$3@>)) nil))
Using @2$2 etc makes it all work.
Org spreadsheets are great!
Bill
--
William Denton
Toronto, Canada
htt
Hi William,
I've added your ABC notation support to Org-mode. Thanks for the
contribution!
If you have time to add ob-ABC documentation to [1] that would be much
appreciated but is not required.
Cheers,
Footnotes:
[1] http://orgmode.org/worg/org-contrib/babel/languages.html
--
Eric Schult
Hi!
There are 2 things working not as promised after calling 'org-indent-mode':
1. Tabs aren't treated correctly.
For example a tab with indentation of 6 spaces counts from the beginning
so it gives 2 spaces from indentation border.
"\tABC" should turn into "XXABC"
while it actually t
On Wed, Sep 25, 2013 at 10:31 AM, Bastien wrote:
> Hi all,
>
> reading Sacha's post on blogging with Emacs* pushed me to write this
> small tutorial on how to use ox-rss.el to write/publish a blog with
> Emacs and Org:
>
> http://bzg.fr/blogging-from-emacs.html
>
> Enjoy!
>
> *
> http://sachachua
On Wed, Sep 25, 2013 at 10:02 AM, John Hendy wrote:
> I started a post a bit ago and thought I had my R/Windows woes resolved:
> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg57170.html
>
> I haven't change anything except for updating my path to the more
> recent R version I now have ins
On 25.9.2013, at 17:29, Scott Randby wrote:
> On Wed, Sep 25, 2013 at 10:31 AM, Bastien wrote:
>> Hi all,
>>
>> reading Sacha's post on blogging with Emacs* pushed me to write this
>> small tutorial on how to use ox-rss.el to write/publish a blog with
>> Emacs and Org:
>>
>> http://bzg.fr/blo
And Eric Abrahamsen writes:
> I've got a table I'm trying to insert into a sqlite
> database. I've been looking at orgtbl-sqlinsert and this
> page[fn:1], but I suspect all that is out of date.
FYI, I have changed employers and thus no longer have up-to-date
paperwork at the FSF for assignment. T
Dear org-mode Users and Developers,
(org-mode v8.1) I use the following function for customizable latex
export processes
#+begin_src emacs-lisp
(defun my-auto-tex-cmd (backend)
"When exporting from .org with latex,
automatically run latex, pdflatex, or xelatex as appropriate,
using latexmk."
Hello,
François Pinard writes:
> The spirit behind :export: is that it marks exactly what is going to be
> exported. This implies, in my understanding, that everything else does
> not get exported. If the lines prior to the first header are exported
> whenever there is an :export: tag somewher
* org-table.el (org-table-recalculate): Generate user error if
an hline relative reference is use on the LHS of a formula.
---
lisp/org-table.el | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lisp/org-table.el b/lisp/org-table.el
index 246cf8d..a3197d3 100644
--- a/lisp/org-table.el
+++ b/li
Michael Albinus writes:
> Alexander Vorobiev writes:
>
>> Hi Michael,
>
> Hi Alex,
>
>> The patch seems to be working, the only thing I noticed is having
>> http://www.emacswiki.org/emacs/setup-cygwin.el loaded together with
>> the patched ob-core.el makes tramp prepend "/cygwin" to /tmp/. When
>
> Maybe I'm missing the point of the :missing header, but I find it
> easier and clearer to include the datafile missing command in the
> gnuplot code block. I don't really see a need for the :missing
> header. Maybe the need stems from wanting to be able to use different
> plotting packages to
> (I'm not so experienced with org-mode, so I would need at least some
> assistance how such a TODO item should look like)
A 'headline' is a 'TODO item' if-and-only-if it contains one of the TODO
Keywords in the appropriate position.
See: http://orgmode.org/worg/dev/org-syntax.html
While you're
Hi Carsten,
Carsten Dominik wrote:
> I have moved the tracker to Worg, discarding the old tracker file that was at
> that location.
>
> http://orgmode.org/worg/org-issues.html
Please note that the "Show Org source" button still shows the old Org file.
Best regards,
Seb
--
Sebastien Vauban
On Wed, Sep 25, 2013 at 06:29:26PM +, Loyall, David wrote:
> > (I'm not so experienced with org-mode, so I would need at least some
> > assistance how such a TODO item should look like)
>
> A 'headline' is a 'TODO item' if-and-only-if it contains one of the TODO
> Keywords in the appropriate
"Loyall, David" writes:
>> (I'm not so experienced with org-mode, so I would need at least some
>> assistance how such a TODO item should look like)
>
> A 'headline' is a 'TODO item' if-and-only-if it contains one of the
> TODO Keywords in the appropriate position.
>
> See: http://orgmode.org/wor
"Sebastien Vauban"
writes:
> If you like text without initial heading in the exported file, but don't mind
> adding an heading in the Org buffer, you could add this:
> * Initial text :ignoreheading:
> and get what you want in the exported file.
As I had to move on t
Eric Schulte writes:
> I'd rather not hard-code the value of "/tmp/". Perhaps you could rework
> the patch so that it introduces a new customizable variable (including a
> documentation string) so that users can set the value for their system.
Will do, tomorrow. I would even prefer a more gener
Nicolas Goaziou writes:
> François Pinard writes:
>> The spirit behind :export: is [...]
> I agree, this is a misfeature. This should be fixed in master. Thank
> you for bringing it out.
Thanks as well. :-)
François
On the ess list (emacs.ess.general) there has been the
announcement [fn:2] of polymode [fn:1] recently, which is going in this
direction.
Since my elisp knowledge is limited to the least, this comment might be
irrelevant here, in which case please ignore it.
Regards,
Andreas
Footnotes:
[fn:1]
> I agree that it is easier and more clear to include "set datafile
> missing..." in the body of a gnuplot code block. I *do* think that the
> :missing header argument has value specifically as a way to replace
> missing values in the original table data.
>
> I've changed the behavior of the :miss
Hello,
In order to make Org much nicer to use, I felt we missed a count of items next
to the lists (or blocks, for multi-block agenda views). Here is a patch to add
this, depending on the new variable `org-agenda-display-count-of-items'
(enabled by default).
The count of items must be updated whe
Michael,
I found that the patch doesn't work for sql code blocks. Here is an example
* this works
#+BEGIN_SRC sh :results output :dir /grid:
ls
#+END_SRC
* this doesn't work
#+BEGIN_SRC sql :engine postgresql :dir /grid: :results output
select 1+2 as three;
#+END_SRC
and here is what appear
Carsten Dominik writes:
> Not really. It would simplify processing to have the list instead
> of a string, but indeed, a filter can accomplish all of it.
Here is a first patch. It doesn't handle export back-ends in contrib.
Regards,
--
Nicolas Goaziou
>From c48974d10e0d57b6332fcfed384a49ee5
Hi Sébastien,
"Sebastien Vauban"
writes:
> Please note that the "Show Org source" button still shows the old
> Org file.
Indeed -- the sources for all Worg files were not properly updated,
I just fixed this. Thanks!
--
Bastien
Hi everyone,
I have an idea for putting links in a pdf that would open python code
blocks in an editor. To do that, I need to modify what happens when an
org-file is published to latex.
Essentially I want it to do exactly what it already does in terms of
running pygments, and making nicely format
Hello Michael,
This is the general structure I'm proposing:
* TODO Subject :emacs_ver:org_ver:org_module:
:PROPERTIES:
:DEBGUGS_ID:
:REPORTER:
:CC_EMAIL:
:END:
I elaborate the ideas below.
On Wed, Sep 25, 2013 at 08:56:50PM +0200, Michael Albinus wro
The problem persists. Can anyone else confirm? Perhaps this should be
added to the bug tracker file. For the record, my local.mk file is:
EMACS = /Applications/Emacs.app/Contents/MacOS/Emacs
prefix = /usr/local/share
On Tue, Sep 24, 2013 at 11:11 AM, Skip Collins wrote:
>
> For the last few days,
I just tried out color-theme with emacs24.
It seems the code on http://orgmode.org/worg/org-color-themes.html is not
quite compatible with elpa packages.
Here is what I used instead.
;---
; To easily cycle between different colour schemes u
Hello all,
I use Bernt Hansen's custom Agenda view. Here is a snippet from that
(tags-todo "-CANCELLED/+WAITING/!"
((org-agenda-overriding-header "Waiting and Postponed
Tasks")
(org-agenda-skip-function 'bh/skip-stuck-project
On 26.9.2013, at 05:50, Noorul Islam K M wrote:
>
> Hello all,
>
> I use Bernt Hansen's custom Agenda view. Here is a snippet from that
>
>(tags-todo "-CANCELLED/+WAITING/!"
There should be no slash before the +WAITING. It is also not present in
Bernt's text.
Does that fix
Carsten Dominik writes:
> On 26.9.2013, at 05:50, Noorul Islam K M wrote:
>
>>
>> Hello all,
>>
>> I use Bernt Hansen's custom Agenda view. Here is a snippet from that
>>
>>(tags-todo "-CANCELLED/+WAITING/!"
>
> There should be no slash before the +WAITING. It is also not pre
Hello all,
I pulled in latest changes from master and the following snippet is
not getting tangled.
#+begin_src emacs-lisp
(message "This is a test")
#+end_src emacs-lisp
Yes, the documentation has plain #+end_src, but somehow the above
snippet was working earlier.
Sending this mail out, just i
Hello,
when trying to export as html an example which contains org-mode headings,
the example is not "quoted" in mono-space as it should be. Example:
*1. Failing example: *
This is a test of publishing an example which contains org mode code in
html:
#+BEGIN_EX
83 matches
Mail list logo
