Re: [O] patch to org-refile for more accurate completing-read
Sure. On Sat, Jan 28, 2012 at 7:42 AM, Bernt Hansen be...@norang.ca wrote: Le Wang l26w...@gmail.com writes: Here: https://gist.github.com/1689071 When we are using using refile as navigation, require must-match regardless of org-refile-allow-creating-parent-nodes. Hi, I suggest you post the patch to the mailing list as an attachment so 1) we can read it inline and comment on it without having to go find it on the web 2) it will get automatically picked up by the patchwork patch tracker so it can be easily applied to the source 3) it will forever be in the mailing list archive Regards, Bernt -- Le org.el.diff Description: Binary data
[O] Bug: get-face-font: Xemacs21.5.29: org-preview-latex-fragment [7.5]
Uwe Brauer writes: (if (featurep 'xemacs) (font-height (get-face-font 'default)) The function you want is `face-font'.
Re: [O] [ANN] ASCII back-end for new export engine
Hi N, Some comments on your great work: Recent version errors with wrong type argument, but I can't privacy-wash yet to show the whole stack trace. make-string(-1 32) (concat aligned-cell (make-string (- col-width ...) 32)) (format %s (concat aligned-cell (make-string ... 32))) (let* ((indent-tabs-mode nil) (align ...) (aligned-cell ...)) (format %s (concat aligned-cell ...))) (let ((col-width ...)) (unless (or org-e-ascii-table-widen-columns ...) (setq cell ...)) (let* (... ... ...) (format %s ...))) For what it's worth. I might need to give you a full stack trace if that is not enough. 22 with latest git. I suspect it is because your exporter actually tries to understand all syntax, while the old one passes through a lot of things (maybe including list-like things). These comments are from an earlier version that worked: I like to separate things like this: === The old exporter left it intact; the new one tries to interpret it even though /text/ and *text* are left intact. I'm guessing this is a new feature that works only on =word=. I'd like to turn it off if it can't be made to not interpret my separator. Most lines are indented by 2 spaces. I'd prefer flush to left. It splits the window even though I have pop-up-windows set to nil. Block quotes indent by 8 or so. That's rather nice, but is there an option to change that to 2 or 4? Lists are not indented although I always indent them by 2. Is there an option to set the fill column and refill paragraphs (roughly like the way HTML does)? I'd find that highly useful. Unfilling too. Feature requesti --export tables using tab characters. If it doesn't exist already. Maybe it does? Footnotes don't have a header. HTML export inserts one. No final newline. One missing footnote . It is going to take me a while to narrow it down. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com === Bigotry against people with serious diseases is still bigotry.
Re: [O] org mode in press
I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Christian Wittern, Kyoto
[O] [PATCH] [Beamer export] Example should better export to exampleblock environment
Dear all, It is great that org mode makes creating Beamer slides so easy! I would like to include some green example blocks in my slides (e.g., for exercises for my students), and I can turn an org headline and its content into an example block by just pressing C-c C-b e -- very nice. Now, my problem is that Org mode exports this as a Beamer example environment, instead of an exampleblock environment. The difference is that the exampleblock environment is just a green block that otherwise behaves like the standard Beamer blocks (in particular, users have full control over its title), while an example environment always adds something to the title like this: Example (ACTUAL TITLE). Such behaviour may be useful in special cases, but the exampleblocks are more flexible and should therefore at least be supported as an alternative option, but likely being the default export option. Attached to this message there is a simple patch that adds support for exampleblocks (short cut C-c C-b E) by keeping everything else as it is. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de org-beamer.el.diff Description: Binary data
Re: [O] [ANN] ASCII back-end for new export engine
Hello, Samuel Wales samolog...@gmail.com writes: Recent version errors with wrong type argument, but I can't privacy-wash yet to show the whole stack trace. I don't need the whole stack trace, but there is at least one table in your buffer that causes problems to the exporter. I'd need to see it. If you don't know which one it is, you can successively mark each table in that buffer and use org-export-dispatch with the region active (it will only export the region) until the culprit is found. These comments are from an earlier version that worked: I like to separate things like this: === The old exporter left it intact; the new one tries to interpret it In Org syntax, this is really a verbatim equal sign. It is exported as such. There are a few solutions to your problem: - Use Org's separator: -; - Disable every emphasis interpretation in the buffer with option *:nil; - Configure format string for verbatim text (org-e-ascii-verbatim-format). That will affect ~code~, =verbatim= and inline src blocks. - Use another separator (i.e. = = =) Most lines are indented by 2 spaces. I'd prefer flush to left. You may customize `org-e-ascii-inner-margin'. It splits the window even though I have pop-up-windows set to nil. This variable is related to `display-buffer', which isn't used to display output. You may want to tweak `org-export-show-temporary-export-buffer', though. Block quotes indent by 8 or so. That's rather nice, but is there an option to change that to 2 or 4? I've pushed a commit introducing variable `org-e-ascii-quote-margin' to solve this. Lists are not indented although I always indent them by 2. e-ascii back-end has its own (configurable) layout. In particular, it doesn't bother with the indentation you use in the original Org buffer. I'm not convinced that lists should be made special and have their own margin variable. There are not many visual markers in the ASCII output, indentation being one of them. I prefer to use them parsimoniously. Is there an option to set the fill column and refill paragraphs (roughly like the way HTML does)? I'd find that highly useful. By default, text is already filled at a fill column of 72. You may customize `org-e-ascii-text-width' for different values. Feature requesti --export tables using tab characters. If it doesn't exist already. Maybe it does? Do you mean inserting tabs instead of white spaces in cells? If that's the case, I'd rather not implement it. Footnotes don't have a header. HTML export inserts one. I've pushed a commit introducing a header for the final footnotes. No final newline. I've pushed a commit fixing this. One missing footnote . It is going to take me a while to narrow it down. I cannot help with so little information. Though, I'd be interested in an ECM. Thanks for your feedback. Regards, -- Nicolas Goaziou
Re: [O] org mode in press
On Jan 28, 2012, at 6:14, Christian Wittern cwitt...@gmail.com wrote: The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). The dot executable is part of the graphviz package. Installing graphviz should install the dot command line executable alongw w/ neato, circo and and other layout engines. Rick
Re: [O] Marking specific elements for folding?
Hello! Thanks for the suggestion, but sadly it doesn't entirely fit my intention; The subheadings in particular kill the purpose of hiding, because it makes something, of which I want only a here is something folded indication in a full text view show up in the content view and forces me to introduce subheadings, were I'd rather not have any (after all, overstructuring is as much a diversion from the actual workflow as understructuring). As an alternative (and when the stuff is too unimportant for the main document but still should be exportable as a separate pdf), outsourcing parts to an external org file would be okay too, but there I did not yet find a possibility to refer to a table in a totally different file, e.g. * There is a data table in the main file. * In a child file I want to do some processing using Babel (in particular with gnuplot, but maybe also python, elisp... depending on the case). Here I want to avoid having to copy the tables back and forth, but would rather directly use the data from the main file in the child file (in order to avoid having outdated data in the child file). HOWEVER: For the case where I really just want to hide parts of the documents, that will never be exported as a document and usually shouldn't be visible while editing, I found a solution right now, using the /drawers/ functionality. : # .. Must add PROPERTIES drawer, because otherwise : # .. tree local property definitions will be exported as text. : #+DRAWERS: PROPERTIES HIDDEN : : * Hello World : : #+TBLNAME: hello-world-table : | This is a data table | : : # .. This block is folded to just : # .. :HIDDEN:... : # .. unless explicitly unfolded. : :HIDDEN: : #+BEGIN_SRC gnuplot :var data=hello-world-table :file foo.pdf :fold that block header argument : set term pdfcairo mono : plot data using 1:2 blablabla : #+END_SRC : :END: : : And this table looks like [[foo.pdf]] when folded. king regards, Yu 2012/1/27 Eric S Fraga e.fr...@ucl.ac.uk: Yu yu_...@gmx.at writes: Hello! I was wondering, if there is a way to mark specific elements for staying folded unless explicitly shown. Reading the manual I only found possibilities to control the global folding of sections and blocks in general. However, what I want to do is: - Embed a table of numerical data in my org-mode file. - Perform calculations on the data, using the spread sheet capabilities. - Plot the data, preferably using a (probably lengthy) gnuplot script. - Export only the result graph. However, the calculations are usually not wanted to be seen, when looking at the file, so I'd like to specify, that this specific table and this specific gnuplot code block are to be folded by default. Is there some way to achieve this? If you are not planning on exporting the data and code, you can put them into a subheading and COMMENT it out. I do this frequently. See the attached file for a simple example. The really nice thing, for me, is that you can have the results appearing *before* the data and code... This is not necessarily so long as you can put the results in some other heading, say. HTH, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1 : using Org-mode version 7.8.03 (release_7.8.03.243.g0e7f)
Re: [O] [PATCH] org-mobile agenda title
Hi Henning, Henning Weiss hdwe...@gmail.com writes: I have been working on a patch for mobileorg-android that improves the displaying of the generated agendas.org file. The problem I'm having is that TITLE: fields of all entries are generated by concatenating the name and the matching criterion of an entry. The issue is discussed in further details here. I have tried to create a patch that removes the match criterions from the generated title entry and attached it below. This could potentially break other org-mobile clients and might not be the best way to solve this. What would it take to include this in orgmode? The patch looks okay to me (I read the discussion you pointed to.) Richard, would this patch break anything on your side? Thanks, -- Bastien
Re: [O] [PATCH] Link to Org file: regard startup view state
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: I would like to ask for a review of the attached patch that resolves an issue with org-open-at-point. Applied, thanks for the detailed explanations and the patch. -- Bastien
Re: [O] [PATCH] [Beamer export] Example should better export to exampleblock environment
Hi Thorsten, Torsten Anders torsten.and...@beds.ac.uk writes: It is great that org mode makes creating Beamer slides so easy! I would like to include some green example blocks in my slides (e.g., for exercises for my students), and I can turn an org headline and its content into an example block by just pressing C-c C-b e -- very nice. Now, my problem is that Org mode exports this as a Beamer example environment, instead of an exampleblock environment. The difference is that the exampleblock environment is just a green block that otherwise behaves like the standard Beamer blocks (in particular, users have full control over its title), while an example environment always adds something to the title like this: Example (ACTUAL TITLE). Such behaviour may be useful in special cases, but the exampleblocks are more flexible and should therefore at least be supported as an alternative option, but likely being the default export option. Attached to this message there is a simple patch that adds support for exampleblocks (short cut C-c C-b E) by keeping everything else as it is. Applied, thanks. As for whether using `exampleblock' should be the default rather than `example', people like Eric S Fraga (or other beamer gurus) would have a better advice than mine. Eric? Thanks! -- Bastien
Re: [O] Drawers within inline tasks
Hi Viktor, Viktor Rosenfeld listuse...@googlemail.com writes: Ideally I would like to be able to configure the visibility behavior of inline tasks. I think I would prefer them to behave just like normal tasks. Unfolding an inline task now keeps the drawers folded. Thanks for the suggestion, -- Bastien
Re: [O] [Babel] [PATCH] Customize regular expression to match noweb references
On Fri, Jan 27, 2012 at 11:05 PM, Eric Schulte eric.schu...@gmx.com wrote: Good idea, I've changed your implementation to rely on two new customization variables `org-babel-noweb-wrap-start' and `org-babel-noweb-wrap-end' as this provides more flexibility to the backend implementation to place constraints on the properties of the noweb names. In you're situation you will now want to set... (setq org-babel-noweb-wrap-start « org-babel-noweb-wrap-end ») Thanks for the great idea, Seems to work fine. Thanks for implementing it so quickly and thanks for org-babel! Regards, Sean
Re: [O] Invalid read syntax #?
Hi Alan, Alan Schmitt alan.schm...@polytechnique.org writes: I'm trying this example to export nicely formatted code in LaTeX: http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3 Unfortunately it fails with an error 'Invalid read syntax #'. If I delete the second code block (the python one), it works. For some reason, the first code block is evaluated twice. 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. -- Bastien
Re: [O] org-remember to org-capture
Hi Martin, Martin Pohlack m...@os.inf.tu-dresden.de writes: I am in the process of switching from org-remember to org-capture. Possibly useless hint: M-x org-capture-import-remember-templates RET Can you restate the problem more directly? What are your capture template, what is it supposed to achieve, how does it fail to do what you want -- we'll work out something from there. Thanks, -- Bastien
Re: [O] BUG: Latex exporter bug
Hi Tomas, Tomas Grigera tgrig...@gmail.com writes: I have found the following issue when exporting to Latex: a headline is sometimes moved to another position when skipping a level in the hierarchy. The following demonstrates the problem: This is a known issue and can't be handled with the current exporter. The workaround is to stick to a logical structure. Best, -- Bastien
Re: [O] Drawers within inline tasks
Hi Bastien, Bastien wrote: Unfolding an inline task now keeps the drawers folded. Thanks for the quick patch, but there's a small problem. The drawer is collapsed if the inline task is opened, but not if the parent task is opened. Example: * Parent Task *** Inline Task :PROPERTIES: :Effort: 0:15 :END: *** END Pressing TAB on Inline Task keeps the property drawer collapsed. Pressing TAB on Parent Task opens it. Cheers, Viktor
Re: [O] [BUG] Inconsistency in src block hiding
Hello, Eric Schulte eric.schu...@gmx.com writes: To my mind a better path moving forward would be to change the behavior of the :RESULTS: drawer so that it is exported but *not* to change the default drawer export behavior. This way with a :wrap header argument the code block results could be hidden with tab but would still be exported. PRO: allows hiding code block results with tab, makes it clear where results begin and end, uses drawers for hiding which is what they are designed for, avoids the potential for hiding anything with a name CON: more syntactic weight around results, changes the existing default behavior, makes the RESULTS drawer a special type of drawer While implementing a recent patch about drawers insertion, I realized my current view about drawers had a flaw. Indeed, while I had correctly put aside properties drawers, which are very different from regular drawers, I had overlooked special drawers like LOGBOOK and CLOCK. Those drawers are different from regular drawers, since they are attached to an headline (this is not the case of a RESULTS drawer), and as such should be classified in another category. Therefore, I suggest the following fixed behaviour with regards to export for drawers: - Properties drawers :: Still ignored in export, independently on d option or `org-export-with-drawers' value. Obviously, back-end can ignore this specification, but it should be followed by major ones. - Special drawers :: Not exported by default. Though, their export can be configured with a new sd option item (i.e. sd:t) or `org-export-with-special-drawers' variable. This category only includes LOGBOOK[1] and CLOCK drawers at the moment. If their export is activated, the special `org-backend-format-drawer-function' (i.e. `org-e-latex-format-drawer-function') can allow to tweak their output. - Regular drawers :: Exported by default. d:nil turns that off. This category includes RESULTS drawers and every user created drawer. `org-backend-format-drawer-function' still can help tweaking their output. Thus, it can be used to filter out some types of drawers. With that model, drawers will be able to fill a niche by allowing to hide data in an Org buffer while still wanting to export it. As a reminder, currently with d:nil, drawers are redundant with #+begin_comment blocks, and with d:t they are redundant with #+begin_example blocks. d:'(some names) is just a mix of comment and example blocks. Note that it has the same advantages as your suggestion. What do you think? Regards, [1] Or whatever the user specified in `org-log-into-drawer'. -- Nicolas Goaziou
Re: [O] org mode in press
Aloha Christian, Thanks for your comments. It is great to have feedback. Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Could you be more specific here? It might be obvious to others, but I don't understand what you mean by proper fontification. All the best, Tom Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Thomas S. Dye http://www.tsdye.com
Re: [O] org mode in press
Christian Wittern cwitt...@gmail.com wrote: The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). On linux, the graphviz package install a bunch of libraries and a bunch of commands. The commands are: , |Graph layout programs |dotfilter for hierarchical layouts of graphs | |neato filter for symmetric layouts of graphs | |twopi filter for radial layouts of graphs | |circo filter for circular layout of graphs | |fdpfilter for symmetric layouts of graphs | |All of the filters work with either directed or undirected graphs, though dot is typically |used for directed graphs and neato for undirected graphs. Note also that neato -n[2] can be |used to render layouts produced by the other filters. | |Graph drawing programs |lefty A Programmable Graphics Editor | |lneato lefty + neato | |dotty lefty + dot | |Graph layout enhancement |gvcolor | flow colors through a ranked digraph | |unflatten | adjust directed graphs to improve layout aspect ratio | |gvpack merge and pack disjoint graphs | |Graph information and transformation |gc count graph components | |acyclic | make directed graph acyclic | |noppretty-print graph file | |ccomps connected components filter for graphs | |sccmap extract strongly connected components of directed graphs | |tred transitive reduction filter for directed graphs | |dijkstra | single-source distance filter | |bcomps biconnected components filter for graphs | |gvpr graph pattern scanning and processing language | |prune prune directed graphs | |Other |gxl2dot, dot2gxl | GXL-DOT converters ` There is no graphviz executable as such. I would expect a similar setup on MacOS. The man page refers to http://www.graphviz.org/Documentation.php for more info. HTH, Nick
Re: [O] org mode in press
I would also like to thank you for this great article and org-mode in general. I learned a few things about variables and chaining that I did not know about. Since I discovered org-mode, I have come to rely upon it as my extended memory for professional as well as domestic ideas and problems that I encounter. I keep one big notes.org file in which my first level headlines is the current date, and my second order headline usually contains a Done/Todo which is a checklist of things that I have to do. I also love the embedded code (though I wish it was possible to syntax highlight it!), external links, and tables. Thanks again! Dov On Sat, Jan 28, 2012 at 18:18, Thomas S. Dye t...@tsdye.com wrote: Aloha Christian, Thanks for your comments. It is great to have feedback. Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Could you be more specific here? It might be obvious to others, but I don't understand what you mean by proper fontification. All the best, Tom Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Thomas S. Dye http://www.tsdye.com
Re: [O] org mode in press
Dov Grobgeld dov.grobg...@gmail.com writes: I would also like to thank you for this great article and org-mode in general. I learned a few things about variables and chaining that I did not know about. Since I discovered org-mode, I have come to rely upon it as my extended memory for professional as well as domestic ideas and problems that I encounter. I keep one big notes.org file in which my first level headlines is the current date, and my second order headline usually contains a Done/Todo which is a checklist of things that I have to do. Great to hear, happy it is useful even to those who already have Org-mode experience. I also love the embedded code (though I wish it was possible to syntax highlight it!), It is possible, just add the following to your Emacs configuration. (setq org-src-fontify-natively t) Cheers, external links, and tables. Thanks again! Dov On Sat, Jan 28, 2012 at 18:18, Thomas S. Dye t...@tsdye.com wrote: Aloha Christian, Thanks for your comments. It is great to have feedback. Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Could you be more specific here? It might be obvious to others, but I don't understand what you mean by proper fontification. All the best, Tom Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Thomas S. Dye http://www.tsdye.com -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] org mode in press
Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Wonderful. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. This is surprising, on the two GNU/Linux distributions I've tested this on I am prompted to pick an R install directory which defaults to ~/R in my home directory so no super-user privileges are required. My original motivation for switching from OSX to GNU/Linux was precisely this sort of weird Mac-specific library install issues across a number of tools (most notably LaTeX). Although, a couple of years after switching my reasons for not switching back are legion. :) Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Keep up the excellent work!! Thanks!, Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel][patch] BUG in inline source blocks
Eric Schulte eric.schu...@gmx.com writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Martyn Jago martyn.j...@btinternet.com writes:
Martyn Jago martyn.j...@btinternet.com writes:
Hi,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
I experience unexpected behaviour when an inline source block is not
preceded by whitespace.
Example:
===
* Test inline
This is a functional inline src_R{print(source block)}.
This (src_R{print(here)}) is not.
===
Regards,
Andreas
I can confirm this behaviour and provide a patch to allow for inline
source blocks to be preceded by punctuation, or, for instance, enclosed
in parenthesis, as in Andreas' example. Patch is attached for
consideration.
Best, Martyn
This is an updated version of the previous patch, with debug noise
removed, and a couple of extra tests.
Best, Martyn
Thanks for this patch Martyn, I just pushed up your [:punct:] change.
Hi Martyn,
thanks for this patch! It does half the job for me. Now export (or
evaluation) already work. But in the export I get a space inserted.
I my example, I'd expect (here) to appear in the export, but I get
( here).
This should now be fixed.
Thanks, Martyn and Eric! Indeed both issues are fixed now.
Regards,
Andreas
Re: [O] Blog-like sitemap for org-publish
Bastien b...@altern.org: Jon Anders Skorpen jasko...@mindmutation.net writes: Yes. Here is a link to a test blog with some test posts, and one real post in norwegian. http://beta.mindmutation.net This looks really great! Maybe the most simple thing to do for now is to submit org-blog.el as a separate file to the mailing list, and add FIXME comments in functions that borrow too much code from org-publish.el -- it will help refactoring. Did anything more happen with this? There is no org-blog.el in contrib/lisp, at least...?
Re: [O] BUG: Latex exporter bug
Hi Bastien I have found the following issue when exporting to Latex: a headline is sometimes moved to another position when skipping a level in the hierarchy. The following demonstrates the problem: This is a known issue and can't be handled with the current exporter. The workaround is to stick to a logical structure. Sorry, I had missed when this was discussed. Thanks for your answer. Cheers, Tomas
Re: [O] org mode in press
Nick Dokos nicholas.do...@hp.com wrote: Christian Wittern cwitt...@gmail.com wrote: The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). On linux, the graphviz package install a bunch of libraries and a bunch of commands. The commands are: ... ... and afaict, all the commands are symlinks to the dot executable (/usr/bin/dot). Nick There is no graphviz executable as such. I would expect a similar setup on MacOS. The man page refers to http://www.graphviz.org/Documentation.php for more info. HTH, Nick
Re: [O] org-src-fontify-natively (was: org-mode in the press)
Great! That must be a new addition that I missed. It is not perfect though, as I use a variable font for org-mode, which is inherited by the embedded source code block when I turn on org-src-fontify-natively . Is there any way of preventing that so blocks are always in e.g. Inconsolata? I found that the block background color may be changed by org-block-background which is nice to make a visual distinction of source code sections! Regards, Dov On Sat, Jan 28, 2012 at 19:06, Eric Schulte eric.schu...@gmx.com wrote: I also love the embedded code (though I wish it was possible to syntax highlight it!), It is possible, just add the following to your Emacs configuration. (setq org-src-fontify-natively t) Cheers, external links, and tables. Thanks again! Dov On Sat, Jan 28, 2012 at 18:18, Thomas S. Dye t...@tsdye.com wrote: Aloha Christian, Thanks for your comments. It is great to have feedback. Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Could you be more specific here? It might be obvious to others, but I don't understand what you mean by proper fontification. All the best, Tom Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote: Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick -- Thomas S. Dye http://www.tsdye.com -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] how do scientists use org mode?
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-src-fontify-natively (was: org-mode in the press)
I investigated this and found that this may almost be fixed by doing: ;; Make all font-lock faces fonts use inconsolata (dolist (face '(font-lock-builtin-face font-lock-comment-delimiter-face font-lock-comment-face font-lock-constant-face font-lock-doc-face font-lock-function-name-face font-lock-keyword-face font-lock-negation-char-face font-lock-preprocessor-face font-lock-regexp-grouping-backslash font-lock-regexp-grouping-construct font-lock-string-face font-lock-type-face font-lock-variable-name-face font-lock-warning-face)) (set-face-attribute face nil :family my-default-family)) But unfortunately not fully, because both source code (at least in python) and org-mode make use of the default font. And since I change this at org-mode startup to the variable-pitch the result is that I inherit this in the source code blocks as well. A solution would be that all org-mode faces would inherit a common org-mode-face. You could then customize this font to a variable-pitch without using the ~variable-pitch-mode~ command. Is this feasible? Regards, Dov On Sat, Jan 28, 2012 at 19:30, Dov Grobgeld dov.grobg...@gmail.com wrote: Great! That must be a new addition that I missed. It is not perfect though, as I use a variable font for org-mode, which is inherited by the embedded source code block when I turn on org-src-fontify-natively . Is there any way of preventing that so blocks are always in e.g. Inconsolata? I found that the block background color may be changed by org-block-background which is nice to make a visual distinction of source code sections! Regards, Dov On Sat, Jan 28, 2012 at 19:06, Eric Schulte eric.schu...@gmx.com wrote: I also love the embedded code (though I wish it was possible to syntax highlight it!), It is possible, just add the following to your Emacs configuration. (setq org-src-fontify-natively t) Cheers, external links, and tables. Thanks again! Dov On Sat, Jan 28, 2012 at 18:18, Thomas S. Dye t...@tsdye.com wrote: Aloha Christian, Thanks for your comments. It is great to have feedback. Christian Wittern cwitt...@gmail.com writes: I think this is an excellent article, introducing an aspect of org-mode, which I think fills a gap that no other software I know of comes even close to approach. I already started mentioning it in conversations and am sure it will be very useful to many members of the academic community. Just to make sure I could answer any follow up questions, I downloaded the replication bundle and started installing the dependencies. I encountered a few problems and hope this is the right place to discuss them. BTW, I am working with this on a Mac OS X 10.6 machine. Most of the dependencies I already had or installed them from macports. One problem I encountered was with installing the RSQLite package. Executing the installation command from the README file did not work because of permission issues, the command needs to run with superuser rights. Is it possible to give these rights to commands run from babel? Since I did not find a way to do that, I installed from the R commandline, where I found that the name of the package is RSQLite, not 'RSQlite' as given in the readme file. The one dependency I could not solve was the 'dot' executable. I assume this is an interpreter for the dot language, for which it seems the program on the Mac is named graphviz. However, I am not sure how to make that work with org/babel. Should I simply symlink to graphviz? Or is there a babel variable to be set? This is a point that probably needs some explanation, at least for Mac users (I realize that the articel might not have been intended as such a general introduction with details for all common OSses, but it would be nice if this can be gradually supplemented). One last remark; since this is an online publication, I think using proper fontification for the examples and org source code would be even more appealing, especially for people who encounter org for the first time. Could you be more specific here? It might be obvious to others, but I don't understand what you mean by proper fontification. All the best, Tom Keep up the excellent work!! Christian On 2012-01-27 23:43, Eric Schulte wrote: Hopefully this will serve as the canonical introduction to working with code blocks in Org-mode. As we acknowledge in the paper this work would not have been possible without the ideas and feedback of the Org-mode community, so thanks all! Nick Dokosnicholas.do...@hp.com writes: Andreas Lehaandreas.l...@med.uni-goettingen.de wrote:
Re: [O] Non-interactive insertion of future-dates
Thanks Borbus, it works! See my followup to Jonathan's answer on my plans to add relative dates to the template expansion. Best wishes, Simon
Re: [O] [PATCH] org-mobile agenda title
On Sat, Jan 28, 2012 at 3:41 PM, Bastien b...@altern.org wrote: Hi Henning, Henning Weiss hdwe...@gmail.com writes: I have been working on a patch for mobileorg-android that improves the displaying of the generated agendas.org file. The problem I'm having is that TITLE: fields of all entries are generated by concatenating the name and the matching criterion of an entry. The issue is discussed in further details here. I have tried to create a patch that removes the match criterions from the generated title entry and attached it below. This could potentially break other org-mobile clients and might not be the best way to solve this. What would it take to include this in orgmode? The patch looks okay to me (I read the discussion you pointed to.) Richard, would this patch break anything on your side? Thanks, -- Bastien Hi again, I have a little revision to the patch to remove the matching criterion from normal (ie. non-block) agendas as well. See below. best regards, Henning Weiss --- a/lisp/org-mobile.el +++ b/lisp/org-mobile.el @@ -574,7 +574,7 @@ The table of checksums is written to the file mobile-checksums. (concat afterKEYS= key TITLE: (if (and (stringp desc) ( (length desc) 0)) desc (symbol-name type)) - match /after)) + /after)) settings)) (push (list type match settings) new)) ((or (functionp (nth 2 e)) (symbolp (nth 2 e))) @@ -592,7 +592,7 @@ The table of checksums is written to the file mobile-checksums. (cons (list 'org-agenda-title-append (concat afterKEYS= gkey # (number-to-string (setq cnt (1+ cnt))) -TITLE: gdesc match /after)) +TITLE: gdesc /after)) settings)) (push (list type match settings) new) (and new (list X SUMO (reverse new)
[O] Xemacs: org-preview-latex-fragment, png not readable.
Hello I made some progress in getting the function to work in Xemacs. The main problem seemed to be the function org-dvipng-color which is called in org-create-formula-image. The original formulation was (defun org-dvipng-color (attr) Return an rgb color specification for dvipng. (apply 'format rgb %s %s %s (mapcar 'org-normalize-color (color-values (face-attribute 'default attr nil) Which does not work for Xemacs. Thanks to Julian Bradfield, the solution seems to be: (defun org-dvipng-color (attr) Return an rgb color specification for dvipng. (apply 'format rgb %s %s %s (mapcar 'org-normalize-color (color-rgb-components (face-property 'default (intern (substring (symbol-name attr) 1))) However the png which were generated where to small to be readable. I attach one at the end of the message. So I tried out in GNU Emacs 21.3 to comment out org-dvipng-color in org-create-formula-image. org-preview-latex-fragment then still works, so is not necessary for generating the pngs. So I tried to do the same in Xemacs but the formulas in the png files keep being too small. What could be the reason for this behavior? Uwe Brauer The following attachment should be an integral. Xemacs: attachment: test3_7801a85c58c7aabc4553724e826b458ba08dda90.png Gnu Emacs attachment: test_7ceb32811fbcd1322f595ca60dcc47456c20b5fe.png
Re: [O] [ANN] ASCII back-end for new export engine
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote: If you don't know which one it is, you can successively mark each table in that buffer and use org-export-dispatch with the region active (it will only export the region) until the culprit is found. I get Before first headline at position ... error. Can't send stack trace now. (org-e-ascii-verbatim-format). That will affect ~code~, =verbatim= and inline src blocks. Can these be affected individually? Or can emphasis be told to be always left in verbatim? It splits the window even though I have pop-up-windows set to nil. Rationale: It is true that this only applies to display-buffer. And this is not only a problem with your exporter. But most of Emacs can be made to work properly with this variable. There are parts that do not. Those require an ever-expanding list of defadvices, same-window-*, and other kludges to use the same window. pop-up-windows is a good candidate for the user to signal the intention to do this for all output buffers. In any case, I added a defadvice. There does not exist any way to say Do not split output windows. So it is a constant struggle. Lists are not indented although I always indent them by 2. e-ascii back-end has its own (configurable) layout. In particular, it doesn't bother with the indentation you use in the original Org buffer. I'm not convinced that lists should be made special and have their own margin variable. There are not many visual markers in the ASCII output, indentation being one of them. I prefer to use them parsimoniously. I might need to stick with the old exporter then. Here are 2 reasons I like indented lists: 1) Notice how it is set off so you know when the end of the list is? 2) Other reasons Feature requesti --export tables using tab characters. If it doesn't exist already. Maybe it does? Do you mean inserting tabs instead of white spaces in cells? If that's the case, I'd rather not implement it. No, I mean that this is a useful way to send things to people who use proportional fonts. Thanks for your feedback. Thanks for your work on the exporter. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] Solved (was: Xemacs: org-preview-latex-fragment, png not readable.)
On Sat, 28 Jan 2012 21:20:48 +0100, Uwe Brauer o...@mat.ucm.es wrote: Which does not work for Xemacs. Thanks to Julian Bradfield, the solution seems to be: (defun org-dvipng-color (attr) Return an rgb color specification for dvipng. (apply 'format rgb %s %s %s (mapcar 'org-normalize-color (color-rgb-components (face-property 'default (intern (substring (symbol-name attr) 1))) However the png which were generated where to small to be readable. I attach one at the end of the message. The issue are the options in call-process dvipng nil nil nil After trying out different configurations, I found out that the option -D dpi Does not work well with Xemacs. So (call-process dvipng nil nil nil -fg fg -bg bg ;; -D dpi ;; -x scale -y scale -T tight -o pngfile dvifile) is ok, however the back and foreground setting as generated by org-dvipng-color, even with Julian Bradfield's patch do not produce very nice results. In my Xemacs setting it is better to comment them out. So there are two small changes necessary to make org-preview-latex-fragment work in Xemacs. One is the above change, the other (font-height (face-font 'default)) instead of (font-height (get-face-font 'default)) I can send a patch against 7.8.03 Uwe Brauer
Re: [O] org-remember to org-capture
Hi Bastien,
thanks for your reply.
On 28.01.2012 17:00, Bastien wrote:
Hi Martin,
Martin Pohlack m...@os.inf.tu-dresden.de writes:
I am in the process of switching from org-remember to org-capture.
Possibly useless hint: M-x org-capture-import-remember-templates RET
Yes thanks. Unfortunately, this does not convert my custom function :-).
In fact, it does not convert anything (with org-mode 7.6).
Can you restate the problem more directly? What are your capture
template, what is it supposed to achieve, how does it fail to do
what you want -- we'll work out something from there.
All right, here is my (stripped down) setup:
'(org-remember-templates (quote (
(Inbox-Arbeit 97 * INBOX %^{Title}
%U%?
%i ~/Daten/plan_arbeit.org my-org-remember-headline nil)
(Inbox-Privat 112 * INBOX %^{Title}
%U%?
%i ~/Daten/plan_privat.org my-org-remember-headline nil)
(Journal 106 * %^{Eintrag}%?%i% ~/Daten/Journal.org
return_formated_date nil
Let' focus on the first entry (Inbox-Arbeit): the only non-standard
thing here is the function my-org-remember-headline.
8
(defun my-host-name ()
Returns the name of the current host minus the domain.
(let ((hostname (downcase (system-name
(save-match-data
(substring hostname (string-match ^[^.]+ hostname) (match-end 0)
(defun my-org-remember-headline ()
(concatenate 'string Inbox: (my-host-name)))
8
Run on “host1” it will return “Inbox:host1”, etc.
My “plan_arbeit.org” file contains this structure:
8
* Inbox
*** Inbox:host1
*** Inbox:host2
8
So that each machine has a separate inbox under a global container.
This reduces git merge conflicts when I merge my plan files from
different machines (but this is a side discussion).
What changed from org-remember to org-capture is that custom functions
used to return a string with a target parent headline. Now they are
expected to modify “point” as a side effect before the actual capturing
happens (and not return anything).
Here is my new capture template:
'(org-capture-templates (quote (
(a Inbox-Arbeit entry
(file+function ~/Daten/plan_arbeit.org my-org-capture-function)
* INBOX %^{Title}
%U%?
%i
I drafted this new function for org-capture:
8
(defun my-org-capture-function ()
(goto-char
(org-find-exact-headline-in-buffer
(concatenate 'string Inbox: (my-host-name)) nil t))
(org-end-of-line)
(org-insert-subheading ))
8
This shall capture again under “Inbox/Inbox:$hostname”.
The function feels clumsy because this functionality should already be
in org-mode (e.g., the refiling stuff). Also, it files new items as
first child under the target and not as last child.
The question is simply: Is there a more elegant approach, maybe using
the refiling mechanism? Have I overlooked something obvious?
Thanks,
Martin
Re: [O] [ANN] ASCII back-end for new export engine
Samuel Wales samolog...@gmail.com writes: On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote: If you don't know which one it is, you can successively mark each table in that buffer and use org-export-dispatch with the region active (it will only export the region) until the culprit is found. I get Before first headline at position ... error. Can't send stack trace now. Ok. Be sure to have latest git, though. (org-e-ascii-verbatim-format). That will affect ~code~, =verbatim= and inline src blocks. Can these be affected individually? No. Or can emphasis be told to be always left in verbatim? Yes. Simply override actual function translating verbatim text by putting this in your config. #+begin_src emacs-lisp (defun org-e-ascii-verbatim (verbatim contents info) Return a VERBATIM object from Org to ASCII. CONTENTS is nil. INFO is a plist holding contextual information. (let ((marker (org-element-get-property :marker verbatim)) (value (org-element-get-property :value verbatim))) (concat marker value marker))) #+end_src 1) Notice how it is set off so you know when the end of the list is? - This is an item with some text. This is obviously inside the list. This is obviously outside the list. Feature requesti --export tables using tab characters. If it doesn't exist already. Maybe it does? Do you mean inserting tabs instead of white spaces in cells? If that's the case, I'd rather not implement it. No, I mean that this is a useful way to send things to people who use proportional fonts. But in the simplest cases, tables will look ugly with proportional fonts, no matter if you use tabs or not. It isn't worth the struggle. Regards, -- Nicolas Goaziou
Re: [O] [ANN] ASCII back-end for new export engine
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote: - This is an item with some text. Sets off much less. No, I mean that this is a useful way to send things to people who use proportional fonts. But in the simplest cases, tables will look ugly with proportional fonts, no matter if you use tabs or not. It isn't worth the struggle. Simplest case is perhaps short numbers which always works perfectly with tabs. Even with ugliness, tabs make it easier to understand the table IMO. I won't press the issues, but did not want those to be misunderstood.
Re: [O] Blog-like sitemap for org-publish
Steinar Bang s...@dod.no writes: Maybe the most simple thing to do for now is to submit org-blog.el as a separate file to the mailing list, and add FIXME comments in functions that borrow too much code from org-publish.el -- it will help refactoring. Did anything more happen with this? There is no org-blog.el in contrib/lisp, at least...? I got no answer to my last email in this thread, so I assumed the author was not motivated enough to make org-blog.el part of contrib/. But hopefully I'll prove wrong :) -- Bastien
Re: [O] Solved
Hi Uwe, Uwe Brauer o...@mat.ucm.es writes: So there are two small changes necessary to make org-preview-latex-fragment work in Xemacs. One is the above change, the other (font-height (face-font 'default)) instead of (font-height (get-face-font 'default)) I can send a patch against 7.8.03 Please do so -- but please make sure the patch adapts current code to XEmacs without suppressing any feature for GNU Emacs. Thanks in advance! -- Bastien
Re: [O] Non-interactive insertion of future-dates
Hey Jonathan,
thanks for the hints, it works like a charm! As far as I can overlook
this, adding relative dates to the template expansion should not be a
lot of work, basically one just has to add a simple wrapper to
org-read-date. I gave some more thoughts to an appropriate symbol and
the best I could come up with is '_'. I therefore propose the following:
% {EXP}t, %_{EXP}T, %_{EXP}u, %_{EXP}U
in a capture-template inserts an (in-)active date-/timestamp that would
have resulted from manually entering the expression EXP at the
interactive date-/timeprompt.
If no serious objections come up, I will put this on my todo-list.
Best wishes,
Simon
On Wed, 25 Jan 2012 12:56:37 -0500, Jonathan Leech-Pepin
jonathan.leechpe...@gmail.com wrote:
Hello,
On Wed, Jan 25, 2012 at 11:42, Simon Campese emacs-orgm...@campese.de wrote:
Dear community,
I want to setup a capture-template that sets a
SCHEDULE-property in the future (say one week from today) without any
user interaction.
Currently, I almost achieve this by inserting the line
:SCHEDULED: %(org-read-date nil nil nil nil nil +1w)
into my template. When I now call the template, I end up in the
date-time-prompt, with +1w prefilled, so that manually have to press
enter.
Maybe it is trivial to call an interactive lisp-function and emulate
some keypress, in which case I would be thankful for the code that
achieves this (my lisp-skills are limited). Also, one should be able to
achieve what I want by using format-time-string and increment the
current time, but again my lisp-skills prohibit me from implementing it
myself.
A similar question had come up on StackOverflow (
http://stackoverflow.com/questions/7986935/using-org-capture-templates-to-schedule-a-todo-for-the-day-after-today/7988809#7988809
).
My answer there should apply, adjusting the offset from +1d to +1w :
SCHEDULED: %(org-insert-time-stamp (org-read-date nil t \+1d\))
Alternately you can include the SCHEDULED: portion within the
timestamp insertion itself. This example will also include a fixed
time at which to schedule the item (unneeded in this case I suspect
but it could be of use elsewhere) :
(org-insert-time-stamp (org-read-date nil t \+1w 12:00\) t nil
\SCHEDULED: \)
In any case, it might be a good idea to include non-interactive access
to relative times in template expansion, so that for example one
can state something like %t[+1w] or %{+1w}t in the template to get the
date one week from today (one should spend some more time to specify the
actual input-format of course...). What do you think?
I agree, adding the ability to automatically have relative dates would
allow for quicker capture templates if you regularly need to to set
them with a specific offset.
Thank you very much,
Simon
Regards,
Jonathan
Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails
-snip--
#+property: session *R-babel*
#+NAME: foo
#+HEADER: :var a=a1.png
#+BEGIN_SRC R :results output silent
cat(in foo block\n)
cat.a - function() { cat(a,\n,sep=) }
cat.a()
#+END_SRC
#+call: foo(a=a1.png)
#+begin_src R :results output raw replace :exports results
cat.a()
#+end_src
--snip-
OK, I see what you mean. When I evaluate this buffer multiple times the
results of the #+call: line *are* replaced as expected, but the final
code block can not replace it's results because of the raw option to
the :results header argument. The raw and replace header arguments
are not compatible because with raw results there is no way to know
where the results end. I believe this is mentioned in the manual, if
not it should be.
Ok, I see. Ideally, incompatible arguments should trigger an error
condition that would be communicated to the user (at the very least,
by printing a message in the minibuffer). Silent failures are
annoying, even if documented :)
On a more practical note, is there _a_ method of achieving what I'm
trying to do here, namely, to place an image in the buffer in a way
that would be understood by Org and that would be properly imported in
HTML?
Referring to what I said in another thread (the principle of least
surprise): it makes a lot of sense for the call lines to behave the
same way a function call, or a source() statement would behave in the
interpreter session of the original language. From that perspective,
the current behavior seems wrong. Can you come up with a scenario /
usage pattern where the current behavior is more desirable?
The only loss of functionality would be the ability in the existing
model to have a call line and it's results live in separate locations.
Given that call lines can not currently be named their results are named
by the information on the call line (called function, header arguments,
etc...) which will be identical for identical call lines, leading to the
current confusing behavior.
I think the best way forward would be to
1. stop auto-naming #+call: lines as we are currently and instead leave
their results anonymous as with code blocks, and by default inserted
immediately after the #+call: line.
2. allow names to be applied to call lines, which can then be used to
identify their results and locate their results remotely in the
buffer.
If this sounds like a good way forward then I'll put it on my queue for
some time in the when-I-have-more-time future. :)
Yes, I think it's a good long-term plan. Enqueue it :) In the
meantime, the current behavior (and the possible workaround) should
probably be mentioned in the docs if it isn't already.
--Leo
Re: [O] Drawers within inline tasks
Hi Viktor, Viktor Rosenfeld listuse...@googlemail.com writes: Thanks for the quick patch, but there's a small problem. The drawer is collapsed if the inline task is opened, but not if the parent task is opened. Example: * Parent Task *** Inline Task :PROPERTIES: :Effort: 0:15 :END: *** END Pressing TAB on Inline Task keeps the property drawer collapsed. Pressing TAB on Parent Task opens it. Fixed, thanks. I first didn't take care of this because it seemed logical to show all the content of an inline task here: the purpose of the inline task is to stay out of the hierarchical structure, such a task is *not* a subtree... so the real content of Parent task is all the text below -- whether it contains inline tasks or not. But I can see that it's not visually consistent with the habit of keeping stuff folded, so let's go that way. Thanks for reporting this, -- Bastien
Re: [O] Possible bug in org-cycle with property drawer
Hi Achim, Achim Gratz strom...@nexgo.de writes: Bastien b...@altern.org writes: Thinking again about your problem, I don't find it natural to have #+DRAWERS /replacing/ existing drawers specified in `org-drawers', instead of just adding new ones. Well, if one had defined a lot of drawers in their configuration and wanted the list to be trimmed in a few documents... This is quite a hypothetical case: the default value for `org-drawers' contains drawers that are hardcoded and correspond to key features: I cannot figure out a good reason for *not* having these drawers in the configuration. I applied the patch. In case that's really a problem, we can have a variable `org-default-drawers-persistent' or something. -- Bastien
Re: [O] Indenting source code blocks in lists
Bastien b...@altern.org writes: The attached patch let `org-metaright' indent a drawer or a block correctly. It introduces two new function ̀org-indent-block' and `org-indent-drawer' which derive from local hacks I'm using quite often now. Perhaps ̀org-metaright' is not the best keybinding for this function, please suggest a better one. I've tested this patch and just applied it. Using M-right on a drawer keyword (like :PROPERTIES:) will indent the whole drawer. org-metaright looks quite natural most of the time, since the purpose is to realign the drawer with the headline/paragraph above, and statistically (?) headlines are more often refiles to subsubtrees than to trees. -- Bastien
Re: [O] [ANN] ASCII back-end for new export engine
Samuel Wales samolog...@gmail.com writes: On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote: - This is an item with some text. Sets off much less. Well. I'm still not sure why plain lists should have their own indentation. In that case, tables, latex-environments, etc. should too. Though, you can still configure what you want with an appropriate filter: #+begin_src emacs-lisp (add-to-list 'org-export-filter-plain-list-functions (lambda (plain-list back-end) (if (not (eq back-end 'e-ascii)) plain-list (replace-regexp-in-string ^plain-list #+end_src No, I mean that this is a useful way to send things to people who use proportional fonts. But in the simplest cases, tables will look ugly with proportional fonts, no matter if you use tabs or not. It isn't worth the struggle. Simplest case is perhaps short numbers which always works perfectly with tabs. Even with ugliness, tabs make it easier to understand the table IMO. I won't press the issues, but did not want those to be misunderstood. I understand. You may want to test this advice, which will convert a table to tsv if #+attr_ascii: tsv is set above the table. #+begin_src emacs-lisp (defadvice org-e-ascii-table (around table-tsv) (if (or (not (member tsv (org-element-get-property :attr_ascii table))) (eq (org-element-get-property :type table) 'table.el)) ad-do-it (setq ad-return-value (orgtbl-to-tsv (org-table-to-lisp (org-element-get-property :raw-table table)) nil #+end_src Regards, -- Nicolas Goaziou
Re: [O] Solved
Bastien b...@altern.org wrote: Hi Uwe, Uwe Brauer o...@mat.ucm.es writes: So there are two small changes necessary to make org-preview-latex-fragment work in Xemacs. One is the above change, the other (font-height (face-font 'default)) instead of (font-height (get-face-font 'default)) I can send a patch against 7.8.03 Please do so -- but please make sure the patch adapts current code to XEmacs without suppressing any feature for GNU Emacs. Thanks in advance! ... and bonus points if you also fix the problems described in http://thread.gmane.org/gmane.emacs.orgmode/50584 :-) Nick
Re: [O] [babel][patch] BUG in inline source blocks
Hi Eric Andreas Leha andreas.l...@med.uni-goettingen.de writes: [...] Thanks for this patch Martyn, I just pushed up your [:punct:] change. Hi Martyn, thanks for this patch! It does half the job for me. Now export (or evaluation) already work. But in the export I get a space inserted. I my example, I'd expect (here) to appear in the export, but I get ( here). This should now be fixed. Thanks, Martyn and Eric! Indeed both issues are fixed now. Regards, Andreas 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 Best, Martyn
Re: [O] how do scientists use org mode?
GMX Christoph 13 christoph-13 at gmx.net writes: 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. Are you putting exclusively your todos in, well, your todo file and perhaps keep project-related things, such as data and progress, notes, ideas etc. somewhere else? Or do you embed your notes and todos within their original context, i.e. is org mode your one-stop solution for data management? Do you maintain a separate file for every major project you are responsible for or involved in or throw everything into one or few humungous files and differentiate using hierarchies and tags? In the past I have hit some road blocks not so much with other softwares but rather concepts such as GTD, which I think is tailored to the needs of people outside science, so I would deeply appreciate your views and experience. If this list is geared towards the proximate aspects of development and less towards philosophy of usage, I apologize Christoph Hey Christoph, Welcome to orgmode! Well, to put it simply: you can use orgmode for everything: right from making notes, to writing papers, to designing websites and presentations, the list goes on and on. For example, you can write your papers and orgmode will generate LaTeX and pdfs automatically for you. It can also generate HTML files automatically, in case you wish to publish something on your website, but lack the time/enthusiasm/expertise to generate a decent looking webpage. Same goes for presentation (orgmode uses Beamer). Bottom-line: all you write is plain text, and everything else is auto-generated, seamlessly and without the user bothering about what is happening at the back. For example, I was recently a part of a team of a few Engineers and a bunch of Research Assistants, and we always used to assign tasks, maintain timesheets, generate reports, make presentations etc. using orgmode. For your questions on how to organize data and files: you can use orgmode to link between files, directories and URLs. So it is up to you to decide how you keep your files/folders. You just need to link them, and then use orgmode to pull it up for you. There are a bunch of tutorials here:http://orgmode.org/worg/org-tutorials/index.html. Please feel free to look at them, in order to gain some perspective on how efficiently orgmode can aid you in your day-to-day activities. Happy document-hacking, Bodhi PS: I hope you are using Emacs, as it seamlessly renders orgmode stuff. Other editors just can't do it as nicely.
Re: [O] Drawers within inline tasks
Hi Bastien, Bastien wrote: Fixed, thanks. I first didn't take care of this because it seemed logical to show all the content of an inline task here: the purpose of the inline task is to stay out of the hierarchical structure, such a task is *not* a subtree... so the real content of Parent task is all the text below -- whether it contains inline tasks or not. I was initially irritated by this behaviour because I kept some plain lists inside inline tasks, but now I can see the advantages of having them always stand out. And I can always put stuff in a drawer now. Thanks for reporting this, Thank you for your work! Cheers, Viktor
[O] Clocking inline tasks
Hi, I have another question regarding inline tasks. When I start the clock on an inline task the clocking information of the parent task is included in the mode line. Is this the intended behavior? In the example below there are three clock lines for a total of 1 hour and 45 minutes. If I start the clock on the inline task I would expect the modeline to show 15 minutes. Instead it shows 1 hour and 45 minutes (including the clocking time of the child task, but that's expected). * Parent task :LOGBOOK: CLOCK: [2012-01-29 Sun 02:00]--[2012-01-29 Sun 03:00] = 1:00 :END: ** Inline task :LOGBOOK: CLOCK: [2012-01-29 Sun 03:00]--[2012-01-29 Sun 03:15] = 0:15 :END: ** END ** Child task :LOGBOOK: CLOCK: [2012-01-29 Sun 01:30]--[2012-01-29 Sun 02:00] = 0:30 :END: Thanks, Viktor
[O] Adding the ability to archive into the datetree (updated)
Hi everyone, I previously sent out a patch to add the ability to archive into the datetree. The ability to store finished items by date (along with any other journal-type entry) seems pretty useful to me, which is why I wrote this. Bernt Hansen did a review of my previous patch, and did a great job in testing it out, catching several issues. Thanks, Bernt! I've fixed all the reported issues, and am attaching the modified patch. I'd love for this to get into the next release. If anyone has a desire to try this out, I'd love to hear if it is clear how to use it, and if you encounter any issues. 0001-Add-the-ability-to-archive-to-the-datetree.patch Description: Binary data
Re: [O] problem with orgstruct/outline-minor-mode with indented headlines
David Rogoff david at therogoffs.com writes: Hi all. I'm still trying to get orgstruct to work right. One thing I found is that I7 was getting confused with outline-magic which set up outline-minor-mode-map but not orgstruct-mode-map. I'm working inside verilog-mode, which uses the same // comment as c. So I defined outline-regexp: (setq outline-regexp \\s-*// [*]+ ) ;; any line that starts with // (possibly preceeded with whitespace) and some number of stars and a space This works fine. I needed the whitespace in front since verilog-mode indents comments along with code. The problem is when I run org-cycle on a headline. The following headline ends up on the same line (also in outline-minor-mode). TRIMMED What's going on? There's some confusion about the headline level being based on the indent and the number of stars. I'm so close, but need help figuring out this last problem. Anyone? I've been trying to learn how outline-mode works to modify the outline level, but I'm not quite there yet. I made my own versions of the outline-level function to try and see what's going on: (defun dhr-outline-level () Return the depth to which a statement is nested in the outline. Point must be at the beginning of a header line. This is actually either the level specified in `outline-heading-alist' or else the number of characters matched by `outline-regexp'. (interactive) (or (cdr (assoc (match-string 0) outline-heading-alist)) (- (match-end 0) (match-beginning 0 (defvar dhr-outline-level 'dhr-outline-level *Function of no args to compute a header's nesting level in an outline. It can assume point is at the beginning of a header line and that the match data reflects the `outline-regexp'.) (defun dhr-disp-ol () (interactive) (message outline level = %d (funcall dhr-outline-level)) ) I'm close but still not quite there and could really use a little help! Again, I had to add variable whitespace to the beginning of outline-regex since verilog-mode indents comments. I want to be able to adjust the outline-level based on where // starts, not from the beginning of the line. Thanks in advance for any help on this! This really makes editing my code so much easier and if I can get this last bit to work right I can convince a bunch of other ASIC engineers to use it and emacs! David
