[Orgmode] Babel & DOS

I'm having trouble executing a shell script under Microsoft Windows using org-babel. When I evaluate this: #+begin_src sh :results output echo Hello #+end_src I get this: #+results: : Microsoft Windows XP [Version 5.1.2600] : (C) Copyright 1985-2001 Microsoft Corp. :

[Orgmode] Re: SQLite in 7.01h?

I believe all you need to do is change 'Sqlite' to 'sqlite' (all lower case) in the +BEGIN_SRC line. --Mike ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/

[Orgmode] Re: Babel & sh & Windows

Srinivas yahoo.com> writes: > I tried the following: > #+srcname: directory-tree > #+BEGIN_SRC sh :dir /bin :results output org replace :exports results > tree > #+END_SRC > > The output is as given below: > > #+results: directory-tree > c:\bin>More? > I've played with babel a little bit on W

[Orgmode] Single quote and inline formatting

Enclosing text in '=' symbols generally causes the text to be formatted as code. I've found this fails if the last character in the text is a single quote ('): + =This works= + =So does 'this= + =But not this'= The text in the first two lines appears in the 'code' face (gray), and i

[Orgmode] org-babel-sh and Microsoft Windows

I tried using org-babel-sh at work, where I run emacs under Microsoft Windows, but only received an oddly-formatted message about (quote sh) not being recognised as a command. After mucking around with org-babel-sh.el, I modified the call to shell-command-on-region, changing the hard-coded "sh" to

[Orgmode] Tables in ASCII export

When I export tables to ASCII, I'd like the rows to expand as necessary so the full contents is visible. I've has a look at org-exp.el, but I'm at a bit of a loss as to where to start mucking in. Any pointers would be greatly appreciated! Thanks, Mike

Re: [Orgmode] org-babel-sh and Microsoft Windows

Thanks! I'll give that a go! ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Tables in ASCII export

carsten.dominik> this behavior is now the default, controlled by the new user option carsten.dominik> `org-export-ascii-table-widen-columns'. Thanks. That's a start, but what I really want is to have long cells folded, so that one table row might become several lines in the ASCII export. For exam

Re: [Orgmode] Estimate ranges in column view

Carsten, Here is a patch for a new 'est+' summary type, including corresponding changes for xemacs and the manual. I've done basic testing on the GNU emacs version, but not the xemacs code. I'm not sure the change to the manual provides the right amount of information in the right place; I'd b

Re: [Orgmode] Estimate ranges in column view

Carsten, I send the from to ass...@gnu.org just before I sent the patch, but I haven't received a reply. Should I expect one, or is that all I need to do? Thanks, Mike ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. E

Re: [Orgmode] Estimate ranges in column view

Great news, Carsten--still works correctly. Thanks for the chance to contribute! --Mike ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [babel] support plantuml

I've run into a minor problem using this under Microsoft Windows. One of my machines puts a space in the temporary folder path, which causes the redirection to fail. I've fixed it locally by applying shell-quote-argument to in-file and out-file in org-bable-execute:plantuml. --Mike ___

Re: [O] monospace (=) and quotes not getting along

Michael Hannon yahoo.com> writes: > To define =my_frabbitz= in this model, we issue the command: >    => my_frabbitz = "someRandomWord"= > The "my_frabbitz" in the sentence comes out in monospace, but the > R codedoesn't.  It seems that the quotation marks are killing the process. I don't remem

[O] [PATCH] EPS support for ob-plantuml

EPS export from Plantuml is now in beta testing; this patch makes it available through org-babel. To generate an EPS from Plantuml, give your source block a ':file' with the extension '.eps'. If you want to include the EPS files in PDF generated from org-export, include the line #+LaTex_h

[O] Re: Use-cases for babel

Marcelo de Moraes Serpa gmail.com> writes: > We could also use this thread for additional ideas on how org-babel > could be used. I generally use org-babel with PlantUML, dot, or ditaa to generate diagrams as part of my exported document. I find this especially useful for programming notes, as i

Re: [O] special characters for HTML

michael holzer gmx.at> writes: > ...when i'm using this in a word (e.g. l\aumlstig) this fails. if i put a > space > behind \auml i get the umlaut, but obviously i don't want the space there... > so how is this supposed to be done? Use an empty set of braces to mark the end of the special chara

[O] [new exporter] Enabling multiple exporters?

I've just started playing with the new exporter. My .emacs files includes: (require 'org-export) (require 'org-e-latex) (require 'org-e-html) (require 'org-e-odt) (require 'org-e-beamer) But when I run org-export-dispatch, the only choices I get are 'Export to ODT' and 'Publish'. If I comment ou

Re: [O] [new exporter] Enabling multiple exporters?

Thomas S. Dye tsdye.com> writes: > If I'm not mistaken, 'org-export is no longer required. Could you try > without that require to see if you get what you expect? Thanks for the reply, Tom. Unfortunately, removing that line doesn't change the behaviour.

Re: [O] [new exporter] Enabling multiple exporters?

On 20/10/12 23:11, Nicolas Goaziou wrote: > Probably nothing (excepted requiring 'org-export, which doesn't hurt, > but is useless). > > Try to restart Emacs first. > > > Thanks for the suggestion, but that doesn't help. I've found that the problem is really with the menu. If I press the appropria

Re: [O] [new exporter] Enabling multiple exporters?

On 22/10/12 02:01, Nicolas Goaziou wrote: > > > Correct. The window displaying the UI is probably too short to display > it completely. > > I've pushed a commit in order to fix this. It is better now? > Thanks for looking into it. I am running a small screen (netbook), but your commit doesn't see

[O] Setting width of babel-generated image in LaTeX export?

I'm having trouble specifying the width of an image I export to LaTeX (with either the new or old exporter). The snippet below demonstrates my problem. It uses plantuml to generate an image file, using ATTR_LaTeX to specify the width. When exported, the .tex file specifies the default width (.9\lin

Re: [O] Setting width of babel-generated image in LaTeX export?

Thomas S. Dye tsdye.com> writes: > ...Here is how I've been generating figures for LaTeX export using the new > exporter: Thanks--that's just what I was looking for.

[O] [new exporter]: LaTeX output from babel escapes comment delimiter

I use the xtables package in R to generate nice-looking tables for LaTeX output, as in the snippet below. The new exporter escapes the % symbol in the R output, so that the comments generated by xtable are no longer comments. * Snippet #+HEADER: :results output latex #+HEADER: :exports result

Re: [O] [new exporter]: LaTeX output from babel escapes comment delimiter

Thanks for trying to reproduce this. I tried again from 'emacs -Q', and couldn't reproduce it either. I'm concluding it's due to some cruft in my .emacs file, and not a problem with the exporter. --Mike

[O] [new exporter] Date format string not handled for LaTeX export

When I provide a format string to the #+DATE: option, the old LaTeX exporter correctly uses it to format the current date; the new exporter just uses the format string for the date. The new HTML exporter does not have this problem.

Re: [O] [new exporter] Date format string not handled for LaTeX export

Nicolas Goaziou gmail.com> writes: > On the other hand, you have a hard-coded macro to solve this problem: > > #+DATE: {{{time(%c)}}} > > It will work across every back-end (but you need the latest Org version, > since I recently to fixed a bug related to it). Thanks--that will do nicely. Unf

Re: [O] [new exporter] Date format string not handled for LaTeX export

Nicolas Goaziou gmail.com> writes: > I just tried with a minimal init and it worked. Could you send the > example you're trying to export? The file is below. With a minimal init, I get the error "Symbol's function definition is void: org-macro-initialize-templates'. If I use my full .emacs file,

Re: [O] [new exporter] Date format string not handled for LaTeX export

On 30/10/12 20:14, Nicolas Goaziou wrote: > This is {{{time(...)}}}, not {{{date(...)}}}. > > {{{date(%c)}}} is another macro that is replaced with the #+DATE: value > during export. Since you try to replace #+DATE: value with itself, you > dive into an inf loop. I think I understand what's going

Re: [O] [new exporter] Date format string not handled for LaTeX export

On 30/10/12 22:29, Nicolas Goaziou wrote: > Doesn't > >#+DATE: {{{time(%Y-%m-%d %H:%M)}}} > > get you what you expect? That gives me an empty date string. signature.asc Description: OpenPGP digital signature

Re: [O] [new exporter] Date format string not handled for LaTeX export

Nicolas Goaziou gmail.com> writes: > > Hello, > > Nick Dokos hp.com> writes: > > Works for me. > > I also get a correct date with it, even with a minimal set-up. Well, this is embarassing. I tackled it fresh, after a cup of coffee (for me) and a re-start (emacs), and it's working. User err

Re: [O] [ANN] Smart quotes in org-export.el

Nicolas Goaziou gmail.com> writes: > > Hello, > > I've installed a smart quotes module in org-export.el (new exporter). It > is off by default. You can turn it on globally with > `org-export-with-smart-quotes' variable, or locally with: > > #+OPTIONS: ':t I thought I'd give this a try, but

Re: [O] [ANN] Smart quotes in org-export.el

Nicolas Goaziou gmail.com> writes: > Fixed. Thank you for testing this feature and reporting back errors. Thanks for the fix. I've verified it works on both emacs 23 (the debian package), and NTemacs (24). Kind Regards, Mike

[O] Generating captions--is there a better way?

I use R to plot data, and like to include information about the plot in the caption. I do this by combining two named SRC blocks--one for the image, and one for the caption--and then put their #+RESULTS: together. The caption is the tricky bit; I use R to print a string that starts with #+CAPTION:,

[O] Anyone using or working on ob-scheme?

I've recently started playing with guile source blocks, and haven't gotten the results I expect. In particular, I've found that: + :results output only returns the first word of the output text. + :results value prompts me for a lisp expression, and returns whatever I give it. + :

Re: [O] Anyone using or working on ob-scheme?

Thorsten Jolitz googlemail.com> writes: > just as a side remark: I remember that, when trying to write > ob-picolisp, I tried to base it on ob-scheme, since it seemed the next > logical thing to do (its about two lisp dialects). And I was surprised > how much had to be changed and how different t

Re: [O] Anyone using or working on ob-scheme?

Thorsten Jolitz googlemail.com> writes: > I forgot all the details, I was an absolute starter with Elisp and I got > stuck sometimes and received help from the org-babel creator Eric > Schulte. Of course some language specific details caused problems, but > the resulting code was not only a copy w

[O] [new exporter] :wrap problems

I've run into trouble using the :wrap option with babel, with the new exporter. Using :wrap to put the result in an EXAMPLE block works consistently, but putting the result into a SRC block is inconsistent. This example: * :wrap example #+BEGIN_SRC ruby :results value :exports both :wrap EXAMPL

Re: [O] [new exporter] :wrap problems

Nicolas Goaziou gmail.com> writes: > I only have time for a cursory look at the problem right now, but > I notice one obvious error: ":wrap src fundamental" generates wrong Org > syntax. It should be "#+END_SRC" not "#+END_SRC fundamental". > > I assume that fixing it on the Babel side should mak

[O] [PATCH] Babel: Fix the #+END_ directive from the :wrap param

* lisp/ob.el: Only use the :wrap argument up to the first space when creating the #+END_ directive. Using an option like ":wrap SRC fundamental" was generating and end marker of "#+END_SRC fundamental", which caused the new exporter to fail to handle to block properly. TINYCHANGE --- lisp/ob.

[O] [PATCH] Edit source: fix 'end' initialisation

marker) to (copy-marker), instead of nil. Kind Regards, Mike Gauland From 9aca6bb03fe92adc7198c85699b2539bc811b414 Mon Sep 17 00:00:00 2001 From: Michael Gauland Date: Fri, 7 Dec 2012 10:44:09 +1300 Subject: [PATCH] Edit source: fix 'end' initialisation * lisp/org-src.el: Create a ma

Re: [O] Babel give "Marker does not point anywhere" first run of LaTeX export; subsequent are fine

John Hendy gmail.com> writes: > > When I open an org file the first time and export to PDF via LaTeX, I > get the error "Marker does not point anywhere" and the LaTeX export > quits. Running it again without doing anything else succeeds, and all > subsequent exports work fine. > What version o

[O] [PATCH] Wrap: override default

* lisp/ob.el (org-babel-insert-result): only wrap if the :wrap value is non-null. It can be convenient to specify the :wrap property at a higher level (e.g., file or tree), rather than for each block. This patch allows you to override the propery by specifying :wrap with no argument. TINYCHANGE

Re: [O] new latex exporter and attr_latex

François Allisson allisson.co> writes: > > Hi, > > The following example used to work for me > > *** > #+ATTR_LATEX: align=lcr > | left | center | right | > *** > Any change recently around attr_latex or align? > Yes, the syntax has changed; see http://thread.gmane.

Re: [O] Anyone using or working on ob-scheme?

On 19/12/12 13:48, Jeff Mickey wrote: > I'm running into these problems as well. I was curious if you've had > any time to work on this. As a general question to the org list: What > dynamic languages similar to how scheme will interact with it's > inferior process (python and ruby?) have decently

Re: [O] [PATCH] Wrap: override default

On 24/12/12 21:43, Bastien wrote > Well, the patch is wrong, if (cdr (assoc :wrap (nth 2 info))) > is in the (and ...) sexp, no need to have it in the (or ...) > sexp? > > I'll mark it as "not applicable". I let you propose another > patch if you still need to fix an issue in this area. > > Thanks

[O] Error exporting empty results block

org-escape-code-in-region produces an 'Invalid search bound (wrong side of point)' error when exporting a block that produces an empty wrapped block. For example: #+BEGIN_SRC emacs-lisp :wrap fundamental :exports both (setq x nil) #+END_SRC I'm exporting an empty block because I want the si

[O] [PATCH] Babel support for scheme using geiser

s are wrapped before being passed to scheme, "(define...)" will generate an error in such blocks. From 655d0c1e870d8957974961c8bfc989a75096c60a Mon Sep 17 00:00:00 2001 From: Michael Gauland Date: Sat, 5 Jan 2013 08:03:19 +1300 Subject: [PATCH] Modify ob-scheme.el to use geiser.

Re: [O] [PATCH] Babel support for scheme using geiser

Bastien altern.org> writes: > In the meantime, please consider adding a > commit ChangeLog for your patch, Most of the file has changed dramatically--would you like the changelog to list all the functions that have been added or altered, or would a simple statement that the file underwent a maj

[O] [PATCH] Use geiser for babel scheme evaluation.

uses geiser to evaluate babel scheme source blocks, and generally improves scheme support. From bc33a46041086abd5d1fec321f104aa034823576 Mon Sep 17 00:00:00 2001 From: Michael Gauland Date: Wed, 9 Jan 2013 12:41:13 +1300 Subject: [PATCH] Use geiser for babel

[O] Error building org-e-publish

I'm having trouble building the latest code from git. I don't normally use 'publish', but it appears to be required for some of the exporters I use. I've added it to ORG_ADD_CONTRIB, but it fails to build: Compiling file /home/mike/elisp/org-mode-clean/lisp/org-e-publish.el at Mon Jan 14 11:51:

Re: [O] Error building org-e-publish

J. David Boyd adboyd.com> writes: > Mine builds with no problem at all, using emacs 24.2.92. > > You sure you have the latest git source? I just did an update a moment > ago... > Thanks for the info. I've got the latest git, but I'm running emacs 23.2 (under Debian). I can evaluate all the co

Re: [O] Error building org-e-publish

Nick Dokos hp.com> writes: > Not sure why emacs24 does not complain but org-e-publish contains this bit of > code: > , > | ... > | (org-export-async-start 'ignore > | `(let ((org-e-publish-use-timestamps-flag > | (if ',force nil ,org-e-publish-use-timestamps-fl

Re: [O] Error building org-e-publish

On 15/01/13 11:11, Nick Dokos wrote: > Not sure I understand. Can you explain why that would be a good fix? > Looking further into it, I'm not sure it *is* right. I'll see if I can track down the source of those lines, and who contributed them, before second-guessing the intent. signature.asc

[O] [PATCH] Turning off wrapping

I have file with a large number of SRC blocks, the output of which I want to wrap as SRC (so I can use the listings package to format them distinctly). The easiest way to do this is to make :wrap a global property. Unfortunately, there are also a couple of places where I want to turn off the wrappi

[O] org tables into R?

"A.B.C": #+RESULTS: : [1] "A.B.C" : A.B.C : 1 115 76 60 : 2 124 78 55 : 3 118 73 65 : 4 114 75 61 : 5 108 74 82 What am I doing wrong? Thanks, Michael Gauland

Re: [O] org tables into R?

I modified the definition of ob-R-transfer-variable-table-with-header in ob-R.el by changing 'sep' from \"\\t\" to \"\". Now #+BEGIN_SRC R :results output :exports both :session :var data.table=data :colnames yes names(data.table) head(data.table) #+END_SRC (note the addition of :colname

[O] [PATCH] Fix R table import

ob-R.el: Fix R table import * ob-R.el (ob-R-transfer-variable-table-with-header): Change separator from tab to whitespace when reading in a table as a variable. TINYCHANGE lisp/ob-R.el |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/ob-R.el b/lisp/ob-R.el index 2470

Re: [O] [PATCH] Fix R table import

I'm using the latest from git, with some unrelated local modifications (though to be sure I did a clean build from origin/master and had the same problem). Versions: Org-mode version 8.3beta (release_8.3beta-758-g034d00.dirty @ /usr/local/share/emacs/site-lisp/org/) GNU Emacs 24.3.1 (x86

Re: [O] [PATCH] Fix R table import

My git has so many more commits because I'm sloppy about my local changes. I had been using ESS 5.14 (from ELPA). When I switched to the latest git version, the problem (at least seems to have) went away. For my needs, I don't think this needs any further investigation, though I'm happy to help i

Re: [O] 13 failures on make ./update

Jude DaShiell shellworld.net> writes: > In toplevel form: > ox.el:80:1:Error: Cannot open load file: tabulated-list I ran into this as well, and resolved it by adding the tabulated-list package from ELPA, and adding "-L ~/.emacs.d/elpa/tabulated-list-0" to the definition of EMACS in my local.mk

Re: [O] :wrap behaviour

Tom Regner goochesa.de> writes: > > I'd suggest: nowrap > > regards > Tom That inspires another idea: specifying :nowrap to turn off wrapping for the block. Thus, #+BEGIN_SRC emacs-lisp :nowrap ... would not be wrapped, even if :wrap were set at a higher level.

[O] [PATCH] ':wrap nowrap' disable wrapping

Babel: Disable wrapping * lisp/ob-core.el (org-babel-insert-result): If the argument to ':wrap' is 'nowrap', don't wrap the results. * doc/org.texi (Header Arguments): Describe 'nowrap' behaviour. This allows the results of a block to be inserted without wrapping, by overriding a ':wrap' propert

[O] Help with babel results

I'm working with an sqlite database of songs, and I've run into trouble with titles that start with a '(' (for example, (I Can't Get No) Satisfaction). 'Verbatim' results work: #+BEGIN_SRC sqlite :db test-db :results verbatim .mode csv .separator | drop table playlist; create t

Re: [O] Help with babel results

On 11/03/13 12:48, Eric Schulte wrote: > I've now committed this patch. Thanks--that was fast. Works for me now. Kind Regards, Mike signature.asc Description: OpenPGP digital signature

Re: [O] :session question

Andreas Röhler easy-emacs.de> writes: > Would find it more natural if ":session" is the default, while a command "refresh" makes a new one. I don't think so, but perhaps I'm just used to the way it works now. I use a mix of session and non-session blocks. When I use plantuml, dot, or asymptote

Re: [O] New logo

Bastien altern.org> writes: > > I asked many Org friends during the last few weeks, and we all > agreed that an ostrich might be a good candidate. I'm afraid this logo sends the wrong message. It should be showing the non-org-users of the world with their heads in the sand. Or maybe the logo sh

[O] Patchwork?

I haven't been able to connect to the patchwork server mentioned on the Worg for the last couple of days. Is this link outdated, or is the server temporarily unavailable? Kind Regards, Mike Gauland

[O] Number formatting in tables for LaTeX export

I have a table representing a memory map, something like this: | Start | End | Purpose| |---+--+| | | 1E08 | Bootloader | | 1E09 | 1FFF | Unused (Bootloader expansion) | | 2000 | 3F39

[O] [PATCH] Agenda: Fortnight time span

Agenda: Add fortnight as a time span * lisp/org-agenda.el (org-agenda-custom-commands-local-options): Add fortnight as a choice for org-agenda-span. (org-agenda-span): Add fortnight as a choice for customising org-agenda-span. (): Add 'Fortnight View' to the org-agenda-menu (org-agenda-list): If n

Re: [O] [PATCH] Emacs Org Babel Scheme (Geiser) support

Thanks for such a well-written, well-documented, and most of all useful contribution! Definitely a big improvement over my initial implementation. I've applied the patch to my system, but I'm having trouble getting it to work--I'm not getting any results. For example, this block: #+BEGIN_SRC sch

Re: [O] Network Diagram

Esben Stien esben-stien.name> writes: > Any way to create something like a network diagram with org-mode? I haven't tried doing network diagrams, but I've found dot (graphviz), PlantUML, and Asymptote very flexible.

[O] ebnf2ps for babel

t (C) your name here ;; Author: Michael Gauland ;; Keywords: literate programming, reproducible research ;; Homepage: http://orgmode.org ;; Version: 0.01 ;;; License: ;; This program is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as

Re: [O] org-babel generated images and +ATTR_LATEX

Mark, I think you want to use named results. My images typically look something like this: #+NAME: architecture #+HEADER: :exports results #+HEADER: :file (org-babel-temp-file "./figure-" ".eps") #+HEADER: :cache yes #+BEGIN_SRC plantuml ... #+END_SRC #+NAME: fig-architect

Re: [O] org-babel generated images and +ATTR_LATEX

Mark Edgington gmail.com> writes: > Anyhow, something that wasn't clear to me about your example is how you make > the filename which is generated via org-babel-temp-file available for use > within the code-block? Babel takes care of that (plantuml interprets the :file argument as the name of the

[O] Exporting Source Blocks with Symbols

t? I didn't find any, but I often miss what's right in front of me (just ask my wife!). Kind Regards, Michael Gauland

Re: [O] Exporting Source Blocks with Symbols

racter (a symbol I've never used for anything else). This code could certainly be improved, but it serves my needs, and may be useful as a starting point for anyone trying to do something similar. --Michael Gauland #+BEGIN_SRC emacs-lisp :session :results value silent :exports none ;; Set up

Re: [O] PNG R plots size

Vicente Vera gmail.com> writes: > How can I control the size of a PNG graphic? Do I need to tweak > something inside Org or specify something in R? I use a line like this: #+HEADER: :res 300 :units cm :width 15 :height 15 to create a 15cm square PNG at 300 dpi.

[O] Different listing styles for same babel language?

My org documents include lots of source code blocks, in a variety of languages. I use the listings package to give each language a distinctive look. Lately, my work has involved using shell commands on different machines, as different users. I'd like to give each shell environment (e.g., local use

[O] Different listing styles for same babel language?

My org documents include lots of source code blocks, in a variety of languages. I use the listings package to give each language a distinctive look. Lately, my work has involved using shell commands on different machines, as different users. I'd like to give each shell environment (e.g., local use

Re: [O] Different listing styles for same babel language?

I recently wrote: >> My org documents include lots of source code blocks, in a variety of >> languages. I use the listings package to give each language a >> distinctive look. >> >> Lately, my work has involved using shell commands on different machines, >> as different users. I'd like to give eac

Customize listings per language?

I often have several different babel languages in the same file. I'd like to be able make them easily distinguished by language (such as having a different background or shadow). As far as I can tell, the listings package doesn't let me override settings by language. The best solution I've so far

Re: Babel: Store script in external file

I've just started playing with #+INCLUDE, so I may not be using it correctly, but this works for me. I have a file 'sh_test', which looks like: for i in $(seq 10); do echo $i done My org file: #+HEADER: :exports both #+INCLUDE: "sh_test" src sh And the results: , | for i in $(seq 10); d

Listings and dialects

My org files typically include source blocks from several different languages. I'm using the listings package for export to LaTeX. I'd like to give each language a distinctive look (by changing the background or border colour). I can do this manually by inserting a bit of LaTeX before each block,

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "

Same here! On 01/05/18 08:46, Peter Dewey Ore wrote: > I second (third?) Richard and Jon. I use appreciate the simplicity. > > On Mon, Apr 30, 2018 at 1:37 PM, Richard Lawrence > mailto:richard.lawre...@berkeley.edu>> > wrote: > > Jon Snader mailto:j...@irreal.org>> writes: > > I use

Re: LaTeX Headers not in partial export

On 24/10/20 4:00 am, Eric S Fraga wrote: > On Friday, 23 Oct 2020 at 15:22, Mike Gauland wrote: >> I have a number of #+LATEX directives at the top of my org file, for >> configuring the minted package. > Could you maybe post a minimal example? > This file demonstrates the problem, at least on my s

Re: LaTeX Headers not in partial export

On 25/10/20 3:45 pm, Kyle Meyer wrote: > Michael Gauland writes: > >> --start of file-- >> >> #+LATEX: \setminted{frame=single,framerule=1pt} >> >> >> * Section >>   #+begin_src sh :exports code >>   echo "This is a code block &

"Org" source blocks and minted

I want to include an "org" source block in a document as an example, and have it formatted with minted. Unfortunately, minted doesn't seem to recognize "org" as a language,and the block is missing in the resulting PDF. For the moment, I've changed this to a "text" source block, but it would be nice

Re: "Org" source blocks and minted

Yes, this looks very promising. I'm looking forward to playing with it when I have more time. On 27/03/21 12:55 am, Juan Manuel Macías wrote: > Hi Timothy, > > I really like your approach. And it is org/emacscentric! Minted has > never quite convinced me, and gives me some trouble with certain >

header-args property

I'm confused about the use of the header-args property. It works as expected when I export a file, but not when I evaluate a code block manually. For example, consider this file:     #+PROPERTY: header-args :var x="Hello" :exports both     #+begin_src shell   echo X is $x     #+end_src When

source blocks mangled when edited

I've stared having trouble editing source blocks.    When I use C-c ' to edit block, the editing behaves as expected, but when I C-c ' to return to the main org file, the code is altered in strange ways.  I've had trouble coming up with a really small example, but the attached file seems to consist

Re: source blocks mangled when edited

On 31/05/21 4:21 pm, Samuel Wales wrote: > idk if this will help as you probably know all of it already. butg > you asked for any help so here goes. i run maint, not master or any > emacs versions. weird that you are missing 3 cols? Switching to the maint branch didn't change anything, but I fou

Re: source blocks mangled when edited

On 31/05/21 8:15 pm, Sébastien Miquel wrote: > The relevant functions are `org-edit-src-exit` and perhaps > `org-src--contents-for-write-back`. > > Can you instrument these functions to see what's happening ? Is > `org-src--contents-for-write-back` populating the buffer correctly ? > Does the `repl

Re: source blocks mangled when edited

On 31/05/21 9:42 pm, Sébastien Miquel wrote: > There must be an issue with the `replace-buffer-contents` calls. Can > you call `trace-function` on `replace-buffer-contents` and trigger the > behaviour again to see what it returns ? > This is all the *trace-output* buffer shows: =