Eric Schulte writes:
>> I'm going to push up a patch which will change to inserting #+RESULTS:
>> by default as well as a user-configurable variable which can be used to
>> customize this behavior.
>
> Done. This variable is named `org-babel-results-keyword'
Great, thanks. I've also changed th
t...@tsdye.com (Thomas S. Dye) writes:
> This patch to the manual fixes a typo.
Applied, thanks!
--
Bastien
pin...@iro.umontreal.ca (François Pinard) writes:
> A tiny typo on page http://orgmode.org/fr/org-mode-support.html:
>
> "3 deniers commits git" should read "3 derniers commits git"
Fixed, thanks.
--
Bastien
Hi Skip,
I love OCD! Thanks for that one.
And, thank goodness the Org mode community is big enough for artists,
artisans, and crafts people.
I find it fascinating to use software created by such a diverse
community. I've often thought I'm glimpsing the future.
All the best,
Tom
Skip Colli
On Wed, Jan 11, 2012 at 12:50 AM, Jambunathan K wrote:
>> You and Jambunathan K. should form a club.
>
> Since I am being dragged in to the conversaion,
Of course I intend no disrespect for you or François. I have noticed
that org, perhaps not surprisingly, attracts people with a certain
detail-o
On Wed, Jan 11, 2012 at 7:40 PM, Leo Alekseyev wrote:
>> Eric S Fraga writes:
>>>
>>> What version of org are you using? I ask because I used to experience
>>> the annoyance you describe a while back; more recently (since at least a
>>> few months ago), hitting C-x C-s no longer has any negative
Hi Eric,
It's great to find :wrap in master. Thanks for augmenting the draft.
All the best,
Tom
Eric Schulte writes:
> Hi Tom,
>
> Thanks for this patch, I've just pushed up an augmented version which
> more closely matches the current behavior.
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>
Hi!
A tiny typo on page http://orgmode.org/fr/org-mode-support.html:
"3 deniers commits git" should read "3 derniers commits git"
François.
Hi Tom,
Thanks for this patch, I've just pushed up an augmented version which
more closely matches the current behavior.
t...@tsdye.com (Thomas S. Dye) writes:
> Hi Eric,
>
> Attached please find a first draft of a patch for the manual entry
> documenting a :wrap header argument.
>
> All the bes
Hi Eric,
Attached please find a first draft of a patch for the manual entry
documenting a :wrap header argument.
All the best,
Tom
>From 4e3a66a4fbfd8d6914fbfd3924981ae5c526aa4a Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Wed, 11 Jan 2012 16:06:17 -1000
Subject: [PATCH] * doc/org.texi: adde
> For instance, when I was doing a lot of Java programming, I used
> hideshow.el all the time to hide block and function bodies. Works very
> well (although the default key bindings are annoying to me). Have a
> look! It's a standard package in emacs, at least in Emacs 24 but much
> earlier than
To include multiple files, I export all of the required files before
the PDF creation and zip them. This way, I only need to include a
single zip file.
#+BEGIN_SRC emacs-lisp :exports none
;; various exports
(save-window-excursion
(org-export-as-ascii org-export-headline-levels))
(save-
> Eric S Fraga writes:
>>
>> What version of org are you using? I ask because I used to experience
>> the annoyance you describe a while back; more recently (since at least a
>> few months ago), hitting C-x C-s no longer has any negative impact: it
>> saves the file, or at least appears to.
>>
>>
Since org-mode v7.8, editing a code block in an indirect buffer causes
any referenced code blocks to be executed. While this behavior is
desired for viewing code in an indirect buffer (as the behavior has
always been) it is not for editing (esp. if the named block takes a
long time to run).
Given
There is a problem with the order of execution of interspersed source
and call blocks will not be executed in order because of the way
org-babel-execute-buffer is written (first all the source blocks, then
all the call blocks).
Therefore, when executing an entire buffer, there is no way to have
t
Fantastic, I've just applied this patch, Thanks
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> The attached patch to the manual includes information on the RESULTS
> keyword.
>
> All the best,
> Tom
>
>
>
> Eric Schulte writes:
>
>>>
>>> I'm going to push up a patch which will change to
András Major writes:
> Hi fellows,
>
> I've just discovered that I'm missing a feature in org-mode. These
> days I write much of my code in an Org buffer and tangle it into a set
> of source files. Currently, I follow a rather cumbersome procedure
> when making changes to the code:
>
> 1. I cha
Aloha all,
The attached patch to the manual includes information on the RESULTS
keyword.
All the best,
Tom
>From 7fbabd20ed1477e706633945c98400ee48fb0ab2 Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Wed, 11 Jan 2012 11:23:19 -1000
Subject: [PATCH] * doc/org.texi: #+RESULTS now user-configura
>
> I'm going to push up a patch which will change to inserting #+RESULTS:
> by default as well as a user-configurable variable which can be used to
> customize this behavior.
Done. This variable is named `org-babel-results-keyword'
,
| org-babel-results-keyword's value is "RESULTS"
|
| Doc
Eric S Fraga writes:
> Leo Alekseyev writes:
>
>> I often edit my org-babel code blocks via org-edit-special (C-'), in
>> part because I find the tabbing behavior within the code blocks to be
>> somewhat flaky. Inevitably, when editing the code block I will press
>> C-x C-s (muscle memory). This
Bastien writes:
> Bastien writes:
>
>> Actually, I'm thinking of another solution:
>>
>> - keep one-line option/environment keywords uppercase
>> #+NAME
>> #+HTML
>> #+TITLE
>> #+...
>>
>> - use lowercase for multi-lines environments keywords
>> #+begin_ascii
>> #+begin_html
>> #+r
Hi András,
András Major wrote:
>> I have the impression it's already there: if you edit your code directly in
>> the Org buffer, without opening an indirect buffer, the only thing you have
>> to
>> do is:
>
> That's precisely what I want to avoid. I'd like to use the
> language-specific indentat
Hi all,
I'd like to be able to call capture such that the captured item is
stored under '* Notes' in the current org-file *from inside an
org-edit-src-code buffer*.
Preferably, I'd like a single capture template, that works
(1) on the current org file normally
(2) on the "parent org file" after d
Hi Sebastien,
> I have the impression it's already there: if you edit your code directly in
> the Org buffer, without opening an indirect buffer, the only thing you have to
> do is:
That's precisely what I want to avoid. I'd like to use the
language-specific indentation and highlighting using th
Applied, Thanks,
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> Attached please find subject patch.
>
> All the best,
> Tom
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Aloha all,
Attached please find subject patch.
All the best,
Tom
>From bd3579cef735c2bb62c37a4d394597be384fe18d Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Wed, 11 Jan 2012 08:46:27 -1000
Subject: [PATCH] * doc/org.texi: Documented :noweb no-export
---
doc/org.texi | 28
Everything has been working fine for month and since yesterday I get
'org-agenda-filter' is void error message when trying to push my org files to
dropbox. I've found a thread on the message board with the suggestion to
install the latest git code, which I did, but I still have the same issue.
Hi François,
François Pinard wrote:
> When using SPC in the Agenda buffer (org-agenda-show-and-scrollup), the
> LOGBOOK drawer is shown opened, which is not a big problem, yet a
> slightly annoying one, as I'm rarely interested to see its contents at
> this stage. Moreover, the manual explains th
Hi Phil
On Tue, Jan 10, 2012 at 14:39, Phil (Philip) Mason
wrote:
> Should I be able to use @> in references to remote tables?
Yes, this issue has been resolved by Carsten with
release_7.7-420-g1432e4b
> Is there a syntax I should be using if I want to get all the entries
> in a table below a c
> | tangle | -| + | - |
> |+--++|
> | need | +| + | - |
>
>>
>> What should the name for such an option be?
>>
>
> Andreas' suggestion, :noweb no-export, seems right to me.
>
Me too,
I've just pushed up a patch adding a "no
Hi, Org people.
When using SPC in the Agenda buffer (org-agenda-show-and-scrollup), the
LOGBOOK drawer is shown opened, which is not a big problem, yet a
slightly annoying one, as I'm rarely interested to see its contents at
this stage. Moreover, the manual explains that one of the purposes of
dr
Aloha all,
This patch to the manual fixes a typo.
All the best,
Tom
>From 96fc5de8a377b69678d5dd82f414d293dea709c6 Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Wed, 11 Jan 2012 06:41:02 -1000
Subject: [PATCH] Fix typo on manual pointed out by Francois Pinard
---
doc/org.texi |2 +-
1 f
pin...@iro.umontreal.ca (François Pinard) writes:
> Hi, Org people.
>
> I'm not familiar with referencing in documents, so I'm not sure. The
> section "11.2 Images and Tables" in the manual says:
>
>
> You can use the following lines somewhere before the table to assign a
> caption and a label fo
Hi, Org people.
I'm not familiar with referencing in documents, so I'm not sure. The
section "11.2 Images and Tables" in the manual says:
You can use the following lines somewhere before the table to assign a
caption and a label for cross references, and in the text you can refer
to the object
This patch makes it easy to select links from among a forest of
similar-looking machine-readable forms. Without it, the human-readable
descriptions tend to fall off the right side of the window.
>From fa9522e8dd1ef602574d0fb58f8f610ef82b15d7 Mon Sep 17 00:00:00 2001
From: Dave Abrahams
Date: Th
Leo Alekseyev writes:
> I often edit my org-babel code blocks via org-edit-special (C-'), in
> part because I find the tabbing behavior within the code blocks to be
> somewhat flaky. Inevitably, when editing the code block I will press
> C-x C-s (muscle memory). This causes all sorts of annoying
pin...@iro.umontreal.ca (François Pinard) writes:
> Hi, Org people.
>
> It seems that if I use diacritics in file names for included images, and
> then asks for a PDF rendering of it (through LaTeX), the image does not
> get included. If I remember correctly, I only get a big hollow square,
> wit
Giovanni Giorgi writes:
>
>
> Hi all,
> I'd like to edit some ruby/python/shell script using
> functions folding.
>
> I'd like to get a way to fold functions or method.
Giovanni,
I wonder, having thought about this some more, whether using org mode is
the correct solution? (as much as I l
Bastien writes:
> Karl Voit writes:
>
>>> `org-write-agenda' has been renamed to `org-agenda-write',
>>> please update your code.
>>
>> Thanks for the hint! Missed in in the change notes ...
>
> You didn't miss anything -- this change is in current git HEAD,
> which used not to be advertised in
"Sebastien Vauban" writes:
> Hi Thomas, Eric(s) and all,
Hi Sebastien,
[...]
> I use HTML export more and more, and would be sad if the solution wasn't
> targeted at all to HTML as well.
I agree although this doesn't preclude target specific customisation
variables; it just means that each ta
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> Let me suggest this tiny patch, so C-k does the proper thing in visual
> line mode.
Applied, thanks.
--
Bastien
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> Could the highlighting be made consistent as well? I would suggest that
> gray is uniformly kept for all one-line option/environment keywords.
> Currently, #+TITLE is gray, #+OPTIONS is red, so #+OPTION would be
> rendered the same
Bastien writes:
> Actually, I'm thinking of another solution:
>
> - keep one-line option/environment keywords uppercase
> #+NAME
> #+HTML
> #+TITLE
> #+...
>
> - use lowercase for multi-lines environments keywords
> #+begin_ascii
> #+begin_html
> #+results
>
> This is the only good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/01/12 08:45, Eric Schulte wrote:
> Frozenlock writes:
>
>> I am a strong advocate in keeping the source of everything.
>>
>> However, a source can easily be lost if it doesn't follow the
>> document. In LaTeX, there's a package to attach a fi
Hi András,
András Major wrote:
> I've just discovered that I'm missing a feature in org-mode. These
> days I write much of my code in an Org buffer and tangle it into a set
> of source files. Currently, I follow a rather cumbersome procedure
> when making changes to the code:
>
> 1. I change the
Hello all,
Should I be able to use @> in references to remote tables?
For example in the tables below I would expect the results table to show "cde"
as the result of both formulas.
#+TBLNAME: TEST1
|---+---|
| a | f |
| b | g |
| c | h |
| d | i |
| e | j |
|---+---|
#+TBLNAME: RESULTS
|---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I am using org-mode-tangle-jump-to-org to jump from tangled code to
the source in the org file. This works nice, but if I remember
correctly, there was talk about implementing that the jump is to the
line of code - has this been implemented yet, be
Hi fellows,
I've just discovered that I'm missing a feature in org-mode. These
days I write much of my code in an Org buffer and tangle it into a set
of source files. Currently, I follow a rather cumbersome procedure
when making changes to the code:
1. I change the Org file using the C-cC-c key
d.tchin writes:
> Eric S Fraga ucl.ac.uk> writes:
>
>>
>> Hello,
>>
>> one of the recent updates
>>
>> commit d6e40fb3472761ed51795f54491b969976167116
>>
>> to org has caused a problem with the latest emacs snapshot (version from
>> 5 January I believe). Specifically, the alias for
>> lis
Eric S Fraga ucl.ac.uk> writes:
>
> Hello,
>
> one of the recent updates
>
> commit d6e40fb3472761ed51795f54491b969976167116
>
> to org has caused a problem with the latest emacs snapshot (version from
> 5 January I believe). Specifically, the alias for
> list-diary-entries-hook would appe
Hello,
one of the recent updates
commit d6e40fb3472761ed51795f54491b969976167116
to org has caused a problem with the latest emacs snapshot (version from
5 January I believe). Specifically, the alias for
list-diary-entries-hook would appear to create an alias loop as
diary-lib.el in emacs a
Michael Bach writes:
> Andreas Leha writes:
>
>> would this noweb-based approach work for you:
>>
>> #+name: inner_test
>> #+begin_src R
>> 4 + 4
>> #+end_src
>>
>> #+name: test
>> #+begin_src latex :noweb yes
>> \begin{equation}
>> <>
>> \end{equation}
>> #+end_src
>>
>
> Yes, that wo
Hi Thomas, Eric(s) and all,
Thomas S. Dye wrote:
> Eric Schulte writes:
>> t...@tsdye.com (Thomas S. Dye) writes:
>>> "Sebastien Vauban" writes:
Thomas S. Dye wrote:
>
> | tangle | -| + | - |
> |+--++|
> | need | +| + | -
53 matches
Mail list logo
