Hi all,
This is what my patch
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg62256.html is
meant to fix. @Neil, can you confirm the fix?
On Sat, Nov 17, 2012 at 8:41 PM, Bastien wrote:
> I will take care of this before the end of the pretest week.
--
Le
On Fri, Nov 9, 2012 at 8:23 AM, Nicolas Goaziou wrote:
> Thank you for your patch.
>
> Would you mind adding comments in the function in order to explain the
> need for two pass. Also, you may want to reverse the if test in order to
> get rid of the progn.
I've refactored and added comments.
> F
2012ko azaroak 17an, Eric Schulte-ek idatzi zuen:
> Oh!, thanks for catching this, I just pushed up a fix.
This is no longer a (complete) fix for the original problem, though. (A
large part of) the slowdown comes from reading the results from a temp
file and transforming them into an elispy form
Aaron Ecay writes:
> 2012ko azaroak 16an, Eric Schulte-ek idatzi zuen:
>
>>
>> The attached patch adds a "really-silent" results header argument. To
>> see the impact compare the running time of the following two code
>> blocks.
>
> Unfortunately, the attached patch doesn’t work correctly. Thi
2012ko azaroak 16an, Eric Schulte-ek idatzi zuen:
>
> The attached patch adds a "really-silent" results header argument. To
> see the impact compare the running time of the following two code
> blocks.
Unfortunately, the attached patch doesn’t work correctly. This can be
seen by replacing the
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>>
>>> t...@tsdye.com (Thomas S. Dye) writes:
>>>
Agreed. Perhaps a new property, OPTIONAL_TITLE? The texinfo back-end
could use this in menus and the latex back-end could pass it to the
>>>
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Agreed. Perhaps a new property, OPTIONAL_TITLE? The texinfo back-end
>>> could use this in menus and the latex back-end could pass it to the
>>> sectioning command, e.g., \chapter
> There is now a "fullframe" environment.
>
>
No need to be clairvoyant to guess that I'm working on yet another course
for next week :-/
So : thanks to be that helpful.
Fabrice
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Agreed. Perhaps a new property, OPTIONAL_TITLE? The texinfo back-end
>> could use this in menus and the latex back-end could pass it to the
>> sectioning command, e.g., \chapter[optional]{title} (if this isn't
>> already poss
t...@tsdye.com (Thomas S. Dye) writes:
> Agreed. Perhaps a new property, OPTIONAL_TITLE? The texinfo back-end
> could use this in menus and the latex back-end could pass it to the
> sectioning command, e.g., \chapter[optional]{title} (if this isn't
> already possible).
Back-ends can indeed use
Fabrice Popineau writes:
> That would be definitely nice. I think it is quite common that you want to
> get rid of everything to have more space for a big drawing
> (moreover it breaks the monotony of the layout)
There is now a "fullframe" environment.
Regards,
--
Nicolas Goaziou
Oh ... it seems you can do it simply this way :
\begin{frame}[plain,t]{}
\includegraphics[width=\textwidth, height=\textheight]{mypicture}
\end{frame}
Fabrice
2012/11/17 Myles English
>
> Hi Fabrice and Nicolas,
>
> Fabrice Popineau writes:
>
> > That would be definitely nice. I think it is q
Fabrice Popineau writes:
> Hmmm ... well ... I was mistaken by using BEAMER_envargs because it is for
> the old exporter,
> but it doesn't work either by using BEAMER_opt which should be recognized
> by the new exporter.
Indeed, that was a bug in org-e-beamer.el: columns environment didn't
accep
Hmmm ... well ... I was mistaken by using BEAMER_envargs because it is for
the old exporter,
but it doesn't work either by using BEAMER_opt which should be recognized
by the new exporter.
Fabrice
2012/11/17 Fabrice Popineau
> Another problem I can't wolve with the new exporter :
>
> I have th
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> An Org manual convention uses title case for the main menu and sentence
>> case for chapter heads, e.g., the chapter "Document structure" shows up
>> in the main menu as "Document Structure".
>>
>> I haven't been abl
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> An Org manual convention uses title case for the main menu and sentence
> case for chapter heads, e.g., the chapter "Document structure" shows up
> in the main menu as "Document Structure".
>
> I haven't been able to get the texinfo exporter to do t
Nicolas Goaziou writes:
>> I didn't manage to get your (Nicolas') or my own attempt working
>> correctly for exporting matrices. I still think it would be nice.
> It's hard to fix this since you're not very explicit here.
Sorry; you posted a code first which didn't work at all for me; I
tried t
Aloha all,
An Org manual convention uses title case for the main menu and sentence
case for chapter heads, e.g., the chapter "Document structure" shows up
in the main menu as "Document Structure".
I haven't been able to get the texinfo exporter to do this.
Perhaps org-e-texinfo--generate-menu-it
Fabrice Popineau writes:
> Hi,
>
> Given that there is this C# mode :
> http://www.emacswiki.org/emacs/csharp-mode.el
> is there a way to plug it in org-mode so that
> C# becomes part of the languages available for src blocks?
>
I don't know much about C#. Assuming it is similar to C/C++ you co
Achim Gratz writes:
> Andreas Leha writes:
>> I would suggest simply "none" for the new "really-silent".
>
> Yes please, especially since I tried ":results none" two days ago to
> achieve that effect and wondered why it wouldn't work. :-)
>
Great, since "none" seems like the obvious choice I ju
Hi Fabrice and Nicolas,
Fabrice Popineau writes:
> That would be definitely nice. I think it is quite common that you want to
> get rid of everything to have more space for a big drawing
> (moreover it breaks the monotony of the layout)
I don't fully understand this thread but to get a full fra
> If such need is common enough, we may provide a special environment,
> much like "againframe", which would provide a frame without title. For
> example:
>
> * Headline
> :PROPERTIES:
> :BEAMER_env: fullframe
> :END:
>
> What do you think about it?
>
>
>
That would be definit
Fabrice Popineau writes:
>> Otherwise, you can define a dummy string, i.e. "NOTITLE", use that as
>> the headline. Then, with the appropriate filter, you can change
>> \begin{frame}[...]{NOTITLE} into \begin{frame}[...]{}.
>>
>>
> But this one will work and is esay enough. Thanks.
If such need i
Would a non-breaking space as the title work?
>
> Nope, because, the space for the title would still be there and I want to
put a full frame image
> Otherwise, you can define a dummy string, i.e. "NOTITLE", use that as
> the headline. Then, with the appropriate filter, you can change
> \begin{fra
Hello,
Fabrice Popineau writes:
> Everything is in the question ...
>
> How to generate :
>
> \begin{frame}[label=...]{}
>
> \end{frame}
>
> It seems that org-requires a non-empty header.
>
> Thanks for any hint,
Would a non-breaking space as the title work?
Otherwise, you can define a dummy s
Philipp Kroos writes:
> That said, I'm fine with the situation, but I'ld suggest a note in the
> documentation that makes this limitation to subtree-exports clear (and
> possibly points out the workarounds). What do you think?
Sure. What should be written in that note? Where to put it? Or, bette
On Sat, Nov 17, 2012 at 03:42:24PM +0100, Nicolas Goaziou wrote:
> Toby Cubitt writes:
>
> > I've replaced the cons cells with additional plist properties, as you
> > suggested. The resulting customization ui still isn't wonderful in my
> > opinion. But it does the job, and I'm not sure how much
Everything is in the question ...
How to generate :
\begin{frame}[label=...]{}
\end{frame}
It seems that org-requires a non-empty header.
Thanks for any hint,
--
Fabrice
Hello,
Myles English writes:
> I forgot the say TINYCHANGE.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Rasmus Pank Roulund writes:
> I didn't manage to get your (Nicolas') or my own attempt working
> correctly for exporting matrices. I still think it would be nice.
It's hard to fix this since you're not very explicit here.
> I tried to use the regexp
>(not (string-match "|[\\+-]+|" table)
I forgot the say TINYCHANGE.
Myles English writes:
> Fixes bug reported to the mailing list with "[O] [BUG] centering export
> of babel results".
>
> From e9e99b22d814c1272475f30e4bc7543cc46603f4 Mon Sep 17 00:00:00 2001
> From: Myles English
> Date: Sat, 17 Nov 2012 15:18:16 +
> Subject: [
Hi Andreas,
Andreas Leha writes:
> Andreas Leha writes:
>
>> Hi all,
>>
>> There is a bug in the newly introduced centering-instead-of-center
>> feature when it comes to babel results.
Thanks for reporting it.
>> Here is the problem (already *unintentionally* centered):
I don't know how to i
Fixes bug reported to the mailing list with "[O] [BUG] centering export
of babel results".
>From e9e99b22d814c1272475f30e4bc7543cc46603f4 Mon Sep 17 00:00:00 2001
From: Myles English
Date: Sat, 17 Nov 2012 15:18:16 +
Subject: [PATCH] org-e-latex: Fixes bug introduced by commit 907110e
* con
Nicolas Goaziou writes:
> Nicolas Goaziou writes:
>
>> It might support "Property+" syntax, but it looks like this is
>> Babel-specific (no sign of such syntax in org.el, where property API is
>> defined). I will look into it (unless you want to do it).
>
> Well, scratch that: it already support
Toby Cubitt writes:
> I've replaced the cons cells with additional plist properties, as you
> suggested. The resulting customization ui still isn't wonderful in my
> opinion. But it does the job, and I'm not sure how much scope there is
> for improving it further. If you see a way, by all means f
Hi,
Given that there is this C# mode :
http://www.emacswiki.org/emacs/csharp-mode.el
is there a way to plug it in org-mode so that
C# becomes part of the languages available for src blocks?
Regards,
Fabrice
On Sat, Nov 17, 2012 at 09:48:09AM +0100, Nicolas Goaziou wrote:
> Toby Cubitt writes:
>
> > Here's an updated patch. Now both org-time-clocksum-format and
> > org-time-clocksum-fractional-format can be plists, as discussed.
>
> That was quick. Thank you.
>
> > In the org-time-clocksum-format c
Hello,
Rasmus writes:
> Hi,
>
> I rely on org-special-blocks.el to provide easy access to the LaTeX
> proof environment and such.
org-export.el supersedes org-special-blocks.el: don't use the latter.
> Up till now I have been placing LaTeX
> labels in them manually, but I would like to #+NAME
Nicolas Goaziou writes:
> It might support "Property+" syntax, but it looks like this is
> Babel-specific (no sign of such syntax in org.el, where property API is
> defined). I will look into it (unless you want to do it).
Well, scratch that: it already support :property+: syntax. I.e. try to
ex
Hi,
I rely on org-special-blocks.el to provide easy access to the LaTeX
proof environment and such. Up till now I have been placing LaTeX
labels in them manually, but I would like to #+NAME them.
Here's an example
#+begin_src org
* section two
#+NAME:p1
#+BEGIN_PROPOSITION
1+1=2
#+END_P
Nicolas Goaziou writes:
>> I'm doing some stuff where the natural output of my tables are
>> matrices. I found a decent translation function here ¹. However,
>> I'm not very successful in making org use it.
>
> Using the new exporter, something like should replace any table using
> default env
On Fri, Nov 16, 2012 at 6:39 PM, Memnon Anon wrote:
>
> Manish writes:
>
> > a way to
> > pick out all #+begin_src parts from the .org version?
>
> (org-babel-tangle &optional ONLY-THIS-BLOCK TARGET-FILE LANG),
> bound to `C-c C-v t' by default.
> Not all emacs-lisp blocks are set to :tangle yes, t
Hello,
Philipp Kroos writes:
> Anyway, I'm still curious if it wouldn't be feasible to treat
> subtree-options more similar to inbuffer-options?
It is feasible but it isn't consistent with Org mode properties.
According to manual (section 7.1):
Note that a property can only have one entry
Hi Andy,
Andy Moreton writes:
>> When I switch to the ELPA version ( "Org-mode version 7.9.2
>> (7.9.2-82-g2aeb28-elpa @ . . . )") this misbehavior is corrected.
>> HTH.
>
> I've filed emacs bug#12905 about this, as it is occurring in on the
> emacs-24 branch, and emacs 24.3 is getting close to
Ok, thanks to both of you. I'll stick with the workarounds pointed out
by Alan for now.
Anyway, I'm still curious if it wouldn't be feasible to treat
subtree-options more similar to inbuffer-options?
Maybe I'll have a look at that in some spare time, though I think my
understanding of the concept
On Fri 16 Nov 2012, Neil Best wrote:
> When I switch to the ELPA version ( "Org-mode version 7.9.2
> (7.9.2-82-g2aeb28-elpa @ . . . )") this misbehavior is corrected.
> HTH.
I've filed emacs bug#12905 about this, as it is occurring in on the
emacs-24 branch, and emacs 24.3 is getting close to rel
Andreas Leha writes:
> Hi all,
>
> There is a bug in the newly introduced centering-instead-of-center
> feature when it comes to babel results.
>
> Here is the problem (already *unintentionally* centered):
> #+begin_src R :exports results :colnames yes
> data.frame(a=1:2, b=3:4)
> #+end_src
>
>
Hi all,
There is a bug in the newly introduced centering-instead-of-center
feature when it comes to babel results.
Here is the problem (already *unintentionally* centered):
#+begin_src R :exports results :colnames yes
data.frame(a=1:2, b=3:4)
#+end_src
#+results:
| a | b |
|---+---|
| 1 | 3 |
Hello,
Sébastien Delafond writes:
> I've put together a somewhat crude confluence exporter that's based on
> the new exporter (as of 7.9.2). For now it's hosted on github[1].
Thank you for your work.
Do not hesitate to ask any technical question on the new export API.
Also, if/when you feel it
Toby Cubitt writes:
> Here's an updated patch. Now both org-time-clocksum-format and
> org-time-clocksum-fractional-format can be plists, as discussed.
That was quick. Thank you.
> In the org-time-clocksum-format case, I made the values cons cells which
> specify both a format string and a bool
50 matches
Mail list logo
