Hi Michael,
Michael Bach wrote:
> 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,
Hi Bastien,
François Pinard wrote:
> Bastien writes:
>> Eric Schulte writes:
>
>>> That said I'm happy that Org-mode is forgiving enough to allow me to
>>> lowercase most of my keywords locally.
>
>> Actually, I'm thinking of another solution:
>
>> - keep one-line option/environment keywords upp
Leo Alekseyev writes:
> I've done a little bit of digging into how Tassilo's code works, and
> realized that it's somewhat broken in the following way: if a mode
> provides its own outline-level function, chances are, his code will
> break (this is why c-mode doesn't work). Even if default
> out
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
consequences: the buffer with th
On Tue, Jan 10, 2012 at 7:21 PM, David Rogoff wrote:
>
>
> David Rogoff
> January 10, 2012 4:34 PM
> Carlos Russo gmail.com> writes:
> I have used both Carsten's and Eric's solution, as well as
> hideshow-org (https://github.com/secelis/hideshow-org), which works
> rather well and deserves
Skip Collins writes:
> 2012/1/10 François Pinard :
>> Some sad people think of me as a programmer. While deep down, I am
>> fundamentally an artist. Programming is mere mean of expression :-).
>
> You and Jambunathan K. should form a club.
Since I am being dragged in to the conversaion, I am d
I'm trying to do simultaneous exports of an org document by doing the following:
#+begin_src emacs-lisp
(org-export-as-ascii org-export-headline-levels)
(org-export-as-html org-export-headline-levels)
#+end_src
Each export done manually is fine, but when done like my code, the
.txt file seems to
Daniel's solution didn't end up working for some reason. After
spending over an hour on it this evening, I couldn't get git-cloned
org to work. I was running into an odd problem with 'cyclic variable
indirection' or something like that. In a trouble-shooting step, I
moved the git-cloned org out of
David Rogoff
January 10, 2012
4:34 PM
Carlos Russo gmail.com> writes:
I have used both Carsten's and Eric's
solution, as well as
hideshow-org (https://github.com/secelis/hideshow-org),
which works
rather well and deserves a mention.
Expanding a bit on Carsten's
Carlos Russo gmail.com> writes:
I have used both Carsten's and Eric's solution, as well as
hideshow-org (https://github.com/secelis/hideshow-org), which works
rather well and deserves a mention.
Expanding a bit on Carsten's post: Tassilo Horn wrote some convenience
functions to set the outline m
2012/1/11 Eric S Fraga
> pin...@iro.umontreal.ca (François Pinard) writes:
>
> [...]
>
> > Should I say, I notice a strong correlation between rotten software and
> > the lack of attention to such details. I'm not saying that avoiding
> > trailing white space is a guarantee of good software. Bu
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 works. Thanks for your thoughts on this, And
On Tue, Jan 10, 2012 at 3:08 PM, Eric S Fraga wrote:
> 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.
>
> Carsten has already given you one possible solution; anothe
pin...@iro.umontreal.ca (François Pinard) writes:
[...]
> Should I say, I notice a strong correlation between rotten software and
> the lack of attention to such details. I'm not saying that avoiding
> trailing white space is a guarantee of good software. But I'm saying
> that people unwilling
Hi all.
I'm using orgmode for outlines and documentation. Since no one else I
work with does this, I export to HTML which generally works
fine. However, I've got a problem with embedded code samples using
#+BEGIN_SRC / #+END_SRC. The faces for the source code are set up
for a black background.
pin...@iro.umontreal.ca (François Pinard) writes:
> Hi, Org people.
>
> I really have mixed feelings about capitalisation of #+WORDS, and wonder
> if some consensus and good taste has developed over time among Org mode
> users. What is the collective wisdom saying as being nicer among:
[...]
>
David Rogoff writes:
> Hi all.
>
> I'm using orgmode for outlines and documentation. Since no one else I
> work with does this, I export to HTML which generally works
> fine. However, I've got a problem with embedded code samples using
> #+BEGIN_SRC / #+END_SRC. The faces for the source code a
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.
Carsten has already given you one possible solution; another is to use
org + babel with tangling to have each function or
Just a testing head's up...
commit f1043a53cc46d2ce2e578d3cb498f895dc65f1ff breaks the tests.
FAILED test-org-property-accumulation-append-use
FAILED test-org-property-accumulation-append-val
FAILED test-org-property-accumulation-top-use
FAILED test-org-property-accumulation-top-
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
[...]
>> Alternatively for LaTeX, some way to wrap exported code blocks in a
>> \begin{listing} ... \end{listing} environment, complete with caption and
>> label. This way the code block name could appear in the caption, and
>> with
pin...@iro.umontreal.ca (François Pinard) writes:
> Bastien writes:
>
>> Eric Schulte writes:
>
>>> That said I'm happy that Org-mode is forgiving enough to allow me to
>>> lowercase most of my keywords locally.
>
>> Actually, I'm thinking of another solution:
>
>> - keep one-line option/environ
pin...@iro.umontreal.ca (François Pinard) writes:
> Some sad people think of me as a programmer. While deep down, I am
> fundamentally an artist. Programming is mere mean of expression :-).
Hence:
D Knuth: The Art of computer programming
https://en.wikipedia.org/wiki/The_Art_of_Computer_Progra
d.tchin writes:
> I have the following message when I stroke C-c a a.
> Press key for agenda command:
> let*: Symbol's value as variable is void: diary-list-entries-hook
Fixed in the git HEAD. Please download org-latest.zip in 24 hours
or use the git repo.
PS: the problem was that list-diary-
Bastien writes:
> Eric Schulte writes:
>> That said I'm happy that Org-mode is forgiving enough to allow me to
>> lowercase most of my keywords locally.
> Actually, I'm thinking of another solution:
> - keep one-line option/environment keywords uppercase
> #+NAME
> #+HTML
> #+TITLE
>
Eric Schulte gmx.com> writes:
> This same issue was raised recently on the mailing list and (I believe)
> a patch has been pushed to the git repository. Would you mind checking
> if the problem persists in the git head?
>
I download org-latest.zip archive and test it. This version solves this
d.tchin writes:
> Hi,
>
> I would like to report a problem of evalation when org-babel is used with
> emacs 22.3 on windows and recent org-mode 7.8.03.
>
> I use the following code :
>
> #+begin_src sh :results silent
> ls
> #+end_src
>
> It breaks when a header is used.
>
> When evaluated with
Eric Schulte writes:
> That said I'm happy that Org-mode is forgiving enough to allow me to
> lowercase most of my keywords locally.
Actually, I'm thinking of another solution:
- keep one-line option/environment keywords uppercase
#+NAME
#+HTML
#+TITLE
#+...
- use lowercase for multi-l
2012/1/10 François Pinard :
> Some sad people think of me as a programmer. While deep down, I am
> fundamentally an artist. Programming is mere mean of expression :-).
You and Jambunathan K. should form a club.
Bastien writes:
> Hi François,
>
> pin...@iro.umontreal.ca (François Pinard) writes:
>
>> P.P.S. How about amending the manual for consistent capitalization?
>
> I've pushed a fix for this.
>
> The manual used mostly uppercase so I fixed the few lowercase
> instances of option/environment keywor
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> P.P.S. How about amending the manual for consistent capitalization?
I've pushed a fix for this.
The manual used mostly uppercase so I fixed the few lowercase
instances of option/environment keywords.
I made an exception for #+re
Hi,
I would like to report a problem of evalation when org-babel is used with
emacs 22.3 on windows and recent org-mode 7.8.03.
I use the following code :
#+begin_src sh :results silent
ls
#+end_src
It breaks when a header is used.
When evaluated with C-c C-c, the following message appears :
Eric S Fraga writes:
> I appreciate your reasoning in each case I've elided but, in the end,
> the different versions or approaches you mention are all essentially
> equivalent (computationally)... :-)
Who cares about computation! :-)
Some sad people think of me as a programmer. While deep dow
Hi Eric,
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Seb,
>>
>> "Sebastien Vauban" writes:
>>
>>> Hi Thomas,
>>>
>>> Thomas S. Dye wrote:
Is there a difference between :noweb tangle and :noweb no?
>>>
>>> Yes: ":noweb no" is the default, and must *not expand* anyt
Hey François,
bh >> I wouldn't spend too much time agonizing over the 'right' way
fp> Truth is that I've been so agonizing for the whole of my computer
fp >life! Each one his sickness, I guess... :-)
I understand your pain. Have you read "The Paradox of Choice" by Bary
Schwartz? Sounds as if you
pin...@iro.umontreal.ca (François Pinard) writes:
> Eric S Fraga writes:
>
> Hi again, Eric. I'll be using your corrections on the code, thanks!
You're welcome!
>> I had to add a call to expand-file-name for getting a file name which
>> worked on my system for some reason.
>
> (make-temp-nam
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,
with the textual name of the image file (rather than the image) i
Applied, Thanks,
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> The attached patch to the manual is intended to make the description of
> :noweb no conform to its behavior.
>
> All the best,
> Tom
--
Eric Schulte
http://cs.unm.edu/~eschulte/
t...@tsdye.com (Thomas S. Dye) writes:
> Hi Seb,
>
> "Sebastien Vauban" writes:
>
>> Hi Thomas,
>>
>> Thomas S. Dye wrote:
>>> Is there a difference between :noweb tangle and :noweb no?
>>
>> Yes: ":noweb no" is the default, and must *not expand* anything.
>>
>>> Based on the documentation and so
Aloha all,
The attached patch to the manual is intended to make the description of
:noweb no conform to its behavior.
All the best,
Tom
>From 7207cdec84daecd31d4e53117c477abaad91bbd1 Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Tue, 10 Jan 2012 06:06:49 -1000
Subject: [PATCH] * doc/org.texi:
François Pinard wrote:
> Nick Dokos writes:
>
> > François Pinard wrote:
> >> P.P.S. How about amending the manual for consistent capitalization?
> >>
>
> > Knock yourself out! ;-)
>
> I've absolutely nothing against doing that little work myself (that one
> is easy enough!), besides the id
Hi Seb,
"Sebastien Vauban" writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> Is there a difference between :noweb tangle and :noweb no?
>
> Yes: ":noweb no" is the default, and must *not expand* anything.
>
>> Based on the documentation and some limited testing, I made the following
>> table.
>>
Nick Dokos writes:
> François Pinard wrote:
>> P.P.S. How about amending the manual for consistent capitalization?
>>
> Knock yourself out! ;-)
I've absolutely nothing against doing that little work myself (that one
is easy enough!), besides the idea that I might be working against the
crowd.
Eric S Fraga writes:
Hi again, Eric. I'll be using your corrections on the code, thanks!
> I had to add a call to expand-file-name for getting a file name which
> worked on my system for some reason.
(make-temp-name
(expand-file-name
(concat (file-name-as-directory name)
(
Hello everyone,
org-mode version 7.8.02
When doing `org-preview-latex-fragment' on a buffer with custom set
#+LaTeX_CLASS and some #+LATEX_HEADER lines, the pdflatex process to
create the ltxpng/*.png images fails e.g. with:
Failed to create dvi file from /tmp/orgtex1650tNa.tex
Now when I check
Michael Bach writes:
> Eric Schulte writes:
>
>
>> I don't know of a way to evaluate inline code blocks which are already
>> inside of regular code blocks.
>
> Thanks for your thoughts on this, Eric. This would be *really*
> convenient for me. Too bad the christmas wishlist was processed
> a
Bernt Hansen writes:
> Andreas Leha writes:
>
>> is it possible to make S-tab call the global org-cycle when the
>> point is in a source block?
>
> Yes,
>
> (setq org-src-tab-acts-natively nil)
Still, we could have TAB indent code in source blocks, and S-TAB
do the global cycling. I'll look i
Bernt Hansen writes:
> Andreas Leha writes:
>
>> is it possible to make S-tab call the global org-cycle when the
>> point is in a source block?
>
> Yes,
>
> (setq org-src-tab-acts-natively nil)
>
> Regards,
> Bernt
Hi Bernt,
thanks. But that "disables" tab as well.
So to clarify: I am lookin
Andreas Leha writes:
> is it possible to make S-tab call the global org-cycle when the
> point is in a source block?
Yes,
(setq org-src-tab-acts-natively nil)
Regards,
Bernt
Eric Schulte writes:
> I don't know of a way to evaluate inline code blocks which are already
> inside of regular code blocks.
Thanks for your thoughts on this, Eric. This would be *really*
convenient for me. Too bad the christmas wishlist was processed
already.
> You could try direct begi
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 http://orgmode.org/Changes.ht
* Bastien wrote:
> Hi Karl,
Hi!
> Karl Voit writes:
>
>> vk-export-agenda: Symbol's function definition is void: org-write-agenda
>
> `org-write-agenda' has been renamed to `org-agenda-write',
> please update your code.
Thanks for the hint! Missed in in the change notes ...
--
Karl Voit
Hi Karl,
Karl Voit writes:
> I am using Org-mode from git and do face a problem when using a
> function that previously worked for a couple of weeks without any
> problem:
>
> Error-Message:
> #+begin_verse
> vk-export-agenda: Symbol's function definition is void: org-write-agenda
> #+end_verse
"Sebastien Vauban" writes:
[...]
> Some time after that, we had block names in the HTML/PDF output, but not
> anymore.
I've been wondering about this for some time. The appearance of source
code block names in exported latex output comes and goes in what appears
to me as a random process! Per
Hi!
I am using Org-mode from git and do face a problem when using a
function that previously worked for a couple of weeks without any
problem:
Error-Message:
#+begin_verse
vk-export-agenda: Symbol's function definition is void: org-write-agenda
#+end_verse
#+begin_src emacs-lisp
(defun vk-export
On Fri, 12 Oct 2007 14:36:42 +0100
Bastien wrote:
> Gijs Hillenius writes:
>
> > But maybe I should not :-). But here goes: I plan to start working on
> > an item by date X -> schedule stamp. The item has a deadline, so ->
> > deadline.
>
> For that I use `org-deadline-warning-days'. I start
Hi all,
is it possible to make S-tab call the global org-cycle when the
point is in a source block?
Best,
Andreas
pin...@iro.umontreal.ca (François Pinard) writes:
[...]
> Hi, Eric. Sorry. Here is a quick correction for that problem. This is
> only this week that I plan to use that function for actual work; last
> week was rather an exploration of the capability of various tools. Of
> course, do not hesi
Am 04.01.2012 11:27, schrieb Bastien:
> Hi Rainer,
>
> Rainer Stengele writes:
>
>> I just pulled and checked but cannot see a change.
>> Did you check in the fix already?
>
> Yes I did.
>
> Try with
>
> (setq org-special-ctrl-a/e nil)
>
> C-e goes *after* the end of the invisible region
"Sebastien Vauban"
writes:
[...]
>> I think it might be good to have a parameter that expands noweb
>> references on evaluation and tangling, but leaves them alone during
>> export. This way the code block would be fully functional, but wouldn't
>> duplicate code during export (when the noweb r
59 matches
Mail list logo
