Giorgio Valoti writes:
> Hi all,
> I’ve just switched from OmniFocus and began using Org mode. But I also
> discovered that it can be used for literate programming and I’d like to ask
> if is there a way to use an included file in the tangling phase. In other
> words, I have a file which inclu
Jambunathan K writes:
> Dan Davison writes:
>
> [Warning: OT]
>
>> tangling is not (technically at least) an Org-mode export method.
>
> This is an implementation artefact (as you have noted).
>
>>From a user-perspective tangling is a specialized form of expo
Dan Davison writes:
> If we allow the current region to be inherited by the code edit buffer
> (patch below), then language major mode commands that operate on the
> region can be called remotely from the org buffer. For example
>
> C-c C-v C-x M-; comment region according
ne could argue that it would permit un-natural code in
languages other than matlab/octave. As you say, we do want things to be
uniform across languages, but perhaps there is an argument for
restricting your suggestion to matlab/octave?
Dan
>
> --
> Darlan
>
> At Sun, 12 Sep 2010 08:45:40 +0
etimecowboy writes:
> Hi everyone,
>
> It seems that my org used the Octave program to evaluate my Matlab
> code block/generate figures, not Matlab itself.
Hmm, shouldn't do. Could you post your example? Have you activated both
octave and matlab? What is the value of your org-babel-load-language
Robert Goldman writes:
> I was looking for a way to put illustrations in my org-mode files so
> that I could actually look at them while editing the org stuff. I found
> a post a while ago suggesting using iimage mode (which is included with
> the Aquamacs that I use, and is readily available if
Robert Goldman writes:
> On 9/16/10 Sep 16 -7:11 AM, Dan Davison wrote:
>> Robert Goldman writes:
>>
>>> I was looking for a way to put illustrations in my org-mode files so
>>> that I could actually look at them while editing the org stuff. I found
>&g
Carsten Dominik writes:
> On Sep 20, 2010, at 10:24 AM, Bastien wrote:
>
>> Hi all,
>>
>> I have improved the experimental export engine I've been promising for
>> way too long. It lives in the EXPERIMENTAL/ directory of the git
>> repo:
>>
>>
>> http://repo.or.cz/w/org-mode.git/blob/b63f5333e
[...]
>>> I was just pulling up my email to share my next iteration when I saw
>>> your next iteration. They look very similar. If my version covers all
>>> of your use cases, then I'd like to add it to the Babel key map,
>>> probably under "d" for demarcate or delimit, unless you can think of a
"Eric Schulte" writes:
> Sébastien Vauban writes:
>
>> Hi Eric,
>>
>> Sébastien Vauban wrote:
>>> "Eric Schulte" wrote:
I've just added [org-babel-demarcate-block] to the org-mode repo.
>>>
For now it still lives in the babel keymap behind (C-c C-v d) since it is
fundamentally cod
into that.
Dan
Dan Davison writes:
> Now that we can issue TAB in a code block and have it act according to
> language [see org-src-tab-acts-natively], the following is a minor
> frustration: if you try to insert a blank line at the beginning/end of
> the block (perhaps to introduce
nt-region) can be called with their native effects from a src
block in the Org buffer; see example below.
Dan
>
> - Carsten
>
> On Sep 14, 2010, at 3:33 PM, Dan Davison wrote:
>
>> Dan Davison writes:
>>
>>> If we allow the current region to be inherited by the
Christian -- thanks, I think your suggestion is better than mine.
Eric -- here's a small change that allows it to work before the first
headline. (protected from patchwork I hope)
Dan
--8<---cut here---start->8---
X diff --git a/lisp/ob.el b/lisp/ob.e
Gary writes:
> Sorry, I've been rather lax on this :( I got dragged onto other stuff,
> went on training courses, and all sorts of other things.
>
> Eric Schulte wrote:
>> Babel does support generating diagrams with graphviz via "dot" code
>> blocks. Babel is also capable of converting Org-mode
I think that the documentation concerning installation should be made
more user-friendly. My impression is that the Org manual makes all this
sound much harder than it needs to be, and I suspect that this is an
entry-barrier for new Org users. For example, the first thing users
encounter in the man
Hi Richard,
Richard Riley writes:
> Dan Davison writes:
>
>> I think that the documentation concerning installation should be made
>> more user-friendly. My impression is that the Org manual makes all this
>> sound much harder than it needs to be, and I suspect that thi
Achim Gratz writes:
> Dan Davison writes:
>
>> I think that the documentation concerning installation should be made
>> more user-friendly. My impression is that the Org manual makes all this
>> sound much harder than it needs to be, and I suspect that this is an
>
Achim Gratz writes:
> Dan Davison writes:
>> OK, so we're agreed. But your points below don't seem to describe a less
>> technical route. Could you describe the less technical version of the
>> instructions for the method that you are advocating?
>
> Instal
Carsten Dominik writes:
> On Sep 26, 2010, at 3:33 PM, Dan Davison wrote:
>
>> I think that the documentation concerning installation should be made
>> more user-friendly. My impression is that the Org manual makes all
>> this
>> sound much harder than it needs to
Sebastian Rose writes:
> Carsten Dominik writes:
org-install would figure out where org.el is, add to .emacs and query
for compilation. This wouod make things independent from make and
other tools.
>>>
>>> Yes I wondered about making something like that yesterday (would it make
>
Hi Austin,
Noorul Islam K M writes:
> "Austin F. Frank" writes:
>> Recently I discovered that I can no longer evaluate R source code blocks
>> on a file opened using TRAMP.
Just btw, I use Org every day at the moment (with emacs24) to execute
code (mostly R) on remote machines. The method I u
John Hendy writes:
> Hi,
>
>
> Is it possible to "fold" the preamble (#+latex_header, #+options, etc.)
> under a first header? Mine get rather long, especially for Beamer documents.
>
> I just attempted it and it appears to work, but I wanted to know if anyone
> else has tried this and succeeded
John Hendy writes:
> Hi,
>
>
> Is it possible to "fold" the preamble (#+latex_header, #+options, etc.)
> under a first header? Mine get rather long, especially for Beamer documents.
>
> I just attempted it and it appears to work, but I wanted to know if anyone
> else has tried this and succeeded
John Hendy writes:
> Hi,
>
>
> Is it possible to "fold" the preamble (#+latex_header, #+options, etc.)
> under a first header? Mine get rather long, especially for Beamer documents.
>
> I just attempted it and it appears to work, but I wanted to know if anyone
> else has tried this and succeeded
John Hendy writes:
> Hi,
>
>
> Is it possible to "fold" the preamble (#+latex_header, #+options, etc.)
> under a first header? Mine get rather long, especially for Beamer documents.
>
> I just attempted it and it appears to work, but I wanted to know if anyone
> else has tried this and succeeded
Currently, if point is in the #+end_src line, then in the org-src edit
buffer it goes to the beginning of the last line. There are two patches
below. Patch 1 changes this so that point goes to the end of the last
line of code. This gives nicer behaviour when creating an active region
in the edit bu
Dan Davison writes:
> Currently, if point is in the #+end_src line, then in the org-src edit
> buffer it goes to the beginning of the last line. There are two patches
> below. Patch 1 changes this so that point goes to the end of the last
> line of code. This gives nicer behaviour w
Sébastien Vauban
writes:
> Hi Dan,
>
> Dan Davison wrote:
>> Now, if the region is contained within a src block, then it will be
>> inherited by the language major mode edit buffer. One consequence is that
>> commands like M-; (comment-region) and C-M-\ (indent-re
I'd appreciate opinions from R users on the following org-babel-R
details:
Currently, Org tables, and lisp lists, are converted into data frames
when they are sent from Org to R, and we have no way to create simple
vectors such as c(1,2). I'd like to know whether users of org and R
would approve o
"Eric Schulte" writes:
> Jambunathan K writes:
>
>> Hello Eric
>>
>> Eric> Hi Jambunathan,
>> Eric>
>> Eric> I've finally had a chance to test out this patch, and it's great!
>> Eric> I'd love to apply this to the core Org repository, however given
>> Eric> the size I have to ask, have you (or a
Hi Seb,
Sébastien Vauban
writes:
> #+TITLE: Org-Babel export environments for shell results
>
> * Example
>
> ** Medium output
>
> #+srcname: is-converted-to-listings
> #+begin_src sh :results output :exports both
> grep autoload ~/Downloads/emacs/site-lisp/org-mode/lisp/ob.el | cut -d "#" -f
>
Rainer M Krug writes:
> Hi
>
> I am about to write an R package, and as I am an org-mode and org-babel
> user, I would (obviously) like to use org-mode for that.
>
> Is there a recommended way of writing an R package in org-babel, or do I
> have effectively wrap the R code for the documentation e
Erik Iverson writes:
> Rainer M Krug wrote:
>> Hi
>>
>> I am about to write an R package, and as I am an org-mode and
>> org-babel user, I would (obviously) like to use org-mode for that.
>>
>> Is there a recommended way of writing an R package in org-babel, or
>> do I have effectively wrap the R
Erik Iverson writes:
> Dan Davison wrote:
>> Erik Iverson writes:
>>
>>> Rainer M Krug wrote:
>>>> Hi
>>>>
>>>> I am about to write an R package, and as I am an org-mode and
>>>> org-babel user, I would (obviously) like t
Rainer M Krug writes:
> On Thu, Oct 7, 2010 at 5:12 PM, Erik Iverson wrote:
>> Dan Davison wrote:
>>> Erik Iverson writes:
>>> Rainer M Krug wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I am about to write an R package, a
>>> #+results: is-converted-to-listings
>>> #+begin_example
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>> autoload
>>>
Sébastien Vauban
writes:
[...]
> Let's imagine I thought (which was the case at some point) I needed to enclose
> the parameters between quotes:
>
> #+srcname: quoted-params
> #+begin_src ledger :cmdline "reg unknown" :noweb yes :session
> <>
> #+end_src
>
> #+results: quoted-params
>
> Nothing
>> Could I ask you to make the source blocks reproducible in the future, so
>> that we can execute them without having to alter file paths etc?)
>
> Sure. I'll do.
>
> Here, I could have used another file that I can expect to be always at a fixed
> place (like grepping in ~/.emacs or some such).
Hi Chuck,
I agree about making use of existing ESS tools and that a more
traditional Org approach might be appropriate.
> If you do decide to go all in for a 'one org file makes one package'
> approach, you might try to get Rd language support added, so you can
> edit Rd directly in an Org Src bu
Antti Kaihola writes:
> Here's another stab at fixing the problem. This one enhances the
> existing trimming algorithm by preserving any leading whitespace on
> the first non-blank line of a block. This probably breaks tangling of
> other languages than Python, but someone more familiar with the
Carsten Dominik writes:
> On Oct 13, 2010, at 12:08 PM, Ian Barton wrote:
>
>>
>> Hi Eric,
>>
>> There is a file in worg called org-color-themes.org, which contains
>> your colour theme (railscast). However, it's not referenced by any
>> of the other worg pages, so you couldn't find it if you did
Hi Austin,
"Austin F. Frank" writes:
> On Thu, Sep 30 2010, Dan Davison wrote:
>
>> Just btw, I use Org every day at the moment (with emacs24) to execute
>> code (mostly R) on remote machines. The method I use is to store all
>> Org files locally, and use the :
Sébastien Vauban
writes:
> #+TITLE: Debugging shell code that misbehaves
> #+DATE: 2010-10-14
> #+LANGUAGE: en_US
>
> * Use case
>
> Let's say that:
>
> - This file is in =~/Client/Spec=
> - I'm working on such a chunk of code:
>
> #+begin_src sh :results output :exports results
> gre
Sébastien Vauban
writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> The following inhibits the insertion of blank lines on tangling.
>>
>> (setq org-babel-tangle-pad-newline nil)
>
> That works for the tangled file, but not for the preview buffer (run with =C-c
> C-v C-v=).
>
> Test it on the fo
[...]
>> and strapped down with a unit test.
>
> Would you have a bit of time (I don't know exactly what's required), could you
> give information about how you'll write this unit test (using this case as an
> example), where you put it and so on.
Hi Seb,
I also need to learn about these tests.
Sébastien Vauban
writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> The snippets used by the starter kit are available in their own git
>> repository at http://github.com/eschulte/yasnippet-org-mode
>
> Trying to clone it, I get:
I think the above URL is for a web browser. The URLs for git are li
Sébastien Vauban
writes:
> Hi Dan,
>
> Dan Davison wrote:
>> Sébastien Vauban writes:
>>
>>> #+TITLE: Debugging shell code that misbehaves
>>> #+DATE: 2010-10-14
>>> #+LANGUAGE: en_US
>>>
>>> * Use case
>>&
diff --git a/lisp/org-inlinetask.el b/lisp/org-inlinetask.el
index 29b1544..041ee29 100644
--- a/lisp/org-inlinetask.el
+++ b/lisp/org-inlinetask.el
@@ -106,7 +106,7 @@ When nil, they will not be exported."
(defvar org-complex-heading-regexp)
(defvar org-property-end-re)
-(defcustom org-inlinet
Hsiu-Khuern Tang writes:
> Hi,
>
> The :latex-listings option appears to be unused at the present. It
> would be great to activate this as an alternative to the
> org-export-latex-listings variable. (Same thing for :latex-minted.)
>
>
> BTW, has anyone used minted with beamer? I get errors lik
Sébastien Vauban
writes:
> Hi Tassilo,
>
> Tassilo Horn wrote:
[...]
> I tried to use this patch, but failed doing so:
[...]
> error: lisp/org-footnote.el: patch does not apply
>
> Any help? (I don't know "anything" of git)
I've been in this situation before! It's quite frustrating. That'
"Eric Schulte" writes:
> Hi Bernd,
>
> It seems that you have already found the best solution in the indirect
> edit buffers (by calling C-c ' from inside of a code block). I would
> only add that in the email you mentioned below, I was specifically
> talking about syntax highlighting of R code
Bernd Weiss writes:
[...]
> As a
> long-time ESS user I wish that I could use things like ESS syntax
> highlighting,
>>
>> This, as Eric mentioned, is turned on with
>> `org-src-fontify-natively'. However from your config below it seems you
>> have set this variable. So that requires
"Thomas S. Dye" writes:
> On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
>
>> "Thomas S. Dye" writes:
>>
>>> Hi Dan,
>>>
>>> Glad to know that Darlan's slowdown is fixed.
>>>
>>> No change here that I ca
Jambunathan K writes:
> Jules Bean writes:
>
>>>
>>> Hi Tom,
>>>
>>> I've used fontification in Org code blocks constantly for a couple of
>>> months now, and I do not agree that there are any editing or unfolding
>>> delays which should deter typical Org users from using fontified src
>>> blo
Eric S Fraga writes:
> Hello,
>
> Just a comment on requirements: ob-octave assumes the presence of the
> =dlmwrite= function. This is available as standard with octave 3.2 but
> requires an extra package (=octave-io=) if you have an older version
> (3.0.x). All of this is for Debian systems; I
"Thomas S. Dye" writes:
> Aloha Sebastien,
>
> Arbitrary markup is possible, see
> http://orgmode.org/worg/org-tutorials/org-latex-export.php#sec-12
>
> Using this approach [[latex:textsc][My small caps]] would export to
> LaTeX as \textsc{My small caps}.
In the Org-buffer I see "My small caps"
"Thomas S. Dye" writes:
> On Oct 31, 2010, at 7:43 AM, Dan Davison wrote:
>
>> "Thomas S. Dye" writes:
>>
>>> Aloha Sebastien,
>>>
>>> Arbitrary markup is possible, see
>>> http://orgmode.org/worg/org-tutorials/org-la
Hi Seb,
Wow, magic. I've totally got no idea how it works, but thanks!
Dan
"Eric Schulte" writes:
> Hi Seb,
>
> This is really great. I finally folded it into my gnus setup, and while
> it looks great when it works, I was getting frequent errors throw by the
> org-mode fontification engine re
Gary writes:
> Is there any way to sort the columns of a table, such that for example
>
> | Col 3 | Col 1 | Col 2 |
>
> can be converted to
>
> | Col 1 | Col 2 | Col 3 |
> |---+---+---|
> | ... | ... | ... |
>
I'd do this using an external language that has a matrix/table data
Hi Jambunathan,
Sorry to be so slow to get to these,
Jambunathan K writes:
> 1. Improper fontification of Babel blocks
>
>With babel native fontification on, I see that the commented elisp
>code down below is not fontified. The problem persists if I kill the
>buffer and find it agai
Hi Seb,
In addition to the Org example, would you mind supplying a concise,
explicit statement of what the putative bug is? With just the Org
example on its own, the bug is implicit and I at least feel that I'm
having to work hard to get there!
Dan
p.s. However, your emails did motivate the fo
Sébastien Vauban
writes:
> Hi Dan,
>
> Dan Davison wrote:
>>> #+begin_src emacs-lisp
>>> ;; (message "Hello World")
>>> #+end_src
>>
>> err, and I haven't had the energy to investigate this one yet!
>
> Another minibug
Carsten Dominik writes:
> Dear all,
>
> yesterday I replaced the previous implementation of
> in-buffer completion (M-TAB of Esc TAB) with a new
> function making use of John Wiegleys pcomplete.el.
> In fact, John did most of the Org-related implementation
> already months ago - I only tied up so
writes:
> Hi Dan,
>
> Dan Davison wrote:
>> In addition to the Org example, would you mind supplying a concise, explicit
>> statement of what the putative bug is? With just the Org example on its own,
>> the bug is implicit and I at least feel that I'm hav
Sunny Srivastava writes:
> Hello Org-moders,
> I have been a very happy ESS user so far. Recently, I was introduced to
> org-mode and I am still a beginner.
>
> I am trying to write a research paper using the literate programming style
> of org-babel-R, instead of Sweave, and the journey has been
hat OK?
> Dan Davison wrote:
>> Sébastien Vauban writes:
>>> Dan Davison wrote:
<...>
> Honestly, the way I update that code has been mainly done by sequences of
> trials and errors. The above code is, for me, still quite complex to
> understand with vars
Hi Eric, Seb,
I'd actually just pushed my local fix that I had made to this so
far. Our emails crossed because mine is being held up by gmane as I
forgot to switch the obfuscated gmane reply address for the normal list
address, but here's what will come through eventually:
,
| Hi Seb,
|
| I
Sébastien Vauban
writes:
> Hi,
>
> A quick wished feature, if you agree on its usefulness.
>
> Currently, all error messages are concatenated to the same buffer, execution
> after execution, which makes it *difficult to distinguish between the new
> errors*, and the ones already seen previously
Erik Butz writes:
> Hi all,
>
> I am trying to run some org-babel code, but while this used to work in
> the past, I am now getting an error which says
>
> "Symbol's function definition is void: org-babel-get-header"
>
> Somehow I am puzzled, since this function is defined in lisp/ob.el and
> sin
Bernt Hansen writes:
> Dan writes:
>
>> Incidentally, can any gnus users tell me -- is there a non-painful way of
>> retrieving an old message from nntp in order to create a reply in the correct
>> thread? Or do you hack the headers to make it appear in the right thread? I'm
>> using the gmane w
Content-Transfer-Encoding: 7bit
>> Subject: [Orgmode] Re: In-buffer completion
>> Date: Sat, 20 Nov 2010 22:50:07 -
>> From: Dan Davison
>> X-Patchwork-Id: 396
>> Message-Id: <874obblwa8@gmail.com>
>> To: Carsten Dominik
>> Cc: John Wiegley , O
Eric S Fraga writes:
> Dan writes:
>
> [...]
>
>> This patch should make ob-ledger use the common org-babel error mechanism.
>> It is
>> in branch ledger of the main repo. However, I'm not yet a ledger user. Could
>> someone test it?
>
> Unfortunately, it doesn't work at all [1] for a very simp
Erik Butz writes:
> Hi,
>
> people with more git experience should comment here, but it seems with:
> ~/elisp/org-mode $ git status
>
> you will get a list of currently untracked files in the local working
> directory. These are of course both files or directories deleted from
> the repository (a
"Eric Schulte" writes:
> You can place the ditaa code into a code block and then evaluate the
> code block with C-c C-c. This will insert a link to the generated image
> into your Org-mode file. If you then turn on inline images with M-x
> org-toggle-inline-images you can preview the generated
. "no")
: (:hlines . "no")
: (:tangle . "no"))
#+begin_src emacs-lisp :results pp
org-babel-default-header-args:ditaa
#+end_src
#+results:
: ((:results . "file")
: (:exports . "results"))
#+begin_src emacs-lisp :results pp
org-babel-default-
Sébastien Vauban
writes:
> Hi Charles,
>
> Thanks a lot for taking a look at this, too...
>
> "Charles C. Berry" wrote:
>> On Sun, 28 Nov 2010, Sébastien Vauban wrote:
>>> Hi Eric and Dan,
>>>
>>> * Abstract
>>>
>>> Reporting two problems:
>>
>> Did you mean to include ":results output" in the
Hi Seb, I definitely have some sympathy with your request. On two
occasions I've had to manually make this change just to carry on
working. The change I made is straightforward if you need it as a
temporary hack:
--8<---cut here---start->8---
diff --git a/lisp/o
"Eric Schulte" writes:
> Hi,
>
> I've just pushed up a new prefix header argument.
"preamble" might be a better name? or "header"? prefix makes me think of
adding a string onto the front of a string[1]; preamble and header are
used by e.g. latex to refer to prelimary lines at the top of a file.
Sébastien Vauban
writes:
> Hi Eric and Dan,
>
> Dan Davison wrote:
>> Sébastien Vauban wrote:
>>> "Eric Schulte" wrote:
>>>> I don't forsee adding partial results insertion both because
>>>>
>>>> - it would add a good
an
commit 85597d28b25f4e64d535f61d2115ed2069a28be8
Author: Dan Davison
Date: Fri Dec 3 18:24:38 2010 +
Reorganize org-edit-src-code; allow buffer-local
`org-edit-src-content-indentation'
* lisp/org-src.el (org-edit-src-code): When generating the code edit
buffer, it is necessary for sever
"Eric Schulte" writes:
> Vincent Beffara writes:
>
>> Hi,
>>
(and it would be excellent to allow for a code block as a preamble,
instead of a string in the header or as an alternative, because
preambles once they are allowed tend to grow uncontrollably ;->)
>>>
>>> This is current
"Thomas S. Dye" writes:
> Hi Dan,
>
> Emacs configuration is one of the highest barriers to entry for
> potential adopters of Org-mode, IMO. The idea of context-sensitive
> configuration is potentially terrific. It gets the user to work more
> quickly than would otherwise be the case. The prob
"Eric Schulte" writes:
> My only worry on this front is that I know how to type "|" and "-" for
> tables, and how to type "*" for headings, but I don't have an easy way
> to type utf8 characters.
>
> If Org-mode starts using exotic utf8 characters which can not easily be
> typed from outside of O
Antti Kaihola writes:
> I have /tmp on my root partition and a separate partition for /home.
> When trying to close an Emacs session which is using org-mode, I get
> this error:
>
> move-file-to-trash: Non-regular file: Is a directory, /tmp/babel-XXX
>
> (where XXX are random characte
Please note the following changes to the way that org-babel handles
file output. These may break existing org-babel files which use
the :file header argument.
:file should be understood as saying "write the result
to and return a link to ".
This works for all languages. For graphics languages (
Dan Davison writes:
> Please note the following changes to the way that org-babel handles
> file output. These may break existing org-babel files which use
> the :file header argument.
>
> :file should be understood as saying "write the result
> to and return a link t
Bernt Hansen writes:
> * lisp/org.el: Skip source block fontification during export when language
> is not defined
> ---
> This may not be the correct fix for this issue but it works for me.
Hi Bernt,
I've checked in a slightly different version[1] of this fix. Thanks for
the report; it wasn't
Sébastien Vauban
writes:
> Hi David,
>
> "David O'Toole" wrote:
>> 2010/12/10 Sébastien Vauban :
>>> In order to make the blocks stand out more clearly in the mix of prose, code
>>> and table results of many Babel Org files, I've added 2 new faces:
>>>
>>> - org-block-begin-line
>>> - org-block-e
There's recently been some advocacy of using buffer-local variables for
Org-mode configuration. It seems like a good idea to me. However, I
think that it raises a problem: there are at least two situations in
which Org internally spawns a buffer that is supposed to be a sort of
"copy" of another Or
Bernt Hansen writes:
> Dan Davison writes:
>
>> Bernt Hansen writes:
>>
>>> * lisp/org.el: Skip source block fontification during export when language
>>> is not defined
>>> ---
>>> This may not be the correct fix for this issue but it
Jeff Horn writes:
> Hey orgsters,
>
> For the holiday trip, I decided to see if I could go a week with only
> the Cr-48. I left my Macbook at home ready for SSH, just in case.
>
> It took approximately 30 minutes of using the computer before I
> started itching for org.
>
> I've been having a hec
Jeff Horn writes:
> On Wed, Dec 22, 2010 at 12:49 PM, Dan Davison wrote:
>
>> The second one is lacking the fboundp protection. Does it help if you
>> put the fboundp test in, as below?
>
> Dan,
>
> Thanks for the suggestion. I tried the patch and got a h
Eric S Fraga writes:
> Dan Davison writes:
>
>> Eric S Fraga writes:
>>
>>> Dan writes:
>>>
>>> [...]
>>>
>>>> This patch should make ob-ledger use the common org-babel error mechanism.
>>>> It is
>>&
ts output :var x=whole-adzes :file r/
> adze_edge_angle.png :width 400 :height 300
>
> The only change was to append graphics to :results output.
>
> All the best,
> Tom
>
> On Dec 21, 2010, at 6:57 AM, Dan Davison wrote:
>
>> Dan Davison writes:
>>
>&
"Eric Schulte" writes:
> Hi Seth,
>
> The easiest way to fontify embedded html is most likely to wrap the html
> in "#+begin_src html" code blocks.
>
> As for defining your own clojure blocks that sounds like a risky
> proposition to me. All of the code block evaluation functions are built
> to
Ben Ward writes:
> #+begin_src R :exports both
> full <- read.csv(file="~/Documents/BSc Biology/Third Year/BY6001-40 -
> Dissertation/Data and Analysis/Evolution Results.csv", head=T)
> library("lattice")
> ecoli = subset(full, Bacterium=="E.coli")
> edett = subset(ecoli, Cleaner=="Detto
Jeff Horn writes:
> Beautiful. Thanks, Tom!
Hi Jeff, so you had two problems:
1. Erroneous fontification outside of blocks
2. Slowness and too much output to *Messages*
I was aware that Tom's fix fixes (2) on OS X, but I haven't heard of (1)
before. Isn't it a bit weird that the same fix shoul
to fontify it, and that it would do this
> regardless of whether code blocks were actually displayed. It has
> been a while since someone on the list pointed out the fix to me, but
> I haven't run into any problems since then and my buffers are
> fontified correctly.
>
>
"Eric Schulte" writes:
> Rainer M Krug writes:
>
>> On 01/18/2011 12:48 AM, Eric Schulte wrote:
>>> Hi,
>>>
>>> This is possible using Babel, the attached org-mode file will execute
>>> its code block every time it is opened. You can replace the contents of
>>> the code block with any arbitrar
Matt Lundin writes:
> Marcelo de Moraes Serpa writes:
>>
>> However, I've got hooked. Vim (in my case, MacVim) has conquered my
>> hands. I know I'm risking myself a lot by saying it on an
>> emacs-related mailing list, but the Vim navigation and the vim model
>> in general is much more efficien
1 - 100 of 587 matches
Mail list logo
