[O] Create a longtable in LaTeX from orgtbl
Dear all,
Can you show how to create a longtable in LaTeX from orgtbl?
When a table in short, I create a LaTeX table in following way, as
demonstrated in manual.
https://www.gnu.org/software/emacs/manual/html_node/org/A-LaTeX-example.html
#+BEGIN_SRC LaTeX
\begin{table}[htdp]
\begin{center}
\caption{My great results}
% BEGIN RECEIVE ORGTBL tbl:my-short-table
% END RECEIVE ORGTBL tbl:my-short-table
\iffalse
#+ORGTBL: SEND tbl:my-short-table orgtbl-to-latex :no-escape t
|+-+|
| date | session | remark |
|+-+|
| 2014-06-18 | s140618 ||
|+-+|
\fi
\label{tbl:my-short-table}
\end{center}
\end{table}
#+END_SRC
For longtable, I do in following way. It barely works, but I have to
copy and paste header every time orgtbl is tossed to RECEIVE.
Can you show how to create a longtable in LaTeX from orgtbl? Thank
you in advance.
Tak
#+BEGIN_SRC LaTeX
%% \usepackage{longtable}
\begin{center}
\begin{longtable}{ rll }
\caption{My great results}\\
\hline
% --- for 1st page ---
date session remarks \\
%
\hline
\endfirsthead
\caption{Continued}\\
\hline
% --- for 2nd+ page --
date session remarks \\
%
\hline
\endhead
%
% BEGIN RECEIVE ORGTBL tbl:my-long-table
% END RECEIVE ORGTBL tbl:my-long-table
\iffalse
#+ORGTBL: SEND tbl:my-long-table orgtbl-to-longtbl :no-escape t :splice nil
:skip 0
| % date | session | remarks |
| 2014-06-18 | s140618 | foo |
\fi
%
\hline
\label{tbl:my-long-table}
\end{longtable}
\end{center}
#+END_SRC
#+BEGIN_SRC emacs-lisp
(defun orgtbl-to-longtbl (table params)
Convert the Orgtbl mode TABLE to LaTeX.
(let* ((alignment (mapconcat (lambda (x) (if x r l))
org-table-last-alignment ))
(params2
(list
:tstart (concat % \\begin{longtable}{ alignment })
:lstart :lend :sep
:efmt %s\\,(%s) :hline \\hline)))
(orgtbl-to-generic table (org-combine-plists params2 params
#+END_SRC
[O] Publishing sitemap
When I publish my web-site using org-mode, with suitable options in my org-publish-projects-alist, I can get org-publish to create a sitemap. Is it possible to just create the sitemap without publishing the whole project? I sometimes update a single file, and just publish it using org-publish-current-file. I would like the changes (for example, date) or if a new file is being published, the file itself, reflected in the sitemap. But I can’t do it unless I publish the whole project. Is there a way to deal with this? Vikas
[O] formatted index entries
Hello, In an org file, I would like to add formatted index entries =word=, !word or similar things, possibly in a hierarchical way as sub entries (I know it's a very peculiar use case, but it turns out that I would appreciate having this feature for writing a technical manual). e.g, something in the spirit of: # verbatim entry: #+INDEX: =word= #+INDEX: category!=word= # # verbatim entry with an exclamation mark: #+INDEX: =!word= #+INDEX: category!=!word= # # or even, let's be audacious: formatted code as an entry: #+INDEX: src_emacs-list[:exports code](let) Using the current development branch of Org mode, exporting to HTML works fine for the verbatim case, yet index entries do not seem to be treated as Org elements when exporting to LaTeX: index entries are named =word=. Also, exclamation marks are category delimiters (as in LaTeX), hence the cases makes Org insert extra categories named =, and adds entries word= in them (both in HTML and LaTeX). This topic has already been discussed on this list before ( http://thread.gmane.org/gmane.emacs.orgmode/41442 ), but apparently this feature is not (yet?) available in org ≥ 8.0. Has it already been implemented by somebody somewhere? Any further thoughts on that point? Best regards, Nicolas -- Nicolas BerthierFSF Member #7975
Re: [O] Discussion request: 15m tangle time, details follow
Hi Aaron, Aaron Ecay wrote: [...] babel needs to fetch 30 properties per source block. Indeed, this is marked “deprecated” in the source, in favor of a system where there is only one header arg. This has been marked deprecated for almost exactly a year in the code (Achim’s commit 90b16870 of 2013-06-23), but I don’t know of any prominent announcement of the deprecation. I neither was aware of such a deprecation. Are you talking of the comment in function `org-babel-params-from-properties' (in ob-core.el)? Thought, I can't parse it yet the way you do -- without understanding much more of that code, as the comments differ in at point of definition vs at point of call: ;; DEPRECATED header arguments specified as separate property at ;; point of definition ;; header arguments specified with the header-args property at ;; point of call What you're talking about is for specifying header arguments in a subtree, anyway always at the same point: [...] You’d then have to update your file: :PROPERTIES: :exports: none :tangle: no :END: becomes :PROPERTIES: :header-args: :exports none :tangle no :END: The new system is also a bit inferior, in that it doesn’t allow header arg inheritance as easily. So with the one-prop-per-arg system the following works as expected: * foo :PROPERTIES: :exports: none :END: ** bar :PROPERTIES: :tangle: no :END: (src block here) On the other hand, in the new system there’s no way to specify some header args at foo and some at bar; the lowest header-args property wins. (At least as far as I can see) Maybe the + mechanism for concatenating property strings would help here? Best regards, Seb -- Sebastien Vauban
Re: [O] Discussion request: 15m tangle time, details follow
Hi Grant, Grant Rettke g...@wisdomandwonder.com writes: Good evening, Over the past few months I've been working on the same literate document. It has been a learning experience for me, trial and error has abounded. The key tenet that I've adhered too though is to truly embrace literate programming, and the more I learn the more it makes sense. The document has grown quite organically and it has been and continues to be a wonderful experience. What I need help, feedback, discussion, and more on is the build time. The average build takes 15m. It didn't start this way; it was about 3 minutes way back when. The last time it got kind of big was 9m and I didn't think too much of it. After literally a day of additions, it shot up to 15m. I tried upgrading to the latest org release with no change. I also removed all of the non-tangleable text with no change there, either.To give a fair picture, I did publish the system here: https://github.com/grettke/home My specific request: I need help with pointers on where I should start looking to speed things up. My goal is to have a full powered literate programming system in org mode that is blazing fast. This is from a user perspective, I use it every chance I get now and have barely scratched the surface. Right now though I'm sort of hobbled by the build time. That is actually understating it, I can't really be productive anymore at all. Little changes take 15m each and if I test it the right way, 30m. Usually I would make little changes and every so often make sure that it can rebuild itself; usually it may :). This build is documented in the github project; it only loads the absolute minimum required to do the build. Ideas: Separate the documents. Hack on org directly. Non-ideas: Faster hardware. More ram. Newer software. Details: Emacs 24.3.1. Org 8.2.6 OSX 10.9 (software updated) Darwin orion 13.2.0 Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64 x86_64 8core 2.x GHz, 16GB ram Anti-virus turned off (compliance) Please let me know any comments, questions, or concerns; looking forward to all and every thought and idea. I do not have the time to look into this, but fortunately, other have done so already ;-) Just one quick idea: Have you tried [fn:1] (setq org-babel-use-quick-and-dirty-noweb-expansion t) This can lead to dramatic speedups in my experience. Best, Andreas Where I may contribute is with time, effort, patience, cheerfulness, and experience. Kind regards, Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson Footnotes: [fn:1] (see article.gmane.org/gmane.emacs.orgmode/50625/match=problem+noweb+ref+property)
Re: [O] Discussion request: 15m tangle time, details follow
Grant Rettke g...@wisdomandwonder.com writes: The average build takes 15m. Which file do you mean - TC3F.org? Thats some 4400 lines, thus not _that_ big really. I once used a giant init.el copied from the web that had some 8000 lines (now I'm back to 2500 again ...). I converted that file to outshine, since its mainly one programming language (emacs-lisp in this case): [with-current-buffer TC3F.org] ,- | (benchmark-run (outorg-convert-org-to-outshine)) | (1.792675211002 8 1.04214547809) `- After this is done *once*, you can always switch between emacs-lisp and org-mode with outorg, It takes 0.4 sec to convert the whole file to org again ,-- | (benchmark-run (outorg-edit-as-org '(4))) | (0.365756325 1 0.1380089740167) `-- and 1.6 sec to convert it back to outshine (I have to fix this speed difference ;) ,- | (benchmark-run (outorg-copy-edits-and-exit)) | (1.616835235 8 1.10669671098) `- But normally you do not convert the whole buffer to Org with outorg, just the subtree at hand, and thats instantly. Then productivity means that your init file *is* in a programming language mode (TC3F.el) and you can modify and eval your code on-the-fly. Whenever you need to edit the comment text, you do M-# M-# ,--- | M-x outorg-edit-as-org `--- and when you are done, M-# ,--- | M-x outorg-copy-edits-and-exit `--- Its just the reverse of Org-mode with souce-blocks, and in cases like an Emacs init-file, when its mostly one programming language and the source-code is more important than the text (and frequently modified), this reverse approach might be more productive. PS I just figured that I ran the benchmarks on an outorg testing branch, which is faster than master but not yet ready. So things might be a bit slower with master branch, but in terms of seconds (maybe 2 or 3 sec to convert the whole file?) -- cheers, Thorsten
[O] Publishing sitemap
When I publish my web-site using org-mode, with suitable options in my org-publish-projects-alist, I can get org-publish to create a sitemap. Is it possible to just create the sitemap without publishing the whole project? I sometimes update a single file, and just publish it using org-publish-current-file. I would like the changes (for example, date) or if a new file is being published, the file itself, reflected in the sitemap. But I can’t do it unless I publish the whole project. Is there a way to deal with this? Vikas
Re: [O] BEAMER_act property documented in ox-beamer.el
On Tuesday, 17 Jun 2014 at 22:01, Sebastien Vauban wrote: Hello, I'm trying to understand the sentence from ox-beamer.el: Headlines also support the BEAMER_act property. [It] is translated as an overlay/action specification (or a default overlay specification when enclosed within square brackets). Rewritten, it says that that property is translated as: - a default overlay specification *when enclosed within square brackets*, or - an overlay/action specification *when NOT enclosed within square brackets*. Though, I don't understand exactly what that *default* specification really means. Moreover, I can't get it: without square brackets, PDFLaTeX becomes crazy... I agree with you: I am not entirely sure what a *default* specification means. However, without square brackets, I get output that makes sense and pdflatex has no problems with it. I am using beamer from debian package latex-beamer 3.24-1 with texlive 2013.20130722. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.7-1110-g25fc4d
Re: [O] BEAMER_act property documented in ox-beamer.el
Hello,
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Tuesday, 17 Jun 2014 at 22:01, Sebastien Vauban wrote:
I'm trying to understand the sentence from ox-beamer.el:
Headlines also support the BEAMER_act property. [It] is translated as
an
overlay/action specification (or a default overlay specification when
enclosed within square brackets).
Rewritten, it says that that property is translated as:
- a default overlay specification *when enclosed within square brackets*, or
- an overlay/action specification *when NOT enclosed within square brackets*.
Though, I don't understand exactly what that *default* specification really
means. Moreover, I can't get it: without square brackets, PDFLaTeX becomes
crazy...
I agree with you: I am not entirely sure what a *default* specification
means.
See Beamer class user guide about \begin{frame} syntax (II.8, p. 59 on
version 3.20). Basically, default specification also applies to all
commands and environments within the frame, as long as they do not
provide their own specification.
Regards,
--
Nicolas Goaziou
[O] [bug?] Tramp tries to open remote file links
Hello, When I just open an Org file that has a link to a remote file, Tramp tries to open it, leading to errors and timeouts when offline, at least. --8---cut here---start-8--- * References Some files of interest: [[file:/m...@somewhere.org:papers/current.pdf][paper]] --8---cut here---end---8--- Errors: ╭ │ Tramp: Opening connection for m...@somewhere.org using plink... │ Tramp: Sending command `plink -l me -ssh -t somewhere.org env 'TERM=dumb' 'PROMPT_COMMAND=' 'PS1=#$ ' /bin/sh exit || exit' │ Tramp: Waiting for prompts from remote shell... │ Tramp failed to connect. If this happens repeatedly, try │ `M-x tramp-cleanup-this-connection' │ Tramp: Waiting for prompts from remote shell...failed │ Tramp: Opening connection for m...@somewhere.org using plink...failed ╰ Is this supposed to be normal? Why does Tramp open the file? Best regards, Seb -- Sebastien Vauban
Re: [O] Discussion request: 15m tangle time, details follow
Thorsten Jolitz tjol...@gmail.com writes: Grant Rettke g...@wisdomandwonder.com writes: The average build takes 15m. [with-current-buffer TC3F.org] After this is done *once*, you can always switch between emacs-lisp and org-mode with outorg, It takes 0.4 sec to convert the whole file to org again ,-- | (benchmark-run (outorg-edit-as-org '(4))) | (0.365756325 1 0.1380089740167) `-- and 1.6 sec to convert it back to outshine (I have to fix this speed difference ;) ,- | (benchmark-run (outorg-copy-edits-and-exit)) | (1.616835235 8 1.10669671098) `- This thread inspired me to profile these two commands - they do roughly the same thing, only in the opposite direction, and I found it strange why converting from Source to Org should be 4x faster than converting from Org to Source. It turned out that , | kill-whole-line is an interactive compiled Lisp function in | `simple.el'. ` was the sole culprit (used for killing the source-block ddelimiters). Its a lisp function and does too many things besides killing the line. Replacing it with C function ,-- | delete-region is an interactive built-in function in `editfns.c'. `-- improves performance to (on whole file TC3): ,- | (benchmark-run (outorg-copy-edits-and-exit)) | (0.66580701 2 0.2889433360266) `- The remaining speed difference is partly because I undo the indendation introduced in the Org source-blocks before the conversion back to source, and thus need to process the file twice. -- cheers, Thorsten
Re: [O] formatted index entries
Hello,
Nicolas Berthier nbe...@member.fsf.org writes:
In an org file, I would like to add formatted index entries =word=,
!word or similar things, possibly in a hierarchical way as sub entries
(I know it's a very peculiar use case, but it turns out that I would
appreciate having this feature for writing a technical manual). e.g,
something in the spirit of:
# verbatim entry:
#+INDEX: =word=
#+INDEX: category!=word=
# # verbatim entry with an exclamation mark:
#+INDEX: =!word=
#+INDEX: category!=!word=
# # or even, let's be audacious: formatted code as an entry:
#+INDEX: src_emacs-list[:exports code](let)
Using the current development branch of Org mode, exporting to HTML
works fine for the verbatim case, yet index entries do not seem to be
treated as Org elements when exporting to LaTeX: index entries are named
=word=. Also, exclamation marks are category delimiters (as in LaTeX),
hence the cases makes Org insert extra categories named =, and adds
entries word= in them (both in HTML and LaTeX).
This topic has already been discussed on this list before
( http://thread.gmane.org/gmane.emacs.orgmode/41442 ), but apparently
this feature is not (yet?) available in org ≥ 8.0.
Has it already been implemented by somebody somewhere? Any further
thoughts on that point?
LaTeX provides its own processor for index entries, so Org just lets it
handle #+INDEX keywords. Therefore #+INDEX: something becomes
\index{something} (see `org-latex-keyword'). You could write, e.g.,
#+INDEX: \texttt{word}
in order to get what you want.
OTOH, every other back-end relies on
`org-publish-index-generate-theindex', which creates a file containing
a list of links. So #+INDEX: something becomes
- [[file:...][something]]
Thus, Org syntax is perfectly allowed, including src_emacs-lisp{...},
the only problem being that exclamation marks are separators in
something. A workaround could be to make ! as a separator
instead:
#+INDEX: word ! !word
but that would break #+INDEX keywords currently used.
Note that the current set-up allows to preserve compatibility between
LaTeX and other back-ends in simple cases.
Regards,
--
Nicolas Goaziou
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Hello, When I just open an Org file that has a link to a remote file, Tramp tries to open it, leading to errors and timeouts when offline, at least. It doesn't happen to me. I tried emacs -Q path/to/test.org and the file opened normally. Grepping, I see that tramp-maybe-open-connection is responsible for the tramp messages. so you could eval: (trace-function-background 'tramp-maybe-open-connection *trace* (lambda () (with-output-to-string (backtrace then reproduce and look into the buffer *trace* to see what called tramp. Call M-x untrace-function RET TAB RET to remove the tracing. -- Nico.
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Hello, Hi Sebastien, When I just open an Org file that has a link to a remote file, Tramp tries to open it, leading to errors and timeouts when offline, at least. * References Some files of interest: [[file:/me-ohc15rc7jgtnlxjtenl...@public.gmane.org:papers/current.pdf][paper]] Errors: ╭ │ Tramp: Opening connection for me-ohc15rc7jgtnlxjtenl...@public.gmane.org using plink... │ Tramp: Sending command `plink -l me -ssh -t somewhere.org env 'TERM=dumb' 'PROMPT_COMMAND=' 'PS1=#$ ' /bin/sh exit || exit' │ Tramp: Waiting for prompts from remote shell... │ Tramp failed to connect. If this happens repeatedly, try │ `M-x tramp-cleanup-this-connection' │ Tramp: Waiting for prompts from remote shell...failed │ Tramp: Opening connection for me-ohc15rc7jgtnlxjtenl...@public.gmane.org using plink...failed ╰ Is this supposed to be normal? Why does Tramp open the file? Because Tramp has been instructed so? I suppose, following the above link results in (insert-file-contents /me-ohc15rc7jgtnlxjtenl...@public.gmane.org:papers/current.pdf) This is remote file name syntax, and Tramp tries to do its job, using the default method plink. You could avoid Tramp's reaction by a link like (untested) [[file:/:/me-ohc15rc7jgtnlxjtenl...@public.gmane.org:papers/current.pdf][paper]] Alternatively, you could choose another file name. Best regards, Seb Best regards, Michael.
[O] [bug, beamer] Frame parameters taken from example code block
Hello,
When having such a code block inside a frame:
--8---cut here---start-8---
#+TITLE: Org Beamer examples
#+LANGUAGE: en
#+OPTIONS: H:2 num:nil ^:{}
#+PROPERTY: eval no
#+LATEX_HEADER: \lstdefinelanguage{org}{}
* ECM
** Allow frame breaks
In your Org file, writing a code such as:
#+begin_src org :eval no
,** A very long frame with breaks
:PROPERTIES:
:BEAMER_opt: allowframebreaks,label=
:END:
#+end_src
will make that frame over multiple slides, as needed.
--8---cut here---end---8---
the frame inherits from the property BEAMER_opt which, though, is only
present in the example code, not in the Beamer frame itself.
See http://screencast.com/t/fc3pNAXTAhK4.
Best regards,
Seb
--
Sebastien Vauban
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Ask savannah-hack...@gnu.org. Then it's not worth the trouble (since it's a temporary change that will need to be modified yet again when we release 24.4). Stefan
Re: [O] [bug, beamer] Frame parameters taken from example code block
Hello,
When having such a code block inside a frame, the frame inherits
from the property BEAMER_opt which, though, is only present in the
example code, not in the Beamer frame itself.
Another example which is not compilable in LaTeX (because of that bug):
--8---cut here---start-8---
#+TITLE: Org Beamer examples
#+LANGUAGE: en
#+OPTIONS: H:2 num:nil ^:{}
#+PROPERTY: eval no
#+LATEX_HEADER: \lstdefinelanguage{org}{}
* ECM
** ~beamercolorbox~ environment
In your Org file, writing this:
#+begin_src org
,#+LaTeX: \setbeamercolor{mycolor}{bg=green,fg=white}
,*** mycolor :B_beamercolorbox:
:PROPERTIES:
:BEAMER_env: beamercolorbox
:BEAMER_opt: wd=6cm
:END:
Lorem ipsum...
#+end_src
displays a green post-it with a width of 6 cm.
--8---cut here---end---8---
See http://screencast.com/t/PY4nFxcKHe.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] formatted index entries
You wrote:
Hello,
Nicolas Berthier nbe...@member.fsf.org writes:
In an org file, I would like to add formatted index entries =word=,
!word or similar things, possibly in a hierarchical way as sub entries
(I know it's a very peculiar use case, but it turns out that I would
appreciate having this feature for writing a technical manual). e.g,
something in the spirit of:
# verbatim entry:
#+INDEX: =word=
#+INDEX: category!=word=
# # verbatim entry with an exclamation mark:
#+INDEX: =!word=
#+INDEX: category!=!word=
# # or even, let's be audacious: formatted code as an entry:
#+INDEX: src_emacs-list[:exports code](let)
Using the current development branch of Org mode, exporting to HTML
works fine for the verbatim case, yet index entries do not seem to be
treated as Org elements when exporting to LaTeX: index entries are named
=word=. Also, exclamation marks are category delimiters (as in LaTeX),
hence the cases makes Org insert extra categories named =, and adds
entries word= in them (both in HTML and LaTeX).
This topic has already been discussed on this list before
( http://thread.gmane.org/gmane.emacs.orgmode/41442 ), but apparently
this feature is not (yet?) available in org ≥ 8.0.
Has it already been implemented by somebody somewhere? Any further
thoughts on that point?
LaTeX provides its own processor for index entries, so Org just lets it
handle #+INDEX keywords. Therefore #+INDEX: something becomes
\index{something} (see `org-latex-keyword'). You could write, e.g.,
#+INDEX: \texttt{word}
in order to get what you want.
OTOH, every other back-end relies on
`org-publish-index-generate-theindex', which creates a file containing
a list of links. So #+INDEX: something becomes
- [[file:...][something]]
Thus, Org syntax is perfectly allowed, including src_emacs-lisp{...},
the only problem being that exclamation marks are separators in
something. A workaround could be to make ! as a separator
instead:
#+INDEX: word ! !word
but that would break #+INDEX keywords currently used.
Putting the question of the separator aside, my objective is to be able
to export the same Org document both as HTML and as LaTeX (at least).
I think, as was discussed in the thread I mentioned, that being able to
use Org markups in index entries could be a nice feature to do that.
I understand the contents coming after `#+INDEX:' is used as is in every
case (except in non-LaTeX exports for entries with `!' in them), but are
handled differently: for HTML, they are put in `theindex.inc' to be
handled later when this file is parsed by Org, and for LaTeX they are
passed directly as argument to the `\index' command.
Note that the current set-up allows to preserve compatibility between
LaTeX and other back-ends in simple cases.
IMHO, the handling of Org markups (at least) by the LaTeX exporter (and
maybe others) would suffice to implement this feature (with a few tricks
to still allow sorting by makeindex). Am I right?
Regards,
Nicolas
--
Nicolas BerthierFSF Member #7975
Re: [O] [bug?] Tramp tries to open remote file links
Michael Albinus wrote: Sebastien Vauban writes: When I just open an Org file that has a link to a remote file, Tramp tries to open it, leading to errors and timeouts when offline, at least. * References Some files of interest: [[file:/m...@somewhere.org:papers/current.pdf][paper]] Is this supposed to be normal? Why does Tramp open the file? Because Tramp has been instructed so? I suppose, following the above link results in I think we did not understand each other (or did we?) because that's the thing: I don't follow the link, I just open the file which contains such a link. See http://screencast.com/t/aXoxf9D1P. (insert-file-contents /m...@somewhere.org:papers/current.pdf) This is remote file name syntax, and Tramp tries to do its job, using the default method plink. You could avoid Tramp's reaction by a link like (untested) [[file:/:/m...@somewhere.org:papers/current.pdf][paper]] Alternatively, you could choose another file name. Best regards, Seb -- Sebastien Vauban
Re: [O] [bug?] Tramp tries to open remote file links
Hello Nicolas, Nicolas Richard wrote: Sebastien Vauban writes: When I just open an Org file that has a link to a remote file, Tramp tries to open it, leading to errors and timeouts when offline, at least. It doesn't happen to me. I tried emacs -Q path/to/test.org and the file opened normally. Grepping, I see that tramp-maybe-open-connection is responsible for the tramp messages. so you could eval: (trace-function-background 'tramp-maybe-open-connection *trace* (lambda () (with-output-to-string (backtrace then reproduce and look into the buffer *trace* to see what called tramp. --8---cut here---start-8--- 1 - (tramp-maybe-open-connection [#(plink 0 5 (tramp-default t)) myself some.where.org papers/last.pdf nil]) backtrace() (let ((standard-output standard-output)) (backtrace)) (progn (let ((standard-output standard-output)) (backtrace)) (save-current-buffer (set-buffer standard-output) (buffer-string))) (unwind-protect (progn (let ((standard-output standard-output)) (backtrace)) (save-current-buffer (set-buffer standard-output) (buffer-string))) (kill-buffer standard-output)) (let ((standard-output (get-buffer-create (generate-new-buffer-name *string-output* (unwind-protect (progn (let ((standard-output standard-output)) (backtrace)) (save-current-buffer (set-buffer standard-output) (buffer-string))) (kill-buffer standard-output))) (lambda nil (let ((standard-output (get-buffer-create (generate-new-buffer-name *string-output* (unwind-protect (progn (let ((standard-output standard-output)) (backtrace)) (save-current-buffer (set-buffer standard-output) (buffer-string))) (kill-buffer standard-output() ... lots of contents... org-mode() set-auto-mode-0(org-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil t) find-file-noselect-1(#buffer test.org ~/test.org nil nil ~/test.org ((8960 3 . 4947) (24647 . 36859))) find-file-noselect(~/test.org nil nil t) (with-no-warnings (funcall ad--addoit-function filename wildcards)) (setq ad-return-value (with-no-warnings (funcall ad--addoit-function filename wildcards))) (let ((filename filename) (find-file-time-start (float-time))) (message (Info) Finding file %s... filename) (setq ad-return-value (with-no-warnings (funcall ad--addoit-function filename wildcards))) (message (Info) Found file %s in %.2f s filename (- (float-time) find-file-time-start))) (let (ad-return-value) (let ((filename filename) (find-file-time-start (float-time))) (message (Info) Finding file %s... filename) (setq ad-return-value (with-no-warnings (funcall ad--addoit-function filename wildcards))) (message (Info) Found file %s in %.2f s filename (- (float-time) find-file-time-start))) ad-return-value) ad-Advice-find-file(... find-file(~/test.org t) funcall-interactively(find-file ~/test.org t) call-interactively(find-file nil nil) command-execute(find-file) --8---cut here---end---8--- See http://screencast.com/t/pXrFeTR5J9 for a video of the full trace. And, yes, I do have an advice around find-file: --8---cut here---start-8--- (defadvice find-file (around leuven-find-file activate) Open the file named FILENAME and report time spent. (let ((filename (ad-get-arg 0)) (find-file-time-start (float-time))) (message (Info) Finding file %s... filename) ad-do-it (message (Info) Found file %s in %.2f s filename (- (float-time) find-file-time-start --8---cut here---end---8--- Though, commenting that did not solve the current problem at hand... Best regards, Seb -- Sebastien Vauban
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Is this supposed to be normal? Why does Tramp open the file? Because Tramp has been instructed so? I suppose, following the above link results in I think we did not understand each other (or did we?) because that's the thing: I don't follow the link, I just open the file which contains such a link. It doesn't for me, when I have a simple org file with just your example. I use org 8.2.6. Do you have some customization, which let org expand links per default? Does it also happen when you start emacs -Q? Or do you have some customization code in the file itself? Local variables, code snippets to be evaluated when opening the file? See http://screencast.com/t/aXoxf9D1P. This does not work for me :-( Best regards, Seb Best regards, Michael.
Re: [O] formatted index entries
Hello, Nicolas Berthier nbe...@member.fsf.org writes: IMHO, the handling of Org markups (at least) by the LaTeX exporter (and maybe others) would suffice to implement this feature (with a few tricks to still allow sorting by makeindex). Am I right? Handling Org markup in the general case is difficult because INDEX keywords, as any other keyword, are not parsed. You can force latex back-end to translate the value of the keyword for a partial support of Org markup (e.g., no macros besides those defined by default, no noweb syntax in Babel). If that sufficient, you can ask `org-latex-keyword' to first split value at exclamation marks, and send each part through `org-export-string-as' in order to get valid LaTeX markup. Regards, -- Nicolas Goaziou
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: ... lots of contents... org-mode() This means that org-mode calls things which in the end calls tramp-maybe-open-connection. But what something is is in the lots of contents part that you didn't show. Unfortunately a video isn't very searchable. Still, I spotted that org-element-context is called at some point, which in turn calls org-element-link-parser, and that's what does expand-file-name. Perhaps that would be a bug ? -- Nico.
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: ... lots of contents... Well, Tramp is invoked via (expand-file-name /myself@...). The call hierarchy is (if I haven't overseen something) expand-file-name org-element-link-parser org-element-context org-image-file-name-regexp org-display-inline-images org-mode Maybe it is worth to find out, why org-display-inline-images is invoked? Best regards, Seb Best regards, Michael.
Re: [O] [bug?] Tramp tries to open remote file links
Nicolas Richard wrote: Sebastien Vauban writes: org-mode() This means that org-mode calls things which in the end calls tramp-maybe-open-connection. But what something is is in the lots of contents part that you didn't show. Unfortunately a video isn't very searchable. Still, I spotted that org-element-context is called at some point, which in turn calls org-element-link-parser, and that's what does expand-file-name. Perhaps that would be a bug ? I found out the responsible line in my setup: --8---cut here---start-8--- ;; show inline images when loading a new Org file (setq org-startup-with-inline-images t) --8---cut here---end---8--- With it, the problem occurs; without, it does not. Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Maybe that's not a bug per se, but rather a feature that should only be enabled for specific file extensions? Best regards, Seb -- Sebastien Vauban
Re: [O] [Babel] 2 new problems with tangling
Thorsten Jolitz wrote: Sebastien Vauban writes: After an update to Org 8.2.7, I have troubles tangling files. It's possible that the error resides on my side, so the first question is: do you see the same as me? No Thanks for confirming that. Though, the problem is more complex than that on my side: I now know that the behavior is there at some point in time, but not always, not from the start. And I still wonder how to debug that... Best regards, Seb -- Sebastien Vauban
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Emacs is also able to open and display a remote PDF file. Maybe that's not a bug per se, but rather a feature that should only be enabled for specific file extensions? I wouldn't parse URI-like file names in org-mode at all. There is url-handlers.el, which shall do it proper. Best regards, Seb Best regards, Michael.
Re: [O] [bug?] Tramp tries to open remote file links
Michael Albinus wrote: Sebastien Vauban writes: Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Emacs is also able to open and display a remote PDF file. IIUC, Emacs can't display real PDF files. It only can convert them (via DocView) to PNG, one per page, in order to give a similar experience. If that's right, a PDF file on itself, be it an image, never will be displayed in Emacs, unless one adds extra machinery in Org mode. Then, should Org try to open a PDF (remote or local, same question)? Best regards, Seb -- Sebastien Vauban
Re: [O] Publishing sitemap
On 2014-06-18 03:54, Vikas Rawal wrote: When I publish my web-site using org-mode, with suitable options in my org-publish-projects-alist, I can get org-publish to create a sitemap. Is it possible to just create the sitemap without publishing the whole project? I sometimes update a single file, and just publish it using org-publish-current-file. I would like the changes (for example, date) or if a new file is being published, the file itself, reflected in the sitemap. But I can’t do it unless I publish the whole project. Is there a way to deal with this? Looking at the source for `org-publish-projects' (grep for sitemamp in ox-publish) it looks like the sitemap is generated in this line: (if sitemap-p (funcall sitemap-function project sitemap-filename)) where `sitemap-function' defaults to `org-publish-org-sitemap'. So (untested), you could try: (org-publish-org-sitemap (assoc my-project-name org-publish-project-alist) where project is the actual properties list from `org-p
Re: [O] formatted index entries
You wrote: Hello, Nicolas Berthier nbe...@member.fsf.org writes: IMHO, the handling of Org markups (at least) by the LaTeX exporter (and maybe others) would suffice to implement this feature (with a few tricks to still allow sorting by makeindex). Am I right? Handling Org markup in the general case is difficult because INDEX keywords, as any other keyword, are not parsed. You can force latex back-end to translate the value of the keyword for a partial support of Org markup (e.g., no macros besides those defined by default, no noweb syntax in Babel). If that sufficient, you can ask `org-latex-keyword' to first split value at exclamation marks, and send each part through `org-export-string-as' in order to get valid LaTeX markup. Ok thanks for the hints. I will probably hack something soon an send a patch for support of basic inline markups, in case people are interested. Regards, -- Nicolas BerthierFSF Member #7975
Re: [O] Publishing sitemap
Sorry, hit the wrong key... completed response below. On 2014-06-18 03:54, Vikas Rawal wrote: When I publish my web-site using org-mode, with suitable options in my org-publish-projects-alist, I can get org-publish to create a sitemap. Is it possible to just create the sitemap without publishing the whole project? I sometimes update a single file, and just publish it using org-publish-current-file. I would like the changes (for example, date) or if a new file is being published, the file itself, reflected in the sitemap. But I can’t do it unless I publish the whole project. Is there a way to deal with this? Looking at the source for `org-publish-projects' (grep for sitemamp in ox-publish) it looks like the sitemap is generated in this line: (if sitemap-p (funcall sitemap-function project sitemap-filename)) where `sitemap-function' defaults to `org-publish-org-sitemap'. So (untested), you could try: (org-publish-org-sitemap (assoc my-project-name org-publish-project-alist) sitemap.txt) rick
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-n...@mygooglest.com writes: Michael Albinus wrote: Sebastien Vauban writes: Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Emacs is also able to open and display a remote PDF file. IIUC, Emacs can't display real PDF files. It only can convert them (via DocView) to PNG, one per page, in order to give a similar experience. That's what I'm speaking about. And if you have a local DocView installation, it works for either remote or local files (Tramp provides a local copy of the remote file). If you want to suppress PDFs in org, you shall do it regardless of its location. Best regards, Seb Best regards, Michael.
Re: [O] Create a longtable in LaTeX from orgtbl
Hello,
I'm just using:
#+CAPTION: Table headline shown in \listoftables
#+NAME: tab:name_for_ref_to
#+ATTR_LATEX: :environment longtable :align |l|l|l|
|---+---+---|
| Col 1 | Col 2 | Col 3 |
|---+---+---|
Works fine on org-version 8.2.5h spanning the table via latex export
over several pages. LaTex \usepackage{longtable} is set in
org-export-latex-default-packages-alist per default.
Just the phrase continued on next page is hardcoded in ox-latex.el
line 2620 if you need a localized output.
Greetings,
Oliver
At 18.06.2014 um 01:11 Tak Kunihiro wrote:
Dear all,
Can you show how to create a longtable in LaTeX from orgtbl?
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org With it, the problem occurs; without, it does not. Also note that this is a problem in master only ; maint has an older version of org-display-inline-images which doesn't use org-element. Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Org Mode is not trying to display the PDF (at least not at that point). The problems occurs when parsing the buffer : org-element-link-parser uses expand-file-name to normalize the URI. Should it ? IDK. Nicolas G might have an opinion on this. -- Nico.
Re: [O] [bug?] Tramp tries to open remote file links
Michael Albinus wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Michael Albinus wrote: Sebastien Vauban writes: Though, is it normal to try to open a remote PDF file while Emacs is unable of displaying it in the buffer (unlike PNG files, IIUC)? Emacs is also able to open and display a remote PDF file. IIUC, Emacs can't display real PDF files. It only can convert them (via DocView) to PNG, one per page, in order to give a similar experience. That's what I'm speaking about. And if you have a local DocView installation, it works for either remote or local files (Tramp provides a local copy of the remote file). But DocView won't display a PDF file as an image inside a buffer of text, will it? Best regards, Seb -- Sebastien Vauban
Re: [O] Create a longtable in LaTeX from orgtbl
Oliver Kappel ngre...@gmx.net writes:
Hello,
I'm just using:
#+CAPTION: Table headline shown in \listoftables
#+NAME: tab:name_for_ref_to
#+ATTR_LATEX: :environment longtable :align |l|l|l|
|---+---+---|
| Col 1 | Col 2 | Col 3 |
|---+---+---|
Works fine on org-version 8.2.5h spanning the table via latex export
over several pages. LaTex \usepackage{longtable} is set in
org-export-latex-default-packages-alist per default.
Just the phrase continued on next page is hardcoded in ox-latex.el
line 2620 if you need a localized output.
Can you show how to create a longtable in LaTeX from orgtbl?
orgtbl is the operative word here: the OP is *not* talking about an
org file, but about a LaTeX file with a radio table. See
(info (org) Radio tables)
for details.
Nick
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
From: Stefan Monnier monn...@iro.umontreal.ca Cc: l...@yun.yagibdah.de, b...@altern.org, 17...@debbugs.gnu.org, g...@gmx.de, theonewiththeevill...@yahoo.fr Date: Wed, 18 Jun 2014 08:04:39 -0400 Ask savannah-hack...@gnu.org. Then it's not worth the trouble (since it's a temporary change that will need to be modified yet again when we release 24.4). Not sure what you have in mind, but perhaps we should rename the branch to something like 'release-branch', and then its name won't need to change with the Emacs versions.
Re: [O] 2 Org tests failing
Bastien wrote: Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Running org_test, please wait (this can take a while)... FAILED test-org-table/org-table-calc-current-TBLFM FAILED test-org-table/org-table-calc-current-TBLFM-when-stop-because-of-error I can't reproduce this. Can you run the tests manually and report the backtrace? --8---cut here---start-8--- Test test-org-table/org-table-calc-current-TBLFM condition: (file-error Opening output file No such file or directory /tmp/org_test/org-test8984aQq) FAILED 354/427 test-org-table/org-table-calc-current-TBLFM Test test-org-table/org-table-calc-current-TBLFM-when-stop-because-of-error backtrace: write-region( nil /tmp/org_test/org-test8984naw nil silent nil e byte-code(\305\30G!\203\307 !\202\310 \! \203\n P\f\203 make-temp-file(org-test) (let ((file (make-temp-file org-test)) (kill-buffer-query-function (lambda nil (let ((file (make-temp-file org-test)) (kill-buffer-qu byte-code(\306\307!q\210\310\216\311 \312\216\313\314\315\316\3 ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc byte-code(\306\307!\211\211r\310\311!q\210\312 d\313\223)L\210)\3 ert-run-test([cl-struct-ert-test test-org-table/org-table-calc-curre ert-run-or-rerun-test([cl-struct-ert--stats \\(org\\|ob\\) [[cl-st ert-run-tests(\\(org\\|ob\\) #[(event-type rest event-args) \306 ert-run-tests-batch(\\(org\\|ob\\)) ert-run-tests-batch-and-exit(\\(org\\|ob\\)) (let ((org-id-track-globally t) (org-test-selector (if org-test-sele org-test-run-batch-tests() call-interactively(org-test-run-batch-tests nil nil) command-execute(org-test-run-batch-tests) command-line-1((-L lisp/ -L testing/ -l org-test.el --e command-line() normal-top-level() --8---cut here---end---8--- These were run successfully from within Emacs itself (on Windows). I've solved the reported problem by creating the missing TMPDIR (set to /tmp/org_test) for the invocation from my Zsh (Cygwin) terminal... Though, now, I do have another test failing when testing from the shell: --8---cut here---start-8--- Test ob-shell/bash-uses-assoc-arrays backtrace: signal(ert-test-failed (((should (equal 20 cm (org-babel-execute-s ert-fail(((should (equal 20 cm (org-babel-execute-src-block))) :fo (if (unwind-protect (setq value-502 (apply fn-500 args-501)) (setq f (let (form-description-504) (if (unwind-protect (setq value-502 (app (let ((value-502 (quote ert-form-evaluation-aborted-503))) (let (for (let ((fn-500 (function equal)) (args-501 (list 20 cm (org-babel-e (save-restriction (org-babel-next-src-block 2) (let ((fn-500 (functi (progn (org-id-goto 82320a48-3409-49d7-85c9-5de1c6d3ff87) (setq to (unwind-protect (progn (org-id-goto 82320a48-3409-49d7-85c9-5de1c6d (let ((save-match-data-internal (match-data))) (unwind-protect (prog (progn (let ((save-match-data-internal (match-data))) (unwind-protec (unwind-protect (progn (let ((save-match-data-internal (match-data)) (let ((wconfig (current-window-configuration))) (unwind-protect (pro (unwind-protect (let ((wconfig (current-window-configuration))) (unw (let* ((id-location (org-id-find 82320a48-3409-49d7-85c9-5de1c6d3ff (lambda nil (let* ((id-location (org-id-find 82320a48-3409-49d7-85c byte-code(\306\307!q\210\310\216\311 \312\216\313\314\315\316\3 ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc byte-code(\306\307!\211\211r\310\311!q\210\312 d\313\223)L\210)\3 ert-run-test([cl-struct-ert-test ob-shell/bash-uses-assoc-arrays Ba ert-run-or-rerun-test([cl-struct-ert--stats \\(org\\|ob\\) [[cl-st ert-run-tests(\\(org\\|ob\\) #[(event-type rest event-args) \306 ert-run-tests-batch(\\(org\\|ob\\)) ert-run-tests-batch-and-exit(\\(org\\|ob\\)) (let ((org-id-track-globally t) (org-test-selector (if org-test-sele org-test-run-batch-tests() call-interactively(org-test-run-batch-tests nil nil) command-execute(org-test-run-batch-tests) command-line-1((-L lisp/ -L testing/ -l org-test.el --e command-line() normal-top-level() Test ob-shell/bash-uses-assoc-arrays condition: (ert-test-failed ((should (equal 20 cm (org-babel-execute-src-block))) :form (equal 20 cm nil) :value nil :explanation (different-types 20 cm nil))) FAILED 24/427 ob-shell/bash-uses-assoc-arrays --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] helm and org-refile
Here is the updated patch and config from my .emacs
(when (and (boundp 'org-completion-handler)
(require 'helm nil t))
(defun org-helm-completion-handler
(prompt collection optional predicate require-match
initial-input hist def inherit-input-method)
(helm-comp-read prompt
collection
;; the character \ is filtered out by default ;(
:fc-transformer nil
:test predicate
:must-match require-match
:initial-input initial-input
:history hist
:default def))
(setq org-completion-handler 'org-helm-completion-handler))
2014-06-17 13:01 GMT+02:00 Eric Abrahamsen e...@ericabrahamsen.net:
Thorsten Jolitz tjol...@gmail.com writes:
Eric Abrahamsen e...@ericabrahamsen.net writes:
Hi
I just started using helm, with some ambivalence. Turning on helm mode
stompled all over my emacs, but for just that reason I suppose it might
be worth trading my ido muscle memory for helm muscle memory.
helm is truly amazing and impressive, and I did not even scratch the
surface of it, but 2 things bother me:
- when using helm, I'm caught in the mini-buffer, no way to switch to
another workgroup/buffer to look up things ...
- helm is somehow too interactive, once done with it, the search/result
buffers
disappear, while I would like them to stay around sometimes
So not an answer to you question, but rather a related question - is
there a way around the problems described?
As a three-hour-old Helm user, I answer with some trepidation... I've
seen a bunch of helm-session-* stuff, and my guess is, that's what
sessions are for: leaving off helm actions, and coming back to them. I
think it's pretty clear how to come back to them, but as for the
leaving off...
From db9c5bce8c994a41e23116f8cd9d695ffad431e1 Mon Sep 17 00:00:00 2001
From: thisirs this...@gmail.com
Date: Wed, 18 Jun 2014 15:36:14 +0200
Subject: [PATCH 1/5] Add custom completion function
---
lisp/org-capture.el | 2 +-
lisp/org.el | 114 ++--
2 files changed, 58 insertions(+), 58 deletions(-)
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index c053640..81f13ca 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -1707,7 +1707,7 @@ The template may still contain \%?\ for cursor positioning.
(member char '(u U))
nil nil (list org-end-time-was-given)))
(t
- (let (org-completion-use-ido)
+ (let (org-completion-handler)
(push (org-completing-read-no-i
(concat (if prompt prompt Enter string)
(if default (concat [ default ]))
diff --git a/lisp/org.el b/lisp/org.el
index 44a4e44..17144e8 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4297,23 +4297,16 @@ This is needed for font-lock setup.)
:tag Org Completion
:group 'org)
-(defcustom org-completion-use-ido nil
- Non-nil means use ido completion wherever possible.
-Note that `ido-mode' must be active for this variable to be relevant.
-If you decide to turn this variable on, you might well want to turn off
-`org-outline-path-complete-in-steps'.
-See also `org-completion-use-iswitchb'.
+(defcustom org-completion-handler nil
+ Non-nil means use other completion handler wherever possible.
+If you decide to turn this variable on, you might well want to
+turn off `org-outline-path-complete-in-steps'.
:group 'org-completion
- :type 'boolean)
-
-(defcustom org-completion-use-iswitchb nil
- Non-nil means use iswitchb completion wherever possible.
-Note that `iswitchb-mode' must be active for this variable to be relevant.
-If you decide to turn this variable on, you might well want to turn off
-`org-outline-path-complete-in-steps'.
-Note that this variable has only an effect if `org-completion-use-ido' is nil.
- :group 'org-completion
- :type 'boolean)
+ :type '(choice
+ (const :tag Default nil)
+ (const :tag Ido ido)
+ (const :tag Iswitchb iswitchb)
+ (function :tag Other)))
(defcustom org-completion-fallback-command 'hippie-expand
The expansion command called by \\[pcomplete] in normal context.
@@ -10163,15 +10156,16 @@ Use TAB to complete link prefixes, then RET for type-specific completion support
(unwind-protect
(progn
(setq link
- (org-completing-read
- Link:
- (append
- (mapcar (lambda (x) (concat x :))
- all-prefixes)
- (mapcar 'car org-stored-links))
- nil nil nil
- 'tmphist
- (caar org-stored-links)))
+ (let (org-completion-handler)
+ (org-completing-read
+ Link:
+ (append
+ (mapcar (lambda (x) (concat x :))
+ all-prefixes)
+ (mapcar 'car org-stored-links))
+ nil nil nil
+ 'tmphist
+ (caar org-stored-links
(if (not (string-match \\S- link))
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: That's what I'm speaking about. And if you have a local DocView installation, it works for either remote or local files (Tramp provides a local copy of the remote file). But DocView won't display a PDF file as an image inside a buffer of text, will it? No, it uses an own buffer. Best regards, Seb Best regards, Michael.
Re: [O] Create a longtable in LaTeX from orgtbl
Hello, I'm just using: #+CAPTION: Table Heading shown in listoftables #+NAME: tab:name_for_ref_to #+ATTR_LATEX: :environment longtable :align |l|l|l| |---+---+---| | Col 1 | Col 2 | Col 3 | |---+---+---| Works fine on org-version 8.2.5h spanning the table via latex export over several pages. Using LaTex package \longtable is set in org-export-latex-default-packages-alist per default. Just the phrase continued on next page is hardcoded in ox-latex.el line 2620 if you need a localized output. Greetings, Oliver At 18.06.2014 um 01:11 Tak Kunihiro wrote: Dear all, Can you show how to create a longtable in LaTeX from orgtbl?
Re: [O] [bug?] Tramp tries to open remote file links
Michael Albinus wrote: Sebastien Vauban writes: That's what I'm speaking about. And if you have a local DocView installation, it works for either remote or local files (Tramp provides a local copy of the remote file). But DocView won't display a PDF file as an image inside a buffer of text, will it? No, it uses an own buffer. OK, so we do agree that trying to open a PDF file in the context of *inline images*[1] does not make much sense, right? Best regards, Seb [1] (setq org-startup-with-inline-images t) -- Sebastien Vauban
Re: [O] [bug?] Tramp tries to open remote file links
Sebastien Vauban sva-n...@mygooglest.com writes: Michael Albinus wrote: Sebastien Vauban writes: That's what I'm speaking about. And if you have a local DocView installation, it works for either remote or local files (Tramp provides a local copy of the remote file). But DocView won't display a PDF file as an image inside a buffer of text, will it? No, it uses an own buffer. OK, so we do agree that trying to open a PDF file in the context of *inline images*[1] does not make much sense, right? Are you trying to say that the org code for inline images should figure out that such a link should *not* be inlined because it would open a non-image file? If so, how would you define non-image file? And would that definition vary depending on the capabilities of one's emacs (e.g. maybe my emacs can display PNG files but not GIF files)? Nick
Re: [O] [bug?] Tramp tries to open remote file links
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Org Mode is not trying to display the PDF (at least not at that point). The problems occurs when parsing the buffer : org-element-link-parser uses expand-file-name to normalize the URI. Should it ? IDK. Nicolas G might have an opinion on this. I guess the only way to know is to remove `expand-file-name'. We'll see if someone complains. Done in master. Regards, -- Nicolas Goaziou
Re: [O] Create a longtable in LaTeX from orgtbl
Am 18.06.2014 um 16:33 schrieb Nick Dokos:
Oliver Kappel ngre...@gmx.net writes:
I'm just using:
#+CAPTION: Table headline shown in \listoftables
#+NAME: tab:name_for_ref_to
#+ATTR_LATEX: :environment longtable :align |l|l|l|
|---+---+---|
| Col 1 | Col 2 | Col 3 |
|---+---+---|
Can you show how to create a longtable in LaTeX from orgtbl?
orgtbl is the operative word here: the OP is *not* talking about an
org file, but about a LaTeX file with a radio table. See
(info (org) Radio tables)
for details.
Nick
Ah, I've missed that and sorry for double posting.
Isn't pretty, but working:
#+BEGIN_SRC LaTeX
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{longtable}
\usepackage{comment}
\begin{document}
\begin{longtable}{rll}
% BEGIN RECEIVE ORGTBL my-long-table
% END RECEIVE ORGTBL my-long-table
\end{longtable}
%
\begin{comment}
#+ORGTBL: SEND my-long-table orgtbl-to-latex :splice t :escape t
|-+-+|
| date| session | remark |
|-+-+|
| \endhead 2014-06-18 | s140618 ||
\end{comment}
%
\end{document}
#+END_SRC
Regards,
Oliver
Re: [O] Discussion request: 15m tangle time, details follow
Hi Sebastien, 2014ko ekainak 18an, Sebastien Vauban-ek idatzi zuen: Hi Aaron, Aaron Ecay wrote: [...] babel needs to fetch 30 properties per source block. Indeed, this is marked “deprecated” in the source, in favor of a system where there is only one header arg. This has been marked deprecated for almost exactly a year in the code (Achim’s commit 90b16870 of 2013-06-23), but I don’t know of any prominent announcement of the deprecation. I neither was aware of such a deprecation. Are you talking of the comment in function `org-babel-params-from-properties' (in ob-core.el)? Thought, I can't parse it yet the way you do -- without understanding much more of that code, as the comments differ in at point of definition vs at point of call: ;; DEPRECATED header arguments specified as separate property at ;; point of definition ;; header arguments specified with the header-args property at ;; point of call That also differs between the two methods. , | | * foo | :PROPERTIES:... | | #+name: xyz | #+begin_src | ... | #+end_src | | * bar | :PROPERTIES:... | | #+call: xyz() ` The current code looks for individual header arg properties at foo, but for the property header-args at bar (for the #+call line) What you're talking about is for specifying header arguments in a subtree, anyway always at the same point: [...] You’d then have to update your file: :PROPERTIES: :exports: none :tangle: no :END: becomes :PROPERTIES: :header-args: :exports none :tangle no :END: The new system is also a bit inferior, in that it doesn’t allow header arg inheritance as easily. So with the one-prop-per-arg system the following works as expected: * foo :PROPERTIES: :exports: none :END: ** bar :PROPERTIES: :tangle: no :END: (src block here) On the other hand, in the new system there’s no way to specify some header args at foo and some at bar; the lowest header-args property wins. (At least as far as I can see) Maybe the + mechanism for concatenating property strings would help here? No, org-entry-get-with-inheritance will not continue climbing the tree once it finds one instance of the property in question, as demonstrated here: , | * foo | :PROPERTIES: | :quux+:abc | :END: | ** bar |:PROPERTIES: |:quux+:foo |:quux+:bar |:END: | | #+BEGIN_SRC emacs-lisp | (org-entry-get nil quux t) | #+END_SRC | | #+RESULTS: | : foo bar ` -- Aaron Ecay
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Not sure what you have in mind, but perhaps we should rename the branch to something like 'release-branch', and then its name won't need to change with the Emacs versions. It's not just the name: after the release we won't ask people to track the release-branch. Maybe we could use a branch alias which we can switch between trunk and release-branch. With Bzr this could be implemented as a symlink (tho I'm not sure if bzr's transport protocol lets us create symlinks). With Git, I'm not sure if it's supported natively or would have to be simulated with symlinks (which we'd have to ask savannah-hack...@gnu.org to createchange). Stefan
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Date: Wed, 18 Jun 2014 20:52:05 +0200 From: Gregor Zattler g...@gmx.de Cc: 17...@debbugs.gnu.org Hi Stefan, * Stefan Monnier monn...@iro.umontreal.ca [07. Jun. 2014]: BTW, I would also point out that people who do not actively develop Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather than the trunk (24.4.50), so as to help us fix problems before the 24.4 release. I'd love to. But the emacs-24 branch gives emacs version 24.4.50, No, the emacs-24 branch's version is 24.3.91. If you have 24.4.50, you've got the trunk there, not the emacs-24 branch. How did you checkout what you think is the emacs-24 branch? I'm a novice to version control, but I think a release-branch (as Eli mentiones in mid:83y4wuth7s@gnu.org) would be great and I think it's doable with a normal branch!? I was just talking about the name of the branch. Your problems are deeper than that.
Re: [O] navigation broken in recent maint
Samuel Wales samologist at gmail.com writes: quick and dirty bug report. recent org maint. 1: jumping from magit (maint) to org using RET always goes to the wrong location now. i don't know that this is org's fault. i have seen it happen once before, which is when i tried longlines-mode and similar modes. i think it was only in org, but i am not sure. was there a change in org visibility? 2: id links always go to the wrong location now. they jump someplace near the link. dunno if 1 and 2 are related. i'd guess not but they started in the same snapshot. can't do ecm at this time. Here is one I've adapted from the navigation broken - occur, org-babel-goto-named-src-block, etc fail thread: http://article.gmane.org/gmane.emacs.orgmode/87575 Before executing the src block in what follows the custom_id links work. After executing the src block the links that are far from their target fail. Anyone who wants to dig into this should see Nicolas Richard's reply at the end of that thread: http://article.gmane.org/gmane.emacs.orgmode/87598 HTH, Chuck == * headline A :PROPERTIES: :CUSTOM_ID: idA :END: [[#idB]] #+NAME: AAA #+BEGIN_SRC x #+END_SRC #+NAME: filler #+BEGIN_SRC emacs-lisp :results output (let ((i ?a)) (while ( i ?z) (princ (format * %s\n\n\n#+NAME: %s\n\n (char-to-string i) (char-to-string i))) (setq i (1+ i #+END_SRC [[#idA]] [[#idB]] #+RESULTS: filler [[#idA]] [[#idB]] * headline B :PROPERTIES: :CUSTOM_ID: idB :END: [[#idA]] [[#idB]] #+NAME: BBB #+BEGIN_SRC x #+END_SRC
Re: [O] babel python example not reproducible
Shiyuan gshy2...@gmail.com writes: Hi all, I found a solution to fix the echo problem of the emacs python shell: http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines That is, in the Interior Python buffer, do M-: (setq comint-process-echoes t) ;; or nil Now, if I enter command directly in the interior python buffer, the command is not echoed and this is what I want. However, When I evaluate the python src code block in org-mode(by `C-c C-c`), the problem persists. I notice every time I evaluate the block, I see 'org_babel_python_eoe' in the interior python buffer. I stumbled on a very strange emacs behavior. When I fiddled around, at some point, I produced the correct answer as the manual. I thought I got the right setup, but when I saved everything and restarted emacs, problem persists. Will it be a sign of anything wrong? What's even stranger is that: the evaluation for the first time gives different results from the evaluation for the second time, on exactly the same src_block: This is what I got when I evaluation the code block for the first time: - #+BEGIN_SRC python :results output :session foo x=100 print hello 2 print bye #+END_SRC #+RESULTS: #+begin_example x=100 print hello hello 2 2 print bye bye #+end_example --- --- The following is what I got when I evaluate the same block again: #+BEGIN_SRC python :results output :session foo x=100 print hello 2 print bye #+END_SRC #+RESULTS: : x=100 : print hello : hello : 2 : 2 : print bye : bye : : Notice that the prompt symbol is in the result for the first evaluation but not in the second evaluation. This issue has been raised before, it is a quirk of how the python session starts up. I think we've done what we can to handle this on the Org-mode side, I'd ask for a fix on the python.el maintainers. Also the result is not embedded in the #+being_example/#+end_example for the second evaluation. Yes, short examples are examplized with : instead of the heavier weight example blocks. The results are functionally equivalent, but you can customize the size at which different methods are used by changing the `org-babel-min-lines-for-block-output' variable. I want to hunt down the problem. Any hints/helps is greatly appreciated. Hope this helps. Sadly Emacs python support is sub-par and as a consumer, Org-mode python code blocks suffer. Best, Shiyuan On Mon, Jun 16, 2014 at 9:12 AM, Doyley, Marvin mdoy...@ur.rochester.edu wrote: Hi Eric, Thanks for showing me the smart way of doing this. cheers, M -- -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
Re: [O] babel python example not reproducible
Hi Guys,
please permit a comment after some times - it's just not to create
heroes :)
IMHO the complexity orb-babel took by creating its own slots for
symbols like function names, variables etc. is not to handle reliably
across the languages.
I don't understand what you mean by the above.
A net and simple way out would be just to employ commands delivered by
existing Emacs modes on org-source sections. Inserting the results
might be provided by a hook.
This is what Org-mode does when possible, and this is why some language
modes are both much simpler and much more reliable than others, e.g.,
because of Emacs' excellent support for common lisp ob-lisp.el is both
shorter and provides higher quality support than ob-python.el.
$ wc -l lisp/ob-{lisp,python}.el
111 lisp/ob-lisp.el
346 lisp/ob-python.el
If I've miss-understood the above please clarify.
Thanks,
Eric
Cheers,
Andreas
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Eli Zaretskii e...@gnu.org writes: From: lee l...@yun.yagibdah.de Date: Tue, 17 Jun 2014 19:15:33 +0200 Cc: Bastien b...@altern.org, 17...@debbugs.gnu.org, g...@gmx.de, Nicolas Richard theonewiththeevill...@yahoo.fr Having cloned as described on http://savannah.gnu.org/git/?group=emacs with 'git clone git://git.savannah.gnu.org/emacs.git', I'm getting the master branch. Master seems to be identical with trunk. Perhaps add some advise to the web page so ppl pull the emacs24 branch instead? It's git, right? The one that has git checkout BRANCH and stuff? Yes, I pulled from the git repo as described on the website. Next time I update, I guess I can pull the emacs24 branch and use that. -- Knowledge is volatile and fluid. Software is power.
Re: [O] 2 Org tests failing
Sebastien Vauban writes: I've solved the reported problem by creating the missing TMPDIR (set to /tmp/org_test) for the invocation from my Zsh (Cygwin) terminal... The first thing the build system does before testing is install -m 755 -d /tmp/tmp-orgtest so you either pick up the wrong install command via path or have otherwise misconfigured MKDIR in local.mk. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Section of Org manual on images in latex export
Hello, Christopher Witte ch...@witte.net.au writes: After quite a bit of mucking around and finally resorting to checking the source code, I worked out how to wrap an image in a figure environment without a caption. The final solution #+ATTR_LATEX: :float figure Actually, it is #+ATTR_LATEX: :float t was trivial, but the manual wasn't too helpful on this particular subject. According to the manual, the first described value for :float is: − ‘t’: if you want to use the standard ‘figure’ environment. It is used by default if you provide a caption to the image. You can also ask Org to export an image as a float without specifying caption by setting the :float attribute. should be change to: You can also ask Org to export an image as a float without specifying a caption by setting the :float attribute *to figure*. That's not quite true. It can be anything but nil, depending on what you want (e.g., :float wrap). Also a summary of the the attributes and their valid values, as is done for Latex tables would be useful. Patches welcome. Regards, -- Nicolas Goaziou
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Hi Stefan, * Stefan Monnier monn...@iro.umontreal.ca [07. Jun. 2014]: BTW, I would also point out that people who do not actively develop Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather than the trunk (24.4.50), so as to help us fix problems before the 24.4 release. I'd love to. But the emacs-24 branch gives emacs version 24.4.50, there is a tag emacs-24.3.91 tough, which is from 2014-05-11, whilst the emacs-24 branch ATM has commits from 2014-06-07. I'm a novice to version control, but I think a release-branch (as Eli mentiones in mid:83y4wuth7s@gnu.org) would be great and I think it's doable with a normal branch!? Ciao; Gregor
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
Hi Eli, * Eli Zaretskii e...@gnu.org [18. Jun. 2014]: * Stefan Monnier monn...@iro.umontreal.ca [07. Jun. 2014]: BTW, I would also point out that people who do not actively develop Emacs should ideally use the emacs-24 (i.e. 24.3.9x) branch now rather than the trunk (24.4.50), so as to help us fix problems before the 24.4 release. I'd love to. But the emacs-24 branch gives emacs version 24.4.50, No, the emacs-24 branch's version is 24.3.91. If you have 24.4.50, you've got the trunk there, not the emacs-24 branch. How did you checkout what you think is the emacs-24 branch? like so: $ cd ~/src/emacs/; rm -rf * ; git co -f emacs-24 Checking out files: 100% (3525/3525), done. Previous HEAD position was 0f0917d... Regenerate AUTHORS and ldefs-boot.el Switched to branch 'emacs-24' then I do $ ./autogen.sh ./configure --prefix=/usr/local/stow/emacs-snapshot --enable-checking --enable-link-time-optimization --without-toolkit-scroll-bars --with-x-toolkit=gtk3 when I now do (long output ahead) $ rgrep -- 24\.4\.50 configure.ac:AC_INIT(GNU Emacs, 24.4.50, bug-gnu-em...@gnu.org) lib/Makefile:PACKAGE_STRING = GNU Emacs 24.4.50 lib/Makefile:PACKAGE_VERSION = 24.4.50 lib/Makefile:VERSION = 24.4.50 lib/Makefile:version = 24.4.50 doc/misc/Makefile:version=24.4.50 doc/lispintro/Makefile:version=24.4.50 doc/lispref/Makefile:version=24.4.50 doc/man/emacs.1:.TH EMACS 1 2007 April 13 GNU Emacs 24.4.50 doc/emacs/Makefile:version=24.4.50 doc/emacs/emacsver.texi:@set EMACSVER 24.4.50 ChangeLog: * configure.ac: Bump version to 24.4.50. README:This directory tree holds version 24.4.50 of GNU Emacs, the extensible, nt/makefile.w32-in:VERSION = 24.4.50 nt/Makefile:version=24.4.50 nt/config.nt:#define VERSION 24.4.50 configure:# Generated by GNU Autoconf 2.69 for GNU Emacs 24.4.50. configure:PACKAGE_VERSION='24.4.50' configure:PACKAGE_STRING='GNU Emacs 24.4.50' configure:\`configure' configures GNU Emacs 24.4.50 to adapt to many kinds of systems. configure: short | recursive ) echo Configuration of GNU Emacs 24.4.50:;; configure:GNU Emacs configure 24.4.50 configure:It was created by GNU Emacs $as_me 24.4.50, which was configure: VERSION='24.4.50' configure:This file was extended by GNU Emacs $as_me 24.4.50, which was configure:GNU Emacs config.status 24.4.50 Makefile:version=24.4.50 autom4te.cache/traces.1:m4trace:configure.ac:26: -1- AC_INIT([GNU Emacs], [24.4.50], [bug-gnu-em...@gnu.org]) autom4te.cache/output.1:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 24.4.50. autom4te.cache/output.1:PACKAGE_VERSION='24.4.50' autom4te.cache/output.1:PACKAGE_STRING='GNU Emacs 24.4.50' autom4te.cache/output.1:\`configure' configures GNU Emacs 24.4.50 to adapt to many kinds of systems. autom4te.cache/output.1: short | recursive ) echo Configuration of GNU Emacs 24.4.50:;; autom4te.cache/output.1:GNU Emacs configure 24.4.50 autom4te.cache/output.1:It was created by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.1: VERSION='24.4.50' autom4te.cache/output.1:This file was extended by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.1:GNU Emacs config.status 24.4.50 autom4te.cache/output.2:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 24.4.50. autom4te.cache/output.2:PACKAGE_VERSION='24.4.50' autom4te.cache/output.2:PACKAGE_STRING='GNU Emacs 24.4.50' autom4te.cache/output.2:\`configure' configures GNU Emacs 24.4.50 to adapt to many kinds of systems. autom4te.cache/output.2: short | recursive ) echo Configuration of GNU Emacs 24.4.50:;; autom4te.cache/output.2:GNU Emacs configure 24.4.50 autom4te.cache/output.2:It was created by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.2: VERSION='24.4.50' autom4te.cache/output.2:This file was extended by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.2:GNU Emacs config.status 24.4.50 autom4te.cache/traces.2:m4trace:configure.ac:26: -1- AC_INIT([GNU Emacs], [24.4.50], [bug-gnu-em...@gnu.org]) autom4te.cache/output.0:@%:@ Generated by GNU Autoconf 2.69 for GNU Emacs 24.4.50. autom4te.cache/output.0:PACKAGE_VERSION='24.4.50' autom4te.cache/output.0:PACKAGE_STRING='GNU Emacs 24.4.50' autom4te.cache/output.0:\`configure' configures GNU Emacs 24.4.50 to adapt to many kinds of systems. autom4te.cache/output.0: short | recursive ) echo Configuration of GNU Emacs 24.4.50:;; autom4te.cache/output.0:GNU Emacs configure 24.4.50 autom4te.cache/output.0:It was created by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.0: VERSION='24.4.50' autom4te.cache/output.0:This file was extended by GNU Emacs $as_me 24.4.50, which was autom4te.cache/output.0:GNU Emacs config.status 24.4.50 lib-src/Makefile:version=24.4.50 msdos/sed2v2.inp:/^#undef VERSION/s/^.*$/#define VERSION 24.4.50/ config.log:It was created by GNU Emacs configure 24.4.50, which was config.log:| #define PACKAGE_VERSION 24.4.50 config.log:| #define PACKAGE_STRING GNU Emacs 24.4.50 config.log:| #define VERSION 24.4.50
[O] Loss of Fontification partway through file
Hello List, I just converted my init file to an init.org to load with babel. I prefer to view the source blocks with font lock (org-src-fontify-natively). My problem is that certain parts of the file don't show the fontification. I had a lot of trouble narrowing down my init to provide a good MWE/recipe for the behavior, but I can reproduce it with: $ emacs -q test.org M-: (package-initialize) RET M-: (setq org-src-fontify-natively t) RET The src block in the level 2 headings of the third heading below doesn't fontify for me. Minor changes (even changing one of the commented load paths) fix the issue, but not in any way that seems predictable to me. If I move headings around in init.org, the exact location where fontification stops varies, but once it stops, all remaining src blocks are un-fontified. Am I violating some sort of convention that is hanging up the fontification code? Thanks for any tips, Jake test.org- * Heading with some add-to-list's (some commented) #+BEGIN_SRC emacs-lisp :tangle yes (add-to-list 'foo bar) ;; (add-to-list 'load-path ~/.emacs.d/jake-lisp/moos-mode/trunk) ;; (add-to-list 'load-path ~/.emacs.d/jake-lisp/moos-mode/devel) (add-to-list 'load-path /home/jacob/.emacs.d/jake-lisp/ai-moos/devel) #+END_SRC * Heading with Note Note: Loading and initializing of package is done in .emacs to ensure that the newer version of org is loaded from elpa in favor of the version distributed with emacs #+BEGIN_SRC emacs-lisp :tangle yes (add-to-list 'package-archives '(marmalade . http://marmalade-repo.org/packages/;)) #+END_SRC * Offending section ** Offending subsection #+BEGIN_SRC emacs-lisp :tangle yes (message foobar) #+END_SRC - org-version is a variable defined in `org.el'. Its value is 8.2.6 emacs-version is a variable defined in `C source code'. Its value is 24.3.1
Re: [O] navigation broken in recent maint
thanks charles. i hope that others can repro. ido refile is also broken, but intermittent. often it just goes to some apparently random place in the same file. i am going to revert to an earlier version of org until this can be fixed.
Re: [O] navigation broken in recent maint
your mce reliably reproduces the magit bug for me, although i have not tried with -q yet. in magit place point on headline b.
Re: [O] Discussion request: 15m tangle time, details follow
On Tue, Jun 17, 2014 at 9:41 PM, Aaron Ecay aarone...@gmail.com wrote: Here you mean time to tangle, correct? Yes, thank you for digging in.
Re: [O] Discussion request: 15m tangle time, details follow
On Wed, Jun 18, 2014 at 3:20 AM, Andreas Leha andreas.l...@med.uni-goettingen.de wrote: Just one quick idea: Have you tried [fn:1] (setq org-babel-use-quick-and-dirty-noweb-expansion t) This can lead to dramatic speedups in my experience. I have not because I am utilizing property inheritance; it makes it really, really pleasant to work with the document.
Re: [O] Discussion request: 15m tangle time, details follow
On Wed, Jun 18, 2014 at 3:18 AM, Thorsten Jolitz tjol...@gmail.com wrote: Grant Rettke g...@wisdomandwonder.com writes: The average build takes 15m. Which file do you mean - TC3F.org? Thats some 4400 lines, thus not _that_ big really. I once used a giant init.el copied from the web that had some 8000 lines (now I'm back to 2500 again ...). Yes. Thank you for digging in. Thanks for the tip, I had not learned out-org yet.
Re: [O] Discussion request: 15m tangle time, details follow
I still want to be using org,, so my plan for now then is to write a pre-processing script for before org-babel-tangle is run that: 1. Checks each headline 2. Checks if there is a source block 3. If that source block doesn't have a noweb-ref name, and there is another source block under that headline, then merge it with the next source block of the same nature in that heading. That is off the top of my head, and I will try it by hand, first and see if it tangles the same result. Thoughts?
Re: [O] How do you capture the intent never to tangle or weave a headline or its children?
Understood, and thank you. Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Sun, Jun 15, 2014 at 10:29 PM, Charles Berry ccbe...@ucsd.edu wrote: Grant Rettke gcr at wisdomandwonder.com writes: Good evening, For both performance and cognitive reasons, sometimes I specifically never want to tangle or weave a headline or any of its children. I still value it though, so it belongs in that document, and it wouldn't make sense for it to be linked as an external document. For performance reasons, I suspect that it would speed up tangling, but I need to verify this. Thus far I just add something like this, so at least it is obvious to *me* what is my intent: # INTENT: never weave or tangle this headline or its children :PROPERTIES: :exports: none :tangle: no :END: You want this: http://orgmode.org/manual/Header-arguments-in-Org-mode-properties.html#Header-arguments-in-Org-mode-properties i.e. :header-args: :exports none :tangle no HTH, Chuck
Re: [O] A simple org tangle and weave makefile
I see. Thank you. Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Thu, Jun 12, 2014 at 2:54 PM, Eric Schulte schulte.e...@gmail.com wrote: Grant Rettke g...@wisdomandwonder.com writes: Hi, My goals was to have a simple makefile to tangle and weave a document; so org-mk was out of scope. Just wondering; how could I have done it better? ## INIT=.emacs.el $(INIT): TC3F.org time emacs --batch --no-init-file --load .org-mode.emacs.el --find-file TC3F.org --funcall org-babel-tangle --kill TC3F.html: $(INIT) time emacs --batch --no-init-file --load .org-mode.emacs.el --find-file TC3F.org --funcall org-html-export-to-html --kill clean: rm $(INIT) rm TC3F.html ## Kind regards, I don't know if this is better, but its closer to what I use locally. Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --ThompsonH -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
[O] bug#17724: 24.4.50; regression: error `recenter'ing a window that does not display current-buffer. when opening org-mode file
From: lee l...@yun.yagibdah.de Cc: monn...@iro.umontreal.ca, b...@altern.org, 17...@debbugs.gnu.org, g...@gmx.de, theonewiththeevill...@yahoo.fr Date: Wed, 18 Jun 2014 13:10:19 +0200 It's git, right? The one that has git checkout BRANCH and stuff? Yes, I pulled from the git repo as described on the website. Next time I update, I guess I can pull the emacs24 branch and use that. If you cloned the repository normally, you already have emacs-24, you just need to checkout it.
Re: [O] babel python example not reproducible
On 18.06.2014 15:59, Eric Schulte wrote: Shiyuan gshy2...@gmail.com writes: Hi all, I found a solution to fix the echo problem of the emacs python shell: http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines That is, in the Interior Python buffer, do M-: (setq comint-process-echoes t) ;; or nil Now, if I enter command directly in the interior python buffer, the command is not echoed and this is what I want. However, When I evaluate the python src code block in org-mode(by `C-c C-c`), the problem persists. I notice every time I evaluate the block, I see 'org_babel_python_eoe' in the interior python buffer. I stumbled on a very strange emacs behavior. When I fiddled around, at some point, I produced the correct answer as the manual. I thought I got the right setup, but when I saved everything and restarted emacs, problem persists. Will it be a sign of anything wrong? What's even stranger is that: the evaluation for the first time gives different results from the evaluation for the second time, on exactly the same src_block: This is what I got when I evaluation the code block for the first time: - #+BEGIN_SRC python :results output :session foo x=100 print hello 2 print bye #+END_SRC #+RESULTS: #+begin_example x=100 print hello hello 2 2 print bye bye #+end_example --- --- The following is what I got when I evaluate the same block again: #+BEGIN_SRC python :results output :session foo x=100 print hello 2 print bye #+END_SRC #+RESULTS: : x=100 : print hello : hello : 2 : 2 : print bye : bye : : Notice that the prompt symbol is in the result for the first evaluation but not in the second evaluation. This issue has been raised before, it is a quirk of how the python session starts up. I think we've done what we can to handle this on the Org-mode side, I'd ask for a fix on the python.el maintainers. The prompts appear as respond from Python-process when setup-code is sent at the beginning. org-babel already knows how to fetch only the results from last prompt. Probably separating a first run-python/py-shell from execute-process would do it. Best, Andreas
