[O] org-preview-latex-fragment and preview-copy-region-as-mml
Hello I am starting to use org-preview-latex-fragment also in non org buffers, including message buffers. What would be extremely helpful is to actually send the images generates in the message buffers as images. Preview-latex provides such a functionality preview-copy-region-as-mml, from a LaTeX buffer. Of course the 2 preview functions org-preview and the latex-preview function work differently. I had a look preview-copy-region-as-mml and it is not clear to me how to make if work for png generated by org-preview-latex-fragment in a message buffer. Maybe some of the maintainers of org mode or auctex are interested in having a look? Uwe Brauer
[O] [PATCH] Minor fix in info documentation
--
Suvayu
Open source is the future. It sets us free.
From d84c66830856c4ff75a3a7b19bbf99219b5e6b99 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Mon, 9 Jan 2012 01:32:08 +0530
Subject: [PATCH] Minor fix in info documentation.
TINY CHANGE
---
doc/org.texi |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 0de59b3..952f740 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10460,9 +10460,7 @@ @subsection Images in @LaTeX{} export
this option can be used with tables as well@footnote{One can also take
advantage of this option to pass other, unrelated options into the figure or
table environment. For an example see the section ``Exporting org files'' in
-@url{http://orgmode.org/worg/org-hacks.html}}. For example the
-@code{#+ATTR_LaTeX:} line below is exported as the @code{figure} environment
-below it.
+@url{http://orgmode.org/worg/org-hacks.html}}.
If you would like to let text flow around the image, add the word @samp{wrap}
to the @code{#+ATTR_LaTeX:} line, which will make the figure occupy the left
--
1.7.7.6
[O] org-version reported as 6.33x after upgrading to the latest and greatest with Emacs' Package Manager
Hi, I'm running Emacs 23.2.1 (bundled with Ubuntu 11.04), and until now I was running the org-mode package that came with it (6.33x). Today I decided to update to the latest org version, and I followed the instructions at http://orgmode.org/worg/org-faq.html#installing-via-elpa When I do M-x locate-library RET org I get: Library is file ~/.emacs.d/elpa/org-20120129/org.elc which looks good, but if I do M-x org-version I get: Org-mode version 6.33x In my .emacs file I have ;; Org-mode ;; (require 'org-install) (add-to-list 'auto-mode-alist '(\\.org$ . org-mode)) (define-key global-map \C-cl 'org-store-link) (define-key global-map \C-ca 'org-agenda) (define-key global-map \C-cb 'org-iswitchb) (global-font-lock-mode 1) (setq org-log-done t) and at the end of the file (setq load-path (cons ~/Emacs-custom load-path)) (require 'package) (package-initialize) Did I miss something else that I should do? I was planning on getting rid of the version that comes with Emacs, but I thought I should ask first... Thanks, -- Ángel de Vicente http://angel-de-vicente.blogspot.com/
[O] Sort TODOs in agenda day
Hello, In the standard agenda view for any single day, apponintments appear in chronolological order before any TODOs which seem to be ordered accoriding to the order in which they appear in their org files. How could I get the TODOs to be sorted by something like effort-up without breaking the chronological sort of the appointments? Thanks.
Re: [O] Invalid read syntax #?
On 28 Jan 2012, at 16:55, Bastien wrote: For some reason, the first code block is evaluated twice. Ah, this explains why I was being asked twice if I allowed the code to run. When putting a headline on top of this first block, the error disappears. Sorry I can't help further with this for now. Hope Eric can make something of these infos, together with Nick's backtrace. Anything I can do to help debug this? Thanks, Alan
[O] Niceties when moving in the Agenda
Hi, Org mode people. How nice! I never observed this before. When I'm moving the cursor up or down within the *Org Agenda* buffer, the mini-buffer cleverly comments on the current entry, giving it context. Maybe I stumbled on the keyboard and activated something without noticing it? If a recent modification -- or even if an old one! :-) -- congratulations and thanks to those having thought or implemented it. François
Re: [O] org-version reported as 6.33x after upgrading to the latest and greatest with Emacs' Package Manager
Angel de Vicente ang...@iac.es writes: Hi, I'm running Emacs 23.2.1 (bundled with Ubuntu 11.04), and until now I was running the org-mode package that came with it (6.33x). Today I decided to update to the latest org version, and I followed the instructions at http://orgmode.org/worg/org-faq.html#installing-via-elpa When I do M-x locate-library RET org I get: Library is file ~/.emacs.d/elpa/org-20120129/org.elc which looks good, but if I do M-x org-version I get: Org-mode version 6.33x In my .emacs file I have ;; Org-mode ;; (require 'org-install) (add-to-list 'auto-mode-alist '(\\.org$ . org-mode)) (define-key global-map \C-cl 'org-store-link) (define-key global-map \C-ca 'org-agenda) (define-key global-map \C-cb 'org-iswitchb) (global-font-lock-mode 1) (setq org-log-done t) and at the end of the file (setq load-path (cons ~/Emacs-custom load-path)) (require 'package) (package-initialize) Did I miss something else that I should do? I was planning on getting rid of the version that comes with Emacs, but I thought I should ask first... 1. Did you restart Emacs? 2. If you remove (require 'org-install) does it help? 3. Emacs-24.1 (currently in pre-test) has the latest and greatest Org. Thanks, --
Re: [O] italicizing urls
prad p...@towardsfreedom.com writes: since a url uses the forward slash as do italicized items, i'm having difficulty italicizing urls on the html export. /just [[http://gohere.com][go here]] will you?/ shows up as /just go here will you?/ on the html export (though the go here link is valid) with nothing italicized and the forward slashes visible. i can get around it this way to some extent: /just/ [[http://gohere.com][go here]] /will you?/ but was wondering if there is a better way since the go here is still not italicized. Aloha prad, Would this work for you? /just/ [[http://gohere.com][/go here/]] /will you?/ All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Unexpected behaviour while adding checkboxes
Bastien b...@altern.org writes: Hi François, Bonjour, mon cher Bastien! :-) Ps: I would advise not mixing list types, e.g. not mixing plain list and descriptive list. Advice taken! Thanks! If you try C-u C-c C-c on the - petit :: chaperon item, you will read this message Cannot add a checkbox to a description list item So no, there is no bug here. OK. I've been a bit mislead by the fact that if I explicitly write: - [ ] petit :: chaperon both the [ ] and the petit word get highlighted. If we may not mix plain lists and descriptive lists, and I happen to write lines like above, maybe the petit word should lose its highlighting? Org mode helps me a bit more, say, if I replace - by * above, none of [ ] or petit are highlighted, so I immediately see I am doing something wrong. François
Re: [O] Niceties when moving in the Agenda
Hi Francois, This is governed by the variable `org-agenda-show-outline-path', which has been in Org for a long time and defaults to t. - Carsten On Jan 30, 2012, at 2:41 PM, François Pinard wrote: Hi, Org mode people. How nice! I never observed this before. When I'm moving the cursor up or down within the *Org Agenda* buffer, the mini-buffer cleverly comments on the current entry, giving it context. Maybe I stumbled on the keyboard and activated something without noticing it? If a recent modification -- or even if an old one! :-) -- congratulations and thanks to those having thought or implemented it. François
Re: [O] Niceties when moving in the Agenda
On Jan 30, 2012, at 4:28 PM, Carsten Dominik wrote: Hi Francois, This is governed by the variable `org-agenda-show-outline-path', Since November 2009, actually: $ git log -S'org-agenda-show-outline-path' gives commit 63fb485e2449e8ee23bee04c76dcb71cce4c0b61 Author: Carsten Dominik carsten.domi...@gmail.com Date: Fri Nov 13 14:48:00 2009 +0100 Implement showing the outline path in the echo area while in the agenda - Carsten which has been in Org for a long time and defaults to t. - Carsten On Jan 30, 2012, at 2:41 PM, François Pinard wrote: Hi, Org mode people. How nice! I never observed this before. When I'm moving the cursor up or down within the *Org Agenda* buffer, the mini-buffer cleverly comments on the current entry, giving it context. Maybe I stumbled on the keyboard and activated something without noticing it? If a recent modification -- or even if an old one! :-) -- congratulations and thanks to those having thought or implemented it. François - Carsten
[O] [BUG]? \\ and `fill-paragraph'
Hello! When using \\ to force linebreaks, these potentially get lost when reformatting the paragraph with Alt+Q (fill paragraph). Given an input : - long sentence long sentence :long sentence long sentence :long sentence long sentence :long sentence: \\ :Next line. pressing Alt+Q (`fill-paragraph') I'd expect to get : - long sentence long sentence long sentence long sentence long :sentence long sentence long sentence: \\ :Next line. but what I get is : - long sentence long sentence long sentence long sentence long :sentence long sentence long sentence: \\ Next line. This is a problem especially as a \\ anywhere but at the end of the line is exported literally (i.e. `fill-paragraph' changes both the appearance in emacs and in exported formats). The Problem occurs in the opposite direction too: If a \\ is m e a n t to occur literally it can end up at the end of a line and thus be interpreted as a line break. The problem can be partially avoided by marking each line and /then/ pressing Alt+Q, but it is inconvinient and hinders fille-wide reformatting (e.g. when the variable `fill-column' has changed).
Re: [O] Unexpected behaviour while adding checkboxes
Tom Regner tomgoochesa...@iro.umontreal.ca writes: Hi François, Hi, Tom. if you check the *Messages* buffer, you should notice a message like : Cannot add a checkbox to a description list item Thanks as well, Tom! :-) François. P.S. Tom, I tried to reply to you alone instead of through the list, but the message was rejected. Strangely, your message had: From: Tom Regner tomgoochesa...@iro.umontreal.ca I'm re-replying through the list as a way to tell you, just in case the problem would lie nearer your end than mine, and that you might be lucky enough to have some control over it. Who knows! :-)
Re: [O] [babel][patch] BUG in inline source blocks
Thanks. But out of interest why were the tests discarded? They are after all the proof that the code works, and the `living specification' of expected behavior. Just wondering My apologies, I didn't see the tests when looking at your patch and didn't realize they were there. Thanks for mentioning this, I have now applied them. BTW: the only reason I didn't apply your patch outright was because by the time I got to your message in the thread I had already pushed up my own (less comprehensive) patch which conflicted with your own. Also, as a more general note to everyone who works with and submits patches. It is worthwhile to review the text of a patch before submitting because often trivial things like changed indentation can add many lines to a patch file hiding the actual code changes. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] #+call-line removes hlines and headings ?
Marc-Oliver Ihm marc-oliver@online.de writes: Am 29.01.2012 11:42, schrieb Andreas Leha: :colnames yes Hi Andreas, Thanx, that is definitely a solution ! And I agree with you, that its a bit puzzling, that both cases behave differently; the #+call-line should just have the same result as the #+begin_src-line, to which after all it just refers. Beeing able to change the behaviour of the #+call-line with header arguments is of course a good thing, but it should not be necessary here in the first place. However, this would require a patch to the babel-code, which I am currently not able to produce, because I already got lost in debugging this problem :-) And of course I am not sure what would be the side effects of changing this behaviour ... So, thanx again for pointing out this very easy workaround ! with kind regards, Marc-Oliver Ihm To explain the cause (if not rationale) for the current behavior; when executing a call line, an ephemeral code block is created at the point of the call line. The result of the called function is passed into this ephemeral block, and the output of the block is inserted into the buffer. This is why call lines have *two* possible sets of header arguments, one to pass to the original called code block, and one for local effect in the ephemeral block. The reason the colnames header argument is required for the call line and not the code block, is because hlines are only stripped when data passes *into* a code block as a variable. In this case the 'hlines are stripped when the table passes into the ephemeral code blocks. Hope the above is more illuminating that confusing, -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] Variable settings in .emacs VS cross device portability.
Hello! I was wondering if there is a possibility to make org-files fully portable in behaviour (especially when exporting) between different emacs installations. When reading the mailing list or other writing about org-mode, commonly suggestions of the type just add (setq org-foo bar) to your .emacs. This however creates a dependency on the local setup of the variables, which likely will be a problem, when sharing the file with someone. My current solution is to use a template file with #+BIND: and #+PROPERTY: lines in a setup section rather than setting anything in configuration files. However, is there some way to turn a user-variable dependent file into a portable file? I was thinking of something along the lines of dumping user-specified variables into a list of #+BIND lines and, if necessary, the magic -*- var: value -*- line at the start of the file (or, less elegant because of spreading options across different positions in the file) the commented local variables structure near the end of the file. The latter two variants only apply if I am right about #+BIND lines applying only during export (whereas the magic emacs lines should create buffer-local bindings). king regards, Yu
[O] noweb-ref: Limiting scope of definitions?
Hello! Scenario - * Maintain a potentially long org file as an appendix. * In this appendix, many independent scripting tasks will be documented. * Each such scripting task has similiar partial tasks, e.g. imports, settings, ... In such a case, many independent scripts may contain a block imports or something or something to the same effect, i.e. an overlap of definitions could be avoided only by some sort of scoping: (a) manually, e.g. by prefixing the names with a script-specific string (e.g. task1-imports. While this is flexible (i.e. allows reuse of code from other script), it also reduces the readability of the NOWEB code). (b) providing some sort of scoping, e.g. declaring definitions section-local. Implementation Idea -- A simple implementation, maintaining the flexibility of the manual solution, would be to create a header argument like :noweb-prefix, that effectively just adds a prefix to the noweb reference names (both in declaring the block (#+name, :noweb-ref) and in using it (name)), unless such a prefix is explicitly specified. This could then be set as needed, for specific blocks or subtrees (as property) or any mixture of such. A prefix would then be recognized by a delimiter string to be specified. This solution would also be downward compatible with existing files, as the syntax for recognizing a prefix would be relevant only when deciding whether to apply an explicitly introduced :noweb-prefix.
Re: [O] org-version reported as 6.33x after upgrading to the latest and greatest with Emacs' Package Manager
On 30 January 2012 19:15, Jambunathan K kjambunat...@gmail.com wrote: Angel de Vicente ang...@iac.es writes: Hi, I'm running Emacs 23.2.1 (bundled with Ubuntu 11.04), and until now I was running the org-mode package that came with it (6.33x). Today I decided to update to the latest org version, and I followed the instructions at http://orgmode.org/worg/org-faq.html#installing-via-elpa When I do M-x locate-library RET org I get: Library is file ~/.emacs.d/elpa/org-20120129/org.elc which looks good, but if I do M-x org-version I get: Org-mode version 6.33x Try going to the *scratch* buffer, doing an M-x load-library org and evaluating the value of the sexp org-version (using C-j with the cursor placed immediately after it). Does that give you a different result, or is it still 6.33x? In my .emacs file I have ;; Org-mode ;; (require 'org-install) (add-to-list 'auto-mode-alist '(\\.org$ . org-mode)) (define-key global-map \C-cl 'org-store-link) (define-key global-map \C-ca 'org-agenda) (define-key global-map \C-cb 'org-iswitchb) (global-font-lock-mode 1) (setq org-log-done t) and at the end of the file (setq load-path (cons ~/Emacs-custom load-path)) (require 'package) (package-initialize) Did I miss something else that I should do? I was planning on getting rid of the version that comes with Emacs, but I thought I should ask first... If you get the newer org installed and running, I don't see a reason to manually remove the one that comes with Emacs, unless you've got space issues. 1. Did you restart Emacs? 2. If you remove (require 'org-install) does it help? 3. Emacs-24.1 (currently in pre-test) has the latest and greatest Org. Thanks, --
Re: [O] org-version reported as 6.33x after upgrading to the latest and greatest with Emacs' Package Manager
Any idea on how to test if org is getting confused with 6.33 beyond reporting that as its version? In your .emacs file, *just before* package-initialize add this and restart Emacs. (when (featurep 'org) (error Some mysterious force has already loaded org. Investigate why this is so.)) In the above operation, if you see that some mysterious force is indeed operating, demystify the force by adding the following line to the *top* of your .emacs and restart emacs. (setq debug-on-error t) (eval-after-load 'org '(error Some mysterious force is loading Org)) Note that Org could be loaded automatically from system path, if somewhere in the init sequence an Org file is visited (are you using desktop save or session save related libraries?) or you have some custom org related code. It is possible that backtrace may give you an hint on what possibly could be happening in your load sequence. Jambunathan K. In my .emacs file I have ;; Org-mode ;; (require 'org-install) (add-to-list 'auto-mode-alist '(\\.org$ . org-mode)) (define-key global-map \C-cl 'org-store-link) (define-key global-map \C-ca 'org-agenda) (define-key global-map \C-cb 'org-iswitchb) (global-font-lock-mode 1) (setq org-log-done t) and at the end of the file (setq load-path (cons ~/Emacs-custom load-path)) (require 'package) (package-initialize)
Re: [O] how do scientists use org mode?
I'm fairly experienced with emacs, ESS, Sweave, and R, but I've only started to dabble in Org mode in the past couple of weeks. Just as Christoph is, I'm trying to decide whether/how Org-mode might be useful in organizing and carrying out research projects, presentations, etc. So this thread has been very useful and timely. I'm trying to envision what a small research project, managed via a single Org file, might look like. There would be notes from meetings, thoughts from brainstorming sessions, scheduled appointments, data, R code, R output, and manuscript/presentation prose. Some of this might be destined for a manuscript, some for a beamer presentation, and some only for internal consumption. How are all these pieces differentiated in the Org file, so that Org knows what to put in the presentation/manuscript, and what not to? Could anyone share or point to a short, perhaps fictional, example? Thanks very much. --Chris Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13904 cryanatbinghamtondotedu Observation is a more powerful force than you could possibly reckon. The invisible, the overlooked, and the unobserved are the most in danger of reaching the end of the spectrum. They lose the last of their light. From there, anything can happen . . . [God, in Joan of Arcadia, episode entitled, The Uncertainty Principle.] Tomas Grigera wrote: Hi Cristoph On Fri, Jan 27, 2012 at 15:27, John Hendy jw.he...@gmail.com wrote: On Thu, Jan 26, 2012 at 3:21 PM, GMX Christoph 13 christoph...@gmx.net wrote: Hi this is my first post here and although I am evaluating org mode with great interest, I am also asking myself in which way other scientists are making use of org mode. It will take a while to get my head around how to accomplish certain things in org mode but for the moment I am intrigued by *why* one would want to approach the problem of organizing one's research with org mode and in which way. [...] Thomas, Eric and John gave very useful answers, I just want to add my $0.02 as a physicist who recently (about a year ago) started using Org mode. I started mainly looking for a workflow organization system, but slowly discovered it has many other possibilities. For research, I find org-babel is a great tool. It allows you to have a document collecting together thoughts and discussion along with data, data analysis, scripts for data manipulations and plots (Org tables are actually more like a spreadsheet since Org supports quite complex formulas and even plotting directly from the table). The many export possibilities mean that you can share your notes with colleagues not using Org (or even Emacs). I have also discovered it is a great tool for drafting presentations and then actually producing your slides via Latex- Beamer export. HTH, Tomas
Re: [O] org-version reported as 6.33x after upgrading to the latest and greatest with Emacs' Package Manager
Angel de Vicente ang...@iac.es writes: and at the end of the file (setq load-path (cons ~/Emacs-custom load-path)) (require 'package) (package-initialize) Did I miss something else that I should do? I was planning on getting rid of the version that comes with Emacs, but I thought I should ask first... If there is a mysterious force loading Org from the *system path* *and* if you *don't* have Org checked out in one of your local directories , then you can as well move the above three lines to the top of your .emacs. This way your elpa path will override system location. --
Re: [O] Niceties when moving in the Agenda
Carsten Dominik carsten.domi...@gmail.com writes: On Jan 30, 2012, at 4:28 PM, Carsten Dominik wrote: commit 63fb485e2449e8ee23bee04c76dcb71cce4c0b61 Author: Carsten Dominik carsten.domi...@gmail.com Date: Fri Nov 13 14:48:00 2009 +0100 Implement showing the outline path in the echo area while in the agenda My optician keeps sending letters inviting me to renew my glasses, and since I do not feel the need, I merely think he wants more money! They all do... Maybe I'm half-blind and do not know it ? :-) In any case, now that I noticed it, I much appreciate it. Thanks again! François
Re: [O] Syntax error warnings? (Especially important with :noweb-ref's)
Hello! Thanks for the reply. The problem was, that I assumed the list `org-babel-noweb-error-langs' to require the same form as `org-babel-load-languages', i.e. something like : ( (latex . t) (python . t) (sh . t) ) I didn't expect it to require a plain list of strings. Now, that this misunderstanding is cleared though, the next problem becomes visible: The common workflow I excepted is: 1. Define an overall structure of the task. 2. Run org-babel-tangle 3. If there are no errors: Finished. Else: - Choose the next block to implement from the list of unresolved blocks. - Rerun from 1. In the current implementation, the first unresolved code block stops at the `error' statement. Idea Instead of throwing an error, just a warning should be given. A simple implementation could be replacing, in ob.el, `org-babel-expand-noweb-references', (error %s (concat (org-babel-noweb-wrap source-name) could not be resolved (see `org-babel-noweb-error-langs'))) by (progn (lwarn 'tangle :warning %s (concat (org-babel-noweb-wrap source-name) could not be resolved (see `org-babel-noweb-error-langs'))) ) (the (progn-wrapping) is needed to ensure the enclosing if statement returns a string as expected by `split-string'). The solution has the weakness though, that the warning buffer doesn't show up automatically (due to the save-excursion I assume, so probably the warnings should be thrown in one go /after/ the save excursion and be collected into a list until then. (Multiple advantages: `add-to-list' can take care of multipli occuring warnings and a single warning is more clear by far then several warnings). king regards, Yu 2012/1/30 Eric Schulte eric.schu...@gmx.com: Yu yu_...@gmx.at writes: I tried my test file just again with a fresh pull from git: : `cat file1 file2' now expands as expected, but otherwise I don't see a change. Because I thought, well, maybe it's language specific, I made a new example. == test.org == #+begin_src emacs-lisp :tangle test.out :noweb tangle (progn task1 task2 (setq 1 2) (setq symbol 1) ) #+end_src #+begin_src emacs-lisp :noweb-ref task1 :noweb tangle (princ Hallo Welt!\n) #+end_src exports to == test.out == (progn (princ Hallo Welt!\n) (setq 1 2) (setq 1) ) == still without any error message. When I add emacs-lisp to the `org-babel-noweb-error-langs' variable then errors are raised for both task2 and symbol. #+BEGIN_SRC emacs-lisp (add-to-list 'org-babel-noweb-error-langs emacs-lisp) #+END_SRC As for the (here pretty artificial) case of symbol, I suppose avoiding that problem would require being able to suppress the special meaning of the construct, which would render the source less readable, so I guess one will just want to avoid this clash (e.g. inserting the spaces in shell scripts before/after the filename in a cmd EOF target construct, so here your solution is certainly sufficient for all but very exotic cases :-) Also, see the recent emails on list in which the ability to set custom alternatives for and we added. The example used in the email was the utf8 symbols « and » which should not occur in code. Best, Suggestion For cases, where a corresponding code block is not found: It would probably help in debugging and prevent compilers/interpreters from ignoring the missing code, if instead of an empty string, the foo construct itself was inserted, i.e. effectively not expanded at all. E.g. my sample code would result in the lisp interpreter trying to get the value for an undefined variable task2, which would be a quite obvious cause of failure. kind regards, Yu 2012/1/24 Eric Schulte eric.schu...@gmx.com: Yu yu_...@gmx.at writes: Actually, I set `org-babel-noweb-error-langs' to be the same as `org-babel-load-languages' (forgot to mention that). Specifically it contains By the way, I retested it again today with the latest version from git. Still the same result. OK, Thanks for your persistence on this. I've just pushed up a fix for two issues. 1. noweb reference names (e.g., that which is between the s) must both start and end with non-whitespace characters 2. some of my recent changes broke the error reporting behavior associated with `org-babel-noweb-error-langs', I've fixed this behavior. Please do let me know if you continue to experience any problems. Best, 2012/1/23 Eric Schulte eric.schu...@gmx.com: Have you tried using the
[O] a kludge (was: [AUCTeX-devel] org-preview-latex-fragment and preview-copy-region-as-mml)
On Mon, 30 Jan 2012 12:25:13 +0100, Antoine Levitt antoine.lev...@gmail.com wrote: Uwe Brauer (ccing gnus mailing list, in case someone is interested) I ran into that the other day. I think it would be very useful to have preview-buffer work on non-latex buffers. Concerning org-preview-latex-fragment: I have some code which indeed attaches the png generated by this function. However it is very primitive. org-preview-latex-fragment generates pngs in a subdirectory called ltxpng. These pngs are then inserted in the buffer where org-preview-latex-fragment was executed. Since one cannot be sure that the ltxpng directory is non-empty, IMHO it should be deleted before generating the png. This is done by function my-delete-ltxpngdir, which needs the trashcan pkg. Then a very simple modification of an already existing function does the rest: message-attach-all-png-from-ltxpngfolder. I attach it if you want to test it. Uwe Brauer my-preview-mml-send-png.el Description: application/emacs-lisp
Re: [O] Niceties when moving in the Agenda
On 30.1.2012, at 18:53, François Pinard wrote: Carsten Dominik carsten.domi...@gmail.com writes: On Jan 30, 2012, at 4:28 PM, Carsten Dominik wrote: commit 63fb485e2449e8ee23bee04c76dcb71cce4c0b61 Author: Carsten Dominik carsten.domi...@gmail.com Date: Fri Nov 13 14:48:00 2009 +0100 Implement showing the outline path in the echo area while in the agenda My optician keeps sending letters inviting me to renew my glasses, and since I do not feel the need, I merely think he wants more money! They all do... Maybe I'm half-blind and do not know it ? :-) :) In any case, now that I noticed it, I much appreciate it. Thanks again! You're of course welcome. - Carsten
[O] Google Tasks Integration
This weekend, while trying to avoid doing any real work, I started noodling around with the Google Tasks API and I got a respectable distance toward a script which will read your Google Tasks and export them to Org-mode. Currently it will capture the task title, the notes, the todo status (TODO or DONE) and the hierarchy, i.e. child tasks will be correctly placed under their parents. There's still a lot of polish to apply, and of course, there is no bidirectional capability as yet. Still, I wanted to send out this notice in case anyone wanted to compare notes or thought it might be an interesting application to share. The mobile apps for Google Tasks are quite good, and if I can get a really good export going, I think this will actually provide a plausible alternative workflow to the existing MobileOrg flow. Patrick
Re: [O] how do scientists use org mode?
Christopher W. Ryan cr...@binghamton.edu writes:
I'm fairly experienced with emacs, ESS, Sweave, and R, but I've only
started to dabble in Org mode in the past couple of weeks. Just as
Christoph is, I'm trying to decide whether/how Org-mode might be useful
in organizing and carrying out research projects, presentations, etc. So
this thread has been very useful and timely.
I'm trying to envision what a small research project, managed via a
single Org file, might look like. There would be notes from meetings,
thoughts from brainstorming sessions, scheduled appointments, data, R
code, R output, and manuscript/presentation prose. Some of this might be
destined for a manuscript, some for a beamer presentation, and some only
for internal consumption. How are all these pieces differentiated in
the Org file, so that Org knows what to put in the
presentation/manuscript, and what not to? Could anyone share or point to
a short, perhaps fictional, example?
Have you looked at
http://orgmode.org/worg/org-contrib/babel/uses.html
??
There are almost too many possibilities --- it is a bit overwhelming.
Here are three things I find useful:
1) The ability to export a subtree allows you to have many documents
within the *.org file. Setting EXPORT_* properties for the subtree gives
you a lot of flexibility. And it is easy to do with TAB completion to
prompt you to fill in the needed pieces.
2) Internal hyperlinks are really useful in staying on course in a big,
complicated document.
3) Noweb syntax allows you to mix and match different parts of the
document. Below is a minimal example. The latex chunks can be used
anywhere I need them. Navigating to '* mini report' and typing
'C-c @ C-c C-e l'
produces mini.tex.
,
| * COMMENT latex chunks
|
| #+name: chunk1
| #+begin_src latex
| \begin{displaymath}
| y = r\sin\theta
| \end{displaymath}
| #+end_src
|
| #+name: chunk2
| #+begin_src latex
| \begin{displaymath}
| x = s\cos\theta
| \end{displaymath}
| #+end_src
|
|
| * mini report
| :PROPERTIES:
| :EXPORT_FILE_NAME: mini.tex
| :EXPORT_TITLE: Minimal Report
| :EXPORT_AUTHOR: Mister CCB
| :END:
|
| #+begin_src latex :noweb yes
| chunk1
| chunk2
| #+end_src
`
HTH,
Chuck
Thanks very much.
--Chris
[snip]
--
Charles C. BerryDept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
[O] [bug] Problem when tangling into LaTeX
#+TITLE: Noweb references in LaTeX document
#+DATE: 2012-01-30
* Summary
** Problem
I use 3 chunks of LaTeX code which I wanna insert in a LaTeX document.
While 1 of them is correctly tangled into the LaTeX document, the 2 others
generate errors when C-c C-v C-t'ing:
if: reference 'who' not found in this buffer
and, if I temporarily replace `who()' by `who', I get the next error:
if: reference 'solde' not found in this buffer
What I don't understand is that there is no -- sorry, I mean: I don't see --
the difference between the 3 noweb references. They all seem correctly
written...
** Note
Remember that, up to now, such a document *must be first tangled* and then
post-processed via =PDFLaTeX=. It can not be exported directly to PDF/HTML
(=args
out of range= error).
* Example
** Part 1
#+name: who
#+begin_src org :results latex
ToMe
#+end_src
** Part 2
#+name: before
#+begin_src org :results latex
BeforeDate
#+end_src
** Part 3
#+name: solde
#+begin_src org :results latex
Rest
#+end_src
** Composed letter
#+begin_src latex :noweb yes :tangle yes
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\begin{document}
\begin{textblock}{85}(98,35)
\titlebox{9.4cm}{Foo}{% HERE
who()
}
\end{textblock}
\begin{textblock}{110}(25,195)
Some sentence
before() \hfill{}% HERE
solde() EUR% HERE
\end{textblock}
\end{document}
#+end_src
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Google Tasks Integration
On Mon, Jan 30 2012 20:33 (@1327951983), Patrick Brennan wrote: This weekend, while trying to avoid doing any real work, I started noodling around with the Google Tasks API and I got a respectable distance toward a script which will read your Google Tasks and export them to Org-mode. Currently it will capture the task title, the notes, the todo status (TODO or DONE) and the hierarchy, i.e. child tasks will be correctly placed under their parents. There's still a lot of polish to apply, and of course, there is no bidirectional capability as yet. Still, I wanted to send out this notice in case anyone wanted to compare notes or thought it might be an interesting application to share. The mobile apps for Google Tasks are quite good, and if I can get a really good export going, I think this will actually provide a plausible alternative workflow to the existing MobileOrg flow. Patrick #secure method=pgpmime mode=sign Sounds awesome; one thought: Make it CalDAV instead of Google only. Google supports CalDAV from what I understand, and using a standard protocol will make your work useful for a much wider public! -- Philipp Haselwarter
Re: [O] [BUG]? \\ and `fill-paragraph'
Hello, Yu yu_...@gmx.at writes: When using \\ to force linebreaks, these potentially get lost when reformatting the paragraph with Alt+Q (fill paragraph). Given an input : - long sentence long sentence :long sentence long sentence :long sentence long sentence :long sentence: \\ :Next line. pressing Alt+Q (`fill-paragraph') I'd expect to get : - long sentence long sentence long sentence long sentence long :sentence long sentence long sentence: \\ :Next line. but what I get is : - long sentence long sentence long sentence long sentence long :sentence long sentence long sentence: \\ Next line. Yes, this is a problem. I'll take a look at it in a few days. I wanted to provide a better filling mechanism backed up with Org elements, anyway. The Problem occurs in the opposite direction too: If a \\ is m e a n t to occur literally it can end up at the end of a line and thus be interpreted as a line break. I've committed a patch that should prevent auto-fill from creating Org line breaks. Regards, -- Nicolas Goaziou
Re: [O] Organizing by time or by subject and an idea
On Mon, Jan 23, 2012 at 3:00 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: Max Mikhanosha m...@openchat.com writes: At Fri, 20 Jan 2012 12:04:51 -0600, John Hendy wrote: [...] Generally I think the way to tackle this is to take advantage that you are working with plain text and not with Word document, and use standard Emacs/Unix tools for working with text. Agreed! Thanks to both of you for input! Some ideas: Before updating each project, cut-n-paste it into the new revision.. Org mode makes it easy to cut-n-paste trees, for myself duplicating a headline is simply pressing Y then P over a folded headline (viper/vimpulse user) Is it not easier to simply make use of any of the revision control systems (git, mercurial, svn, even RCS) that are out there? You can easily tag a particular revision based on milestones and then see diffs between the current content and any previous version. In terms of the original questions, I use a combination of hierarchical structure that is filled in as a project develops, with revision control to allow me to see progress, together with a log based recording of activities (e.g. meetings, deliverables delivered, issues raised). That is, I mix both of the approaches mentioned by John in his initial email. This is intriguing. I don't suppose you have a sample file of sorts? Specifically, I'm interested in how you mix 'n match hierarchical/topical vs. time-based organization. I really struggle with this and my purely time based stuff is *definitely* not the way to go in my opinion, as I have tons of related things in separate trees with time stamps, which makes finding some little tidbit silly since I'm looking through different dates for it. Also, I'm a super git newb. The furthest I've gotten to is setting up a repo for sharing stuff between work and home, for example, and simply doing `git pull` from each location when I want to work on something and then `git push` when I'm done. I'm assuming I could set up some sort of cron job to `git commit; git push` each day/week or something? And then learn more git commands to show progress? Is there a way to spit git timeline based output into separate file revisions? Sorry if this is getting too off-track from org. I should probably look into the power of git on my own... The key, as John has already stated, is to record everything! With emacs, I can usually pull out what I want *if* the information was recorded in the first place. Finally, tags can be very useful for quick searching as well. I still need to figure out a better tag system as well. Currently, I just have a project acronym under each main header: - * Tracking Odds and ends tasks * Project 1 :proj1: Stuff for project 1 * Project 2 :proj2: Stuff for project 2 * References :ref: Misc things I need to refer back to now and then (project reporting IDs, etc.) - That's quasi helpful, but not really... Do you tag by type of data stored? Project/task type/name? Thanks again, John -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.03 (release_7.8.03.192.g32af)
Re: [O] Organizing by time or by subject and an idea
John Hendy jw.he...@gmail.com writes: On Mon, Jan 23, 2012 at 3:00 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: The key, as John has already stated, is to record everything! With emacs, I can usually pull out what I want *if* the information was recorded in the first place. Finally, tags can be very useful for quick searching as well. I still need to figure out a better tag system as well. Currently, I just have a project acronym under each main header: - * Tracking Odds and ends tasks * Project 1 :proj1: Stuff for project 1 * Project 2 :proj2: Stuff for project 2 * References :ref: Misc things I need to refer back to now and then (project reporting IDs, etc.) - That's quasi helpful, but not really... Do you tag by type of data stored? Project/task type/name? Hi John, I have lots of projects that have similar structure and headlines. I use tags sparingly -- mainly for filtering in the agenda and for information about tasks. I almost always work from the agenda to find what to do next and having the tags indicating which project the task is for is very convenient. Tags are inherited so I'll normally tag the top level project with some unique name and a few file tags are added for grouping tasks. I keep multiple projects in a single file but they are all related to some larger projects. I'll archive done state tasks away when they are 2 months old. Something like this: ,[ fileX.org ] | #+FILETAGS: XX | | * Tasks | ** TODO Do this | * TODO SomeProject :someproject: | ** TODO Create design document | ** TODO Coding | *** TODO FileA | TODO FunctionQ | *** TODO FileB | * TODO OtherProject :otherproject: | ** TODO Create design document | ** TODO Coding | *** TODO FileF | TODO FunctionR | *** TODO FileG ` ,[ fileY.org ] | #+FILETAGS: YY | | * Tasks | ** TODO Do this | * TODO ProjA :proja: | ** TODO Create design document | ** TODO Coding | *** TODO FileA | TODO FunctionQ | *** TODO FileB | * TODO ProjB :projb: | ** TODO Create design document | ** TODO Coding | *** TODO FileF | TODO FunctionR | *** TODO FileG ` When looking for tasks to work on in the agenda it's obvious what a task belongs to. Each task has an XX or YY tag from the FILETAGS line and all projB tasks have a :projb: tag. I use this a lot to quickly distinguish tasks from each other in the global todo list. My current global todo list has tasks with 1 - 5 tags. Only HOLD tasks have 5 tags (where :HOLD: is automatically added when I change the task state) All tasks have at least 1 tag (coming from the FILETAGS entry). Filtering the agenda with tags is immensely useful. You can limit to a specific tag, or exclude tasks with some tag, etc which helps me focus on the thing I'm working on now. I also limit my block agenda view to subtree and project using my fairly recent changes on http://doc.norang.ca/org-mode.html. HTH, Bernt
Re: [O] Sort TODOs in agenda day
Jacek Generowicz jacek.generow...@cern.ch writes: Hello, In the standard agenda view for any single day, apponintments appear in chronolological order before any TODOs which seem to be ordered accoriding to the order in which they appear in their org files. How could I get the TODOs to be sorted by something like effort-up without breaking the chronological sort of the appointments? Look at the variable org-agenda-sorting-strategy. Regards, Bernt
Re: [O] Variable settings in .emacs VS cross device portability.
Yu yu_...@gmx.at writes: Hello! I was wondering if there is a possibility to make org-files fully portable in behaviour (especially when exporting) between different emacs installations. When reading the mailing list or other writing about org-mode, commonly suggestions of the type just add (setq org-foo bar) to your .emacs. This however creates a dependency on the local setup of the variables, which likely will be a problem, when sharing the file with someone. My current solution is to use a template file with #+BIND: and #+PROPERTY: lines in a setup section rather than setting anything in configuration files. However, is there some way to turn a user-variable dependent file into a portable file? I was thinking of something along the lines of dumping user-specified variables into a list of #+BIND lines and, if necessary, the magic -*- var: value -*- line at the start of the file (or, less elegant because of spreading options across different positions in the file) the commented local variables structure near the end of the file. The latter two variants only apply if I am right about #+BIND lines applying only during export (whereas the magic emacs lines should create buffer-local bindings). Aloha Yu, I favor Eric Schulte's solution for reproducible research, which you can find here: http://www.jstatsoft.org/v46/i03 The trick is to launch a fresh instance of Emacs and supply it with an initialization file tailored to the content. Eric uses a Makefile for this, and I've been able to copy and tweak his Makefile for use on other projects. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Variable settings in .emacs VS cross device portability.
Yu yu_...@gmx.at writes: Hello! I was wondering if there is a possibility to make org-files fully portable in behaviour (especially when exporting) between different emacs installations. File Local Variables [1] make it possible to explicitly specify the values of variables from within the text of a .org file. This can be placed in a single line at the top of a file for small changes or in a larger section at the end of the file. Cheers, When reading the mailing list or other writing about org-mode, commonly suggestions of the type just add (setq org-foo bar) to your .emacs. This however creates a dependency on the local setup of the variables, which likely will be a problem, when sharing the file with someone. My current solution is to use a template file with #+BIND: and #+PROPERTY: lines in a setup section rather than setting anything in configuration files. However, is there some way to turn a user-variable dependent file into a portable file? I was thinking of something along the lines of dumping user-specified variables into a list of #+BIND lines and, if necessary, the magic -*- var: value -*- line at the start of the file (or, less elegant because of spreading options across different positions in the file) the commented local variables structure near the end of the file. The latter two variants only apply if I am right about #+BIND lines applying only during export (whereas the magic emacs lines should create buffer-local bindings). king regards, Yu Footnotes: [1] http://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Syntax error warnings? (Especially important with :noweb-ref's)
Yu yu_...@gmx.at writes: Hello! Thanks for the reply. The problem was, that I assumed the list `org-babel-noweb-error-langs' to require the same form as `org-babel-load-languages', i.e. something like : ( (latex . t) (python . t) (sh . t) ) I didn't expect it to require a plain list of strings. Now, that this misunderstanding is cleared though, the next problem becomes visible: The common workflow I excepted is: 1. Define an overall structure of the task. 2. Run org-babel-tangle 3. If there are no errors: Finished. Else: - Choose the next block to implement from the list of unresolved blocks. - Rerun from 1. In the current implementation, the first unresolved code block stops at the `error' statement. I would suggest that you stubb out empty code blocks for those blocks which you want to reference elsewhere but have not yet implemented. Such blocks could all hold the same indicator string (something like TODO or FIXME) so that the presence of unimplemented blocks is easy to find in tangled code. As you mention below there are complications with a multi-tiered warning and error system which I believe would make the noweb error system more confusing and harder to use. Idea Instead of throwing an error, just a warning should be given. A simple implementation could be replacing, in ob.el, `org-babel-expand-noweb-references', (error %s (concat (org-babel-noweb-wrap source-name) could not be resolved (see `org-babel-noweb-error-langs'))) by (progn (lwarn 'tangle :warning %s (concat (org-babel-noweb-wrap source-name) could not be resolved (see `org-babel-noweb-error-langs'))) ) (the (progn-wrapping) is needed to ensure the enclosing if statement returns a string as expected by `split-string'). The solution has the weakness though, that the warning buffer doesn't show up automatically (due to the save-excursion I assume, so probably the warnings should be thrown in one go /after/ the save excursion and be collected into a list until then. (Multiple advantages: `add-to-list' can take care of multipli occuring warnings and a single warning is more clear by far then several warnings). king regards, Yu 2012/1/30 Eric Schulte eric.schu...@gmx.com: Yu yu_...@gmx.at writes: I tried my test file just again with a fresh pull from git: : `cat file1 file2' now expands as expected, but otherwise I don't see a change. Because I thought, well, maybe it's language specific, I made a new example. == test.org == #+begin_src emacs-lisp :tangle test.out :noweb tangle (progn task1 task2 (setq 1 2) (setq symbol 1) ) #+end_src #+begin_src emacs-lisp :noweb-ref task1 :noweb tangle (princ Hallo Welt!\n) #+end_src exports to == test.out == (progn (princ Hallo Welt!\n) (setq 1 2) (setq 1) ) == still without any error message. When I add emacs-lisp to the `org-babel-noweb-error-langs' variable then errors are raised for both task2 and symbol. #+BEGIN_SRC emacs-lisp (add-to-list 'org-babel-noweb-error-langs emacs-lisp) #+END_SRC As for the (here pretty artificial) case of symbol, I suppose avoiding that problem would require being able to suppress the special meaning of the construct, which would render the source less readable, so I guess one will just want to avoid this clash (e.g. inserting the spaces in shell scripts before/after the filename in a cmd EOF target construct, so here your solution is certainly sufficient for all but very exotic cases :-) Also, see the recent emails on list in which the ability to set custom alternatives for and we added. The example used in the email was the utf8 symbols « and » which should not occur in code. Best, Suggestion For cases, where a corresponding code block is not found: It would probably help in debugging and prevent compilers/interpreters from ignoring the missing code, if instead of an empty string, the foo construct itself was inserted, i.e. effectively not expanded at all. E.g. my sample code would result in the lisp interpreter trying to get the value for an undefined variable task2, which would be a quite obvious cause of failure. kind regards, Yu 2012/1/24 Eric Schulte eric.schu...@gmx.com: Yu yu_...@gmx.at writes: Actually, I set `org-babel-noweb-error-langs' to be the same as `org-babel-load-languages' (forgot to mention that). Specifically it contains By the way, I retested it again today with the latest version from git.
Re: [O] [bug] Problem when tangling into LaTeX
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
#+TITLE: Noweb references in LaTeX document
#+DATE: 2012-01-30
* Summary
** Problem
I use 3 chunks of LaTeX code which I wanna insert in a LaTeX document.
While 1 of them is correctly tangled into the LaTeX document, the 2 others
generate errors when C-c C-v C-t'ing:
if: reference 'who' not found in this buffer
and, if I temporarily replace `who()' by `who', I get the next error:
if: reference 'solde' not found in this buffer
What I don't understand is that there is no -- sorry, I mean: I don't see --
the difference between the 3 noweb references. They all seem correctly
written...
** Note
Remember that, up to now, such a document *must be first tangled* and then
post-processed via =PDFLaTeX=. It can not be exported directly to PDF/HTML
(=args
out of range= error).
* Example
** Part 1
#+name: who
#+begin_src org :results latex
ToMe
#+end_src
** Part 2
#+name: before
#+begin_src org :results latex
BeforeDate
#+end_src
** Part 3
#+name: solde
#+begin_src org :results latex
Rest
#+end_src
** Composed letter
#+begin_src latex :noweb yes :tangle yes
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\begin{document}
\begin{textblock}{85}(98,35)
\titlebox{9.4cm}{Foo}{% HERE
who()
}
\end{textblock}
\begin{textblock}{110}(25,195)
Some sentence
before() \hfill{}% HERE
solde() EUR% HERE
\end{textblock}
\end{document}
#+end_src
Best regards,
Seb
Currently newlines are allowed in noweb reference names causing the
problems you noticed above. I've just pushed up a change which
disallows newline characters in noweb references and fixes the odd
behavior you describe.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
[O] Feature request for noweb mode that strips references on export
Presently there are three noweb modes: yes, no, and tangle. I would like a fourth, which would behave as follows: On tangle: normal noweb expansion is performed. On evaluation: normal noweb expansion is performed. On export: noweb references are STRIPPED. Not just ignored, but the lines containing the references are removed before export. The use case is this: I find myself writing articles where I have a series of code examples like this: #+begin_src ruby boilerplate 2 + 2 # = #+end_src The boilerplate is required to make the sample work, but I don't want to have the boilerplate code show up in the finished article, because it would be repeated for every example. I also don't want the noweb reference to show up in the finished article, because it will confuse readers and syntax highlighters. Is this possible now, and/or a feature that could be easily added? Thanks, -- Avdi Grimm http://avdi.org
Re: [O] [ODT] image scaling overridden by long caption
Andreas Leha andreas.l...@med.uni-goettingen.de writes: #+label: fig:baz #+name: baz #+attr_odt: :scale 0.5 #+header: :file baz.png #+header: :width 7200 :height 3600 :res 600 #+begin_src R :exports results :results graphics plot(1:10, 1:10) #+end_src Image that R outputs is 7200-by-3600. #+begin_src emacs-lisp (list (* max-image-size (frame-pixel-width)) (* max-image-size (frame-pixel-height))) #+end_src #+results: | 3648.0 | 4320.0 | Emacs will refuse to load images that cannot fit in 3640-by-4320 area. Note that max-image dimensions is tightly coupled with the frame size. #+begin_src emacs-lisp (message %S (ignore-errors (image-size (create-image baz.png) 'pixels))) #+end_src #+results: : (30 . 30) Instead of loading a large image, Emacs tries to create a safe 30-by-30 pixel area (whatver it is). The solution is to instruct Emacs to handle higher image sizes. Just bump the value of max-image-size. For example, add this to init file. #+begin_src emacs-lisp (setq max-image-size (* 2 max-image-size)) ;; modify scale #+end_src Side note: == If you have imagemagick on your machine(s) and identify program is in your load path, #+begin_src emacs-lisp (executable-find identify) #+end_src you can configure ODT export to use imagemagick as primary source for probing image dimensions. This you can do by adding the following to your .emacs. #+begin_src emacs-lisp (setq org-export-odt-image-size-probe-method '(imagemagick force)) #+end_src Ps: If you happen to try out imagemagick-only setting, let me know if you run in to any issues. You will be the first person (that I know of) to try it out. --
[O] 24.0.92; (image-size ...) on large images
org-odt.el relies on (image-size ...) to determine pixel dimensions of an image. For large images, this API returns false values. It would be wonderful, if Emacs returns just the true value of the image or nothing at all. On a related note, IIRC, during batch export there is no way I can use create-image + image-size to determine pixel dimensions of the image. Is there a reliable and uniform way to determine size of images that are *never* intended to be displayed. Original issue: http://www.mail-archive.com/emacs-orgmode@gnu.org/msg51014.html My notes: http://www.mail-archive.com/emacs-orgmode@gnu.org/msg51441.html , http://www.mail-archive.com/emacs-orgmode@gnu.org/msg51441.html | Re: [O] [ODT] image scaling overridden by long caption | | Jambunathan K | Mon, 30 Jan 2012 20:59:37 -0800 | | Andreas Leha andreas.l...@med.uni-goettingen.de writes: | | | #+label: fig:baz | #+name: baz | #+attr_odt: :scale 0.5 | #+header: :file baz.png | #+header: :width 7200 :height 3600 :res 600 | #+begin_src R :exports results :results graphics |plot(1:10, 1:10) | #+end_src | | Image that R outputs is 7200-by-3600. | | #+begin_src emacs-lisp |(list (* max-image-size (frame-pixel-width)) | (* max-image-size (frame-pixel-height))) | #+end_src | | #+results: | | 3648.0 | 4320.0 | | | Emacs will refuse to load images that cannot fit in 3640-by-4320 | area. Note that max-image dimensions is tightly coupled with the frame | size. | | #+begin_src emacs-lisp | (message %S (ignore-errors | (image-size (create-image baz.png) 'pixels))) | #+end_src | | #+results: | : (30 . 30) | | Instead of loading a large image, Emacs tries to create a safe | 30-by-30 pixel area (whatver it is). | | The solution is to instruct Emacs to handle higher image sizes. Just | bump the value of max-image-size. For example, add this to init file. | | #+begin_src emacs-lisp | (setq max-image-size (* 2 max-image-size)) ;; modify scale | #+end_src `
[O] [bug]Bug in export to LaTex: Lists with source code blocks
Hello, Today I found a bug which was well described in http://thread.gmane.org/gmane.emacs.orgmode/48388 is still there. (emacs-version) GNU Emacs 24.0.92.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.8) (org-version) Org-mode version 7.8.03
[O] Anyone going to FOSDEM?
Hi all I'm trying to figure out what talks and DevRooms I should go to at FOSDEM and I was wondering if some fellow orgers are going to be there. Maybe we could meet for a chat, for dinner or even some hacking. Unfortunately there doesn't seem to be a GNU devroom this year. Is there any interest for a meetup? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Feature request for noweb mode that strips references on export
Hi Avdi, Avdi Grimm wrote: Presently there are three noweb modes: yes, no, and tangle. I would like a fourth, which would behave as follows: Just for the sake of completeness, there is already a fourth option: no-export which expands noweb references during tangling and execution, but not during weaving (export). Best regards, Seb -- Sebastien Vauban
