Achim Gratz writes:
> Eric Schulte writes:
>> I just pushed up a new customization variable named
>> `org-babel-noweb-separator' which is used to join multiple accumulated
>> noweb references like the above. The value defaults to a newline giving
>> the same behavior resulting from your patch b
Eric Schulte writes:
> I just pushed up a new customization variable named
> `org-babel-noweb-separator' which is used to join multiple accumulated
> noweb references like the above. The value defaults to a newline giving
> the same behavior resulting from your patch but can be set to any
> strin
Hi François,
Hi Bastien,
At Mon, 09 Jan 2012 07:50:54 -0500,
François Pinard wrote:
>
> Bastien writes:
>
> > Hi François, please be patient -- your patches are under radar,
> > resending them does not help.
>
> OK, sorry. I do not know enough, yet, how Org works. I sent a problem,
> got a q
Hello,
When I use a python code block in a document any export-as-html results in
the error "Invalid file-name". Without a code block the export goes without
a hitch. Other exports work no probs such as export-as-ascii. The code
block within the document acts as expected, it is only the export tha
On Mon, Jan 23, 2012 at 10:05 PM, Eric Schulte wrote:
> Leo Alekseyev writes:
>
>> On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte wrote:
>>> Leo Alekseyev writes:
>>>
Since all source blocks are evaluated on export, I don't think it
should be necessary to issue org-babel-execute-buffe
Wow - this is /fast/ development :-); now I'm glad my son kept me awake
this night, so that I could check my mails sooner than I normaly would have...
Eric Schulte writes:
> Tom Regner writes:
>
>> Eric Schulte writes:
>>
>>> I'd rather not change the default silently in this way.
>> I unders
Leo Alekseyev writes:
> "Tucking stuff away" can mean different things to different users.
> Personally, I have treated them purely as an organizational device for
> supplementary information (I have :DETAILS: drawers all over my org
> files).
(Out of Context)
Drawer contents => Marginalia[1]?
> statement above. The tag-line to the "Drawers" section in the manual is
> "Tucking stuff away" which I think is often how drawers are used.
> Changing the default drawer export behavior from "don't export" to "do
> export" would be surprising, would break many existing work flows, and
> would li
On 2012-01-24 00:01 +0800, François Pinard wrote:
> Commands `C-c .' and `C-c !' both insert a time stamp in the buffer, and
> the date is prompted in the mini-buffer in the same way for both
> commands. One of them is going to insert , the other [DATE]. The
> mini-buffer always show , like this:
Leo Alekseyev writes:
> On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte wrote:
>> Leo Alekseyev writes:
>>
>>> Since all source blocks are evaluated on export, I don't think it
>>> should be necessary to issue org-babel-execute-buffer before invoking
>>> export. However, running HTML export wit
On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte wrote:
> Leo Alekseyev writes:
>
>> Since all source blocks are evaluated on export, I don't think it
>> should be necessary to issue org-babel-execute-buffer before invoking
>> export. However, running HTML export without org-babel-execute-buffer
>
Nicolas Goaziou writes:
> Hello,
>
> Eric Schulte writes:
>
>> Thanks for taking the time to collect these changes into a patch,
>> however I believe the changes you describe present /new/ behavior (e.g.,
>> new export semantics for drawers), rather than a bug repair.
>
> I'd rather say that its
Tom Regner writes:
> Eric Schulte writes:
>
>> I'd rather not change the default silently in this way.
> I understand that.
My apologies, now that I understand the issue I see that the current
behavior is most likely confusing and I agree with your original
suggestion to change the default.
>
François Pinard wrote:
> It usually does not do the proper thing alone, but `C-l C-l C-l' is
> closer to what I want.
>
Well, the proper thing is very much in the eye of the beholder :-)
Also, I never noticed the binding change: I've been living my life thinking
that C-l *is* recenter... Than
Nick Dokos writes:
> François Pinard wrote:
>> Very, very often, after a Shift-TAB that collapses all entries, [...]
>> I [...] scroll down so see it all.
> You'd need to code it somewhat carefully sp that you wouldn't lose the
> property that after a couple of S-TABs, the buffer looks the same
Eric Schulte writes:
> I'd rather not change the default silently in this way.
I understand that.
>
> Could you provide a minimal example of the difference you describe? I
> just tried viewing the expanded form of the following code block and saw
> no difference between :noweb-ref and normal #+n
François Pinard wrote:
> Hi again.
>
> Very, very often, after a Shift-TAB that collapses all entries, a few
> lines in the vicinity of the cursor are shown at the top of the window,
> which is mainly empty for its reminder; we contemplate the vacuum
> *after* the file. As my Org files are such
Hi Jambunathan,
On 2012-01-24 01:34, Jambunathan K wrote:
In my case, I have simply separated the columns by a character
and set the tab-width to a sensible value for nice on-screen display.
These are 'text' and 'translation of that text' side-by-side,
When you are saying on-screen display,
Hi again.
Very, very often, after a Shift-TAB that collapses all entries, a few
lines in the vicinity of the cursor are shown at the top of the window,
which is mainly empty for its reminder; we contemplate the vacuum
*after* the file. As my Org files are such that all the top level lines
usually
Nicolas Goaziou writes:
>> It all depends if we read the letter or the spirit of the second
>> sentence. "[ ]" is a kind of TODO, and "[X]" is a kind of DONE, as
>> demonstrated by the commands `C-x -' and `C-x *'. That's why I quite
>> naturally expect the cursor to be positioned after the che
On 12-Jan-23, at 3:30 PM, Nicolas Goaziou wrote:
> pin...@iro.umontreal.ca (François Pinard) writes:
>
>> It all depends if we read the letter or the spirit of the second
>> sentence. "[ ]" is a kind of TODO, and "[X]" is a kind of DONE, as
>> demonstrated by the commands `C-x -' and `C-x *'.
It's been irritating me that after saving an edit buffer, the undo
history disappears; the attached patch restores the undo history.
diff --git a/lisp/org-src.el b/lisp/org-src.el
index 8cdf81e..e85e04e 100644
--- a/lisp/org-src.el
+++ b/lisp/org-src.el
@@ -661,7 +661,7 @@ the language, a switch te
Eric S Fraga writes:
> If so, I suggest you could achieve what you want by using the
> org-export-* hooks to, for instance, save current position before export
> and then jump to that position after export? Maybe
> org-export-first-hook and org-export-latex-final-hook could be used?
>
Thanks fo
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> A quick question and a couple of comments on the LaTeX exporter.
>>
>> With the old exporter I set (setq org-export-latex-hyperref-format
>> "\\ref{%s}") so a link to a headline would cross reference properly in
>> L
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The file name passed to \includegraphics is formed like this:
>> ~/path/to/graphics/file
>>
>> My LaTeX doesn't recognize this as a path.
>>
>> The old exporter passed a file name where the tilde was expanded:
>> /Users/user/pa
Lolo le 13 writes:
> Hi !
>
> If I understood well, I think that the difference between C-c . and
> C-c ! is that the timestamp is active or not.
>
> is an active date that appear in agenda view. So you have ti
> use it if you want to see the task scheduled or deadlined.
>
> [DATE] format does n
Hello,
Jambunathan K writes:
> Does the existing behaviour as captured in [[Side-by-Side images laid
> out by hand]] be preserved with new export driver?
I'm not sure to get the syntax right, but in the new exporter, you can
see what is the next or previous element, along with its
properties. T
Hello,
Eric Schulte writes:
>> It's out of exporter's scope.
>
> I disagree. The current exporter conforms to the value of the :results
> header argument (e.g., silent, replace, append, etc...) when executing
> code blocks during export. I see no reason why the new exporter should
> not as wel
pin...@iro.umontreal.ca (François Pinard) writes:
> It all depends if we read the letter or the spirit of the second
> sentence. "[ ]" is a kind of TODO, and "[X]" is a kind of DONE, as
> demonstrated by the commands `C-x -' and `C-x *'. That's why I quite
> naturally expect the cursor to be pos
I'd rather not change the default silently in this way.
Could you provide a minimal example of the difference you describe? I
just tried viewing the expanded form of the following code block and saw
no difference between :noweb-ref and normal #+name: based expansions.
* examples
#+name: first
#
At the moment using the :noweb-ref: property approach on subtrees results in
the tangled code beeing broken
because the newlines before the #+end_src line are excluded from the output.
This patch uses :padline
to check if a newline should be added. The default being yes, tangling with
subtree ma
>> 2) If the source block is executed in buffer with (org-ctrl-c-ctrl-c),
>> as shown above, then the exporter appears to export the in-buffer
>> results /and/ the export-generated results (where :exports is results
>> or both) resulting in two sets of identical results in the export.
>
> It's out
Leo Alekseyev writes:
> Currently, my org files look something like this:
>
> * And now, let's do the analysis !
> #+call: foo(bar)
>
> #+results:
> : earth-shattering results
> : gonna land me a Nobel /and/ a Fields!
>
> But because #+call is not exported, it's not clear what function was
> ca
Hello Andreas
I have added support for character anchored images as part of the
following commit release_7.8.03-201-g1d99fd7.
I am attaching a sample Org file and the associated ODT output.
Nicolas/Eric
Don't be surprised. Please Read on ...
--8<---cut here---start--
Hi !
If I understood well, I think that the difference between C-c . and C-c ! is
that the timestamp is active or not.
is an active date that appear in agenda view. So you have ti use it if
you want to see the task scheduled or deadlined.
[DATE] format does not allow the timestamp to intera
Hello!
An older topic was here:
http://lists.gnu.org/archive/html/emacs-orgmode/2010-01/msg00573.html
The problem seems to persist as of now for latex (and thus pdf)
export. The results are sort of diffuse though.
I am working with emacs on Cygwin using the latest git-version and
native Windows
t...@tsdye.com (Thomas S. Dye) writes:
> The file name passed to \includegraphics is formed like this:
> ~/path/to/graphics/file
>
> My LaTeX doesn't recognize this as a path.
>
> The old exporter passed a file name where the tilde was expanded:
> /Users/user/path/to/graphics/file
It should be fi
Leo Alekseyev writes:
> On Thu, Jan 12, 2012 at 7:52 PM, Rick Frankel wrote:
>> On Thu, Jan 12, 2012 at 06:07:41PM -0700, Eric Schulte wrote:
>>> Rick Frankel writes:
>>>
>>> Turns out it was not that difficult to change this behavior. You and
>>> Leo are both correct that in-buffer-order eval
Fixed. Thanks,
"Sebastien Vauban" writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> there are two related functions which should help.
>>
>> ,[org-babel-view-src-block-info] bound to C-c C-v I
>> | org-babel-view-src-block-info is an interactive Lisp function in
>> | `ob.el'.
>> |
>> | (org-bab
Have you tried using the `org-babel-noweb-error-langs' variable that I
mentioned previously? It should help in these situations.
Yu writes:
> Hello again!
>
> I thought about the *noweb* part again. I tried the following:
>
> ==
> #+begin_src sh :tangle test.
Hi Andrzej,
This looks wonderful, thanks for sharing!
Would you be willing to complete the FSF copyright assignment [1] so
that we can include this into the Org-mode core? If that is not
possible then we could still distribute this in the contrib directory,
but inclusion in the core is definitel
There are currently begin/end_comment blocks implemented as part of
org-exp-blocks.el. See the `org-export-blocks-format-comment' function
which is fairly simple and should not be difficult to customize.
Best,
Samuel Wales writes:
> We had a wonderful discussion of it once, along with differen
Leo Alekseyev writes:
> Since all source blocks are evaluated on export, I don't think it
> should be necessary to issue org-babel-execute-buffer before invoking
> export. However, running HTML export without org-babel-execute-buffer
> currently produces garbage output.
>
What do you mean by "g
Litvinov Sergey writes:
> "Narrowing" in the agenda file does not "survive" agenda redo. Please
> see an example in the first patch. I think the second patch fixes this
> problem.
Hi Sergey,
I haven't had a chance to try your patch yet but I recently tried to fix
this behaviour as well but ther
Nicolas Goaziou writes:
> pin...@iro.umontreal.ca (François Pinard) writes:
>> On check lists however, I would have expected a corresponding
>> behavior. Currently, on the first C-a, the cursor moves back on the
>> "[" character, while I think it should move after the space following
>> "]".
>
sergio writes:
> On 01/23/2012 07:17 AM, Bernt Hansen wrote:
>
>> (setq org-agenda-start-on-weekday nil)
>>
>> C-c a a j -3 w
>
> OK, it works. But it's complicated and week was just an example.
> How to do the same for 3 days? For one day (show 12 hours before, and 12
> after the current moment
pin...@iro.umontreal.ca (François Pinard) writes:
> Hi, Org people! :-)
>
> Commands `C-c .' and `C-c !' both insert a time stamp in the buffer, and
> the date is prompted in the mini-buffer in the same way for both
> commands. One of them is going to insert , the other [DATE]. The
> mini-buffer
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> The documentation string for org-e-latex-remove-logfiles might better
> be:
>
> "Non-nil means remove files with the extensions listed in
> org-e-latex-extensions."
I think that the first sentence of the doc-string should be a tad bit
shorter.
In
Hello,
pin...@iro.umontreal.ca (François Pinard) writes:
> On check lists however, I would have expected a corresponding
> behavior. Currently, on the first C-a, the cursor moves back on the
> "[" character, while I think it should move after the space following
> "]".
According to the document
Tom Regner writes:
> From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
> From: Tom Regner
> Rcpt To: emacs-orgmode@gnu.org
> Date: Mon, 23 Jan 2012 12:39:52 +0100
> Subject: [PATCH] ob.el Adhere to current :padline header during noweb
> dereferencing.
[...]
I'm awfully sorr
Hello Christian
Christian Wittern writes:
> On 2012-01-20 05:03, Jambunathan K wrote:
>> "side-by-side" has surfaced in the list for the second time, I think it
>> deserves to be supported "out of the box".
> I strongly support this, since I have a lot of files with side-by-side
> content. The
Hi all,
I just reviewed code in org.el and noticed that function org-show-subtree,
which is called by org-cycle, unconditionally shows whole subtree (exactly
what I wanted to have in my shortcuts!).
So the question is - why such useful functions like org-show-subtree,
hide-subtree, show-children
Hi, Org people! :-)
Commands `C-c .' and `C-c !' both insert a time stamp in the buffer, and
the date is prompted in the mini-buffer in the same way for both
commands. One of them is going to insert , the other [DATE]. The
mini-buffer always show , like this:
Date+time [2012-01-23]: => <20
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> #+CAPTION[An example photograph]: An example photograph.
>> #+NAME: fig:photo
>>
>> for me, yields:
>>
>> \caption{\label{fig:photo}An example photograph}
>>
>> I was expecting:
>>
>> \caption[An example photograph]{
Hi Guido,
Guido Arnold writes:
> Hello,
> please forgive me for not filing a proper bug report, I am not even a
> org-mode user yet, but I am very interested. I just had a look at the
> quick guide and found a typo in line 1908:
> http://orgmode.org/w/?p=org-mode.git;a=blob;f=doc/orgguide.texi;h
"Narrowing" in the agenda file does not "survive" agenda redo. Please
see an example in the first patch. I think the second patch fixes this
problem.
>From 60ef46625131391c6a49fccd26861f933a984515 Mon Sep 17 00:00:00 2001
From: Litvinov Sergey
Date: Mon, 23 Jan 2012 14:22:53 +0100
Subject: [PATCH
Hi, Org people.
This morning, I activated org-special-ctrl-a/e (setting it to "t"). It
works as documented on header lines having TODO keywords. On check
lists however, I would have expected a corresponding behavior.
Currently, on the first C-a, the cursor moves back on the "[" character,
while
Nicolas Goaziou writes:
[...]
>
> As a side note, #+label has been deprecated in favor of #+name (though
> the former is immediately translated into the latter at parse time).
Sorry for hijacking this thread. But this side note is only valid for
the new exporter, correct? As it does not yiel
>From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
From: Tom Regner
Rcpt To: emacs-orgmode@gnu.org
Date: Mon, 23 Jan 2012 12:39:52 +0100
Subject: [PATCH] ob.el Adhere to current :padline header during noweb
dereferencing.
At the moment using the :noweb-ref: property approach
On 1/23/12 11:48 AM, Andreas Leha wrote:
Jambunathan K writes:
Just pushed a fix whereby one can control the width of the tables.
Thanks for this very useful feature. Works nicely for me.
+1!
Thanks,
Christian
Jambunathan K writes:
> Jambunathan K writes:
>
>> Btw, I was trying to make the tables cute-looking
>
> Just pushed a fix whereby one can control the width of the tables.
>
> , commit f9d242
> | Customize table width using :rel-width option. For example, to create a
> | table of width 60%
Jambunathan K writes:
>> The following snippet exports correctly to LaTeX and to html, but
>> produces the text "Figure Figure" in odt.
>
> Fixed.
Works great for me, thanks! And thanks for all these fast responses!
Best,
Andreas
Bernt Hansen writes:
> Eric S Fraga writes:
>
>> Bernt Hansen writes:
>>
>>
>> [...]
>>
>>> I added the following to my .emacs to keep lowercase.
>>
>> Thanks. This is a great suggestion! Two possible typos, by the way,
>> that would only affect you if you use muse tags:
>>
>>> ("v"
Max Mikhanosha writes:
> At Fri, 20 Jan 2012 12:04:51 -0600,
> John Hendy wrote:
[...]
> Generally I think the way to tackle this is to take advantage that you
> are working with plain text and not with Word document, and use
> standard Emacs/Unix tools for working with text.
Agreed!
> Some i
> The following snippet exports correctly to LaTeX and to html, but
> produces the text "Figure Figure" in odt.
Fixed.
66 matches
Mail list logo
