Re: [O] Repeated teaching classes and stopping date
Dear all, James Harkins writes: > Rasmus gmx.us> writes: > >> Also check >> `org-clone-subtree-with-time-shift'. > > FWIW, I always create a separate subtree, with a single timestamp, for every > class session. Advantages: > > - Individual status for each session: DONE, POSTPONED or CANCELED. > > - If a single class in a series needs to be rescheduled, it's easy. > > - I can add notes under the subtree, to plan for the session or note > important things that happened in class. So then my calendar is not just a > calendar -- it also helps with content organization. (That IMO is the whole > point of org-mode: it's not just a calendar!) I like the idea of `org-clone-subtree-with-time-shift', but wouldn't it make the parsing of the files slower? I admit that in the example, this would not have a big impact since there would be only 9 entries. Nevertheless, I wonder if this can be considered as a general solution. In my org files that sum up to 51425 lines (not taking into account the archives), the creation of the agendas takes minutes to generate. There are a lot of repeated items with final date¹. I cannot imagine the time it would take if I would use `org-clone-subtree-with-time-shift'... My two cents :-) ¹ Like in the case mentioned by Xavier -- Konubinix GPG Key: 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A pgpfJmOtqwxXD.pgp Description: PGP signature
[O] [whishlist] unified export template / property keys for presentations
Hello, orgmode has a nice interface for specifying things like frames, blocks, quotes etc with org-beamer-mode and the special access keys (C-c C-b). Although these serve only latex-beamer - and since orgmode has a lot of non-beamer export options for presentations - I was wondering if we could have something like this: 1) a function 'org-insert-presentation-template' that allows for different basic options like type of transition, default heading depth for slides, toc and so on. 2) a special minor mode 'org-presentation-mode' where more options can be used by providing keybindings for inserting properties. The main idea behind this is that it is perfectly fine for most presentations to define at what heading level slides are, what font and what colors org should use. All these things are basically similar in all export backends for presentations and could therefore be handled by the same set of options. I guess that 80% of what the style and structure of a presentation consists of would be covered by this, regardless of whether it is going to be a beamer, s5, or reveal.js presentation. This would make creating presentations a lot more user friendly. Because it should not really matter whether or not I understand all the latex markup that the export to beamer has to handle or the the html when using another presentation export backend - for producing a quick and still nice-looking presentation from an org-file. What do you think?
Re: [O] pdf images in html export
On Wednesday, 12 Nov 2014 at 21:32, Andreas Leha wrote: > Hi John, > > John Hendy writes: [...] >> If the names are always the same, could you just sed or replace-regexp >> all *.pdf for *.png? > > I could. And I would need to do the conversion manually as well. > > But I still want the pdfs to go into the LaTeX export. If the conversions have been done, a simple function that changes all occurrences of [[file:xxx.pdf] to [[file:xxx.png] on export can be written and added to org-export-before-processing-hook. This function could also, if you're adventurous, do the conversion if the png isn't there already... That hook passes the export backend so that you will know if you are exporting to LaTeX or HTML. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-558-g83d8a2
Re: [O] Repeated teaching classes and stopping date
On Thursday, 13 Nov 2014 at 09:26, Samuel Loury wrote: [...] > I like the idea of `org-clone-subtree-with-time-shift', but wouldn't it > make the parsing of the files slower? Maybe but O(n)... I doubt it would make much difference in practice compared with parsing a complex date structure. > I admit that in the example, this would not have a big impact since > there would be only 9 entries. Nevertheless, I wonder if this can be > considered as a general solution. It's a solution that works well for the reasons given by others. I use it for all of my lectures and it turns out better than a single repeat directive would because you can annotate each instance separately, not to mention being able to easily remove lectures that might be cancelled or change ones that may have a different location or time. Etc. > In my org files that sum up to 51425 lines (not taking into account the > archives), the creation of the agendas takes minutes to generate. There Minutes! What version of org and what kind of system? I have >35k lines in my org agenda files and generating an agenda on a 5 year old system takes seconds. On my wee Pandora, it takes a minute or so but this is a very slow system with slow SD cards... -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.1, Org release_8.3beta-558-g83d8a2
Re: [O] Repeated teaching classes and stopping date
Eric S Fraga writes: > On Thursday, 13 Nov 2014 at 09:26, Samuel Loury wrote: [...] >> In my org files that sum up to 51425 lines (not taking into account the >> archives), the creation of the agendas takes minutes to generate. There > Minutes! What version of org and what kind of system? Org version 8.2.7c. The system is a Samsung galaxy S3. --8<---cut here---start->8--- $ cat /proc/cpuinfo Processor : ARMv7 Processor rev 0 (v7l) processor : 0 BogoMIPS: 1592.52 processor : 1 BogoMIPS: 2189.72 processor : 2 BogoMIPS: 2189.72 processor : 3 BogoMIPS: 1592.52 Features: swp half thumb fastmult vfp edsp neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part: 0xc09 CPU revision: 0 Chip revision : 0011 Hardware: SMDK4x12 Revision: 000c Serial : cfca7043323016d7 --8<---cut here---end--->8--- With a RAM of 800Mo. > I have >35k lines in my org agenda files and generating an agenda on a >5 > year old system takes seconds. On my wee Pandora, it takes a minute or > so but this is a very slow system with slow SD cards... I don't understand how the SD card speed is to be taken into account since org mode by default loads into emacs (and then in memory) all the org files prior to computing the agenda. -- Konubinix GPG Key: 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A pgpNsyfoXxwMy.pgp Description: PGP signature
[O] Problem with org-agenda-clockreport-mode and tag-filtered view in agenda
Dear all, Starting from around two weeks ago, I have a problem with org-agenda-clockreport-mode. In agenda view, calling org-agenda-clockreport-mode with the prefix C-u (so C-u R) used to give me a summary of the hours excluding the task which had been filtered out by the tag filter (called with / and tags). Now this feature seems to have disappeared: on a filtered by tag list, the clock report table called with R alone or with C-u R gives exactly the same results. This means that C-u R lists also all the tasks which have been hidden by the tag filtering. This happens on the following configuration: - Windows 7 32-bit - Emacs 24.3.1 for Windows (GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN) - Org-mode 8.2.10 (Org-mode version 8.2.10 (8.2.10-16-g4c37a9-elpa @ c:/Users/BEBI/AppData/Roaming/.emacs.d/elpa/org-20141110/)) I also use the same configuration on a Linux system, and I had managed to temporarily solve the problem uninstalling the latest (at the time) version of org-mode and using the old version bundled with emacs. I don't have the info on the emacs and org-mode version of the linux system now, but if required I can look for it later. Has anyone experiences something similar? Did the command change? Am I missing something? Thank you very much, best regards. Benoît
[O] org-caldav problem; used to work
Hi!
Finally I want to put my org-calendar into owncloud for easy access
everywhere.
I tried before, but had difficulties with UIDs maybe a year before
and gave up.
Nevertheless: Last time I tried the basics were easy and I had
a script working for small files. Now I get an error and am running out
of steam after a few hours of trying:
==
testtodo.org looks like this:
* Test1
SCHEDULED: <2014-11-20 Mi 19:00-20:00>
==
If now I enter M-x org-caldav-sync
I get the following in *Messages*
Contacting host: CORPORATESERVER:443
auth-source-search: found 1 results (max 1) matching (:max 1 :host
"CORPORATESERVER:443" :port "https")
auth-source-search: found 1 CACHED results matching (:max 1 :host
"CORPORATESERVER:443" :port "https")
Contacting host: CORPORATESERVER:443
org-check-agenda-file: Wrong type argument: stringp, nil
gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly
terminated.
And in *org-caldav-debug*
== Started sync.
Check connection for
https://cloud.unibw-hamburg.de/owncloud/remote.php/caldav/calendars/steuer/testtodo/.
Generating ICS file /tmp/org-caldav-70960sU.
The ICS file is empty.
My minimal init.el used for these experiments:
Org Mode ;;;
(setq load-path (cons "~/.emacs.d/org-mode/lisp" load-path))
(setq load-path (cons "~/.emacs.d/org-mode/contrib/lisp" load-path))
(require 'org)
;; The following lines are always needed. Choose your own keys.
(add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
(add-hook 'org-mode-hook 'turn-on-font-lock)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
(setq org-directory "~/Test/Orgmodetest/CaldavKalender")
(setq org-default-notes-file (concat org-directory "/inbox.org"))
(define-key global-map "\C-cc" 'org-capture)
(setq org-agenda-files
(quote("~/Test/Orgmodetest/CaldavKalender/testtodo.org")))
(require 'auth-source)
(setq auth-sources '((:source "~/.netrc" :host t :protocol t)))
(setq auth-source-debug t)
; for org-caldav
;;(setq org-icalendar-include-todo t)
;;(setq org-icalendar-use-deadline '(todo-due))
;;(setq org-icalendar-use-scheduled '(event-if-not-todo))
(setq org-icalendar-timezone "Europe/Berlin")
(setq load-path (cons "~/.emacs.d/org-caldav" load-path))
(setq org-caldav-url
"https://CORPORATESERVER/owncloud/remote.php/caldav/calendars/steuer";)
(setq org-caldav-calendar-id "testtodo")
(setq org-caldav-files '("~/Test/Orgmodetest/CaldavKalender/testtodo.org") )
(setq org-caldav-inbox "~/Test/Orgmodetest/CaldavKalender/caldav-inbox.org")
(require 'org-caldav)
---
emacs is invoked as
emacs -Q -l init.el testtodo.org
emacs-24.4.1
org 8.3beta from today
The server (and the paths) works. At least I can sync my mobile.
Any obvious mistake on my side?
Where does org-check-agenda-file happen?
How can I debug any further?
Any help appreciated!
Detlef
[O] Tangling src blocks to files as part of export
Is it possible to have certain blocks tangled as part of export so that they are available as input files to later source blocks? E.g., #+BEGIN_SRC python :tangle hello.py print "Hello World" #+END_SRC #+BEGIN_SRC sh python hello.py #+END_SRC If I tangle before running, then the second code block will work; else, it fails because 'hello.py' is not found. [1] I can run tangle and export in a row (and I have my own function to do just that) but is there a native org way to do so? Michael [1] My actual case involves a JAGS model file and the R code to run it, so executing the first source block directly isn't an option.
Re: [O] Tangling src blocks to files as part of export
> On Nov 13, 2014, at 10:54 AM, Michael Weylandt > wrote: > > Is it possible to have certain blocks tangled as part of export so that they > are available as input files to later source blocks? > > E.g., > > #+BEGIN_SRC python :tangle hello.py > print "Hello World" > #+END_SRC > > #+BEGIN_SRC sh > python hello.py > #+END_SRC > > If I tangle before running, then the second code block will work; else, it > fails because 'hello.py' is not found. [1] > > I can run tangle and export in a row (and I have my own function to do just > that) but is there a native org way to do so? Adding org-babel-tangle to the org-export-before-processing-hook does the job, but I'd still be interested in knowing if there's a more official method.
[O] Long table with NAME but no CAPTION
If I export a table with
#+ATTR_LATEX: :environment longtable
#+NAME: mytable
then the beginning of the longtable environment (in the exported
latex file) has, e.g.,
\begin{longtable}{lrrl}
\label{mytable}
\\
\hline
This is a problem, because of the extra space created by the \\. I
tried to fix it by changing ox-latex.el, but the longtable environment
(in latex) requires the \\ when there is a \label{} command, even in the
absence of a caption. This looks like a bug in longtable to me, but it
is also true that in a pure LaTeX context it would be very unusual for a
table to have a \label{} without a \caption{}, because there would be no
printed target for \ref{mylabel} to refer to.
Note that there is no problem if the org table has no NAME, since then
the lines
\label{mytable}
\\
are not produced. But I want the NAME in the org file because because I
use data from the table to do calculations in other tables via
"remote(mytable, ...)".
So my sugggestion would be for org's latex export to produce no \label{}
(and hence no \\) when the table has no caption, or at least I would
prefer to have this as an option. Is there some way to achieve this?
Perhaps I should also file a bug report with the author/maintainer of
longtable, David Carlisle?
One more minor comment: I notice that org-mode's latex export puts the
\label{} inside the argument of the \caption{} command. This seems
unusual to me.
Re: [O] Tangling src blocks to files as part of export
Hello Michael, Michael Weylandt wrote: >> On Nov 13, 2014, at 10:54 AM, Michael Weylandt >> wrote: >> >> Is it possible to have certain blocks tangled as part of export so >> that they are available as input files to later source blocks? >> >> E.g., >> >> #+BEGIN_SRC python :tangle hello.py >> print "Hello World" >> #+END_SRC >> >> #+BEGIN_SRC sh >> python hello.py >> #+END_SRC >> >> If I tangle before running, then the second code block will work; >> else, it fails because 'hello.py' is not found. [1] >> >> I can run tangle and export in a row (and I have my own function to >> do just that) but is there a native org way to do so? > > Adding org-babel-tangle to the org-export-before-processing-hook does > the job, but I'd still be interested in knowing if there's a more > official method. For such a work, I'm using this home-made function: --8<---cut here---start->8--- (with-eval-after-load "org" (defun org-save-buffer-and-do-related () "Save buffer, execute/tangle code blocks, and export to HTML/PDF." (interactive) (let* ((orgfile (buffer-file-name)) (base-name (file-name-base orgfile)) (htmlfile (concat base-name ".html")) (pdffile (concat base-name ".pdf"))) (save-buffer) ; See other commands in ; `before-save-hook': ; `org-update-all-dblocks' ; `org-table-iterate-buffer-tables'. (when (derived-mode-p 'org-mode) ;; (org-babel-execute-buffer) ; XXX Why should we execute all code blocks? (let ((before-save-hook nil)) (save-buffer)) (org-babel-tangle) (when (file-exists-p htmlfile) (if (file-newer-than-file-p orgfile htmlfile) (org-html-export-to-html) (message "HTML is up to date with Org file"))) (when (file-exists-p pdffile) (if (file-newer-than-file-p orgfile pdffile) (if (string-match "^#\\+BEAMER_THEME: " (buffer-string)) (org-beamer-export-to-pdf) (org-latex-export-to-pdf)) (message "PDF is up to date with Org file"))) (beep (define-key org-mode-map (kbd "") 'org-save-buffer-and-do-related)) --8<---cut here---end--->8--- Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/
Re: [O] Repeated teaching classes and stopping date
On Thursday, 13 Nov 2014 at 11:44, Samuel Loury wrote: [...] >> Minutes! What version of org and what kind of system? > > Org version 8.2.7c. > The system is a Samsung galaxy S3. Ah, interesting. Yes, not a terribly fast system so probably eplains your performance issues. Mind you, more than twice as fast as my pandora :) : Processor : ARMv7 Processor rev 3 (v7l) BogoMIPS: 795.51 Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls I do periodically go through and archive sections of my org files to keep the times bearable on the pandora and I use sticky agenda views to help avoid unnecessary regeneration. > I don't understand how the SD card speed is to be taken into account > since org mode by default loads into emacs (and then in memory) all the > org files prior to computing the agenda. Are you sure? I had the impression that my org files were not accessed until I asked for the agenda. But maybe they are in which case you are correct that the SD card doesn't matter. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-558-g83d8a2
Re: [O] pdf images in html export
I think the best thing to do here is create a derived backend. Filters could work to, but you will have to parse the img link, get the pdf file, convert it and replace the path in the link. with a derived backend you can get that a little more directly like this. This code block works on a minimal example for me. I guess you could make a little function to do the last line, and put this all in your init files and it would work. This is a very unsophisticated format function that does not check for attributes like width or height or link descriptions... but, I get a png image in the html export of an org file with a pdf image ;) #+BEGIN_SRC emacs-lisp (defun my-link-format (link contents info) (let ((type (org-element-property :type link)) (path (org-element-property :path link))) (cond ((and (string= type "file") (string-match "\.pdf" path)) (shell-command (format "convert %s %s" path (replace-regexp-in-string "\.pdf" ".png" path))) (format "" (replace-regexp-in-string "\.pdf" ".png" path))) ;; anything else, we just do the regular thing (t (org-html-link link contents info) (org-export-define-derived-backend 'my-html 'html :translate-alist '((link . my-link-format))) (browse-url (org-export-to-file 'my-html "custom-link.html")) #+END_SRC Rainer M Krug writes: > Andreas Leha writes: > >> Hi Rainer, >> >> Rainer M Krug writes: >>> Andreas Leha writes: >>> Hi Marco, Marco Wahl writes: > Andreas Leha writes: > >> how would I export an org file containing >> >> [[file:./myimage.pdf]] >> >> to html so that a say png version myimage.pdf is inlined in the html >> which links to the pdf? >> >> I guess it should be possible to run imagemagick on all pdf links during >> export somehow. > > You could introduce a relation of the pdf-filenames to the respective > thumb-filenames e.g. by using the suffix '_thumb'. Before the export > the conversion tool would create the thumbs. > > The org-file could reference the data as > > [[file:./myimage.pdf][file:myimage_thumb.png]] > > See the info page (info "(org)Images in HTML export")? > > Untested. I just accidentially browsed that info page yesterday. > > Thanks for your thoughts. I would like to automate all of that. So, I guess the first question is where to put code that would trigger the conversion and how to best detect links to pdfs. >>> >>> Well - this is coming again and again - but no solution out of the >>> box. There are effectively two approaches: >>> >>> 1) Macro to change properties according to backend used. >>> >>> One usage is changing the file name extension according to the >>> backend. This is implemented as a simplified macro below. This could >>> be done by using ~(by-backend (html "graph.png") (latex "graph.pdf") (t >>> "graph.pdf"))~ >>> >>> See >>> [[http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html#sec-4-3][work >>> section ob-doc-LaTeX]] for details. >>> >>> #+begin_src emacs-lisp >>> (setq org-babel-latex-htlatex "htlatex") >>> (defmacro rmk-by-backend (&rest body) >>> `(case (if (boundp 'backend) (org-export-backend-name backend) nil) >>> ,@body)) >>> #+end_src >>> >>> 2) To use svg image format, which is supported by both (although has >>>it's drawbacks: slow rendering of the html, need to run external >>> programs upon compilation) >>> >>> So the first might be the modst feasible option. >>> >> >> Thanks for this. I am aware of how to *produce* graphics in different >> formats for different export backends. I use your first approach, >> which I think is the better solution. > > I agree with you. > >> >> Here, I am after a solution, that works on images that are not produced >> but merely included via [[file:./some.pdf]]. > > OK - understood. > >> >> I think there should be the possibility to include these into html (and >> odt) export without any user interaction. So, I >> - do not want to write a source block just to produce the by-backend image >> - do not want to change the link manually >> - do not want to run the converter manually > > I agree with you - this *should* be possible, and I assume not to > difficult to implement. In my opinion, this should also work out of the > box when enabling it e.g. via a property. > >> >> I am pretty sure this should be achievable with standard orgmode tools >> (like filters, export hooks, or anything). > > Yes - it should be. > >> >> Since 'this is coming again and again' it seems a non-esoteric task. >> And as there is 'no solution out of the box', I assume(d) that somebody has >> written these filters already. > > Unfortunately not... > > Cheers, > > Rainer > >> >> Regards, >> Andreas >> >> >> -- --- John Kitchin Professor Doherty Hall A207F Department of Chemical En
Re: [O] [PATCH] inline src block results can be removed
Hello,
"Charles C. Berry" writes:
> I like the flexibility that macros would allow.
I like it too. Macros are much better than export snippets for the task.
> I don't think the usual #+MACRO works here, as the definition would be
> found in `org-macro-templates' by the first call and existing stuff
> would be expanded instead of being left for babel to remove it. But
> setting it up as a document keyword should work, right?
>
> Don't know if there are other gotchas.
>
> Maybe a limited collection of formats could be set up to support basic
> markup options and the macro could choose amongst them with a second
> arg set by a babel header arg.
I think {{{results()}}} should remain a dumb wrapper itself and not try
to do some formatting (i.e., a simple, hard-coded macro). Formatting
should be on the side of Babel and, possibly, its arguments. Let's not
duplicate features.
> I am not quite sure how to marry this to header args. Maybe the :wrap
> header arg should be hijacked for inline src blocks to specify a macro
> for the results.
Macro can be the default output. If you don't want a macro, use raw
header. IOW, there is no need for a specific header arg.
> I mean, does anyone actually use stuff like src_R[:wrap latex]{1+2}?
> The current result cannot be parsed as an export block, AFAICS.
It could evaluate to @@latex:3@@. Parsing can also be solved if
necessary.
Thanks for your work.
Regards,
--
Nicolas Goaziou
[O] Feature Request - Comments in noweb expansions
Hello orgmode community! using ":comments org" as a header argument to a code block allows the header and text above the code block to be inserted into the tangled file as comments. Very awesome. This does not work for noweb reference expansions however. For example, given the following org mode file: --8<---cut here---start->8--- * File Description :PROPERTIES: :comments: org :tangle: file.sh :noweb: yes :END: ** A function call This is foo #+BEGIN_SRC sh :noweb-ref myfunction :tangle no hello_world() #+END_SRC ** Additional info This is bar #+BEGIN_SRC sh :noweb yes hello_person() <> #+END_SRC --8<---cut here---end--->8--- When I tangle the file with C-c C-v t, my expectation would be the following result. --8<---cut here---start->8--- # Additional info # This is bar hello_person() # A function call # This is foo hello_world() --8<---cut here---end--->8--- But this isn't what happens, The comment from the myfunction noweb-ref is stripped from the final result and it looks like this. --8<---cut here---start->8--- # Additional info # This is bar hello_person() hello_world() --8<---cut here---end--->8--- Is there a native way to get this behaviour or do I advise org-babel-expand-noweb-references? I am keen to hack a patch myself, would just appreciate a pointer in the right direction. (drowning in org-mode code) First time poster. -- Thanks Gambo
Re: [O] Sub-tree EXPORT_ properties are not over-riding file-level options
Hello, "Daniel J. Sinder" writes: > My exports are not picking up sub-tree EXPORT_ properties. > > Emacs: GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN > Org: Org-mode version 8.2.10 (release_8.2.10-16-g4c37a9 [...] > I've verified the same problem for other EXPORT_ properties and other > export formats (e.g., html). Is this a bug in the new export engine, or am > I doing something wrong? Any suggestions/help would be appreciated. The EXPORT_ properties are only meaningful when you do a subtree export, i.e., Export scope is "Subtree" in export dispatcher. Regards, -- Nicolas Goaziou
Re: [O] Embedded LaTeX does not work with Unicode quotes
Hello,
Florian Beck writes:
> Nick Dokos writes:
>
>> "punctuation" in the syntax tables. Look for org-latex-regexps in
>> org.el
>
> The line in question is
>
> #+BEGIN_SRC emacs-lisp
> ("$" "\\([^$]\\|^\\)\\(\\(\\$\\([^
> \r\n,;.$][^$\n\r]*?\\(\n[^$\n\r]*?\\)\\{0,2\\}[^
> \r\n,.$]\\)\\$\\)\\)\\([- .,?;:'\")\000]\\|$\\)" 2 nil)
> #+END_SRC
>
> It's probably not too hard to see that the culprit is the bunch of
> punctuation characters towards the end. Indeed if you change .,?;:'\"
> to .,?;:'\"” -- that solves the OPs problem. However, it might be even
> better to use a more general syntax, [:punct:], which matches all
> punctuation (as we want). So:
>
> #+BEGIN_SRC emacs-lisp
> ("$" "\\([^$]\\|^\\)\\(\\(\\$\\([^
> \r\n,;.$][^$\n\r]*?\\(\n[^$\n\r]*?\\)\\{0,2\\}[^
> \r\n,.$]\\)\\$\\)\\)\\([- [:punct:]\000]\\|$\\)" 2 nil)
> #+END_SRC
Actually this variable is hardly used throughout Org code base. See
org-element-latex-fragment-parser instead (which has the same "problem"
anyway).
Also, according to Elisp manual; [:punct:] is not ideal either:
`[:punct:]'
This matches any punctuation character. (At present, for multibyte
characters, it matches anything that has non-word syntax.)
There is also "\s.".
Anyway, it might be better to know exactly what kind of false positives
we want to avoid.
Regards,
--
Nicolas Goaziou
Re: [O] Inline code :results replace not working
Ista Zahn gmail.com> writes:
>
> On Mon, Nov 10, 2014 at 3:04 PM, Grant Rettke
wisdomandwonder.com> wrote:
> > On Mon, Nov 10, 2014 at 11:03 AM, Ista Zahn gmail.com>
wrote:
> >> On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry
ucsd.edu> wrote:
> >>> On Mon, 10 Nov 2014, Andreas Leha wrote:
> >>
> >> [snip]
> >>
> >>>
> >>
> >> Nonetheless, from a literate programming perspective, I think that
> >> replaceable (and raw) inline results are definitely desirable.
> >> Regardless of the state of their implementation in orgmode right
now.
> >>>
> >>>
> >>> +1.
> >>
> >> +1 from me as well. For exactly the reason Andreas illustrated I've
> >> given up on using inline results for the past year or so. Would be
> >> great to see this feature become usable by implementing a system for
> >> replacing them.
> >
> > My approach here has been to use "hidden" source blocks that aren't
> > exported but make it
> > really easy to see the result during development. These settings
> > should work on any configuration,
> > so I didn't include mine here.
> >
> > ✂✂
> > #+BEGIN_SRC R
> > a = 10
> > b = 23
> > c = a + b
> > #+END_SRC
> >
> > #+BEGIN_SRC R :results output silent :exports none
> > c
> > #+END_SRC
> >
> > The user calculated src_R{c}.
> > ✂✂
> >
> > When you use these functions
> > http://orgmode.org/manual/Key-bindings-and-useful-functions.html#Key-
bindings-and-useful-functions
> > the addition of these "hidden" blocks hav almost zero cost and give me
> > what I want.
>
> The problem I have is not that I miss being able to see results of the
> inline block in the org-mode buffer. The problem is that I don't want
> blocks to be evaluated on export (too time consuming in many cases).
> So I turn that off, and either evaluate the blocks one at a time (I'm
> aware of the dangers of this, not my point here) or call
> org-babel-execute-buffer. Everytime I do that I get duplicate output
> from inline code. As far as I can see inline code +
> org-babel-execute-buffer is incompatible, which is why I gave up on
> the former.
>
> Best,
> Ista
>
>
+1
First of all nice that something is "happening" on the issue - happy not to
be the only one missing something.
+ 1
on I also don't bother too much about the eval-on-export functionality as
long as I can evaluate the buffer and get non repeated inline results.
For now I don't use inline blocks anymore.
As an intermediate solution I would like to specify document wide options
for inline code blocks only (:results silent); sorry - cannot find the
example I saw on the net recently on how to do so. I could not get it
working.
I could set results silent argument in every inline src code but don't want
the inline source code to be too long unnecessarily (affects readability of
text).
Re: [O] [PATCH] inline src block results can be removed
Hi,
Nicolas Goaziou writes:
> Hello,
>
> "Charles C. Berry" writes:
>
>> I like the flexibility that macros would allow.
>
> I like it too. Macros are much better than export snippets for the task.
>
>> I don't think the usual #+MACRO works here, as the definition would be
>> found in `org-macro-templates' by the first call and existing stuff
>> would be expanded instead of being left for babel to remove it. But
>> setting it up as a document keyword should work, right?
>>
>> Don't know if there are other gotchas.
>>
>> Maybe a limited collection of formats could be set up to support basic
>> markup options and the macro could choose amongst them with a second
>> arg set by a babel header arg.
>
> I think {{{results()}}} should remain a dumb wrapper itself and not try
> to do some formatting (i.e., a simple, hard-coded macro). Formatting
> should be on the side of Babel and, possibly, its arguments. Let's not
> duplicate features.
>
>> I am not quite sure how to marry this to header args. Maybe the :wrap
>> header arg should be hijacked for inline src blocks to specify a macro
>> for the results.
>
> Macro can be the default output. If you don't want a macro, use raw
> header. IOW, there is no need for a specific header arg.
>
>> I mean, does anyone actually use stuff like src_R[:wrap latex]{1+2}?
>> The current result cannot be parsed as an export block, AFAICS.
>
> It could evaluate to @@latex:3@@. Parsing can also be solved if
> necessary.
>
Without too much value to add to this thread at this point, I just want
to say, that I love the direction this thread has taken. There is
good reason now to hope for better inline results handling in org.
> Thanks for your work.
I second that! Thanks, Chuck!
Regards,
Andreas
Re: [O] pdf images in html export
Hi John, Instructor account writes: > I think the best thing to do here is create a derived backend. Filters > could work to, but you will have to parse the img link, get the pdf > file, convert it and replace the path in the link. > > with a derived backend you can get that a little more directly like > this. This code block works on a minimal example for me. I guess you > could make a little function to do the last line, and put this all in > your init files and it would work. This is a very unsophisticated format > function that does not check for attributes like width or height or link > descriptions... but, I get a png image in the html export of an org file > with a pdf image ;) > > #+BEGIN_SRC emacs-lisp > (defun my-link-format (link contents info) > (let ((type (org-element-property :type link)) > (path (org-element-property :path link))) > (cond > ((and >(string= type "file") >(string-match "\.pdf" path)) > (shell-command >(format > "convert %s %s" > path > (replace-regexp-in-string "\.pdf" ".png" path))) > (format "" (replace-regexp-in-string "\.pdf" ".png" > path))) > ;; anything else, we just do the regular thing > (t > (org-html-link link contents info) > > (org-export-define-derived-backend 'my-html 'html > :translate-alist '((link . my-link-format))) > > > (browse-url (org-export-to-file 'my-html "custom-link.html")) > #+END_SRC That is really nice. From all solutions so far this seems to be the one to pursue. I will look into that. [...] Thanks, Andreas
Re: [O] [RFC] Change property drawer syntax
Hello, Sebastien Vauban writes: > I've done that but, now, it does not support anymore the structure I had > in all my Org files: > > ** TODO Show typical Org entry >SCHEDULED: <2014-11-08 Sat> >:LOGBOOK: >CLOCK: [2014-11-11 Tue 12:35]--[2014-11-11 Tue 14:19] => 1:44 >:END: > > I have the planning lines and the drawers indented at the level of the > entry. > > On the other hand, the "body text" of the entry always begins at > column 0. This makes a clear distinction between "meta-stuff" and the > contents of the entry itself. This distinction is not known by Org. "Meta-stuff" is stuff bound to a headline: planning info and, now, properties drawer. OTOH, a LOGBOOK drawer is a regular drawer, which can be inserted anywhere within the section. As such, it belong to the body of the section. > Now, with `org-adapt-indentation' set to `t', the whole "block" moves to > the right when demoting, and to the left (except for the LOGBOOK > drawer!? [1]) when promoting. When demoting, everything, i.e., "meta-stuff" and body, is moved to the right. When promoting, "meta-stuff" is moved unconditionally (due to `org-adapt-indentation'), but line beginning at column 0 prevents the body from being moved. Maybe behaviour could be more symmetric (i.e., refuse to demote body if promoting it would fail). I didn't think about it much, but I have the feeling that there are pitfalls, however. `org-adapt-indentation' is really useful if you indent everything, e.g., using C-j to start new lines. Here you are using something in-between. I suggest to keep `org-adapt-indentation' to nil and "fix" meta stuff and logbook by indentation by hand, using `org-after-demote-entry-hook' and `org-after-promote-entry-hook'. > With `org-adapt-indentation' set to `nil', nothing moves (but the > headline), when demoting or promoting. This sounds right. > [1] See http://screencast.com/t/nsGNuoHL. This requires Flash, which I don't have. Regards, -- Nicolas Goaziou
Re: [O] org-insert-heading
Hello, Luke Crook writes: > Question concerning the behaviour of org-insert-heading; > > The manual states the following. >>> > If the command is used at the end of a folded subtree (i.e., behind the > ellipses at the end of a headline), then a headline will be inserted after > the end of the subtree. > << > > However at least in my installation (Emacs 34.3, org-mode 8.2.10), the new > heading is created prior to the ellipses. > > For example > > * Heading folded... > > ^ cursor here, then M- results in the following. Point is /before/ the ellipses here. You need to move after them, e.g., using C-f or mess with `org-special-ctrl-a/e'. Regards, -- Nicolas Goaziou
[O] error when sending radio table
Hello experts Since a while I get the following error message when I try to send a radio table in a LaTeX document with C-c C-c: org-trim: Wrong type argument: stringp, nil The table is not sent. This happens only if there are empty cells. If the table is filled all throughout, sending works just fine. As this is something I use quite frequently, and usually with some empty cells, any help will be highly appreciated. TIA, Salome (I have Org-mode version 8.2.10, installed from elpa. Orgtable-minor-mode is active in the LaTeX-Buffer.)
Re: [O] problem with auto-fill-mode in gnus with org
Hello, Eric S Fraga writes: > So I decided to not enable orgstruct mode. However, by doing so, I get > the following error whenever I try to type in a line longer than my > auto-fill-column: > > , > | Debugger entered--Lisp error: (void-variable orgtbl-line-start-regexp) > | org-adaptive-fill-function() > | org-auto-fill-function() > | self-insert-command(1) > | funcall-interactively(self-insert-command 1) > | call-interactively(self-insert-command nil nil) > | command-execute(self-insert-command) > ` > > I have > > (setq auto-fill-function 'org-auto-fill-function) > > in my message-mode-hook so I do expect org to be involved in my message > composition. Am I responsible for initialisation of org in this > context? What am I missing? Odd. I'm not able to reproduce it. However, using `org-auto-fill-function' without Org major mode may be asking for trouble (variables not initialized...). Regards, -- Nicolas Goaziou
Re: [O] error when sending radio table
Hello, Salome Soedergran writes: > Since a while I get the following error message when I try to send a radio > table in a LaTeX document with C-c C-c: > > org-trim: Wrong type argument: stringp, nil > > The table is not sent. This happens only if there are empty cells. > If the table is filled all throughout, sending works just fine. I cannot reproduce it. Could you send an ECM? Regards, -- Nicolas Goaziou
Re: [O] Sub-tree EXPORT_ properties are not over-riding file-level options
On Thu, Nov 13, 2014 at 10:14 AM, Nicolas Goaziou wrote: > > The EXPORT_ properties are only meaningful when you do a subtree export, > i.e., Export scope is "Subtree" in export dispatcher. > > Thank you! That does the trick. I must say, this is a little confusing because an active region limits the output of the export to the active region. Thus, the output of a single subtree misled me to believe that the "scope" of the export had been already limited to "Subtree." I now see the variable org-export-initial-scope, but that's a little too heavy handed (since one can't export the entire file if it is left set to Subtree. It would be nice if there was some way to have 'C-c @' automatically (and temporarily) set this variable to Subtree until the next export or until the region is de-activated. Thanks again, Dan
[O] Possible to recalculate tables automatically before exporting?
Is it possible to make tables recalculate automatically when exporting? In a file I'm working on now, I have a table with formulas that take two columns of numbers I enter and turn them into two columns of derived numbers. I had missed one line of data, so I entered it, but forgot to recalculate the table, so when I exported some numbers were missing. It was trivial to do by hand, of course, but I looked for a setting that would automate this and didn't see it. Did I overlook it, or is it not there? Thanks, Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [O] Sub-tree EXPORT_ properties are not over-riding file-level options
>From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org >[mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On >Behalf Of >Daniel J. Sinder >Sent: Thursday, November 13, 2014 12:29 PM >To: emacs-orgmode >Subject: Re: [O] Sub-tree EXPORT_ properties are not over-riding file-level >options > >On Thu, Nov 13, 2014 at 10:14 AM, Nicolas Goaziou >wrote: > >The EXPORT_ properties are only meaningful when you do a subtree export, >i.e., Export scope is "Subtree" in export dispatcher. > >Thank you! That does the trick. > >I must say, this is a little confusing because an active region limits the >output of the export to the active region. Thus, the output of a single >subtree >misled me to believe that the "scope" of the export had been already >limited to "Subtree." > >I now see the variable org-export-initial-scope, but that's a little too heavy >handed (since one can't export the entire file if it is left set to Subtree. >It >would be nice if there was some way to have 'C-c @' automatically (and >temporarily) set this variable to Subtree until the next export or until the >>region is de-activated. > >Thanks again, >Dan C-c C-e followed by C-s limits the export scope to the subtree at point quite nicely in my experience. It resets when the dispatcher is closed This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
Re: [O] [patch] Bug (regression) in org-replace-disputed-keys. Bisected.
Hello,
Teika Kazura writes:
> Glad to contribute. I attached two patches, the first for the lisp
> fix,
Thank you. I applied it, with corrections to the commit message. In
particular, you need to add "TINYCHANGE" at its end, unless you sign FSF
papers.
> and the second for org.texi.
Thanks. Some comments follow.
> Now, release notes (http://orgmode.org/Changes.html) fix proposal. I here
> write "the full version". (Sorry. I know concise is better.)
>
> 1. Version 8.1, "Important bugfixes" section
>
> The following sentence should be moved to "Incompatible changes" section:
> "The replacement of disputed keys is now turned of when reading a date"
>
> Furthermore, the following should be added: "N.B. This is reverted in Version
> 8.3."
>
> 2. Please add this to the next version "Incompatible changes" section:
> "`org-replace-disputed-keys' has been ignored when reading date since version
> 8.1, but the former behavior is restored again."
>
> Perhaps to "New features" can be added: "Keybinding for reading date
> can be customized with a new variable
> `org-read-date-minibuffer-local-map'. (In fact, it was introduced in
> version 8.0, but it was not announced.)"
Done, with some tiny change.
> Some comments on my org.texi patch. I renamed the section "Creating
> timestamps" to "Timestamp commands," since not all commands don't
> create. (Links are updated.) I rewrote some explanations. I think it's
> better, but I'm not sure if my tone of voice (e.g. "Date/time prompt
> is ``smart enough''") is acceptable. Some whitespace cleanup
> accompanies, so you may want to use "git show -b".
>
> I added the description of key "!" in timestamp creation. But I don't
> know what "diary" in Emacs is, so you may want to improve it.
> Subject: [PATCH 2/2] org.texi: Timestamp sections.
>
> Section "Creating timestamp" is renamed to "Timestamp commands".
> `org-read-date-minibuffer-local-map' is described. Other contents improvement
> in that section.
Please fill your paragraphs.
You need to document what parts are changed.
Also, commit messages, as Texinfo, require sentences to be separated
with two spaces.
> For Org mode to recognize timestamps, they need to be in the specific
> -format. All commands listed below produce timestamps in the correct
> -format.
> +format. All commands listed below automatically fix incomplete
> existing timestamps.
Two spaces.
Also, I don't get the "fix incomplete existing timestamps" part.
> +Many commands prompt for a date. Details for timestamp prompt will be
> explained in a later subsection. (@pxref{The date/time prompt})
Two spaces.
> -Change date at cursor by one day. These key bindings conflict with
> +Change date at cursor by one day. These key bindings conflict with
This change is incorrect.
> @vindex org-read-date-prefer-future
> -When Org mode prompts for a date/time, the default is shown in default
> -date/time format, and the prompt therefore seems to ask for a specific
> -format. But it will in fact accept date/time information in a variety of
> -formats. Generally, the information should start at the beginning of the
> -string. Org mode will find whatever information is in
> -there and derive anything you have not specified from the @emph{default date
> -and time}. The default is usually the current date and time, but when
> +Date/time prompt is ``smart enough'', accepting shorthand notations,
> visual input while viewing the calendar, etc.
I don't think this is better: "smart enough" doesn't explain much.
However, splitting the paragraph in three parts and reordering them
a bit is a good idea.
> @cindex calendar, for selecting date
> @vindex org-popup-calendar-for-date-prompt
> -Parallel to the minibuffer prompt, a calendar is popped up@footnote{If
> -you don't need/want the calendar, configure the variable
> -@code{org-popup-calendar-for-date-prompt}.}. When you exit the date
> -prompt, either by clicking on a date in the calendar, or by pressing
> -@key{RET}, the date selected in the calendar will be combined with the
> -information entered at the prompt. You can control the calendar fully
> -from the minibuffer:
> +Parallel to the minibuffer prompt, a calendar is popped up@footnote{If you
> +don't need/want the calendar, configure the variable
> +@code{org-popup-calendar-for-date-prompt}.}. Calendar-based visual input is
> +possible, too, and it will be combined with the information entered at the
> +prompt. You can control the calendar fully from the minibuffer:
Two spaces (twice).
> +C-.@r{Go to today.}
> +! @r{Show diary entries. @ref{Displaying the Diary, ,
> Displaying the Diary, emacs, The Emacs Editor}}
Two spaces.
> +@vindex org-read-date-minibuffer-local-map
> +S- keys conflict with other modes. For the details see
> @xref{Conflicts}. You can fully customize the key binding with the
> variable @code{org-read-date-minibuffer-local-map}.
I don't think it deserves to appear in the manual. Moreover, thi
[O] Bug: Export to html and latex fails on these (relatively common) strings [8.2.10 (8.2.10-16-g4c37a9-elpa @ /home/mzimmermann/.emacs.d/elpa/org-20141110/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Hi:
Any of the strings in Ex 1) to Ex 4) below, even individually, including the
extremely simple example 4, fails the export of the org file to latex and html.
The failure appears to happen in the first step (converting to an intermediate
format)
*Steps to reproduce:*
- Open a file containing any of the 4 examples (or this text named as org)
- C-c C-e l L
- Backtrace is attaches
These type of strings on which the failure happens are not unusual to find in
documents pasted from mysql or git.
*Ex 1)* - real life example from git output which fails to export
git pull origin master
>From github.com:airlift-group/cubifier
>
\* branchmaster -> FETCH_HEAD
Updating 28d0c00..8d3abef
Fast-forward
grails-app/conf/Aaaa.groovy| 10 +-
src/java/org/Bbbb.java | 19 +++
src/java/org/Cccc.java | 30
--
*Ex 2)* - real life from Mysql output which fails to export (note the
misalligned | in the data row - no issues when alligned)
+---++---+
| label | long_label | isEnabled |
+---++---+
| | 2 | |
+---++---+
*Ex 3)* Simple example which fails to export
++--+
*Ex 4)* Simpliest example which fails to export
+
Emacs : GNU Emacs 24.3.1 (x86_64-suse-linux-gnu, GTK+ Version 3.10.4)
of 2014-01-23 on cloud107
Package: Org-mode version 8.2.10 (8.2.10-16-g4c37a9-elpa @
/home/mzimmermann/.emacs.d/elpa/org-20141110/)
current state:
==
(setq
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-html-format-drawer-function '(lambda (name contents) contents)
org-table-tab-recognizes-table.el nil
org-latex-format-inlinetask-function 'ignore
org-confirm-shell-link-function 'yes-or-no-p
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-emphasis-alist '(("*" bold "" "") ("/" italic "" "")
("_" underline
""
"")
("=" org-code "" "" verbatim)
("~" org-agenda-restriction-lock "" ""
verbatim)
("+" (:strike-through t) "" ""))
org-support-shift-select t
org-latex-format-headline-function 'org-latex-format-headline-default-function
org-startup-indented t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-latex-format-drawer-function '(lambda (name contents) contents)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '((lambda nil
(org-add-hook (quote change-major-mode-hook)
(quote org-show-block-all) (quote append) (quote local))
)
(lambda nil
(org-add-hook (quote change-major-mode-hook)
(quote org-babel-show-result-all) (quote append)
(quote local))
)
do-org-plot
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all
append local]
5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook
org-babel-show-result-all append local]
5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
org-ascii-format-drawer-function '(lambda (name contents width) contents)
org-c
[O] Inconsistency between clocking time in the modeline and what gets recorded after C-c C-x C-o
Hi there, when I clock in at 12:34:56, the modeline says that I'm working for 00:00 minutes until 12:35:56. However, when I clock out at 12:35:01, the entry in :LOGBOOK: says I have worked for 00:01. This bugs me. Is it intended? Are there other people annoyed by this, too? Is it a bug? Is asking for increasing clocking "resolution" from minutes to seconds a reasonable feature request? Regards, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/pl/Marcin_Borkowski Wydział Matematyki i Informatyki Uniwersytet im. Adama Mickiewicza
Re: [O] org-insert-heading
Nicolas Goaziou nicolasgoaziou.fr> writes: > > Point is /before/ the ellipses here. You need to move after them, e.g., > using C-f or mess with `org-special-ctrl-a/e'. > > Regards, > OK thanks. I understood "behind the ellipses at the end of a headline" as "before" the ellipses, not "after". But I still don't think it works as it is meant to. Org creates a new list item in the folded heading if the last line is a list item. Otherwise org creates a new heading at the same level as the folded heading. So * TEST - skfjdskjfs gives the following * TEST * - skfjdskjfs But * Test... gives the following * TEST - skfjdskjfs - Also the following won't create a new header or list item at all. * TEST... Doesn't do anything
Re: [O] org-insert-heading
Luke Crook balooga.com> writes: > > * TEST... > > > Doesn't do anything > The above I cannot consistently reproduce. So ignore for now. Thanks.
