Re: [O] Deeper sectioning in report class
Sanjib Sikder wrote: > When using report class in org-mode and having the following structure > --- > * Another Part of my report > ** Chapter Heading > *** Heading 1 > Subheading 1 > --- > The subheading () is pdf exporting as paragraph having bullets. The > result is like following for > example > --- > Part IV > Chapter 4 Chapter heading > 4.1 Hading 1 > > * Subheading 1 > > - > I need the subheading to be considered as numbered subsections (4.1.1). like > below > Part IV > Chapter 4 Chapter heading > 4.1 Hading 1 > 4.1.1 Subheading 1 > --- > > How can I achieve this ? #+OPTIONS: H:4 See (info "(org) Export options") Nick
[O] Deeper sectioning in report class
hi, When using report class in org-mode and having the following structure --- * Another Part of my report ** Chapter Heading *** Heading 1 Subheading 1 --- The subheading () is pdf exporting as paragraph having bullets. The result is like following for example --- Part IV Chapter 4 Chapter heading 4.1 Hading 1 - Subheading 1 - I need the subheading to be considered as numbered subsections (4.1.1). like below Part IV Chapter 4 Chapter heading 4.1 Hading 1 4.1.1 Subheading 1 --- How can I achieve this ? - *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* *
Re: [O] [new exporter]: LaTeX output from babel escapes comment delimiter
Thomas S. Dye wrote:
> Aloha Mike,
>
> It looks like your source block and results are indented. IIRC, that's
> not a good thing.
>
> This might work better:
>
> #+name: gauland-eg
> #+HEADER: :results output raw
> #+HEADER: :exports results
> #+BEGIN_SRC R
> library(xtable)
> library(ascii)
> print(ascii(xtable(matrix(c(1,2,3,4),nrow=2,ncol=2))),type="org")
> #+END_SRC
>
> #+results: gauland-eg
> | |1 |2 |
> |---+--+--|
> | 1 | 1.00 | 3.00 |
> | 2 | 2.00 | 4.00 |
>
> Then you can let the new exporter do the work of making the LaTeX export
> look nice. This has the (possible) advantage that it also exports to the
> other back ends, not just LaTeX.
>
I agree with Tom's comments in general, although there might exist
special situations where the output would have to be tweaked and made
less generic.
But even in the original form below, I cannot reproduce Michael's problem: the
% signs are not escaped. I get
--8<---cut here---start->8---
\section{Snippet}
\label{sec-1}
% latex table generated in R 2.12.1 by xtable 1.5-6 package
% Wed Oct 24 23:38:22 2012
\begin{table}[ht]
\begin{center}
\begin{tabular}{rrr}
\hline
& 1 & 2 \\
\hline
1 & 1.00 & 3.00 \\
2 & 2.00 & 4.00 \\
\hline
\end{tabular}
\end{center}
\end{table}
% Generated by Org mode 7.9.2 in Emacs 24.2.50.1.
--8<---cut here---end--->8---
Org-mode version 7.9.2 (release_7.9.2-459-g6f7e92 @
/home/nick/elisp/org-mode/lisp/)
Nick
>
> Michael Gauland writes:
>
> > I use the xtables package in R to generate nice-looking tables for LaTeX
> > output,
> > as in the snippet below. The new exporter escapes the % symbol in the R
> > output,
> > so that the comments generated by xtable are no longer comments.
> >
> > * Snippet
> > #+HEADER: :results output latex
> > #+HEADER: :exports results
> > #+BEGIN_SRC R
> > library(xtable)
> > xtable(matrix(c(1,2,3,4),nrow=2,ncol=2))
> > #+END_SRC
> >
> > #+RESULTS:
> > #+BEGIN_LaTeX
> > % latex table generated in R 2.15.1 by xtable 1.7-0 package
> > % Thu Oct 25 13:11:30 2012
> > \begin{table}[ht]
> > \begin{center}
> > \begin{tabular}{rrr}
> > \hline
> >& 1 & 2 \\
> > \hline
> > 1 & 1.00 & 3.00 \\
> > 2 & 2.00 & 4.00 \\
> > \hline
> > \end{tabular}
> > \end{center}
> > \end{table}
> > #+END_LaTeX
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
Re: [O] [new exporter]: LaTeX output from babel escapes comment delimiter
Aloha Mike,
It looks like your source block and results are indented. IIRC, that's
not a good thing.
This might work better:
#+name: gauland-eg
#+HEADER: :results output raw
#+HEADER: :exports results
#+BEGIN_SRC R
library(xtable)
library(ascii)
print(ascii(xtable(matrix(c(1,2,3,4),nrow=2,ncol=2))),type="org")
#+END_SRC
#+results: gauland-eg
| |1 |2 |
|---+--+--|
| 1 | 1.00 | 3.00 |
| 2 | 2.00 | 4.00 |
Then you can let the new exporter do the work of making the LaTeX export
look nice. This has the (possible) advantage that it also exports to the
other back ends, not just LaTeX.
hth,
Tom
Michael Gauland writes:
> I use the xtables package in R to generate nice-looking tables for LaTeX
> output,
> as in the snippet below. The new exporter escapes the % symbol in the R
> output,
> so that the comments generated by xtable are no longer comments.
>
> * Snippet
> #+HEADER: :results output latex
> #+HEADER: :exports results
> #+BEGIN_SRC R
> library(xtable)
> xtable(matrix(c(1,2,3,4),nrow=2,ncol=2))
> #+END_SRC
>
> #+RESULTS:
> #+BEGIN_LaTeX
> % latex table generated in R 2.15.1 by xtable 1.7-0 package
> % Thu Oct 25 13:11:30 2012
> \begin{table}[ht]
> \begin{center}
> \begin{tabular}{rrr}
> \hline
>& 1 & 2 \\
> \hline
> 1 & 1.00 & 3.00 \\
> 2 & 2.00 & 4.00 \\
> \hline
> \end{tabular}
> \end{center}
> \end{table}
> #+END_LaTeX
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] org-mobile-push fails
This is strange, since I get the whole emacs from a repository (http://emacs.naquadah.org/ unstable/ ). I should not have to compile anything. I guess there must be a bug in the package from the repository. What do you recommend me to do? Install the org from source? On Wed, Oct 24, 2012 at 5:35 AM, Bastien wrote: > Hi Jorge, > > "Jorge A. Alfaro Murillo" writes: > >> Hi, I am having trouble with org-mobile-push, it fails and gives the >> following error: >> org-mobile-create-index-file: Symbol's function definition is void: >> org-prepare-agenda-buffers > > The function `org-prepare-agenda-buffers' has been renamed to > `org-agenda-prepare-buffers'. > >> It might be related to the fact that now when run org-version the result is: >> Org-mode version 7.9.2 (7.9.2-GNU-Emacs-24-3 @ org-install.el can not be >> found!) > > Bingo! It is related. :) > >> My emacs version is: >> GNU Emacs 24.2.50.1 (i486-pc-linux-gnu, GTK+ Version 3.4.2) of >> 2012-10-18 on dex, modified by Debian >> >> I updated today and since then the issue has come up. > > You certainly need to run make && make install so that the correct > functions' names are autoloaded when Emacs fires up. > > See http://orgmode.org/worg/dev/org-build-system.html for details. > >> This is also my first post to this list, which I hope to check out >> more regularly, since lately org-mode has taken over my life. Thanks >> for the help, best > > Welcome! > > -- > Bastien
[O] [new exporter]: LaTeX output from babel escapes comment delimiter
I use the xtables package in R to generate nice-looking tables for LaTeX output,
as in the snippet below. The new exporter escapes the % symbol in the R output,
so that the comments generated by xtable are no longer comments.
* Snippet
#+HEADER: :results output latex
#+HEADER: :exports results
#+BEGIN_SRC R
library(xtable)
xtable(matrix(c(1,2,3,4),nrow=2,ncol=2))
#+END_SRC
#+RESULTS:
#+BEGIN_LaTeX
% latex table generated in R 2.15.1 by xtable 1.7-0 package
% Thu Oct 25 13:11:30 2012
\begin{table}[ht]
\begin{center}
\begin{tabular}{rrr}
\hline
& 1 & 2 \\
\hline
1 & 1.00 & 3.00 \\
2 & 2.00 & 4.00 \\
\hline
\end{tabular}
\end{center}
\end{table}
#+END_LaTeX
Re: [O] Filling comments in Org code block vs in temporary buffer
"Sebastien Vauban" writes: > Is there no way to make such a practical feature[1] available? There's a mechanism to send commands to the src-block through the appropriate major-mode. It may be possible to ask for a filling with that. But I don't think Org should treat a src-block as plain text when M-q is used. > [1] For example, mails I get are enclosed in a "verse" block, and I've the > habit of reformatting them before saving my "inbox" file. Verse blocks are for free-form poetry and cannot be filled. I suggest to use quote blocks, which can be filled, for that. Regards,
Re: [O] Setting width of babel-generated image in LaTeX export?
Thomas S. Dye tsdye.com> writes: > ...Here is how I've been generating figures for LaTeX export using the new > exporter: Thanks--that's just what I was looking for.
Re: [O] Web site bug
Hi Simon, Simon Thum writes: > I just set up another machine and noticed that the ELPA install still > recommends (require 'org-install). > > http://orgmode.org/elpa.html > > That worked but got me warnings. I added a note about (require 'org-install) not being required for Org > 7.9.2 -- thanks! -- Bastien
Re: [O] Setting width of babel-generated image in LaTeX export?
Aloha Mike,
Perhaps #+ATTR_LaTeX: width=3cm will work? I don't believe the square
brackets following #+ATTR_LaTeX in your initial image are correct.
Here is how I've been generating figures for LaTeX export using the new
exporter:
#+name: fundamental-model
#+header: :exports results
#+header: :file fundamental-model.pdf
#+BEGIN_SRC dot
graph G
{
graph [margin="0.01"];
d [label = "Dated event", shape ="box"];
t [label = "Target event"];
d -- t [label = "Association", dir = "both", len = 2];
{rank=same; d t;}
}
#+END_SRC
#+CAPTION[The fundamental relationship of a chronological model]:
#+CAPTION: The fundamental relationship of a chronological model based on
radiometric dating.
#+ATTR_LaTeX: width=232pt
#+NAME: fig:fundamental
#+RESULTS: fundamental-model
[[file:fundamental-model.pdf]]
Naming the results lets me cross reference, e.g.,
These two types of events are often referred to as the dated
event and the target event, respectively (fig. [[fig:fundamental]]).
hth,
Tom
Michael Gauland writes:
> I'm having trouble specifying the width of an image I export to LaTeX (with
> either the new or old exporter). The snippet below demonstrates my problem. It
> uses plantuml to generate an image file, using ATTR_LaTeX to specify the
> width.
> When exported, the .tex file specifies the default width (.9\linewidth) for
> the
> first image; the second image correctly specifies a width of 4cm.
>
> Am I doing something wrong, or is this a bug?
> Thanks,
> Mike
>
> * Snippet
> #+ATTR_LaTeX[width=3cm]:
> #+BEGIN_SRC plantuml :file test-output.png
> FirstState: A Really Wide State To Make The Image Wider Than The Text
> SecondState: Another Really Wide State To Make The Image Wider Than The Text
> FirstState -right-> SecondState
> #+END_SRC
>
> #+RESULTS:
> [[file:test-output.png]]
>
>
> #+ATTR_LaTeX: width=4cm
> [[file:test-output.png]]
>
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] Setting width of babel-generated image in LaTeX export?
Hi Michael, Michael Gauland writes: > I'm having trouble specifying the width of an image I export to LaTeX (with > either the new or old exporter). The snippet below demonstrates my problem. It > uses plantuml to generate an image file, using ATTR_LaTeX to specify the > width. > When exported, the .tex file specifies the default width (.9\linewidth) for > the > first image; the second image correctly specifies a width of 4cm. > > Am I doing something wrong, or is this a bug? > Thanks, > Mike > > * Snippet > #+ATTR_LaTeX[width=3cm]: Try: #+ATTR_LaTeX: width=3cm Myles > #+BEGIN_SRC plantuml :file test-output.png > FirstState: A Really Wide State To Make The Image Wider Than The Text > SecondState: Another Really Wide State To Make The Image Wider Than The Text > FirstState -right-> SecondState > #+END_SRC > > #+RESULTS: > [[file:test-output.png]] > > > #+ATTR_LaTeX: width=4cm > [[file:test-output.png]]
[O] Setting width of babel-generated image in LaTeX export?
I'm having trouble specifying the width of an image I export to LaTeX (with either the new or old exporter). The snippet below demonstrates my problem. It uses plantuml to generate an image file, using ATTR_LaTeX to specify the width. When exported, the .tex file specifies the default width (.9\linewidth) for the first image; the second image correctly specifies a width of 4cm. Am I doing something wrong, or is this a bug? Thanks, Mike * Snippet #+ATTR_LaTeX[width=3cm]: #+BEGIN_SRC plantuml :file test-output.png FirstState: A Really Wide State To Make The Image Wider Than The Text SecondState: Another Really Wide State To Make The Image Wider Than The Text FirstState -right-> SecondState #+END_SRC #+RESULTS: [[file:test-output.png]] #+ATTR_LaTeX: width=4cm [[file:test-output.png]]
Re: [O] new exporter / org-element
Hello, Achim Gratz writes: > In the following Org snippet > > * Heading 1... * Footnotes... #+LATEX: \pagebreak[4] * Heading 2 > > the pagebreak does not get exported to LaTeX since the Footnotes section > will not be exported and the pagebreak is interpreted as being part of > that section. It would be nice if there was a way to "bind" it to the > following heading or alternatively move it past the heading but have it > export before. Is that possible already or can it be implemented? Can't you move footnotes section at the end of your document instead? Regards, -- Nicolas Goaziou
[O] Web site bug
Hi, I just set up another machine and noticed that the ELPA install still recommends (require 'org-install). http://orgmode.org/elpa.html That worked but got me warnings. Cheers, Simon
Re: [O] [ANN] Editable HTML export of Org-mode files
On 10/22/2012 10:38 PM, Eric Schulte wrote: Simon Thum writes: --8<---cut here---start->8--- foo bar --8<---cut here---end--->8--- all of the spaces and newlines are inserted into the Org-mode file. However, when that Org-mode file is re-exported, it uses the normal html exporter (which *does* ignore whitespace by default). So, if you are not having the spaces inserted into your Org-mode file that is a problem with org-ehtml, but if you *are* having the spaces appear in your .org file (server-side), but they are not appearing in the exported HTML, that is expected behavior. I meant when editing in the HTML page via the server call-back. Changing the WS means all lines change, regardless of whether I edited them. From your description I assume the edit box content comes out of the export, too? I guess that needs to change for this to work reliably. 2) I cannot use the auth handler: Perhaps you could provide a minimal .el initialization file which shows how you are trying to launch the server? Essentially from your README - sadly with -Q it does not work, but I'll be back to this in a week or so. Cheers, Simon Hope this Helps,
[O] new exporter / org-element
In the following Org snippet --8<---cut here---start->8--- * Heading 1... * Footnotes... #+LATEX: \pagebreak[4] * Heading 2 --8<---cut here---end--->8--- the pagebreak does not get exported to LaTeX since the Footnotes section will not be exported and the pagebreak is interpreted as being part of that section. It would be nice if there was a way to "bind" it to the following heading or alternatively move it past the heading but have it export before. Is that possible already or can it be implemented? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] Filling comments in Org code block vs in temporary buffer
Hello Nicolas, Nicolas Goaziou wrote: > "Sebastien Vauban" writes: > >> When trying to refill the comment directly in the following code block >> (staying in the Org file), it has *no effect*. >> >> #+begin_src emacs-lisp >> ;; a single space does end a sentence. But this sentence is the longest I >> could write... >> (setq-default sentence-end-double-space nil) >> #+end_src > > Org doesn't know how to fill foreign code. Thus, you cannot fill > directly a src-block (or an example block or even an export block for > that matter). > > As you tried, you can edit that chunk of code in a separate buffer with > the appropriate major mode (and subsequent filling rules) using C-c '. For sure, that did work before -- at least in my setup... Maybe because of FillAdapt and such, which I used back then. Is there no way to make such a practical feature[1] available? Best regards, Seb [1] For example, mails I get are enclosed in a "verse" block, and I've the habit of reformatting them before saving my "inbox" file. -- Sebastien Vauban
[O] bug#12718: /srv/bzr/emacs/trunk r110652: Fix error in previous merge from Org.
>> * lisp/org/org-lparse.el: Move some hooks from org-lparse to >> org-do-lparse. > > I pushed another fix in Org's git repo here: > > http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=c33909 > > Can you revert this change? Otherwise it will create a merge > conflict. If you think the issue is really important, I can > fix it in Emacs trunk, using the same fix I made in Org. OK, reverted. Please go ahead and commit your other fix.
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
>>> The error message makes sense ... as soon as you know where the problem >>> comes from :) >> Also, while it's good to signal to the user that his bookmark file is >> corrupted (and to make sure we don't overwrite it with something else), >> I don't see why that should prevent Org's Refile from working. > By default, org-refile and org-capture store bookmarks to the last > refiled/captured Org headline. (There is org-capture-bookmark in > case users want to deactivate this for captured headlines.) > We could skip this step in Org in case the bookmark format is > corrupted, or have a more informative message that makes clear to > the user that Org tries to store a bookmark. I don't know the details of what happens currently when the bookmark file is corrupted but at least such an occurrence shouldn't prevent org-refile from working (tho obviously in a degraded way). IOW, if needed we could wrap the calls to bookmark-set in with-demoted-errors, but maybe those errors are signaled late enough already that while the command signals an error, it did do what it was expected to do. Stefan
Re: [O] Header Jumping
You can also pass C-u two times to go to the last refiled/captured headline, that is, "C-u C-u C-c C-w" and "C-u C-u C-c c". At Thu, 25 Oct 2012 00:02:22 +1100, tony day wrote: > > > Esben Stien writes: > > > >> Is there some way to go directly to a node? > >> > >> F.ex, I have: > >> > >> * foo > >> ** bar.. > >> ** baz.. > >> ** hukarz.. > >> > >> I do C-c a s to search for baz, which brings up a buffer with baz > >> somewhere in there and I have to move down the list to hit TAB on baz. > >> > > Whoever crafted org-refile thought ahead. C-u C-c C-w selects and jumps to > the header selected rather than doing a refiling. > > Just played around with that and =bookmark-set= and it works nicely with > norang settings eg > > #+begin_src emacs-lisp > ; Targets include this file and any file contributing to the agenda - up to 4 > levels deep > (setq org-refile-targets (quote ((nil :maxlevel . 2) > (org-agenda-files :maxlevel . 2 > ; Use full outline paths for refile targets - we file directly with IDO > (setq org-refile-use-outline-path t) > ; Targets complete directly with IDO > (setq org-outline-path-complete-in-steps nil) > ; Allow refile to create parent tasks with confirmation > (setq org-refile-allow-creating-parent-nodes (quote confirm)) > ; every header is a refile target > (setq org-refile-target-verify-function nil) > ; use IDO > (setq org-completion-use-ido t) > > (defun org-jump () > (interactive) > (bookmark-set "org-jumped-from") > (org-refile t nil nil "Jump") > (bookmark-set "org-jumped-to")) > > > (defun org-jump-back() > (interactive) > (if (equal (point) (bookmark-get-position "org-jumped-from")) > (bookmark-jump "org-jumped-to") > (if (bookmark-get-position "org-jumped-to") > (bookmark-jump "org-jumped-from" > > > (bind-key "C-. j" 'org-jump) > (bind-key "C-. l" 'org-jump-back) > #+end_src > > tony > > > > > >
Re: [O] Filling comments in Org code block vs in temporary buffer
Hello, "Sebastien Vauban" writes: > When trying to refill the comment directly in the following code block > (staying in the Org file), it has *no effect*. > > #+begin_src emacs-lisp > ;; a single space does end a sentence. But this sentence is the longest I > could write... > (setq-default sentence-end-double-space nil) > #+end_src Org doesn't know how to fill foreign code. Thus, you cannot fill directly a src-block (or an example block or even an export block for that matter). As you tried, you can edit that chunk of code in a separate buffer with the appropriate major mode (and subsequent filling rules) using C-c '. Regards, -- Nicolas Goaziou
[O] bug#12718: bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument
Hi, Bastien, Apologies. I was the original poster of this bug report, and I had to correct it later: The problem is not that ODT export fails, but that ODT export-and-open fails to locate the exported file. Please see if you can reproduce it with a capital O in the export command: C-c C-e O One other user already reported reproducing it, and I still get it with emacs -Q running Org 7.9.2 on Emacs 24.1.1. Yours, Christian On 10/24/12 3:32 PM, Bastien wrote: Hi Jambunathan, Jambunathan K writes: When I try to export to ODT (without invoking the new exporter or anything), I get: OpenDocument export failed: Wrong type argument: stringp, (org-export-odt-preprocess-latex-fragments) I cannot reproduce this with current Emacs trunk and emacs -Q C-x C-f test.org RET [some simple org file] C-c C-e o How can I reproduce the problem above? Thanks,
[O] Issue when jumping from agenda view to clock line
Hi, I'm having an issue when jumping from the C-c a a / v c view (check log view in the agenda view) to a clock line. Here's a small example. #+begin_src org * My tasks ** First task :LOGBOOK: CLOCK: [2012-10-22 Mon 13:00]--[2012-10-22 Mon 14:30] => 1:00 CLOCK: [2012-10-23 Tue 13:00]--[2012-10-23 Tue 14:30] => 1:00 CLOCK: [2012-10-24 Wed 13:00]--[2012-10-24 Wed 14:30] => 1:00 :END: #+end_src In the agenda view (C-c a a) for Wed 24, enable the check view (v c), then press ENTER on the log line for "First task", you jump to the corresponding heading (First task) but it positions the cursor just after the :LOGBOOK: keyword and the drawer remains closed. The previous and correct behaviour was to jump to the corresponding line (in the example, the third clock line) in the opened drawer. I'm using org-mode version 7.9.2 (release_7.9.2-53-g93040f). Thanks for your help. Francesco
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
Hi Stefan, Stefan Monnier writes: >> The error message makes sense ... as soon as you know where the problem >> comes from :) > > Also, while it's good to signal to the user that his bookmark file is > corrupted (and to make sure we don't overwrite it with something else), > I don't see why that should prevent Org's Refile from working. By default, org-refile and org-capture store bookmarks to the last refiled/captured Org headline. (There is org-capture-bookmark in case users want to deactivate this for captured headlines.) We could skip this step in Org in case the bookmark format is corrupted, or have a more informative message that makes clear to the user that Org tries to store a bookmark. What do you think? -- Bastien
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
> >> I found a way to reproduce this: have a corrupt bookmarks file. > >> Check the contents of your bookmark-default-file. Try > >> (re)moving it. > > Wonderfull. I had an empty ~/.emacs.d/bookmarks file. > > I removed it and the problem is gone. > > Hmm... it would be good if Emacs were a bit more helpful here by > maybe including the bookmark file name in the error. > > > The error message makes sense ... as soon as you know where > > the problem comes from :) > > Also, while it's good to signal to the user that his bookmark file > is corrupted (and to make sure we don't overwrite it with > something else), I don't see why that should prevent Org's > Refile from working. Sorry, I have not been following this thread - excuse me if I misunderstand. But AFAIK an empty bookmark file should not present any problems for Emacs (for bookmark handling, at least, and I would hope for Org mode and anything else too). Is that really what the problem was - an empty bookmark file was interpreted (by something) as a corrupt bookmark file? If so, that in itself sounds like a bug, to me. I use Bookmark+, but I would guess that vanilla bookmark.el too handles the existence of an empty bookmark file with no problem. If not, that would be the first thing to fix, I would think. (Again, ignore if I've misunderstood.)
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
>> I found a way to reproduce this: have a corrupt bookmarks file. >> Check the contents of your bookmark-default-file. Try (re)moving it. > Wonderfull. > I had an empty ~/.emacs.d/bookmarks file. > I removed it and the problem is gone. Hmm... it would be good if Emacs were a bit more helpful here by maybe including the bookmark file name in the error. > The error message makes sense ... as soon as you know where the problem > comes from :) Also, while it's good to signal to the user that his bookmark file is corrupted (and to make sure we don't overwrite it with something else), I don't see why that should prevent Org's Refile from working. Stefan
[O] Filling comments in Org code block vs in temporary buffer
#+TITLE: Filling comments #+LANGUAGE: en * Context I've stopped using FillAdapt in Org files, and do not suffer any particular problems, except this one (though, certainly unrelated). * Problem When trying to refill the comment directly in the following code block (staying in the Org file), it has *no effect*. #+begin_src emacs-lisp ;; a single space does end a sentence. But this sentence is the longest I could write... (setq-default sentence-end-double-space nil) #+end_src FYI, C-h k M-q gives: ╭ │ M-q runs the command fill-paragraph, which is an interactive compiled │ Lisp function in `fill.el'. │ │ It is bound to M-q. │ │ (fill-paragraph &optional JUSTIFY REGION) │ │ Fill paragraph at or after point. ╰ * Workaround - Open it in a temporary buffer (via C-c ') - Re-run M-q anywhere on the comment #+begin_src emacs-lisp ;; a single space does end a sentence. But this sentence is the longest I ;; could write... (setq-default sentence-end-double-space nil) #+end_src FYI, when inside the temporary buffer, C-h k M-q just gives exactly the same (and expected command): =fill-paragraph=. * Questions I think this is quite new, but could not identify anything peculiar in my config. Do you have the same? Do you understand why? Best regards, Seb -- Sebastien Vauban
Re: [O] Keyboard command to force "done"
HI Nathan, Nathan Neff writes: > (defun njn/force-done () > (interactive) > (setq current-prefix-arg '(64)) ; specify universal argument as > C-u C-u C-u (4*4*4) > (call-interactively 'org-todo)) ; don't know the syntax to pass > 'done to 'org-todo > ) (org-todo 'done) HTH, -- Bastien
Re: [O] Short article on how I implement my GTD
Hi Ivan, Ivan Kanis writes: > http://ivan.kanis.fr/gtd-and-org-mode.html I like this one: "For those who don't know org mode is an outliner on steroids." :) -- Bastien
Re: [O] Org-sync with redmine
Hi Aurélien, Aurélien Aptel writes: > On Sun, Oct 14, 2012 at 3:05 AM, Tim wrote: >> Any idea where i should look for what may be causing the error ? > > The redmine backend is incomplete and poorly tested, sorry. > Unfortunately, I'm very busy and I have not found the time to work on > org-sync yet. The redmine backend is at the top of my TODO list > though. Great to read that you still have a TODO for Org ;) And thanks in advance for your work in this area! -- Bastien
Re: [O] Last org-lparse.el changes make swriter not to open after org-export-as-odt-and-open
Hi Miguel, Miguel Ruiz writes: > Last org-lparse.el changes make swriter not to open after > org-export-as-odt-and-open This should be fixed now. Please try and report any problem. Thanks, -- Bastien
Re: [O] Speeding up the agenda search
Hi Marcelo, Marcelo de Moraes Serpa writes: > My list of files in the agenda got to a considerable size. It still > searchable, but some types of search, such as PROPERTY, usually lock > down emacs and I'm forced to kill the process. Is there any way to > speed it up? Perhaps by compiling the elisp files to bytecode? Speed of the agenda generation is a often a problem. It's a delicate one because subjective and objective problems are often closely entangled in this area (speed of your machine, perceived acceptable speed for generating the agenda, complexity of the query, size of your agenda files, etc.) The only way we can make progress here is by rolling our sleeves and performing tiny optimizations, one after another. As a first step, you can try to make a diagnosis the problem by instrumenting the agenda functions: M-x elp-instrument-package RET org-agenda RET Then doing your agenda query then reporting results M-x elp-results RET We'll get a rough idea of the time spent and be able to compare it with the one on other machines. Thanks, -- Bastien
Re: [O] [BUG] [ODT] ODT export (old) fails with wrong-type-argument
Hi, I confirm -- this is fixed in release_7.9.2-513-gad17c4. Thanks! Yours, Christian On 10/24/12 3:59 PM, Bastien wrote: Hi Christian, Christian Moe writes: When I try to export to ODT (without invoking the new exporter or anything), I get: OpenDocument export failed: Wrong type argument: stringp, (org-export-odt-preprocess-latex-fragments) This also happens in a document with no latex fragments. I'm running Org-mode version 7.9.2 (release_7.9.2-458-ged698d @ /Applications/Emacs.app/Contents/Resources/site-lisp/org/) on GNU Emacs 24.1.1. Is it just me? Nope, this was a bug -- I've just fixed this in the maint and master branches. Can you have a try and let me know? Thanks for reporting this!
Re: [O] Using git-annex with org-attach
Hi John, "John Wiegley" writes: > I pushed a change to master that allows you to use the wonderful git-annex > utility[1] seamlessly with org-attach. That's a great addition! I didn't now git annex but from your description it looks like a win. Thanks again, -- Bastien
Re: [O] Per-file characters for underlining headlines on ASCII export?
Hi Loris, "Loris Bennett" writes: > Is it possible to set the characters for underlining headlines on ASCII > export on a per-file basis? Yes. See `org-export-ascii-underline' and the use of #+BIND in Org's buffers. HTH, -- Bastien
Re: [O] Select a region and archive
Hi Chris, Chris Henderson writes: > I am trying to select a region and archive it. At the moment it only > archives where the cursor is. This is what I am doing: > > - select a region - ctrl- and C-e to go the end of the line. > - archive - C-c C-x C-x (setq org-loop-over-headlines-in-active-region t) Then select the region and C-c C-x C-a (or C-c $). HTH, -- Bastien
Re: [O] [BUG] [ODT] ODT export (old) fails with wrong-type-argument
Hi Christian, Christian Moe writes: > When I try to export to ODT (without invoking the new exporter or > anything), I get: > > OpenDocument export failed: Wrong type argument: stringp, > (org-export-odt-preprocess-latex-fragments) > > This also happens in a document with no latex fragments. > > I'm running Org-mode version 7.9.2 (release_7.9.2-458-ged698d @ > /Applications/Emacs.app/Contents/Resources/site-lisp/org/) on GNU Emacs > 24.1.1. > > Is it just me? Nope, this was a bug -- I've just fixed this in the maint and master branches. Can you have a try and let me know? Thanks for reporting this! -- Bastien
[O] bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument
Jambunathan K writes: > Capital 'O'. Thanks. Now fixed in Org maint branch. -- Bastien
[O] bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument
Bastien writes: > Hi Jambunathan, > > Jambunathan K writes: > >> When I try to export to ODT (without invoking the new exporter or >> anything), I get: >> >> OpenDocument export failed: Wrong type argument: stringp, >> (org-export-odt-preprocess-latex-fragments) > > I cannot reproduce this with current Emacs trunk and > > emacs -Q > C-x C-f test.org RET > [some simple org file] > C-c C-e o > > How can I reproduce the problem above? Capital 'O'. http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00431.html http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00429.html > Thanks, --
Re: [O] Bug: Status of the org-mediawiki.el [7.8.11]
Hi Bernhard, Bernhard Gschaider writes: > May question: Is the support for Mediawiki-export abandoned? For now, yes. But I think it would be a nice format to export to. > If yes: I'd suggest to remove the reference to it from > http://orgmode.org/worg/org-contrib/ Done, thanks! -- Bastien
Re: [O] Different faces for different "flavors" of org-mode files
Hi Dov, Dov Grobgeld writes: > Does someone have any idea of how to implement this? I suggest defining and using themes. Have a look at (info "(emacs)Custom Themes") (You can C-x e after the parenthesis above.) HTH, -- Bastien
[O] bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument
Hi Jambunathan, Jambunathan K writes: > When I try to export to ODT (without invoking the new exporter or > anything), I get: > > OpenDocument export failed: Wrong type argument: stringp, > (org-export-odt-preprocess-latex-fragments) I cannot reproduce this with current Emacs trunk and emacs -Q C-x C-f test.org RET [some simple org file] C-c C-e o How can I reproduce the problem above? Thanks, -- Bastien
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
Hi Jonathan, Jonathan Schaeffer writes: >> Perhaps Org could trap and report such errors more gracefully. >> > The error message makes sense ... as soon as you know where the problem > comes from :) I enhanced the error message, which now says to save the buffer in a file when refiling to the current non-file buffer. (Reporting an error when the bookmark format is corrupted is left to the bookmark library.) I'm closing this bug now. Thanks for reporting this! -- Bastien
Re: [O] modeline vs modeline
Hi Brendan, Brendan Halpin writes: > but that still leaves the problem of dealing with the Emacs/Xemacs > compatibility. Is there a way of aliasing face attributes? Aliasing the face name should be enough. But the 'modeline face has been removed from Emacs at the beginning of this month, so I'm not in favor of recreating an alias in Org's core. If the alias is needed by XEmacs people, it should be made in XEmacs, as this is not an Org-only compatibility issue. Best, -- Bastien
Re: [O] [PATCH] Babel: add results value support to Scala
Hi Andrzej,
Asrail posted this patch against ob-scala.el a while ago.
Can you confirm it is okay to apply it? I'm reattaching
the patch in case you are not reading the Orgmode mailing
list anymore.
Thanks in advance!
Asrail writes:
> * lisp/ob-scala.el (org-babel-scala-wrapper-method): Use an scala
> block enclosing the submitted code
>From 0d7b1b3e7e5d63a77a1fe47cee80fd7f7bcb4cce Mon Sep 17 00:00:00 2001
From: Caio Tiago Oliveira
Date: Mon, 15 Oct 2012 15:52:50 -0300
Subject: [PATCH] Babel: add results value support to Scala
* lisp/ob-scala.el (org-babel-scala-wrapper-method): Use an scala block enclosing the submitted code
The string representing an well formed block was not an Scala code. I put the string from the user into an block, surrounded by an call to replace the default output stream.
TINYCHANGE
---
lisp/ob-scala.el | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/lisp/ob-scala.el b/lisp/ob-scala.el
index bd855a8..ea3c3f2 100644
--- a/lisp/ob-scala.el
+++ b/lisp/ob-scala.el
@@ -72,9 +72,17 @@ Emacs-lisp table, otherwise return the results as a string."
(defvar org-babel-scala-wrapper-method
- "(
+
+"var str_result :String = null;
+
+Console.withOut(new java.io.OutputStream() {def write(b: Int){
+}}) {
+ str_result = {
%s
-) asString print
+ }.toString
+}
+
+print(str_result)
")
--
1.7.10.4
--
Bastien
[O] org-mobile-push and SUMO buffer
Dear All, I think that the behavior of org-mobile-push has changed in some recent update. Since a few days ago (when I upgraded to v. 7.9.1-2, from Debian), whenever org-mobile-push runs, a new agenda buffer called *SUMO* is created, and the display redrawn. I can see (in file org-mobile.el) where this code lives. Now, I am not sure to understand this new behavior, nor if I should try to override it, nor what is the recommended approach. This is my problem: - I often have a bunch of org files opened in a single Emacs frame (split horizontally and vertically, etc). - One of the windows in that Emacs frame is always the org-mode agenda, called *Org Agenda*, and generated with M-x org-agenda (this command I call as soon as I start up that Emacs). - Then, when org-mobile-push runs (either because it tell it do so, or because the timer says so), the display gets redrawn, and I get only two windows, one with *Org Agenda* and the other with the *SUMO* buffer. This is very annoying to me because: a) as far as I can tell, the info in both buffers is the same; b) I get all my previous window setup messed up; yes, I do get back to it with winner mode. But I'd rather not have to do that every 30'. I guess I could hack the org-mobile.el file so that org-mobile-push does not redraw the display, or rename the org-agenda-buffer (either globally or just for org-mobile), etc, but I think there is something much simpler that I am missing. How can I fix this problem? Best, R. -- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdia...@gmail.com ramon.d...@iib.uam.es http://ligarto.org/rdiaz
[O] Header Jumping
> Esben Stien writes: > >> Is there some way to go directly to a node? >> >> F.ex, I have: >> >> * foo >> ** bar.. >> ** baz.. >> ** hukarz.. >> >> I do C-c a s to search for baz, which brings up a buffer with baz >> somewhere in there and I have to move down the list to hit TAB on baz. >> Whoever crafted org-refile thought ahead. C-u C-c C-w selects and jumps to the header selected rather than doing a refiling. Just played around with that and =bookmark-set= and it works nicely with norang settings eg #+begin_src emacs-lisp ; Targets include this file and any file contributing to the agenda - up to 4 levels deep (setq org-refile-targets (quote ((nil :maxlevel . 2) (org-agenda-files :maxlevel . 2 ; Use full outline paths for refile targets - we file directly with IDO (setq org-refile-use-outline-path t) ; Targets complete directly with IDO (setq org-outline-path-complete-in-steps nil) ; Allow refile to create parent tasks with confirmation (setq org-refile-allow-creating-parent-nodes (quote confirm)) ; every header is a refile target (setq org-refile-target-verify-function nil) ; use IDO (setq org-completion-use-ido t) (defun org-jump () (interactive) (bookmark-set "org-jumped-from") (org-refile t nil nil "Jump") (bookmark-set "org-jumped-to")) (defun org-jump-back() (interactive) (if (equal (point) (bookmark-get-position "org-jumped-from")) (bookmark-jump "org-jumped-to") (if (bookmark-get-position "org-jumped-to") (bookmark-jump "org-jumped-from" (bind-key "C-. j" 'org-jump) (bind-key "C-. l" 'org-jump-back) #+end_src tony
Re: [O] org-mobile-push fails
Hi Jorge, "Jorge A. Alfaro Murillo" writes: > Hi, I am having trouble with org-mobile-push, it fails and gives the > following error: > org-mobile-create-index-file: Symbol's function definition is void: > org-prepare-agenda-buffers The function `org-prepare-agenda-buffers' has been renamed to `org-agenda-prepare-buffers'. > It might be related to the fact that now when run org-version the result is: > Org-mode version 7.9.2 (7.9.2-GNU-Emacs-24-3 @ org-install.el can not be > found!) Bingo! It is related. :) > My emacs version is: > GNU Emacs 24.2.50.1 (i486-pc-linux-gnu, GTK+ Version 3.4.2) of > 2012-10-18 on dex, modified by Debian > > I updated today and since then the issue has come up. You certainly need to run make && make install so that the correct functions' names are autoloaded when Emacs fires up. See http://orgmode.org/worg/dev/org-build-system.html for details. > This is also my first post to this list, which I hope to check out > more regularly, since lately org-mode has taken over my life. Thanks > for the help, best Welcome! -- Bastien
Re: [O] modeline vs modeline
Hi Brendan, Brendan Halpin writes: > I've just updated to emacs-snapshot 24.2.50.1 (of 2012-10-18) on Debian, > and have run in to a faces problem. In short references to modeline > should be to mode-line. Making 4 changes in org-faces.el is enough. Fixed, thanks. -- Bastien
[O] bug#12702: 24.2; Orgmode Refile complains "Not bookmark format"
Le 23/10/2012 18:24, Glenn Morris a écrit : I found a way to reproduce this: have a corrupt bookmarks file. Check the contents of your bookmark-default-file. Try (re)moving it. Wonderfull. I had an empty ~/.emacs.d/bookmarks file. I removed it and the problem is gone. Thanks a lot for your help. Perhaps Org could trap and report such errors more gracefully. The error message makes sense ... as soon as you know where the problem comes from :) cheers, Jonathan PS. I'm kind of new to emacs, and use orgmode intensively now, and it's my first emacs bug report. Your reactivity is realy great, I appreciate it. -- IUEM - Service Informatique rue Dumont D'Urville Technopôle Brest-Iroise 29280 Plouzané France tel: +33 2 98 49 87 94
Re: [O] modeline vs modeline
On Wed, Oct 24 2012, Sebastien Vauban wrote: > Maybe you could provide a patch? > > Though, a quick note: AFAICT, in GNU Emacs, the modeline is written > "mode-line"; but written "modeline" under XEmacs. I don't know how that fact > is supported in Org (as it is still supposed to run under XEmacs as well). You could express the patch like this: (progn (find-file "org-mode/lisp/org-faces.el") (goto-char (point-min)) (replace-string "modeline" "mode-line") (save-buffer)) or more conventionally: 695c695 < (org-compatible-face 'modeline --- > (org-compatible-face 'mode-line 701c701 < (org-compatible-face 'modeline --- > (org-compatible-face 'mode-line 773c773 < (org-copy-face 'modeline 'org-mode-line-clock --- > (org-copy-face 'mode-line 'org-mode-line-clock 775c775 < (org-copy-face 'modeline 'org-mode-line-clock-overrun --- > (org-copy-face 'mode-line 'org-mode-line-clock-overrun but that still leaves the problem of dealing with the Emacs/Xemacs compatibility. Is there a way of aliasing face attributes? Brendan -- Brendan Halpin, Department of Sociology, University of Limerick, Ireland Tel: w +353-61-213147 f +353-61-202569 h +353-61-338562; Room F1-009 x 3147 mailto:brendan.hal...@ul.ieULSociology on Facebook: http://on.fb.me/fjIK9t http://teaching.sociology.ul.ie/bhalpin/wordpress twitter:@ULSociology
Re: [O] modeline vs modeline
Hi Brendan, Brendan Halpin wrote: > I've just updated to emacs-snapshot 24.2.50.1 (of 2012-10-18) on Debian, > and have run in to a faces problem. In short references to modeline > should be to mode-line. Making 4 changes in org-faces.el is enough. Maybe you could provide a patch? Though, a quick note: AFAICT, in GNU Emacs, the modeline is written "mode-line"; but written "modeline" under XEmacs. I don't know how that fact is supported in Org (as it is still supposed to run under XEmacs as well). Best regards, Seb -- Sebastien Vauban
