[O] [PATCH] org-crypt: make org-decrypt disable auto-save-mode (configurable)
As auto-save-mode can only cause leakage when there's actual decrypted data lying around, don't check for it (and potentially cause annoyance) on init, but only when org-decrypt-entry is called. * lisp/org-crypt.el: - add defcustom `org-crypt-disable-auto-save' - `org-decrypt-entry': before decrypting, check whether `auto-save-mode' is enabled for the current buffer, and act on it according to how `org-crypt-disable-auto-save' is set. - remove comment re "encrypt[ing] Org auto-saved buffers" - remove on-init check for `auto-save-default' Signed-off-by: Pieter Praet --- lisp/org-crypt.el | 60 +--- 1 files changed, 47 insertions(+), 13 deletions(-) diff --git a/lisp/org-crypt.el b/lisp/org-crypt.el index 4bff7a1..1ff24b9 100644 --- a/lisp/org-crypt.el +++ b/lisp/org-crypt.el @@ -94,6 +94,29 @@ This setting can also be overridden in the CRYPTKEY property." :type 'string :group 'org-crypt) +(defcustom org-crypt-disable-auto-save 'ask + "What org-decrypt should do if `auto-save-mode' is enabled. + +t: Disable auto-save-mode for the current buffer + prior to decrypting an entry. + +nil : Leave auto-save-mode enabled. + This may cause data to be written to disk unencrypted! + +'ask : Ask user whether or not to disable auto-save-mode + for the current buffer. + +'encrypt : Leave auto-save-mode enabled for the current buffer, + but automatically re-encrypt all decrypted entries + *before* auto-saving. + NOTE: This only works for entries which have a tag + that matches `org-crypt-tag-matcher'." + :group 'org-crypt + :type '(choice (const :tag "Always" t) + (const :tag "Never" nil) + (const :tag "Ask" ask) + (const :tag "Encrypt" encrypt))) + (defun org-crypt-key-for-heading () "Return the encryption key for the current heading." (save-excursion @@ -142,6 +165,30 @@ This setting can also be overridden in the CRYPTKEY property." (defun org-decrypt-entry () "Decrypt the content of the current headline." (interactive) + + ; auto-save-mode may cause leakage, so check whether it's enabled. + (when buffer-auto-save-file-name +(cond + ((or + (eq org-crypt-disable-auto-save t) + (and +(eq org-crypt-disable-auto-save 'ask) +(y-or-n-p "org-decrypt: auto-save-mode may cause leakage. Disable it for current buffer? "))) + (message (concat "org-decrypt: Disabling auto-save-mode for " (or (buffer-file-name) (current-buffer + ; The argument to auto-save-mode has to be "-1", since + ; giving a "nil" argument toggles instead of disabling. + (auto-save-mode -1)) + ((eq org-crypt-disable-auto-save nil) + (message "org-decrypt: Decrypting entry with auto-save-mode enabled. This may cause leakage.")) + ((eq org-crypt-disable-auto-save 'encrypt) + (message "org-decrypt: Enabling re-encryption on auto-save.") + (add-hook 'auto-save-hook +(lambda () + (message "org-crypt: Re-encrypting all decrypted entries due to auto-save.") + (org-encrypt-entries)) +nil t)) + (t nil))) + (require 'epg) (unless (org-before-first-heading-p) (save-excursion @@ -201,19 +248,6 @@ This setting can also be overridden in the CRYPTKEY property." 'org-mode-hook (lambda () (add-hook 'before-save-hook 'org-encrypt-entries nil t -;; FIXME Find a better way to encrypt Org auto-saved buffers? -;; When `auto-save-default' is non-nil, make sure entries are -;; encrypted before auto-saving -;; (when auto-save-default -;;(add-hook -;; 'org-mode-hook -;; (lambda () (add-hook 'auto-save-hook 'org-encrypt-entries nil t - -(when (and (functionp 'daemonp) - (not (daemonp)) auto-save-default) - (message "Warning: turn auto-save-mode off in Org buffers containing crypted entries.") - (sit-for 1)) - (add-hook 'org-reveal-start-hook 'org-decrypt-entry) (provide 'org-crypt) -- 1.7.4.1
[O] Changing the font family in HTML export
Dear org mode users, I'm trying to change the font used when exporting .org to .html. At the moment, I get "
Re: [O] Problem with autoloads
Hi Nick, On Tue, 28 Jun 2011 08:56:59 +0200 Michael Markert wrote: > Hi Nick, > > thanks for looking into it. > > But the patch doesn't work. I think that stems from the fact, that the > first thing `generate-file-autoloads' does is to bind it new: I can confirm, I still get the error: Cannot open load file: lisp/org -- Suvayu Open source is the future. It sets us free.
Re: [O] [babel] using #+call for inline results
Hi Erics and Christian, Eric Schulte wrote: > Thanks for sharing these issues, it appears I messed some functionality > up with some of my recent changes. I believe that I have fixed these > issues. The following examples should now all export as described. > > The following exports as a normal call line > #+call: double(it=1) > > Now here is an inline call call_double(it=1) stuck in the middle of > some prose. > > This one should not be exported =call_double(it=2)= because it is > quoted. > > Finally this next one should export, even though it starts a line > call_double(it=3) because sometimes inline blocks fold with a > paragraph. > > And, a call with raw results call_double(4)[:results raw] should not > have quoted results. > > Please let me know if you experience any more problems, and thanks for > helping to get this sorted before the impending release! I did test, and it seems to work for me with a Org pulled 30 mins ago: http://i.imgur.com/WhaVs.png Well, I have many other problems with this version (such as speed commands not working anymore, yasnippet expansion not working anymore on TAB, some files which say they're not in Org-agenda-files, etc.) but that's another story. About this, my only weirdness is that I had to confirm 12 times (yes, 12!) that I wanted to execute the calls. I have this in my emacs config file for months ;; don't be prompted on every code block evaluation (setq org-confirm-babel-evaluate nil) ... has this var become a local file variable? Last thing: the questions in the echo area sometimes display the block name in parentheses, sometimes not... - "Evaluate this emacs-lisp code block (square) on your system? (yes or no)" - "Evaluate this emacs-lisp code block on your system? (yes or no)" Best regards, Seb -- Sebastien Vauban
Re: [O] Changing the font family in HTML export
Dror Atariah writes: > Can you help me? Thanks in advance, I think you could use an external css file for that. You can do so by setting the STYLE property in you org file like that: --8<---cut here---start->8--- #+TITLE: My page #+STYLE: * My first title --8<---cut here---end--->8--- Best regards, -- Manuel Giraud
[O] Errors with current version (git pull'ed at 10:30 CET)
Hello,
Just want to report 2 errors I got with the latest version of Org-mode. I'm
sure (with 5 nine, ie 99.999%) that I did not change anything in my setup
which could explain this.
Both errors were generated after a fresh Emacs startup.
* First
I try to open the file Work.org in which I had an open clock, on task "TODO
Organize work" (misc for project organization, etc.).
--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
looking-at(nil)
(and (looking-at org-complex-heading-regexp) (match-string 4))
(save-excursion (goto-char (cdr resume-clock)) (org-back-to-heading t) (and
(looking-at org-complex-heading-regexp) (match-string 4)))
(save-current-buffer (set-buffer (find-file ...)) (save-excursion (goto-char
...) (org-back-to-heading t) (and ... ...)))
(with-current-buffer (find-file (car resume-clock)) (save-excursion
(goto-char ...) (org-back-to-heading t) (and ... ...)))
(concat "Resume clock (" (with-current-buffer (find-file ...) (save-excursion
... ... ...)) ") ")
(y-or-n-p (concat "Resume clock (" (with-current-buffer ... ...) ") "))
(or (not org-clock-persist-query-resume) (y-or-n-p (concat "Resume clock ("
... ") ")))
(and resume-clock org-clock-persist (file-exists-p (car resume-clock)) (or
(not org-clock-persist-query-resume) (y-or-n-p ...)))
(if (and resume-clock org-clock-persist (file-exists-p ...) (or ... ...))
(progn (when ... ...)))
(when (and resume-clock org-clock-persist (file-exists-p ...) (or ... ...))
(when (file-exists-p ...) (with-current-buffer ... ... ...)))
(if (not (file-readable-p filename)) (message "Not restoring clock data; %s
not found" org-clock-persist-file) (message "%s" "Restoring clock data") (setq
org-clock-loaded t) (load-file filename) (when stored-clock-history
(save-window-excursion ...)) (when (and resume-clock org-clock-persist ... ...)
(when ... ...)))
(let ((filename ...) (org-clock-in-resume ...) resume-clock
stored-clock-history) (if (not ...) (message "Not restoring clock data; %s not
found" org-clock-persist-file) (message "%s" "Restoring clock data") (setq
org-clock-loaded t) (load-file filename) (when stored-clock-history ...) (when
... ...)))
(progn (let (... ... resume-clock stored-clock-history) (if ... ... ... ...
... ... ...)))
(if (and org-clock-persist (not org-clock-loaded)) (progn (let ... ...)))
(when (and org-clock-persist (not org-clock-loaded)) (let (... ...
resume-clock stored-clock-history) (if ... ... ... ... ... ... ...)))
org-clock-load()
run-hooks(text-mode-hook outline-mode-hook org-mode-hook)
apply(run-hooks (text-mode-hook outline-mode-hook org-mode-hook))
run-mode-hooks(org-mode-hook)
org-mode()
set-auto-mode-0(org-mode nil)
set-auto-mode()
normal-mode(t)
after-find-file(nil t)
find-file-noselect-1(# "~/emacs/site-lisp/pfitools.org"
nil nil "~/emacs/site-lisp/pfitools.org" ((2816 6 . 35967) (21669 . 36592)))
find-file-noselect("~/emacs/site-lisp/pfitools.org" nil nil nil)
ad-Orig-find-file("~/emacs/site-lisp/pfitools.org" nil)
find-file("~/emacs/site-lisp/pfitools.org")
(progn (find-file file))
(if file (progn (find-file file)))
(when file (find-file file))
(save-window-excursion (when file (find-file file)) (setq to-be-removed
(current-buffer)) (goto-char (point-min)) (while (re-search-forward
org-babel-src-block-regexp nil t) (goto-char ...) (let ... ... ...)))
(let* ((file file) (visited-p ...) (point ...) to-be-removed)
(save-window-excursion (when file ...) (setq to-be-removed ...) (goto-char ...)
(while ... ... ...)) (unless visited-p (kill-buffer to-be-removed)) (goto-char
point))
(org-babel-map-src-blocks file (let* (... ...) (when source-name ...)))
(let ((lob-ingest-count 0)) (org-babel-map-src-blocks file (let* ... ...))
(message "%d src block%s added to Library of Babel" lob-ingest-count (if ...
"s" "")) lob-ingest-count)
org-babel-lob-ingest("~/emacs/site-lisp/pfitools.org")
(progn (setq org-open-non-existing-files t) (setf
org-self-insert-cluster-for-undo nil) (quote (defadvice undo ... "Make point
and context visible after an undo command in Org mode." ...)) (add-hook (quote
org-mode-hook) (lambda nil ... ... ... ... ... ... ... ... ...)) (setq
org-fontify-done-headline t) (setq org-fontify-quote-and-verse-blocks t) (setq
org-hide-emphasis-markers t) (section "1.3 (org)Activation") (setq
org-insert-mode-line-in-empty-file t) (when (boundp ...) (add-to-list ... ...)
(add-to-list ... ...)) (setq org-ellipsis (quote org-ellipsis)) (setq
org-return-follows-link t) (setq org-blank-before-new-entry (quote ...))
(section "2.2 (org)Headlines") (section "2.3 (org)Visibility cycling") (setq
org-startup-folded t) (section "2.4 (org)Motion") (setq org-goto-interface
(quote outline-path-completion)) (section "2.5 (org)Structure editing")
(section "2.6 (org)Sparse trees") (setq org-show-hierarchy-above t) (setq
org-show-following-hea
[O] patch for doc string typos in org-mobile.el
--- org-mobile.el~ 2010-04-03 23:26:09.0 +0100 +++ org-mobile.el 2011-06-28 09:47:17.0 +0100 @@ -86,12 +86,12 @@ :type 'file) (defcustom org-mobile-force-id-on-agenda-items t - "Non-nil means make all agenda items carry and ID." + "Non-nil means make all agenda items carry an ID." :group 'org-mobile :type 'boolean) (defcustom org-mobile-force-mobile-change nil - "Non-nil means, force the change made on the mobile device. + "Non-nil means force the change made on the mobile device. So even if there have been changes to the computer version of the entry, force the new value set on the mobile. When nil, mark the entry from the mobile with an error message.
Re: [O] Changing the font family in HTML export
This solved the problem. However, as you pointed out, in case I want to publish/share this generated html, I have to send as well another file, and it is not longer self contained. In the automatically, generated html, there is a section at the beginning: --==--
Re: [O] Changing the font family in HTML export
On Tue, 28 Jun 2011 11:00:43 +0200, Dror Atariah wrote: > This solved the problem. However, as you pointed out, in case I want to > publish/share this generated html, I have to send as well another file, and > it is not longer self contained. In the automatically, generated html, there > is a section at the beginning: > --==-- >
Re: [O] Org-mode is not able to manage complex calendar events
Hi Karl, Karl Voit writes: > Although this is mentioned in chapter 2 of the Org-mode manual, I > strongly urge to mention this in section 8.3.2 «Repeated tasks»[1] > too! > > Where can I place this wish? for your next wish -- one that is not already accomplished :) -- please create a new thread with your wish as the subject of the email. Org community is very email-centric, and everything that eases the way I can stumble on wishes will help us accomplish them. Thanks! -- Bastien
Re: [O] ob-lilypond
Hi Eric > Eric Schulte gmail.com> writes: > > Hi Martyn, > > This looks great, I look forward to testing it out, although my music > composition experience is limited to using Finale in a high-school music > theory class. > > It sounds like your plan is to keep this on github during the first > trial and debugging stages. At some point I would love to include this > into the Org-mode core. > Thanks - I'm no LilyPond expert myself, and so a heads-up from a more proficient LilyPond user would be great. Likewise the ins and outs of LilyPond-mode. That said, it is working well for me and my use-case, and it is great to be generating music and score out of org-mode - it feels a good fit, which is testament to the flexability of org-babel and org-mode. > Part of me is tempted to push for immediate integration so that this is > released with Emacs24 (we could push bug fixes throughout the fall), > however this may be too much code for just before an Org-mode release. > > Thanks for sharing! -- Eric > I'll leave that decision to you, but certainly if the software is useful to others, I am happy to see it distributed. Actually, I only recently discovered how busy Lilypond development is, so there must be potential users out there. Perhaps I should bite the bullet and approach the Lilypond user mailing list to see if there is any interest there? Regards Martyn > Martyn Jago btinternet.com> writes: <...> >
Re: [O] a window with my agenda at all times
dmg writes: > here is a patch worg (org-hacks.org) describing the hack. > > Hopefully somebody with write access to can commit it. Applied, thanks. -- Bastien
Re: [O] Changing the font family in HTML export
Dror Atariah writes: > I'm trying to change the font used when exporting .org to .html. (setq org-export-html-style-include-default nil) (setq org-export-html-style ...) HTH -- Bastien
Re: [O] patch for doc string typos in org-mobile.el
Hi Stephen, Stephen Eglen writes: > --- org-mobile.el~2010-04-03 23:26:09.0 +0100 > +++ org-mobile.el 2011-06-28 09:47:17.0 +0100 > @@ -86,12 +86,12 @@ >:type 'file) > > (defcustom org-mobile-force-id-on-agenda-items t > - "Non-nil means make all agenda items carry and ID." > + "Non-nil means make all agenda items carry an ID." >:group 'org-mobile >:type 'boolean) > > (defcustom org-mobile-force-mobile-change nil > - "Non-nil means, force the change made on the mobile device. > + "Non-nil means force the change made on the mobile device. > So even if there have been changes to the computer version of the entry, > force the new value set on the mobile. > When nil, mark the entry from the mobile with an error message. The patch doesn't apply, these typos have been fixed long ago I guess. Please always try to test your patches against the latest git version of Org! Thanks, -- Bastien
Re: [O] [dev] footnotes improvements
Hi Nicolas, Nicolas Goaziou writes: > I've made some additional changes to the footnote branch, and fixed > a merge conflict due to a recent patch. > > Since Org 7.6 is about to be released, I'd appreciate if someone using > footnotes could test it and report back the results here. If some > serious problem arises, its integration will be delayed until 7.7. Thanks a lot for this -- I did some preliminary testing and things work smoothly so far. -- Bastien
Re: [O] Changing the font family in HTML export
On Tue, 28 Jun 2011 11:18:58 +0200, Pieter Praet wrote: > On Tue, 28 Jun 2011 11:00:43 +0200, Dror Atariah wrote: > > This solved the problem. However, as you pointed out, in case I want to > > publish/share this generated html, I have to send as well another file, and > > it is not longer self contained. In the automatically, generated html, > > there is a section at the beginning: > > --==-- > >
Re: [O] ob-lilypond
Hi Martyn, Martyn Jago writes: > Actually, I only recently discovered how busy Lilypond development is, > so there must be potential users out there. Indeed -- Lilypond is an old GNU project, I guess there are many Emacs gnusers. I would love to include ob-lilypond.el in the next release, it adds a nice functionality and cannot break anything. Thanks! -- Bastien
Re: [O] [PATCH] org-crypt: make org-decrypt disable auto-save-mode (configurable)
Hi Pieter, Pieter Praet writes: > As auto-save-mode can only cause leakage when there's actual decrypted > data lying around, don't check for it (and potentially cause annoyance) > on init, but only when org-decrypt-entry is called. Applied, thanks for this! -- Bastien
Re: [O] [PATCH] org-crypt: only warn about auto-save-mode when running org-decrypt
Hi Pieter, Pieter Praet writes: > 2 lessons I've learned today: > - DON'T test this stuff in a *scratch* buffer (seriously...) > - DO consume sufficient quantities of coffee (IOW, org-encrypt-entries > doesn't encrypt entries unless they're *tagged* to be) :) >> I'm not confident in disabling auto-save-mode globally by default, this >> would surprise users -- even with a **BiG WaRnInG** message. > > No worries, it's buffer-local. > > And I've now changed the default to "ask first, shoot in the foot > later". This is good. Thanks! -- Bastien
Re: [O] ob-lilypond
Bastien writes: > Indeed -- Lilypond is an old GNU project, I guess there are many Emacs > gnusers. I would love to include ob-lilypond.el in the next release, it > adds a nice functionality and cannot break anything. I forgot to mention that I leave this decision to Eric, of course. -- Bastien
Re: [O] org-mode documentation question
Hi Jude, Jude DaShiell writes: > I just checked with make targets and the Makefile has no rule to show > available targets. Such a rule would give builders a clue as to what > additional possibilities exist with the Makefile if it existed. Can you provide a patch? -- Bastien
[O] How to place a feature wish (was: Org-mode is not able to manage complex calendar events)
* Bastien wrote: > Hi Karl, Hi! > for your next wish -- one that is not already accomplished :) -- please > create a new thread with your wish as the subject of the email. > > Org community is very email-centric, and everything that eases the way I > can stumble on wishes will help us accomplish them. Sorry, I should have thought about that because I am already aware of this fact. You are absolutely right. -- Karl Voit
Re: [O] Changing the font family in HTML export
Hi,
The tips you have received from others about customizing various
variables are likely to be what you want (will work for all your
documents). But for completeness' sake: to change things on a
file-by-file basis, you can do it Manuel's way, but without an
external stylesheet, like this:
#+STYLE:html { font-family: Helvetica, sans-serif; font-size:
12pt; }
Your custom CSS is included in the HEAD of the generated document,
after the default CSS, which it overrides.
Yours,
Christian
On 6/28/11 11:00 AM, Dror Atariah wrote:
This solved the problem. However, as you pointed out, in case I want to
publish/share this generated html, I have to send as well another file, and it
is not longer self contained. In the automatically, generated html, there is a
section at the beginning:
--==--
Re: [O] ob-lilypond
Hi, I'm thrilled that Lilypond has been added to Babel, grateful for the extra thought given to Mac users -- and completely bowled over by your demos! Rather than put together complex scores or generate arpeggios the literate programming way, though, all I'd like to do is to easily include simple snippets of music notation in Org documents (elaboration follows). So please consider this a polite request to bump up "Consider the option to embed resultant partial musical output into org file" from SOMEDAY to TODO in your task list... Use cases: - Self-contained documentation, e.g. using Org to author a text like the Lilypond documentation: much prose with code examples and the results of those examples interspersed. - Writing a musicology paper, with captioned and cross-referenced examples (not /my/ use case, but someone might...) - Putting together a simple song booklet, such as for a summer camp, with lyrics and possibly illustrations. (This is my main interest.) Ways to do it: One (imperfect) solution would be a header argument to just surround the exported content of Lilypond blocks with the appropriate HTML tags / LaTeX environment for lilypond-book to act on, and perhaps a post-processing step to automatically call lilypond-book on the exported document. I can probably set up something like this for myself. But much better, IMO, would be a way to `evaluate' a single Lilypond block and get #+RESULTS with a link to a PNG representing just that snippet of music. The snippet would then show up in subsequent exports as an included graphic without any post-processing, and could also be viewed in-buffer with `C-c C-x C-v'. (For my money, this and not `tangle all' would be the intuitive use of `C-c C-c' on a block, but I understand how your choice makes sense for other uses.) Yours, Christian On 6/27/11 3:00 PM, Martyn Jago wrote: Hi This is an invitation to try / test ob-lilypond - enabling LilyPond Score Generation / Arrangement from within org-mode. Available on Github at https://github.com/mjago/ob-lilypond This is a beta release, but includes examples, instructions, and tests, and has been tested on OSX and nix. Any further testing would be helpful. Following is the readme.org file which is rendered correctly on Github... ---> * Emacs Org Babel LilyPond Mode ** Purpose Allow LilyPond Score Generation to take place within Emacs Org-mode using literate programming principles. ** Examples Several examples are included *** Misty (Jazz Standard utilising org-mode to organise voice and other data) - Here is an example Org LilyPond File]] exported as HTML - Resultant Score exported in pdf format - Generated Score export of individual Pages (png) *** Modal Cycles (Utilises org-babel and noweb to generate notes) - Generated Score - Generated Midi File *** Modal Cycles 2 (Utilises org-babel and noweb to generate notes) - Generated Score - Generated Midi File *** Modes in the Key of C (another example of polyglot lilypond programming) - Generated Score Generated MIDI File ** Features - Optional Automated LilyPond Compilation following the "Tangling" of a "Literate Org LilyPond" file - Optional Automated display of resultant Musical Score following compilation - Optional Automated playing of the resultant MIDI file following compilation - Highlights syntax errors in Org file following a failed compilation - Integrates with LilyPond-Mode - Cross-Platform (OSX, nix, win32) ** Usage *** Compiling lilypond source Hitting 'C-c C-c' within a lilypond block initiates ly-tangle (tangling of all lilypond blocks). Depending on the feature settings, ob-lilypond will then either display a pdf of the score, play the generated midi file, both, or neither. 'M-x ly-tangle' can also be called from anywhere in the file and can be tied to a function key with something like... #+begin_src emacs-lisp (global-set-key [f8] 'ly-dev-tangle) #+end_src *** Commands Some commands are included to quickly disable certain post-tangle activities... - ly-toggle-midi-play (toggle whether midi will be played following a successful compilation) - ly-toggle-pdf-display (toggle whether pdf will be displayed following a successful compilation) NOTE:- If using Timidity for midi playback, kill the midi stream with C-g in Emacs ** Setup (add to emacs init file) *** Cloning ob-lilypond The Files need to be downloaded to your relevant dotfiles directory... #+BEGIN_SRC sh git clone https://github.com/mjago/ob-lilypond.git ob-lilypond #+END_SRC *** Emacs Initialisation file setup Require library... #+BEGIN_SRC emacs-lisp (add-to-list 'load-path (concat dotfiles-dir "ob-lilypond/lib")) (require 'ob-lilypond) #+END_SRC Add lilypond to your list of babel languages... #+BEGIN_SRC emacs-lisp (org-babel-do-load-languages 'org-babel-load-languages '((ruby . t) (C . t) (emacs-
Re: [O] Problem with autoloads
On 28 Jun 2011, Michael Markert wrote: > [1 ] > On 28 Jun 2011, Nick Dokos wrote: >> >> >> Suvayu and I worked on this in an email exchange: it turns out that >> Michael was right in that (recent) emacs 24 is indeed the culprit. In >> particular, the variable generated-autoload-file is now initialized >> to nil: >> >> , >> | (defvar generated-autoload-file nil >> | "File into which to write autoload definitions. >> | A Lisp file can set this in its local variables section to make >> | its autoloads go somewhere else. >> | >> | If this is a relative file name, the directory is determined as >> | follows: >> | - If a Lisp file defined `generated-autoload-file' as a >> |file-local variable, use its containing directory. >> | - Otherwise use the \"lisp\" subdirectory of `source-directory'. >> | >> | The autoload file is assumed to contain a trailer starting with a >> | FormFeed character.") >> ` >> >> whereas before (e.g. in the version of emacs 24 that I'm running: GNU >> Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of >> 2011-04-13) it was initialized to "loaddefs.el": >> >> >> , | (defvar generated-autoload-file "loaddefs.el" | "*File >> \\[update-file-autoloads] puts autoloads into. | A `.el' file can >> set this in its local variables section to make its | autoloads go >> somewhere else. The autoload file is assumed to contain a | trailer >> starting with a FormFeed character.") ` >> >> The particular value is not that important: the fact that it was >> a relative file name is, as indicated by the comment above. >> >> I think the following patch fixes it and does not break any earlier >> versions of org. Suvayu, Michael (and anybody else who cares to try >> it): would you mind checking and reporting back? With this patch for the makefile I can get it running: -- --- diff --git a/Makefile b/Makefile index 239ab2e..2d1d324 100644 --- a/Makefile +++ b/Makefile @@ -230,12 +230,11 @@ autoloads: lisp/org-install.el lisp/org-install.el: $(LISPFILES0) Makefile $(BATCH) --eval "(require 'autoload)" \ - --eval '(find-file "org-install.el")' \ + --eval '(find-file "lisp/org-install.el")' \ --eval '(erase-buffer)' \ - --eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote ($(LISPFILES0' \ + --eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote ($(LISPF' \ --eval '(insert "\n(provide (quote org-install))\n")' \ --eval '(save-buffer)' - mv org-install.el lisp doc/org: doc/org.texi (cd doc && $(MAKEINFO) --no-split org.texi -o org) -- --- I have some problems with writing org-install directly but otherwise autoload.el generates lisp/ autoloads (with LISPFILES0) or fails to find (with LISPF). But because org-install is automatically generated I don't consider them as such grave in the case it kills the old file and leaves garbage (maybe use a backup file?). I tried several things that all failed: 1. Let-bind `generated-autoload-load-name' per run 2. add `generated-autoload-file' to the elisp files 3. 1. with LISPFILES0 4. ... I'll spare you the rest. :( Michael pgpTlcpRH8mJ4.pgp Description: PGP signature
Re: [O] worg page problem?
Hi Nick, Nick Dokos writes: > But it's not clear to me why \and and \or appear in the list: as far > as LaTeX is concerned, they are not symbols (afaik): they are boolean > operators in the ifthen package. Similarly for \divide which is an > arithmetic operator in the calc package. I removed \and \or and \divide. > OTOH, there are several symbols which seem to be misspelled: > > \Agrav\Agrav-> should be \Agrave > \Aacut\Aacut-> should be \Aacute > \Atild\Atild-> should be \Atilde I fixed those. > Â \Acirc This I don't understand -- what is the error? -- Bastien
Re: [O] Changing the font family in HTML export
On Jun 28, 2011, at 14:10 PM, Christian Moe wrote:
> Hi,
>
> The tips you have received from others about customizing various variables
> are likely to be what you want (will work for all your documents). But for
> completeness' sake: to change things on a file-by-file basis, you can do it
> Manuel's way, but without an external stylesheet, like this:
>
> #+STYLE:html { font-family: Helvetica, sans-serif; font-size: 12pt;
> }
>
> Your custom CSS is included in the HEAD of the generated document, after the
> default CSS, which it overrides.
This was most helpful actually! Thanks!
>
> Yours,
> Christian
>
> On 6/28/11 11:00 AM, Dror Atariah wrote:
>> This solved the problem. However, as you pointed out, in case I want to
>> publish/share this generated html, I have to send as well another file, and
>> it is not longer self contained. In the automatically, generated html, there
>> is a section at the beginning:
>> --==--
>>
Re: [O] ob-lilypond
this is fantastic :) org mode is becoming like the Jupiter of the emacsian solar system. On Tue, Jun 28, 2011 at 8:11 AM, Christian Moe wrote: > Hi, > > I'm thrilled that Lilypond has been added to Babel, grateful for the extra > thought given to Mac users -- and completely bowled over by your demos! > > Rather than put together complex scores or generate arpeggios the literate > programming way, though, all I'd like to do is to easily include simple > snippets of music notation in Org documents (elaboration follows). > > So please consider this a polite request to bump up "Consider the option to > embed resultant partial musical output into org file" from SOMEDAY to TODO > in your task list... > > Use cases: > > - Self-contained documentation, e.g. using Org to author a text like the > Lilypond documentation: much prose with code examples and the results of > those examples interspersed. > > - Writing a musicology paper, with captioned and cross-referenced examples > (not /my/ use case, but someone might...) > > - Putting together a simple song booklet, such as for a summer camp, with > lyrics and possibly illustrations. (This is my main interest.) > > Ways to do it: > > One (imperfect) solution would be a header argument to just surround the > exported content of Lilypond blocks with the appropriate HTML tags / LaTeX > environment for lilypond-book to act on, and perhaps a post-processing step > to automatically call lilypond-book on the exported document. I can probably > set up something like this for myself. > > But much better, IMO, would be a way to `evaluate' a single Lilypond block > and get #+RESULTS with a link to a PNG representing just that snippet of > music. The snippet would then show up in subsequent exports as an included > graphic without any post-processing, and could also be viewed in-buffer with > `C-c C-x C-v'. (For my money, this and not `tangle all' would be the > intuitive use of `C-c C-c' on a block, but I understand how your choice > makes sense for other uses.) > > Yours, > Christian > > > > On 6/27/11 3:00 PM, Martyn Jago wrote: >> >> Hi >> >> This is an invitation to try / test ob-lilypond - enabling LilyPond >> Score Generation / Arrangement from within org-mode. >> >> Available on Github at https://github.com/mjago/ob-lilypond >> >> This is a beta release, but includes examples, instructions, and >> tests, and has been tested on OSX and nix. >> >> Any further testing would be helpful. >> >> Following is the readme.org file which is rendered correctly on >> Github... >> >> ---> >> >> * Emacs Org Babel LilyPond Mode >> ** Purpose >> Allow LilyPond Score Generation to take place within Emacs Org-mode >> using literate programming principles. >> >> ** Examples >> Several examples are included >> *** Misty (Jazz Standard utilising org-mode to organise voice and other >> data) >> - Here is an example Org LilyPond File]] exported as HTML >> - Resultant Score exported in pdf format >> - Generated Score export of individual Pages (png) >> *** Modal Cycles (Utilises org-babel and noweb to generate notes) >> - Generated Score >> - Generated Midi File >> *** Modal Cycles 2 (Utilises org-babel and noweb to generate notes) >> - Generated Score >> - Generated Midi File >> *** Modes in the Key of C (another example of polyglot lilypond >> programming) >> - Generated Score >> Generated MIDI File >> >> ** Features >> - Optional Automated LilyPond Compilation following the "Tangling" >> of a "Literate Org LilyPond" file >> - Optional Automated display of resultant Musical Score following >> compilation >> - Optional Automated playing of the resultant MIDI file following >> compilation >> - Highlights syntax errors in Org file following a failed compilation >> - Integrates with LilyPond-Mode >> - Cross-Platform (OSX, nix, win32) >> >> ** Usage >> >> *** Compiling lilypond source >> Hitting 'C-c C-c' within a lilypond block initiates ly-tangle (tangling of >> all >> lilypond blocks). Depending on the feature settings, ob-lilypond will >> then either display a pdf of the score, play the generated midi file, >> both, or neither. >> >> 'M-x ly-tangle' can also be called from anywhere in the file >> and can be tied to a function key with something like... >> >> #+begin_src emacs-lisp >> >> (global-set-key [f8] 'ly-dev-tangle) >> >> #+end_src >> >> *** Commands >> >> Some commands are included to quickly disable certain post-tangle >> activities... >> - ly-toggle-midi-play (toggle whether midi will be played following a >> successful compilation) >> - ly-toggle-pdf-display (toggle whether pdf will be displayed following >> a successful compilation) >> >> >> NOTE:- If using Timidity for midi playback, kill the midi stream with >> C-g in Emacs >> >> ** Setup (add to emacs init file) >> *** Cloning ob-lilypond >> >> The Files need to be downloaded to your relevant dotfiles directory... >> >> #+BEGIN_SRC sh >> >> git clone http
Re: [O] Errors with current version (git pull'ed at 10:30 CET)
Hi Sebastien, "Sebastien Vauban" writes: > Just want to report 2 errors I got with the latest version of Org-mode. I'm > sure (with 5 nine, ie 99.999%) that I did not change anything in my setup > which could explain this. > > Both errors were generated after a fresh Emacs startup. > > * First > > I try to open the file Work.org in which I had an open clock, on task "TODO > Organize work" (misc for project organization, etc.). Can you send a minimal .org file to help reproduce the problem? > * Second > > I try to write a mail -- this launches Org thanks to autoloads, here for > correctly highlighting code blocks in Gnus. This looks like a problem with Babel -- can you help narrow down the problem a bit more? Thanks! -- Bastien
Re: [O] Documentation suggestion re: buffers containing crypted entries
I think we can disable auto-save locally using file variables, but what org-crypt seem to check is auto-save-default and its value probably won't change when auto-save is disabled locally. -- Darlan Cavalcante At Mon, 27 Jun 2011 18:56:54 +0200, Bastien wrote: > > Hi Eric, > > Eric S Fraga writes: > > > The question is where should this information be most appropriate to > > appear. In my view, this should be in the documentation (highlighted > > etc), not in the Emacs mini-buffer! I don't know enough texi (any at > > all, actually) so cannot suggest a patch. However, I would suggest that > > the warning that is in the code be moved into the entry for org-crypt.el > > in the info manual. > > I did so -- I added this to the config example in org.texi: > > , > | (setq auto-save-default nil) > | ;; Auto-saving does not cooperate with org-crypt.el: so you need > | ;; to turn it off if you plan to use org-crypt.el quite often. > | ;; Otherwise, you'll get an (annoying) message each time you > | ;; start Org. > | > | ;; To turn it off only locally, you can insert this: > | ;; > | ;; # -*- buffer-auto-save-file-name: nil; -*- > ` > > > Or, as originally proposed, the warning in the code > > could be wrapped in a customisable variable but this seems like overkill > > to me. > > To me too, unless we have a clean way to disable auto-save-mode locally. > > > Just my 2¢! > > 2thx! > > -- > Bastien >
Re: [O] [Orgmode] Links to datestamped headings broken?
Simon Guest writes: > I think the info file section 4.4. Handling Links would benefit from a > note on the fact that Org removes the timestamp, and how to work > around this. Done, thanks. -- Bastien
Re: [O] [PATCH] Org-Velocity incremental display
Hi Paul, "Paul M. Rodriguez" writes: > This patch makes Org-Velocity display search results incrementally, and > implements a more general approach to completion based on dabbrev. The > documentation has also been rewritten. Applied, thanks a lot! -- Bastien
Re: [O] ob-lilypond
This is very exciting. I use LilyPond a lot for various projects and I think integration with orgmode is an obvious solution to a problem I hope to find very soon! LilyPond is largely written in Scheme and I'm pretty sure a few of the devs use emacs. There are some interesting emacs/Lily projects around, not least Nicolas Sceaux' lyqi-mode which does some pretty groovy things, including midi keyboard input via rumor. I'm looking forward to having a chance to play with this. Well done, and thank you! Cameron Horsburgh blog: http://spiritcry.wordpress.com On 28 June 2011 19:38, Martyn Jago wrote: > > Hi Eric > >> Eric Schulte gmail.com> writes: >> >> Hi Martyn, >> >> This looks great, I look forward to testing it out, although my music >> composition experience is limited to using Finale in a high-school music >> theory class. >> >> It sounds like your plan is to keep this on github during the first >> trial and debugging stages. At some point I would love to include this >> into the Org-mode core. >> > > Thanks - I'm no LilyPond expert myself, and so a heads-up from a more > proficient LilyPond user would be great. Likewise the ins and outs of > LilyPond-mode. That said, it is working well for me and my use-case, and > it is great to be generating music and score out of org-mode - it feels a > good fit, which is testament to the flexability of org-babel and org-mode. > >> Part of me is tempted to push for immediate integration so that this is >> released with Emacs24 (we could push bug fixes throughout the fall), >> however this may be too much code for just before an Org-mode release. >> >> Thanks for sharing! -- Eric >> > > I'll leave that decision to you, but certainly if the software is useful > to others, I am happy to see it distributed. Actually, I only recently > discovered how busy Lilypond development is, so there must be potential > users out there. Perhaps I should bite the bullet and approach the Lilypond > user mailing list to see if there is any interest there? > > Regards > > Martyn > > >> Martyn Jago btinternet.com> writes: > <...> >> > > > > > >
Re: [O] Bug: org-time-stamp loses repeater interval
* Bastien wrote: > Karl Voit writes: > >> Same to me. Unfortunately I am using timestamps not only in the >> context of DEADLINE or SCHEDULED but also for events that should >> simply show up on the agenda (without deadline or scheduled >> timestamp at all). >> >> To me this *is* a bug since my expected behavior of org-time-stamp >> to modify an existing timestamp is different. > > It is now fixed in the latest git version. Please test and report, > if possible. I checked out d7c693c1ffe2ebf38604dd30fdd2f9d51a1c44d0 which should fix the problem and tested with «Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on rothera, modified by Debian» and «Org-mode version 7.5 (release_7.5.462.gd7c69)» created timestamp with «C-c .» <2011-06-28 Tue> modified with «C-c.» to wednesday: <2011-06-29 Wed> manually added repeater: <2011-06-29 Wed +1w> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater is lost :-( created another one with warning period: <2011-06-28 Tue -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> warning period is lost :-( created another one with repeater and warning period: <2011-06-28 Tue +1w -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater and warning period is lost :-( -- Karl Voit
Re: [O] Errors with current version (git pull'ed at 10:30 CET)
I'm also having problems with recent changes (since yesterday, but it has
been a few days since my last update before that) that may be due to the
same cause.
It seems to be related to the library of babel.
I can reproduced with the following steps
--8<---cut here---start->8---
1. Start Emacs with:
: "Emacs -Q"
2. Add the folder where I pulled org-mode (evaluate the code below in my
case):
: (let ((default-directory "~/Org-mode-dev/org-mode"))
: (normal-top-level-add-to-load-path '("."))
: (normal-top-level-add-subdirs-to-load-path)
: )
3. Put the code below in an org file, for instance
"~/Muse/org/my_library_of_babel.org"
: #+source: identity(var)
: #+begin_src python
: return var
: #+end_src
4. Ingest this file in the library of babel with
: (org-babel-lob-ingest "~/Muse/org/my_library_of_babel.org")
--8<---cut here---end--->8---
I get an error with the back-trace below
--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument consp nil)
#[(pair) "@\306=\203] mapc(#[(pair) "@\306=\203] #[(plist)
"\301\302\"\207" [plist mapc #[(pair) "@\306=\203] mapc(#[(plist)
"\301\302\"\207" [plist mapc #[(pair) "@\306=\203]
org-babel-merge-params(((:var . "var")) ((:comments . "") (:shebang . "")
(:cache . "no") (:padline . "") (:noweb . "no") (:tangle . "no") (:exports .
"code") (:results . "replace") (:padnewline . "yes") (:hlines . "no") (:session
. "none")))
org-babel-get-src-block-info(light)
org-babel-lob-ingest("~/Muse/org/my_library_of_babel.org")
eval((org-babel-lob-ingest "~/Muse/org/my_library_of_babel.org") nil)
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)
--8<---cut here---end--->8---
--
Darlan Cavalcante
At Tue, 28 Jun 2011 15:02:01 +0200,
Bastien wrote:
>
> Hi Sebastien,
>
> "Sebastien Vauban" writes:
>
> > Just want to report 2 errors I got with the latest version of Org-mode. I'm
> > sure (with 5 nine, ie 99.999%) that I did not change anything in my setup
> > which could explain this.
> >
> > Both errors were generated after a fresh Emacs startup.
> >
> > * First
> >
> > I try to open the file Work.org in which I had an open clock, on task "TODO
> > Organize work" (misc for project organization, etc.).
>
> Can you send a minimal .org file to help reproduce the problem?
>
> > * Second
> >
> > I try to write a mail -- this launches Org thanks to autoloads, here for
> > correctly highlighting code blocks in Gnus.
>
> This looks like a problem with Babel -- can you help narrow down the
> problem a bit more?
>
> Thanks!
>
> --
> Bastien
>
Re: [O] worg page problem?
Bastien wrote: > > Â \Acirc > > This I don't understand -- what is the error? > No error - it just got caught up in the cut and paste and I didn't delete it. Sorry. Nick
Re: [O] Bug: org-time-stamp loses repeater interval
Karl Voit writes: > -> repeater and warning period is lost :-( I cannot reproduce this. Did you take care of loading the freshly pulled Org version? -- Bastien
Re: [O] Errors with current version (git pull'ed at 10:30 CET)
Hi Bastien, Bastien wrote: > "Sebastien Vauban" writes: > >> Just want to report 2 errors I got with the latest version of Org-mode. I'm >> sure (with 5 nine, ie 99.999%) that I did not change anything in my setup >> which could explain this. >> >> Both errors were generated after a fresh Emacs startup. >> >> * First >> >> I try to open the file Work.org in which I had an open clock, on task "TODO >> Organize work" (misc for project organization, etc.). > > Can you send a minimal .org file to help reproduce the problem? > >> * Second >> >> I try to write a mail -- this launches Org thanks to autoloads, here for >> correctly highlighting code blocks in Gnus. > > This looks like a problem with Babel -- can you help narrow down the problem > a bit more? Very difficult to send an ECM -- otherwise, I'd have done it since this morning -- as the errors I get are not always exactly the same. Though, I now can tell that adding the following Org file to the list of agenda files (and restarting Emacs) *does* make a difference, and is at least the source of the second problem. Note -- This file is part of my agenda files for months, and has been unchanged for many, many weeks. Why it now is a problem is very obscure to me. The disturbing file: --8<---cut here---start->8--- #+TITLE: Babel ECM #+DATE: 2011-06-28 #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en_US #+LaTeX_CLASS: mcreport #+LaTeX_CLASS_OPTIONS: [final] #+BABEL: :eval never :engine msosql :cmdline -S cauchy -U sa -P LpmdlP -d pfi-paiestag -n -w 700 :results output :exports both :noweb yes * Introduction This library is an extensible *collection of* ready-made *code blocks* for handling common tasks. * "Generic" Transact-SQL ** Add a column into a table #+srcname: add-column-in-table(table, column, type, nullability) #+begin_src sql -- add column `$column' (if column does not exist yet) IF NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = '$table' AND COLUMN_NAME = '$column') BEGIN ALTER TABLE $table ADD $column $type $nullability END #+end_src --8<---cut here---end--->8--- Having it in org-agenda-files causes troubles, such as this other error: --8<---cut here---start->8--- if: Agenda file c:/home/sva/Personal/House.org is not in `org-mode' --8<---cut here---end--->8--- This error message occurred a couple of times to me, over the last few weeks. Today, I got it many times. I now am aware that a couple of colleagues already saw it as well. Current workaround: restart Emacs (and, often, the problem is "solved" by itself). Very disturbing. Can anyone confirm my observation by adding the above file in his org-agenda ones, and restarting Emacs? Thanks. Best regards, Seb -- Sebastien Vauban
Re: [O] Problem with autoloads
Suvayu Ali wrote: > Hi Nick, > > On Tue, 28 Jun 2011 08:56:59 +0200 > Michael Markert wrote: > > > Hi Nick, > > > > thanks for looking into it. > > > > But the patch doesn't work. I think that stems from the fact, that the > > first thing `generate-file-autoloads' does is to bind it new: > > I can confirm, I still get the error: > > Cannot open load file: lisp/org > OK, thanks to both you and Michael for checking: back to the drawing board. Things would be easier if I could reproduce it: I'll install emacs latest and try again. Nick
Re: [O] worg page problem?
Nick Dokos writes: > No error - it just got caught up in the cut and paste and > I didn't delete it. Sorry. All right, no problem! -- Bastien
Re: [O] Problem with autoloads
Nick Dokos wrote: > Suvayu Ali wrote: > > > Hi Nick, > > > > On Tue, 28 Jun 2011 08:56:59 +0200 > > Michael Markert wrote: > > > > > Hi Nick, > > > > > > thanks for looking into it. > > > > > > But the patch doesn't work. I think that stems from the fact, that the > > > first thing `generate-file-autoloads' does is to bind it new: > > > > I can confirm, I still get the error: > > > > Cannot open load file: lisp/org > > > > OK, thanks to both you and Michael for checking: back to the drawing > board. Things would be easier if I could reproduce it: I'll install > emacs latest and try again. > I cannot reproduce it even with latest org, latest emacs: org-install.el makes properly with autoloads that look like this: , | (autoload 'org-mode "org" "\ | Outline-based notes management and organizer, alias | \"Carsten's outline-mode for keeping track of everything.\" ` No lisp/org anywhere in sight (except in comments). I also tried with Michael's patch and it still works for me, so if it fixes things for him and Suvayu, it should probably be applied (but I wish I understood what goes wrong and how the patch fixes it). Nick
Re: [O] Bug: org-time-stamp loses repeater interval
* Bastien wrote: > Karl Voit writes: > >> -> repeater and warning period is lost :-( > > I cannot reproduce this. > Did you take care of loading the freshly pulled Org version? «git pull» on the master and then I re-started my Emacs. I thought this should be enough ... Or is there any setting that can conflict and produce the behavior of my Org-mode? -- Karl Voit
Re: [O] Bug: org-time-stamp loses repeater interval
Bastien wrote: > Karl Voit writes: > > > -> repeater and warning period is lost :-( > > I cannot reproduce this. > > Did you take care of loading the freshly pulled Org version? > I can't reproduce this either. Both repeaters and warning periods are preserved with C-c . (and with C-c C-s and C-c C-d as well). Nick
Re: [O] Bug: org-time-stamp loses repeater interval
Karl Voit writes: > «git pull» on the master and then I re-started my Emacs. I thought > this should be enough ... If you byte-compiled the previous version of Org, Emacs will load this one, not the fresh one. > Or is there any setting that can conflict and produce the behavior > of my Org-mode? Try M-x org-reload RET to explicitely reload Org. -- Bastien
Re: [O] Bug: org-time-stamp loses repeater interval
Karl Voit wrote: > * Bastien wrote: > > Karl Voit writes: > > > >> -> repeater and warning period is lost :-( > > > > I cannot reproduce this. > > Did you take care of loading the freshly pulled Org version? > > «git pull» on the master and then I re-started my Emacs. I thought > this should be enough ... > > Or is there any setting that can conflict and produce the behavior > of my Org-mode? > Do you use compiled (.elc) files? If so, you need to "make clean; make" before restarting. You can also check with M-x locate-library RET org RET to see what would get loaded. Nick
Re: [O] Bug: org-time-stamp loses repeater interval
After re-compiling my elc files, I have now the following behavior: * Karl Voit wrote: > > created timestamp with «C-c .» > <2011-06-28 Tue> > > modified with «C-c.» to wednesday: > <2011-06-29 Wed> > > manually added repeater: > <2011-06-29 Wed +1w> > > «C-c .» + click on Jul 5th: <2011-07-05 Tue +1w> ... which is the fix to the original bug. Thanks! :-) > created another one with warning period: > <2011-06-28 Tue -1d> > > «C-c .» + click on Jul 5th: > <2011-07-05 Tue> > > -> warning period is lost :-( The warning period still gets deleted though :-( -- Karl Voit
Re: [O] Bug: org-time-stamp loses repeater interval
* Nick Dokos wrote: > > Do you use compiled (.elc) files? Not intentionally. > If so, you need to "make clean; make" before restarting. You can > also check with This one did the trick. Thanks! -- Karl Voit
Re: [O] Problem with autoloads
Michael Markert wrote: > On 28 Jun 2011, Nick Dokos wrote: > > > > > > I cannot reproduce it even with latest org, latest emacs: > > org-install.el makes properly with autoloads that look like this: > > > > , > > | (autoload 'org-mode "org" "\ > > | Outline-based notes management and organizer, alias > > | \"Carsten's outline-mode for keeping track of everything.\" > > ` > > > > No lisp/org anywhere in sight (except in comments). > > That sounds great. I'm running on Julien's emacs-snapshot so I'm not > using an latest version. > > > I also tried with Michael's patch and it still works for me, so if > > it fixes things for him and Suvayu, it should probably be applied > > I didn't test for compability and if the problem is only temporarily it > should not be applied. > > > (but I wish I understood what goes wrong and how the patch fixes it). > > I try to summarize (sorry for being incomprehensible in the other mail > -- it's to hot here): > > Problem: autoload.el generates file names with lisp/ prefix. For you and Suvayu, but not for me. It's the discrepancy that bothers me. > Solution: > - We generate the autoloads file in the org directory. > - To get valid file names we use the non-prefixed file names. I would like to understand the root cause. Nick
Re: [O] Problem with autoloads
On 28 Jun 2011, Nick Dokos wrote: > > > I cannot reproduce it even with latest org, latest emacs: > org-install.el makes properly with autoloads that look like this: > > , > | (autoload 'org-mode "org" "\ > | Outline-based notes management and organizer, alias > | \"Carsten's outline-mode for keeping track of everything.\" > ` > > No lisp/org anywhere in sight (except in comments). That sounds great. I'm running on Julien's emacs-snapshot so I'm not using an latest version. > I also tried with Michael's patch and it still works for me, so if > it fixes things for him and Suvayu, it should probably be applied I didn't test for compability and if the problem is only temporarily it should not be applied. > (but I wish I understood what goes wrong and how the patch fixes it). I try to summarize (sorry for being incomprehensible in the other mail -- it's to hot here): Problem: autoload.el generates file names with lisp/ prefix. Solution: - We generate the autoloads file in the org directory. - To get valid file names we use the non-prefixed file names. Michael pgp9noFQQ5Zm6.pgp Description: PGP signature
Re: [O] [PATCH] Introduce CLOCK_INTO_DRAWER property like the existing LOG_INTO_DRAWER
Hi Achim, Achim Gratz writes: > Bastien writes: >> Applied, thanks a lot. Let take at least one day to let people test >> this patch -- feedback welcome. > > Here's a template I've been using for testing. Try it with different > settings for both global and file local variables. Works well here, thanks for sharing this. -- Bastien
Re: [O] Typo in 'org-without-partial-completion'
Hi Paul, Paul Sexton writes: > I think there's an error in 'org-without-partial-completion' in org-macs.el. > The variable pc-mode gets bound to the value of partial-completion-mode - but > this is a VARIABLE (t if that mode is enabled). Funcalling the value of > the variable produces an error, unsurprisingly. This breaks insertion of > properties with 'org-set-property'. > > Fixing it involves quoting the the symbol as shown below: > > > (defmacro org-without-partial-completion (&rest body) >`(let ((pc-mode (and (boundp 'partial-completion-mode) > 'partial-completion-mode))) ; <-- quote added > (unwind-protect > (progn > (when pc-mode (funcall pc-mode -1)) > ,@body) > (when pc-mode (funcall pc-mode 1) You're right -- thanks for spotting this, and for the clear analysis. I've committed a patch. -- Bastien
Re: [O] ob-lilypond
Hi Cameron > Cameron Horsburgh gmail.com> writes: > > This is very exciting. I use LilyPond a lot for various projects and I > think integration with orgmode is an obvious solution to a problem I > hope to find very soon! > > LilyPond is largely written in Scheme and I'm pretty sure a few of the > devs use emacs. There are some interesting emacs/Lily projects around, > not least Nicolas Sceaux' lyqi-mode which does some pretty groovy > things, including midi keyboard input via rumor. I had come across lyqi-mode but haven't checked it out yet. Added to the TODO list. Thanks for the feedback. Regards Martyn
Re: [O] org-insert-link and partial-completion-mode incompatibility?
Hi Holger, Holger Wenzel writes: > in emacs 23.3 with the org-mode release_7.5-421-ge734e I experience an > incompatibility between org-insert-link and partial-completion-mode. This should be fixed now. Thanks, -- Bastien
Re: [O] [PATCH] org-latex: Convert quote marks in section headers
Hi Laurence, Lawrence Mitchell writes: > * lisp/org-latex.el (org-export-latex-fontify-headline): Convert > quotes to their LaTeX equivalents using > org-export-latex-quotation-marks. Applied, thanks! > It would appear to be so, though I'm not sure if the decision not > to convert quotation marks is a deliberate one. Although looking > at the commit logs, it would appear that it's probably an oversight. Yes, it was. -- Bastien
Re: [O] Make M-up and M-down transpose paragraphs in org buffers
Hi Paul, Paul Sexton writes: > By default, if used within ordinary paragraphs in org mode, M-up and M-down > transpose *lines* (not sentences). This was not useful to me. To me neither. > The following > code makes these keys transpose paragraphs, keeping the point at the start > of the moved paragraph. Behaviour in tables and headings is unaffected. It > would be easy to modify this to transpose sentences. I like it, and have a patch to integrate this directly in org-metaup and org-metadown. There is one problem though: when you try to move down a paragraph when it is followed by a list, Emacs doesn't understand the list should be treated as a paragraph. Any idea on how to circumvent this? Or should we live with this and implement the solution? Thanks for this idea, -- Bastien
Re: [O] exporting emphasised text (bold, italics etc.) in ORGTBL
Hi Benjamin,
Benjamin Slade writes:
> But what I was wondering is this: orgmode generally interprets *word*
> as bolding of "word" and /word/ as italicising of "word". So is there
> a way to make it export *word* as \textbf{word} and /word/ as \textit
> {word}, when using orgtbl.
Not for now, sorry.
--
Bastien
Re: [O] ob-lilypond
Hi Cameron > Hi, > > I'm thrilled that Lilypond has been added to Babel, grateful for the > extra thought given to Mac users -- and completely bowled over by your > demos! > > So please consider this a polite request to bump up "Consider the > option to embed resultant partial musical output into org file" from > SOMEDAY to TODO in your task list... Thanks for the encouraging comments! Status changed from SOMEDAY to TODO. > > But much better, IMO, would be a way to `evaluate' a single Lilypond > block and get #+RESULTS with a link to a PNG representing just that > snippet of music. The snippet would then show up in subsequent exports > as an included graphic without any post-processing, and could also be > viewed in-buffer with `C-c C-x C-v'. (For my money, this and not > `tangle all' would be the intuitive use of `C-c C-c' on a block, but I > understand how your choice makes sense for other uses.) > > Yours, > Christian > This is very doable since it is the first thing I tried on initial experimentation. I think I had some difficulty cropping the snippet (png) in that the result had no padding at all, but I'm guessing that can be overcome. Certainly with the use cases you suggest, the defaults would need to change, and C-c C-c would need to act as you describe, but that wouldn't be an issue if we can define seperate 'modes' for the different ways of working (I think for now the 'modes' can be considered mutually exclusive). Regards Martyn
[O] Capture from GNU screen to Org-mode (was: Email -> Org-mode: charset problem)
* David Maus wrote:
>
> As far as I know a lot, if not most, email messages are transfered in
> 7bit for backward compatibility reasons and getting things other than
> text/plain; charset=3Dus-ascii across the net via email requires a lot
> of things to consider (RFC2045-49 in all their glory).
Yes. The header is always 7-bit ASCII. The body has to be
interpreted by very advanced algorithms in order to show the various
types of content properly.
> So dumping the raw message won't help, you need functions for
> processing the raw message informaton.
I came to the very same conclusion. :-( I thought «formail» would be
able to handle charset for me.
> Here's an idea (or two).
Thanks for your ideas!
Those are perfectly good tips for someone who is using a MUA and
Org-mode on the same computer.
But my system is different since I am using «mutt»[1] as MUA
(running in a GNU screen[2] session) on a remote server (accessed by
ssh).
Org-mode is (only) running on my local machine since the (very slow)
root server is an old Debian stable one (with emacs21 only).
My personal solution for the moment is following system:
Since I am using GNU screen which has the ability to dump its screen
content (non graphical!) into a file, I wrote a shell script that
generates an Org-mode entry and appends it to the input.org which
will be synchronized over all my systems anyway (by cron and
unison[3] although dvcs-autosync[4] seems to be very handy too for
building your own Dropbox[5] alternative, respectively).
,[ *one* line from my .screenrc ]
| bind O eval "hardcopy_append off" "hardcopy
| $HOME/screen-capture.tmp" "screen sh
| $HOME/bin/add-screensnapshot-to-org.sh"
`
... this one creates a screenshot when I press «Ctrl-a O» in GNU
screen. Then «$HOME/screen-capture.tmp» gets filled with the screen
content (which is the start of an email or a usenet posting[6] or
similar - whichever is shown currently in GNU screen).
Then following script generates the (simple) Org-mode entry:
,[ $HOME/bin/add-screensnapshot-to-org.sh ]
| #!/bin/sh
| ## generates an org-file-entry from a screen capture file from GNU screen
|
| SCREENCONTENTFILE="$HOME/screen-capture.tmp"
| ORGFILE="$HOME/org-mode/inbox.org"
|
| ## not very elegant, I know:
| echo "* TODO screen "`date '+%Y-%m-%dT%H:%M'` >> ${ORGFILE}
| echo ":PROPERTIES:" >> ${ORGFILE}
| echo ":CREATED: <"`date '+%Y-%m-%d %a %H:%M'`">" >> ${ORGFILE}
| echo ":END:" >> ${ORGFILE}
| echo >> ${ORGFILE}
| echo "#+BEGIN_VERB" >> ${ORGFILE}
| cat "${SCREENCONTENTFILE}" >> ${ORGFILE}
| echo "#+END_VERB" >> ${ORGFILE}
| echo >> ${ORGFILE}
|
| #end
`
Probably this method could be handy for other users of GNU screen
and Org-mode too.
1. http://www.mutt.org/
2. https://secure.wikimedia.org/wikipedia/en/wiki/GNU_Screen
3. http://www.cis.upenn.edu/~bcpierce/unison/
4. http://www.mayrhofer.eu.org/dvcs-autosync
5. https://www.dropbox.com/
6. http://www.slrn.org/
--
Karl Voit
Re: [O] Bug: org-time-stamp loses repeater interval
Karl Voit writes: > The warning period still gets deleted though :-( You're right, should be fixed now. Thanks! -- Bastien
Re: [O] Problem with autoloads
On 28 Jun 2011, Nick Dokos wrote:
> Michael Markert wrote:
>>
>> Problem: autoload.el generates file names with lisp/ prefix.
>
> For you and Suvayu, but not for me. It's the discrepancy
> that bothers me.
I dug into emacs because I thought "Sure, there must be some change in
the meantime", well now I'm bothered, too.
The bzr autoloads.el is identical to mine.
But this code makes me curious:
#+begin_src emacs-lisp
(defun autoload-file-load-name (file)
"Compute the name that will be used to load FILE."
;; OUTFILE should be the name of the global loaddefs.el file, which
;; is expected to be at the root directory of the files we're
;; scanning for autoloads and will be in the `load-path'.
(let* ((outfile (default-value 'generated-autoload-file))
(name (file-relative-name file (file-name-directory outfile)))
(names '())
(dir (file-name-directory outfile)))
;; If `name' has directory components, only keep the
;; last few that are really needed.
(while name
(setq name (directory-file-name name))
(push (file-name-nondirectory name) names)
(setq name (file-name-directory name)))
(while (not name)
(cond
((null (cdr names)) (setq name (car names)))
((file-exists-p (expand-file-name "subdirs.el" dir))
;; FIXME: here we only check the existence of subdirs.el,
;; without checking its content. This makes it generate wrong load
;; names for cases like lisp/term which is not added to load-path.
(setq dir (expand-file-name (pop names) dir)))
(t (setq name (mapconcat 'identity names "/")
(if (string-match "\\.elc?\\(\\.\\|\\'\\)" name)
(substring name 0 (match-beginning 0))
name)))
#+end_src emacs-lisp
if I read it correctly we decompose our path-name (say lisp/org.el), by
rebasing it on outfile (org-install.el, which gives lisp/org.el) and
split in dirs, which gives '("lisp" "org.el"), then we are in the else
branch, build "lisp/org.el" and then in the last if we chop of the
".el".
I can't see how you get there correct path names :(
Michael
pgp9ss3LwuIbr.pgp
Description: PGP signature
Re: [O] Bug: org-time-stamp loses repeater interval
* Bastien wrote: > Karl Voit writes: > >> The warning period still gets deleted though :-( > > You're right, should be fixed now. Sorry when I disagree for one case: When I change each entry in my test data using «C-c .» and clicking on 1st of July ... ,[ test data ] | <2011-06-28 Tue> | <2011-06-28 Tue +1w> | <2011-06-28 Tue -1d> | <2011-06-28 Tue +1w -1d> ` ... I end up having this: ,[ result ] | <2011-07-01 Fri> | <2011-07-01 Fri +1w> | <2011-07-01 Fri -1d> | <2011-07-01 Fri -1d> ` In the last case, the repeater gets lost :-( -- Karl Voit Hallo, mein Name ist Web 2.0. Gib mir dein Adressbuch und lass mich Emails lesen
Re: [O] Make M-up and M-down transpose paragraphs in org buffers
Hello, Bastien writes: > There is one problem though: when you try to move down a paragraph when > it is followed by a list, Emacs doesn't understand the list should be > treated as a paragraph. > > Any idea on how to circumvent this? Or should we live with this and > implement the solution? Imo, a clean way to implement this (because it would also simplify existing functions) would be to define a forward paragraph-function for Org. It isn't difficult, but it raises some questions that need to be answered. For example, should forward-paragraph move into constructs or skip them. I.e. if point is outside a block and that block contains paragraphs, should forward-paragraph skip the block or move inside? Regards, -- Nicolas Goaziou
Re: [O] ob-lilypond
On 6/28/11 7:06 PM, Martyn Jago wrote: Status changed from SOMEDAY to TODO. Great, I'll be looking out for it. Yours, Christian
Re: [O] ob-lilypond
Hi Martyn Thank you very much for sharing your work. On Tue, Jun 28, 2011 at 19:06, Martyn Jago wrote: >> But much better, IMO, would be a way to `evaluate' a single Lilypond >> block and get #+RESULTS with a link to a PNG representing just that >> snippet of music. The snippet would then show up in subsequent exports >> as an included graphic without any post-processing, and could also be >> viewed in-buffer with `C-c C-x C-v'. (For my money, this and not >> `tangle all' would be the intuitive use of `C-c C-c' on a block, but I >> understand how your choice makes sense for other uses.) >> >> Yours, >> Christian > > This is very doable since it is the first thing I tried on initial > experimentation. I think I had some difficulty cropping the snippet (png) > in that the result had no padding at all, but I'm guessing that can be > overcome. > Certainly with the use cases you suggest, the defaults would need to > change, and C-c C-c would need to act as you describe, but that wouldn't > be an issue if we can define seperate 'modes' for the different ways of > working (I think for now the 'modes' can be considered mutually exclusive). For me it would be great to have Lilypond snippets that can be evaluated into a linked score image file visible inline the Org buffer, permanently in #+results: or temporarily as an overlay (similar to org-preview-latex-fragment). Michael
Re: [O] Problem with autoloads
Hello Nick and Michael, Sorry for the delayed response. I had an important appointment. On Tue, 28 Jun 2011 14:39:13 +0200 Michael Markert wrote: > > With this patch for the makefile I can get it running: > > -- --- > > diff --git a/Makefile b/Makefile > index 239ab2e..2d1d324 100644 > --- a/Makefile > +++ b/Makefile > @@ -230,12 +230,11 @@ autoloads: lisp/org-install.el > > lisp/org-install.el: $(LISPFILES0) Makefile > $(BATCH) --eval "(require 'autoload)" \ > - --eval '(find-file "org-install.el")' \ > + --eval '(find-file "lisp/org-install.el")' \ > --eval '(erase-buffer)' \ > - --eval '(mapc (lambda (x) (generate-file-autoloads > (symbol-name x))) (quote ($(LISPFILES0' \ > + --eval '(mapc (lambda (x) (generate-file-autoloads > (symbol-name x))) (quote ($(LISPF' \ --eval '(insert "\n(provide > (quote org-install))\n")' \ --eval '(save-buffer)' > - mv org-install.el lisp > > doc/org: doc/org.texi > (cd doc && $(MAKEINFO) --no-split org.texi -o org) > > -- --- This patch to the Makefile generates the autoloads without the lisp/ prefix for me and works without errors. However as Nick says, maybe its worthwhile to understand why this was happening in the first place. My lisp knowledge is very little, but please let me know if I can help track this down. > > Michael Thanks a lot. :) -- Suvayu Open source is the future. It sets us free.
[O] Exporting latex without preamble
Hi,
is it possible to export an org file to latex with no preamble and no
\begin{document}?? I just needed to translate org-mode syntax to latex
syntax, with no other headers and preambles around the text. Is this
possible?
I tried to add a "clean" class to my .emacs like this:
;
(add-to-list 'org-export-latex-classes
'("clean"
"
[NO-DEFAULT-PACKAGES]
[NO-PACKAGES]
[NO-EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
;
But when I try to export this file:
* Test
** Test 1
blablabla
** Test 2
lorem ipsum blabla
I get this:
% Created 2011-06-28 Tue 16:13
\providecommand{\alert}[1]{\textbf{#1}}
\title{bla}
\author{Rafael S. Calsaverini}
\date{\today}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{Test}
\label{sec-1}
\subsection{Test 1}
\label{sec-1-1}
blablabla
\subsection{Test 2}
\label{sec-1-2}
lorem ipsum blabla
\end{document}
Is there any option to turn the preamble off?
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo
rafael.calsaver...@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803
[O] Fwd: Exporting latex without preamble
Hi,
is it possible to export an org file to latex with no preamble and no
\begin{document}?? I just needed to translate org-mode syntax to latex
syntax, with no other headers and preambles around the text. Is this
possible?
I tried to add a "clean" class to my .emacs like this:
;
(add-to-list 'org-export-latex-classes
'("clean"
"
[NO-DEFAULT-PACKAGES]
[NO-PACKAGES]
[NO-EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
;
But when I try to export this file:
* Test
** Test 1
blablabla
** Test 2
lorem ipsum blabla
I get this:
% Created 2011-06-28 Tue 16:13
\providecommand{\alert}[1]{\textbf{#1}}
\title{bla}
\author{Rafael S. Calsaverini}
\date{\today}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{Test}
\label{sec-1}
\subsection{Test 1}
\label{sec-1-1}
blablabla
\subsection{Test 2}
\label{sec-1-2}
lorem ipsum blabla
\end{document}
Is there any option to turn the preamble off?
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo
rafael.calsaver...@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803
Re: [O] org-odt (Applying custom templates)
Hi Jumba, Sorry for testing this out late. Been busy. See my comments below. On Wed, Mar 23, 2011 at 4:38 AM, Jambunathan K wrote: >> In addition, is there a way to set up a header, or some text, before >> the title, similar to the attached file (including the image)? I >> don't mind if the solution is pasting some raw xml code in the >> org-mode file, as this part will remain constant. > > What is required is that you extract styles.xml and any images files > that it referenced from your odt/ott file and instruct org-odt.el to > package these files in the resulting directory. You can do these > manually. > > I also have a prototype code (that is not committed yet) that achieves > the above functionality. Suppose I have styles.xml and ./Pictures/1274034B83A526F3.png in the working directory of my org file, both extracted from my original odt file that I did myself. What exactly must I do to get these files packaged into the generated odt file? How do I set org-export-odt-styles-file in my org file? Thanks! -- Vinh
[O] org-evaluate-time-range
Hello, I have a question about the use-case for org-evaluate-time-range, because for what I would use it for, its behavior seems counter-intuitive. Consider a time range: <2011-08-12 Fri>--<2011-08-14 Sun> Calling org-evaluate-time-range on this range reports 2 days, but for situations when I would use time ranges, I would have expected an _inclusive_ count of 3 days. The span represented from a friday through a sunday is indeed a span of 3 days. Can anyone explain the logic behind the current behavior? Thank you. I'm using org version 6.33x. -- John Foerch
Re: [O] ob-lilypond
This is very doable since it is the first thing I tried on initial experimentation. I think I had some difficulty cropping the snippet (png) in that the result had no padding at all, but I'm guessing that can be overcome. I guess most of us who would be interested in this would have ImageMagick *convert* at hand, if it's difficult to get Lilypond or lilypond-book to do it directly. Certainly with the use cases you suggest, the defaults would need to change, and C-c C-c would need to act as you describe, but that wouldn't be an issue if we can define seperate 'modes' for the different ways of working (I think for now the 'modes' can be considered mutually exclusive). I'd tentatively suggest things should be done in a way that is roughly analogous with how other Babel languages work, not in the way that makes one or another use case super-easy to do. For our different use cases we might then each have to tweak some :tangle, :exports, :results or :file header arguments. But using Org-Babel's provisions for system-wide, language-specific and buffer-wide heading arguments, the user should be able to define her own `modes' by changing a few settings, and avoid littering a complex document with those header arguments. Maybe. Haven't thought this very far through... Yours, Christian
Re: [O] tangle paths
Herbert Sitz writes: > Eric Schulte gmail.com> writes: >> skip gmail.com> writes: >> >> > Is there a way I can produce output of tangle blocks to specific file >> > paths? >> > >> >> The manual is useful: http://orgmode.org/manual/tangle.html >> > > Eric -- > > I was wondering similar thing, but manual wasn't clearing things up for me. > As > far as I know, 'basename' conventionally refers to a filename (root plus > extension) that does _not_ include a directory path to the file itself. See, > e.g., http://en.wikipedia.org/wiki/Basename > > Is the manual using 'basename' to refer to a full path designation, minus the > extension? E.g., > > /path/to/file/filename > Thanks for pointing this out, I've just pushed up an update to the manual. Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] using #+call for inline results
> > Well, I have many other problems with this version (such as speed commands not > working anymore, yasnippet expansion not working anymore on TAB, some files > which say they're not in Org-agenda-files, etc.) but that's another story. > I don't understand, are you saying that all of the above problems are caused by the introduction of inline call lines? I have not experienced any of these problems. > > About this, my only weirdness is that I had to confirm 12 times (yes, 12!) > that I wanted to execute the calls. > > I have this in my emacs config file for months > > ;; don't be prompted on every code block evaluation > (setq org-confirm-babel-evaluate nil) > > ... has this var become a local file variable? > This has not become a buffer local variable and I can not reproduce your problem, could you please submit a minimal configuration with which I can reproduce this problem. > > Last thing: the questions in the echo area sometimes display the block name in > parentheses, sometimes not... > > - "Evaluate this emacs-lisp code block (square) on your system? (yes or no)" > - "Evaluate this emacs-lisp code block on your system? (yes or no)" > When the code block has a name, the name is shown in parens, when the code block is not named no name is shown. Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] ob-lilypond
Bastien writes: > Bastien writes: > >> Indeed -- Lilypond is an old GNU project, I guess there are many Emacs >> gnusers. I would love to include ob-lilypond.el in the next release, it >> adds a nice functionality and cannot break anything. > > I forgot to mention that I leave this decision to Eric, of course. Great, I have a commit ready to push to add lilypond support to Org-mode, first I just have two questions. 1. I see Shelagh Manton mentioned as an author, would it be possible for Shelagh to complete the FSF copyright assignment forms? Otherwise I don't believe we can add ob-lilypond to the Org-mode core, although we could still place it in the contrib directory with ob-oz. 2. I see you have a test suite which is fantastic. Additionally this test suite uses ert, which is what the main Org-mode test suite uses. Would it be possible to fold this test suite into Org-mode's test suite in the testing directory? If these tests require a lilypond executable we may have to partition them off from the main Org-mode test suite so that they can be run independently of each other. I'm happy to continue to push in updates to the Org-mode core as ob-lilypond development continues. Thanks to Martyn for this exciting addition! -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] new babel latex feature :imagemagick
Hi Andreas and Eric,
Could this patch be part of 7.6? Very useful...
Best regards,
Seb
Andreas Leha wrote:
> It's on the way.
>
> Am 26.02.2011 01:13, schrieb Eric Schulte:
>> Hi Andreas,
>>
>> This patch looks like a great idea and a clean implementation. Thanks
>> for sharing. Would you be willing to sign the FSF copyright assignment
>> papers? If not I probably can not apply your patch as it changes over
>> 10 lines -- which I'm pretty sure is the copyright assignment cutoff.
>>
>> For more information on contributing to Org-mode see the following
>> http://orgmode.org/worg/org-contribute.html
>>
>> Thanks! -- Eric
>>
>> Andreas Leha writes:
>>
>>
>>> Hi all,
>>>
>>> Just a small patch that might make life easier for
>>> LaTeX (and esp. tikz) users. It enables the output of graphics in a
>>> lot of formats using imagemagick. See below for an example.
>>>
>>> This is my first patch, I have never programmed emacs lisp before, and
>>> my common lisp experiences have been short and a while ago. So please
>>> excuse a (possibly) bad patch.
>>>
>>> Details:
>>> LaTeX source blocks now have three new options:
>>> - :imagemagick
>>> When not nil the source block is processed to pdf and the pdf is
>>> converted with imagemagick to whatever is given as :file
>>> Thus, the format is not limited to png.
>>> - :iminoptions
>>> This is passed to imagemagick before the pdf file
>>> - :imoutoptions
>>> This is passed to imagemagick before the output file
>>>
>>> Small Example:
>>> #+begin_src latex ... :file test.jpg :imagemagick yes :iminoptions
>>> -density 300 :imoutoptions -geometry 400 ...
>>> will use this command for conversion:
>>> convert -density 300 -geometry 400 test.jpg
>>>
>>> Full example:
>>> Export this to pdf and to html to see the effect.
>>> ===
>>> * Test
>>> #+begin_src R :session :exports both :results silent
>>> library("tikzDevice")
>>> #+end_src
>>> #+srcname: test_plot
>>> #+begin_src R :session :exports code :results output latex
>>> tikz(console=TRUE, width=4, height=4)
>>> plot(rnorm(100), rnorm(100))
>>> dummy <- dev.off()
>>> #+end_src
>>>
>>> #+srcname: test_plot_png
>>> #+begin_src latex :exports (if (and (boundp 'backend) (eq backend
>>> 'latex)) "none" "results") :file test.png :imagemagick yes :iminoptions
>>> -density 600 :imoutoptions -geometry 400 :fit yes :noweb yes :headers
>>> '("\\usepackage{tikz}")
>>> <>
>>> #+end_src
>>>
>>> #+srcname: test_plot_tikz
>>> #+begin_src latex :noweb yes
>>> <>
>>> #+end_src
>>>
>>> * Latex Options :noexport:
>>> #+LATEX_HEADER: \usepackage{tikz}
>>> ===
>>>
>>> Regards,
>>> Andreas
>>>
>>> ___
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>> ___
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Sebastien Vauban
Re: [O] ob-lilypond
Hi > I guess most of us who would be interested in this would have > ImageMagick *convert* at hand, if it's difficult to get Lilypond or > lilypond-book to do it directly. > I tentatively disagree. Arrangement mode needs to work for me with the minimal of fuss. Annotation mode similarly for you. That aside you can configure locally all you wish. Thus is the beauty of org-babel's configuration. Regards Martyn
Re: [O] HTML Postamble is inside Content DIV
Hi,
"Sebastien Vauban" wrote:
> Sébastien Vauban wrote:
>> Jonathan BISSON wrote:
>>> Sébastien Vauban writes:
After a couple of tests, I've observed that the postamble is forced to be
included *inside* the div "content".
Proof on Line 1764... These are the ending tags of every HTML page:
#+begin_src emacs-lisp
(unless body-only (insert "\n\n\n\n"))
#+end_src
... the closing referring to the opening of "content".
Shouldn't it make sense to be able to insert something *out of* the
"content" div?
>>>
>>> I think so (and the same for preamble)!
>>>
>>> I rewrote org-export-as-html and did a custom org-publish-org-to-html to
>>> call it, in order to get them out off the content div (you can look at a
>>> first test on my webpage http://www.bjonnh.net). It's easy to do it I can
>>> send you my file if you are interested.
>>
>> I think sharing the code here is always a good idea.
>>
>> However, I'd favor an approach commonly shared by others, ie by either:
>>
>> - moving the postamble out of the content DIV
>>
>> - adding an extra "environment" next to the content DIV, if the postamble
>> must
>> stay where it currently is -- for historical or compliance reasons?
>>
>> (same applies for preamble)
>
> I'm hijacking my own thread, as it received little support, and as the new
> question is quite related to that:
>
> - if we customize the preamble, our string will be inserted as is;
>
> - if we customize the postamble, our string will be inserted as is... between
> a wrapping div called "postamble".
>
> Shouldn't it be normal to apply the same reasoning for both cases: either
> impose a wrapper, either not?
>
>> Any comment for others?
Except for the reply of Jonathan, I received no answer on this. Here is thus
my proposition for a better div-structured HTML.
There are only four parts required in the HTML for all the magic to work with
the CSS:
- The first part is a container div ("content", by default) that surrounds
everything.
- Inside that are three more parts:
+ a preamble (in a div, if the user wants it),
+ a div "body" and
+ a postamble (in a div, if the user wants it).
The patch is attached.
Best regards,
Seb
--
Sebastien Vauban
diff --git a/lisp/org-html.el b/lisp/org-html.el
index f6108fc..daf61d2 100644
--- a/lisp/org-html.el
+++ b/lisp/org-html.el
@@ -1325,7 +1325,10 @@ lang=\"%s\" xml:lang=\"%s\">
org-export-html-preamble-format))
(cadr (assoc "en" org-export-html-preamble-format)))
`((?t . ,title) (?a . ,author)
- (?d . ,date) (?e . ,email)
+ (?d . ,date) (?e . ,email
+
+ ;; insert opening tag for body
+ (insert "\n\n"))
(if (and org-export-with-toc (not body-only))
(progn
@@ -1721,6 +1724,8 @@ lang=\"%s\" xml:lang=\"%s\">
;; export html postamble
(unless body-only
+ ;; insert closing tag for body
+ (insert "")
(let ((html-post (plist-get opt-plist :html-postamble))
(email
(mapconcat (lambda(e)
@@ -1732,12 +1737,13 @@ lang=\"%s\" xml:lang=\"%s\">
(number-to-string emacs-major-version
(when (plist-get opt-plist :html-postamble)
(cond ((stringp html-post)
- (insert "\n")
+ ;; (insert "\n")
(insert (format-spec html-post
`((?a . ,author) (?e . ,email)
(?d . ,date) (?c . ,creator-info)
(?v . ,html-validation-link
- (insert ""))
+ ;; (insert "")
+ )
((functionp html-post)
(funcall html-post opt-plist))
((eq html-post 'auto)
Re: [O] org-evaluate-time-range
John J Foerch writes: > Hello, > > I have a question about the use-case for org-evaluate-time-range, > because for what I would use it for, its behavior seems > counter-intuitive. Consider a time range: > > <2011-08-12 Fri>--<2011-08-14 Sun> > > Calling org-evaluate-time-range on this range reports 2 days, but for > situations when I would use time ranges, I would have expected an > _inclusive_ count of 3 days. The span represented from a friday through > a sunday is indeed a span of 3 days. > > Can anyone explain the logic behind the current behavior? Thank you. Timestamps with no time are considered to be at midnight (00:00) So Midnight Friday to Midnight Sunday is 48 hours. -Bernt -- Bernt
Re: [O] Bug: org-time-stamp loses repeater interval
Hello Karl, Karl Voit writes: > Sorry when I disagree for one case: > > When I change each entry in my test data using «C-c .» and clicking > on 1st of July ... > > ,[ test data ] > | <2011-06-28 Tue> > | <2011-06-28 Tue +1w> > | <2011-06-28 Tue -1d> > | <2011-06-28 Tue +1w -1d> > ` > > ... I end up having this: > > ,[ result ] > | <2011-07-01 Fri> > | <2011-07-01 Fri +1w> > | <2011-07-01 Fri -1d> > | <2011-07-01 Fri -1d> > ` > > In the last case, the repeater gets lost :-( I cannot reproduce this. Note that if you use the warning _before_ the repeater, then it gets losts: <2011-06-28 Tue -1d +1w> That because the warning should always be _after_ the repeater: See section 8.3.2 "Repeated tasks" in the manual "the repeater should come first and the warning period last: `DEADLINE: <2005-10-01 Sat +1m -3d>'." HTH, -- Bastien
Re: [O] Fwd: Exporting latex without preamble
Hi Rafael,
Rafael Calsaverini writes:
> is it possible to export an org file to latex with no preamble and no
> \begin{document}??
Not at the moment. Is it something you need regularily?
--
Bastien
Re: [O] ob-lilypond
Hi Eric, Eric Schulte writes: > 1. I see Shelagh Manton mentioned as an author, would it be possible for >Shelagh to complete the FSF copyright assignment forms? Otherwise I >don't believe we can add ob-lilypond to the Org-mode core, although >we could still place it in the contrib directory with ob-oz. There is little chance to get the assignement before the release of 7.6, so yes, let's take that route (contrib/) for now. -- Bastien
Re: [O] Bug: org-time-stamp loses repeater interval
Bastien wrote: > Hello Karl, > > Karl Voit writes: > > > Sorry when I disagree for one case: > > > > When I change each entry in my test data using «C-c .» and clicking > > on 1st of July ... > > > > ,[ test data ] > > | <2011-06-28 Tue> > > | <2011-06-28 Tue +1w> > > | <2011-06-28 Tue -1d> > > | <2011-06-28 Tue +1w -1d> > > ` > > > > ... I end up having this: > > > > ,[ result ] > > | <2011-07-01 Fri> > > | <2011-07-01 Fri +1w> > > | <2011-07-01 Fri -1d> > > | <2011-07-01 Fri -1d> > > ` > > > > In the last case, the repeater gets lost :-( > > I cannot reproduce this. > I can - but after earlier today, I'm not sure I trust my eyes: anybody else? Org-mode version 7.5 (baseline.387.gf9cc.dirty) (the dirty part is because of some Makefile experiments, nothing to do with timestamps). > Note that if you use the warning _before_ the repeater, > then it gets losts: > > <2011-06-28 Tue -1d +1w> That's not the problem - check the "before" state of the third of Karl's examples. > > That because the warning should always be _after_ the repeater: > > See section 8.3.2 "Repeated tasks" in the manual > > "the repeater should come first and the warning period last: > `DEADLINE: <2005-10-01 Sat +1m -3d>'." > Nick
Re: [O] org and microsoft exchange
Hi Matthieu, Matthieu Lemerre writes: > - With a bit of elisp (to implement RFC-2446 compliant export), I think > full outlook/exchange compliance could be really doable. Can you give an example of a RFC-2446 compliant entry (with the new field you mentioned in the previous email)? I guess adding this files to org-icalendar.el is not a big fuss. Thanks, -- Bastien
Re: [O] Bug: org-time-stamp loses repeater interval
Okay, I've pushed another fix. This let me stumble upon another case: the one with org-schedule and org-deadline ignoring warning cookies -- these cases are also fixed. Please confirm! Thanks, -- Bastien
Re: [O] ob-lilypond
Bastien writes: > Hi Eric, > > Eric Schulte writes: > >> 1. I see Shelagh Manton mentioned as an author, would it be possible for >>Shelagh to complete the FSF copyright assignment forms? Otherwise I >>don't believe we can add ob-lilypond to the Org-mode core, although >>we could still place it in the contrib directory with ob-oz. > > There is little chance to get the assignement before the release of 7.6, > so yes, let's take that route (contrib/) for now. This is now located in contrib/babel/langs. Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] new babel latex feature :imagemagick
Hi Sebastien,
As far as I know we have not received FSF papers for Andreas, so I do
not believe it will be possible to apply this patch before the 7.6
release.
Best -- Eric
"Sebastien Vauban" writes:
> Hi Andreas and Eric,
>
> Could this patch be part of 7.6? Very useful...
>
> Best regards,
> Seb
>
> Andreas Leha wrote:
>> It's on the way.
>>
>> Am 26.02.2011 01:13, schrieb Eric Schulte:
>>> Hi Andreas,
>>>
>>> This patch looks like a great idea and a clean implementation. Thanks
>>> for sharing. Would you be willing to sign the FSF copyright assignment
>>> papers? If not I probably can not apply your patch as it changes over
>>> 10 lines -- which I'm pretty sure is the copyright assignment cutoff.
>>>
>>> For more information on contributing to Org-mode see the following
>>> http://orgmode.org/worg/org-contribute.html
>>>
>>> Thanks! -- Eric
>>>
>>> Andreas Leha writes:
>>>
>>>
Hi all,
Just a small patch that might make life easier for
LaTeX (and esp. tikz) users. It enables the output of graphics in a
lot of formats using imagemagick. See below for an example.
This is my first patch, I have never programmed emacs lisp before, and
my common lisp experiences have been short and a while ago. So please
excuse a (possibly) bad patch.
Details:
LaTeX source blocks now have three new options:
- :imagemagick
When not nil the source block is processed to pdf and the pdf is
converted with imagemagick to whatever is given as :file
Thus, the format is not limited to png.
- :iminoptions
This is passed to imagemagick before the pdf file
- :imoutoptions
This is passed to imagemagick before the output file
Small Example:
#+begin_src latex ... :file test.jpg :imagemagick yes :iminoptions
-density 300 :imoutoptions -geometry 400 ...
will use this command for conversion:
convert -density 300 -geometry 400 test.jpg
Full example:
Export this to pdf and to html to see the effect.
===
* Test
#+begin_src R :session :exports both :results silent
library("tikzDevice")
#+end_src
#+srcname: test_plot
#+begin_src R :session :exports code :results output latex
tikz(console=TRUE, width=4, height=4)
plot(rnorm(100), rnorm(100))
dummy <- dev.off()
#+end_src
#+srcname: test_plot_png
#+begin_src latex :exports (if (and (boundp 'backend) (eq backend
'latex)) "none" "results") :file test.png :imagemagick yes :iminoptions
-density 600 :imoutoptions -geometry 400 :fit yes :noweb yes :headers
'("\\usepackage{tikz}")
<>
#+end_src
#+srcname: test_plot_tikz
#+begin_src latex :noweb yes
<>
#+end_src
* Latex Options :noexport:
#+LATEX_HEADER: \usepackage{tikz}
===
Regards,
Andreas
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>> ___
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] Bug: org-time-stamp loses repeater interval
Bastien wrote: > Okay, I've pushed another fix. > > This let me stumble upon another case: the one with org-schedule and > org-deadline ignoring warning cookies -- these cases are also fixed. > > Please confirm! > Confirmed. There is a peculiar corner case: If I have a headline that's both scheduled and deadlined, like this: --8<---cut here---start->8--- * scheduled DEADLINE: <2011-07-04 Mon +2w -3d> SCHEDULED: <2011-07-06 Wed +1w -2d> --8<---cut here---end--->8--- and I C-c C-s in the scheduled date, I get a second SCHEDULED: item with the new date on the DEADLINE line. The original SCHEDULED: is still on the next line, unchanged - like this: --8<---cut here---start->8--- * scheduled DEADLINE: <2011-07-04 Mon +2w -3d> SCHEDULED: <2011-07-03 Sun +1w -2d> SCHEDULED: <2011-07-06 Wed +1w -2d> --8<---cut here---end--->8--- Nick Org-mode version 7.5 (baseline.403.g13573)
