Hello,
Aaron Ecay writes:
> The org-target face is created in org-faces.el, but never used for
> font-locking. This patch fixes that.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Yagnesh Raghava Yakkala writes:
> IIUC, Achim means,
Thanks for spelling that out for me. :-)
> Given texi generation is very slow, I wonder which format of manual
> will be included in Emacs trunk.?
Well, there obviously needs to be improvement on that front. I've
profiled the export already,
Hi Achim,
thanks for doing the profiling.
Achim Gratz writes:
> org-macro-replace-all2222.371024111.185512
This one looks suspicious: if the function does what it says,
why does it run twice? If we can spare 111 secs here, that's
already an improvement. I'll have a look at some p
Hi Ken,
Ken Williams writes:
> Would this be helpful to include by default? Patch attached.
I committed something deeply inspired by your patch,
but slightly different. Please have a look (from master)
and let me know if you think this is okay.
Thanks for this idea!
--
Bastien
Aaron Ecay writes:
> The org-target face is created in org-faces.el, but never used for
> font-locking. This patch fixes that.
Thanks. It is easier for the maintainers to deal with your patches if
you produce them with
git format-patch HEAD~n
where n is the number of commits your patch compris
Hello,
aarone...@gmail.com writes:
> This should now be handled. The new patch will follow this email. In
> related news, I have completed the FSF copyright assignment process, so
> the patch can be merged whenever it is deemed ready.
Your patch looks good. I have pushed it with minor stylisti
Hello,
Bastien writes:
> Hi Achim,
>
> thanks for doing the profiling.
>
> Achim Gratz writes:
>
>> org-macro-replace-all2222.371024111.185512
>
> This one looks suspicious: if the function does what it says,
> why does it run twice? If we can spare 111 secs here, that's
> already
Bastien writes:
>> org-macro-replace-all2222.371024111.185512
>
> This one looks suspicious: if the function does what it says,
> why does it run twice? If we can spare 111 secs here, that's
> already an improvement. I'll have a look at some point but
> feel free to beat me on this!
Michael Strey writes:
> Here is a draft proposal for a user interface using Nicola's suggestion:
I like this. About the :BODY: tag, do we really need it if it's
optional? Also, do we enfore the order: what if there is a section after
we start on the ENCL or PS tags?
Alan
Hello,
Alan Schmitt writes:
> Michael Strey writes:
>
>> Here is a draft proposal for a user interface using Nicola's suggestion:
>
> I like this. About the :BODY: tag, do we really need it if it's
> optional? Also, do we enfore the order: what if there is a section after
> we start on the ENCL
Hi Tassilo,
Tassilo Horn writes:
> Bastien writes:
>
>>> I have seven agenda files, all not too big (~10K on average), and I
>>> use an averagely performant computer (5 years old dual core laptop).
>>> For me, the difference between `org-agenda-inhibit-startup' set to t
>>> or nil is not notica
Hello,
Is the asynchronous exporter supposed to work when a request to evaluate
a code block needs to be answered? I was wondering why the exporter was
getting stuck, and found a buffer where the question was asked but I had
no way to answer it.
Thanks,
Alan
Achim Gratz writes:
[...]
> No, nothing complete yet. Here's what I have so far, some autoload
> definitions might still be there, but will error out due to the fact
> that their target files are not in load-path anymore.
Thanks for this. I've incorporated it into my emacs startup. It shoul
Nicolas Goaziou writes:
[...]
> Indeed, this won't work anymore: `org-latex-translate-alist' has been
> removed. The equivalent would just be to use a defadvice:
>
> #+begin_src emacs-lisp
> (defadvice org-latex-headline (around my-latex-skip-headlines
> (he
Charles Berry writes:
[...]
> If you just want the latex to have "\section{}" you can do this
[...]
Chuck,
thanks for this. It makes sense and I will give it a try. This
approach still does require creating a new backend. The implications of
this are not clear to me but I will play with th
Nicolas Goaziou writes:
[...]
> Bind keywords are supported. Unfortunately, `org-latex-pdf-process' is
> not bind-able.
>
> BIND variables are set as buffer-local variables in the buffer where the
> transcoding takes place. So, they affect the way the current buffer is
> changed into LaTeX code.
Hi all,
I wrote a worg page with some advice on how to speed up agenda
commands:
http://orgmode.org/worg/agenda-optimization.html
I also reverted the change for two variables:
org-agenda-inhibit-startup
org-agenda-dim-blocked-tasks
Those used to be respectively nil and t, and while worki
> > I have migrated the migration instructions and tips here:
> > http://orgmode.org/worg/org-8.0.html
>
I have managed to get the new exporter working. Thank you everyone for
helping.
In case any one else is struggling with the same, following links
helped me in getting it to work:
http://org
Hello Jambunathan,
Jambunathan K writes:
> Torrey
>
One small problem, though: I see that if there is a TOC at the top and
then one included later using #+TOC, the exporter gives them both the
same id (). Duplicate ID's makes the XML
invalid.
>>>
>>> What do you suggest inst
There has been some change in the behaviour of #+CAPTION in case of
tables made by source blocks. In the old exporter, #+CAPTION just
before #+BEGIN_SRC was sufficient to place the caption before the
table when the file was exported.
The new exporter does not produce captions the same way.
When I
Hi Bastien,
I think this is the right decision, thanks. And thanks for the nice
documentation! Tis might deserve a spot in the manual, in the final
chapter.
Cheers
- Carsten
On 6 mrt. 2013, at 10:45, Bastien wrote:
> Hi all,
>
> I wrote a worg page with some advice on how to speed up
Hello,
Vikas Rawal writes:
> There has been some change in the behaviour of #+CAPTION in case of
> tables made by source blocks. In the old exporter, #+CAPTION just
> before #+BEGIN_SRC was sufficient to place the caption before the
> table when the file was exported.
>
> The new exporter does n
tftor...@tftorrey.com (T.F. Torrey) writes:
>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage. For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they co
Hello,
Alan Schmitt writes:
> Is the asynchronous exporter supposed to work when a request to evaluate
> a code block needs to be answered?
Well, no, but its somewhat difficult to prevent it. Besides security
considerations, even if we set `org-confirm-babel-evaluate' to nil
during an asynchron
Hi Bastien,
>> Ok, the testfile looks like
>>
>> * The folded top-level headline
>>
>> ** TODO Some test todo headline 0
>>
>>- also some contents
>>
>> ** TODO Some test todo headline 1
>>
>>- also some contents
>>
>> and has 2000 such subheadlines. File size is 127K.
>> `org-startup-fo
Hello,
Eric Abrahamsen writes:
> I've attached a minimum org file that shows what I'm trying to do:
> essentially to attach a hook to the export process that ends up calling
> org-map-entries to make alterations to the file just before it's
> exported.
>
> As I've got it now, the hook does chang
Achim Gratz writes:
> Bastien writes:
>>> org-macro-replace-all2222.371024111.185512
>>
>> This one looks suspicious: if the function does what it says,
>> why does it run twice? If we can spare 111 secs here, that's
>> already an improvement. I'll have a look at some point but
>> f
Eric S Fraga writes:
> Nicolas Goaziou writes:
>
> [...]
>
>> Bind keywords are supported. Unfortunately, `org-latex-pdf-process' is
>> not bind-able.
>>
>> BIND variables are set as buffer-local variables in the buffer where the
>> transcoding takes place. So, they affect the way the current bu
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> I've attached a minimum org file that shows what I'm trying to do:
>> essentially to attach a hook to the export process that ends up calling
>> org-map-entries to make alterations to the file just before it's
>> exported.
>>
>> A
tftor...@tftorrey.com (T.F. Torrey) writes:
> extensive experience developing XSLT and lisp to process the XHTML
> output of Org,
Is there a way your specific problem could be solved if we were to use
CSS counters for numbering various things? Would you like to submit a
patch to ox-html.el that
> CAPTION keyword above a source block applies to the source block only.
> If the source block generates a table, you have to put a CAPTION above
> it, as it will not inherit the caption of the source block.
>
> It also implies that you need to name the results. Otherwise, source
> block will not
Hi orgers,
If there a way to disable auto-fill-mode within org-babel code block ? I
had look through the FAQ as well as search in the mailing list archives
but do not find any related answers.
I am using org version 7.8.11.
Thanks for your help,
Xavier
The aren't really content elements but merely structuring
or styling elements.
I think there should be a clear separation between contents and how it
is wrapped. The base HTML exporter should just generate content with no
divs at all. There could be a fancy HTML exporter which does generate
Hi,
While PDF exporting a .org file, the underlined lines which are at the
right end of the page (in PDF) or underlined lines which are large and
spans to next line (in pdf) are not breaking properly.
How do I solve this problem ?
Thanks.
-
*Sanjib Sikder
**
*
Hi Xavier,
Xavier Garrido writes:
> If there a way to disable auto-fill-mode within org-babel code block ? I
> had look through the FAQ as well as search in the mailing list archives but
> do not find any related answers.
>
> I am using org version 7.8.11.
You need to update to the current Org
Hello Sanjib,
On Wed, Mar 06, 2013 at 05:07:44PM +0530, Sanjib Sikder wrote:
> Hi,
>
> While PDF exporting a .org file, the underlined lines which are at the
> right end of the page (in PDF) or underlined lines which are large and
> spans to next line (in pdf) are not breaking properly.
>
> How
Jambunathan K writes:
>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage. For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they could link to each sepa
On Wed, Mar 06, 2013 at 12:52:24AM +0100, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I'm not sure what a \tableofcontents outside a frame would look like.
> > Can someone show an example?
>
> I think that the idea behind a frameless TOC is that you provide your
> own frame for it.
>
> It
I can confirm this is fixed now. :)
Thanks,
On Wed, Mar 06, 2013 at 12:29:10AM +0100, Nicolas Goaziou wrote:
> Hello,
>
> Suvayu Ali writes:
>
> > Hi Achim,
> >
> > On Tue, Mar 05, 2013 at 07:26:54PM +0100, Achim Gratz wrote:
> >> Suvayu Ali writes:
> >> > That said, I have noticed something
Vikas Rawal writes:
>> CAPTION keyword above a source block applies to the source block only.
>> If the source block generates a table, you have to put a CAPTION above
>> it, as it will not inherit the caption of the source block.
>>
>> It also implies that you need to name the results. Otherwis
Nicolas Goaziou gmail.com> writes:
> Well, no, but its somewhat difficult to prevent it. Besides security
> considerations, even if we set `org-confirm-babel-evaluate' to nil
> during an asynchronous export, this won't handle the case of the user
> explicitly uses a :query keyword in a source bloc
Hello,
Andreas Leha writes:
> Nicolas Goaziou writes:
>>
>> Andreas Leha writes:
>>
>>> from a recent thread I learned about #+TOC (there's always something new
>>> to learn about org mode).
>>>
>>> I'd like to use it in a beamer document. Here I find it hard to use
>>> because it introduces
Thanks Bastien for your prompt answer. For the time being, I prefer to
wait the 8.0 release.
Xavier
Le 06/03/2013 12:41, Bastien a écrit :
Hi Xavier,
Xavier Garrido writes:
If there a way to disable auto-fill-mode within org-babel code block ? I
had look through the FAQ as well as search i
emacs-orgmode-requ...@gnu.org writes:
> Today's Topics:
> 39. Re: org-exp-bibtex missing in git? (Vikas Rawal)
> Message: 39
> Date: Mon, 4 Mar 2013 10:10:37 +0530
> From: Vikas Rawal
> To: emacs-orgmode
> Subject: Re: [O] org-exp-bibtex missing in git?
>
>>
>> I do confirm.
>
> Thank you.
Hello,
Achim Gratz writes:
>> A very ugly hack would be to use:
>>
>> (defalias 'yes-or-no-p 'ignore)
>
> Ugh. I hope this won't be necessary.
I hope too.
> I've recently refactored the evaluation check so it determines first whether
> the
> code-block should be run and only in the affirma
Hello,
Andreas Leha writes:
> I'd very much like to see org-latex-timestamp-format adhere to a
> possibly present #+LANGUAGE setting.
There is no such variable as `org-latex-timestamp-format'.
> If I set org-latex-timestamp-format to "%A, %Y-%m-%d" the following org
> file produces
> "Donnerst
Achim Gratz writes:
> I've recently refactored the evaluation check so it determines first whether
> the
> code-block should be run and only in the affirmative checks if it should query
> the user. So it should be much easier now to have another dynamic binding for
> preventing the question _and
Eric Abrahamsen writes:
>> The problem is not directly related to the export framework, but to its
>> relationship with `org-map-entries'.
>>
>> If you use the following function:
>>
>> (defun before-export-test (backend)
>> ;; (org-map-entries 'test-map "TODO=\"TODO\"" 'file)
>> (while
Hello,
First of all, if this question has been answered before or I should direct
it elsewhere then please let me know. I've spent some time researching and
experimenting, but I'm new to Emacs so I may well have overlooked something
obvious.
I'm trying to get org-protocol working, and I've hit a
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> Nicolas Goaziou writes:
>>
>>> Bastien writes:
>>>
Hi Vikas,
François Allisson writes:
> org-exp-bibtex, because of its dependency on the old exporter, was first
> moved from contrib/lisp to contrib/old
Hi Sanjib,
This is a known LaTeX issue that has nothing to do with Org. Please
check the LaTeX packages ulem.sty and soul.sty or simply don't use
underlining -- it's anyway ugly.
Best regards
--
Michael Strey
www.strey.biz
Hi Nicolas,
thanks for taking this up!
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I'd very much like to see org-latex-timestamp-format adhere to a
>> possibly present #+LANGUAGE setting.
>
> There is no such variable as `org-latex-timestamp-format'.
>
Of course I meant 'or
Hello Sanjib,
On Wed, Mar 06, 2013 at 06:55:36PM +0530, Sanjib Sikder wrote:
>
> If you feel that the problem is not related to org-mode, then ignore this
> email and thanks for your time and patience.
It is indeed a LaTeX issue! And I have an answer too :). Org mode
translates _underlined tex
Hi,
Thanks for the suggestions.
For an user like me, who depends heavily on org-mode for several purposes,
a basic feature like this (underline) is frequently used. Though it is ugly
or (may be) not used for serious published materials, but for personal
usage, this is very handy and very often I
Hi,
having
- [2013-01-24 Do] text
- [2013-01-25 Fr] text
- [2013-02-01 Fr] text
which in full view is
- [2013-01-24 Do] text
* text
- [2013-01-25 Fr] text
#+BEGIN_EXAMPLE
TEXT
#+END_EXAMPLE
- [2013-02-01 Fr] text
* othe
Hello,
Rainer Stengele writes:
> having
>
> - [2013-01-24 Do] text
> - [2013-01-25 Fr] text
> - [2013-02-01 Fr] text
>
[...]
> I would like to sort the highest level entries, alphabetically would do
> in this case, ending up with
>
> - [2013-02-01 Fr] text
> - [2
Bastien writes:
> Achim Gratz writes:
>
>> I hope to put this together in the next week or
>> so, then it will be possible to nuke all traces fr4om an old Org and
>> then start from a clean slate with a new Org installation.
>
> Okay, thanks. Let us know how it goes,
What temporary (as in ever
Am 06.03.2013 15:30, schrieb Nicolas Goaziou:
> Hello,
>
> Rainer Stengele writes:
>
>> having
>>
>> - [2013-01-24 Do] text
>> - [2013-01-25 Fr] text
>> - [2013-02-01 Fr] text
>>
>
> [...]
>
>
>> I would like to sort the highest level entries, alphabetically would do
>> in t
Rainer Stengele writes:
> Am 06.03.2013 15:30, schrieb Nicolas Goaziou:
>> Hello,
>>
>> Rainer Stengele writes:
>>
>>> having
>>>
>>> - [2013-01-24 Do] text
>>> - [2013-01-25 Fr] text
>>> - [2013-02-01 Fr] text
>>>
>>
>> [...]
>>
>>
>>> I would like to sort the highest lev
Am 06.03.2013 16:51, schrieb Nicolas Goaziou:
> Rainer Stengele writes:
>
>> Am 06.03.2013 15:30, schrieb Nicolas Goaziou:
>>> Hello,
>>>
>>> Rainer Stengele writes:
>>>
having
- [2013-01-24 Do] text
- [2013-01-25 Fr] text
- [2013-02-01 Fr] text
>>
Rainer Stengele writes:
> I reread the manual:
>
> C-c ^ (org-sort)
> Sort same-level entries. When there is an active region, all entries
> in the region will be sorted. Otherwise the children of the current
> headline are sorted. The command prompts for the sorting method, which
> can b
Julien Cubizolles writes:
> Bastien writes:
>
>> Achim Gratz writes:
>>
>>> I hope to put this together in the next week or
>>> so, then it will be possible to nuke all traces fr4om an old Org and
>>> then start from a clean slate with a new Org installation.
>>
>> Okay, thanks. Let us know how
Hello,
David Engster writes:
> Julien Cubizolles writes:
>> Bastien writes:
>>
>>> Achim Gratz writes:
>>>
I hope to put this together in the next week or
so, then it will be possible to nuke all traces fr4om an old Org and
then start from a clean slate with a new Org installati
Nicolas Goaziou writes:
> Hello,
>
> David Engster writes:
>
>> Julien Cubizolles writes:
>>> Bastien writes:
>>>
Achim Gratz writes:
> I hope to put this together in the next week or
> so, then it will be possible to nuke all traces fr4om an old Org and
> then start from a
David Engster writes:
> I just pushed a change which should fix this (if the new exporter is
> compatible;
It doesn't seem to be, I get
--8<---cut here---start->8---
apply: Symbol's function definition is void: org-export-icalendar
--8<---cut h
Julien Cubizolles writes:
> David Engster writes:
>> I just pushed a change which should fix this (if the new exporter is
>> compatible;
>
> It doesn't seem to be, I get
>
> apply: Symbol's function definition is void: org-export-icalendar
>
> when running org-caldav-sync, which is weird since o
David Engster writes:
>> What do you need from org-icalendar.el?
>
> Only org-export-icalendar. As long as that one is producing the same
> output, everything should be fine.
Unfortunately, there is no `org-export-icalendar' anymore.
There is:
(org-icalendar--combine-files nil FILES)
which
David Engster writes:
> Julien Cubizolles writes:
>> David Engster writes:
>>> I just pushed a change which should fix this (if the new exporter is
>>> compatible;
>>
>> It doesn't seem to be, I get
>>
>> apply: Symbol's function definition is void: org-export-icalendar
>>
>> when running org-
Nicolas Goaziou writes:
> David Engster writes:
>
>>> What do you need from org-icalendar.el?
>>
>> Only org-export-icalendar. As long as that one is producing the same
>> output, everything should be fine.
>
> Unfortunately, there is no `org-export-icalendar' anymore.
>
> There is:
>
> (org-ica
Hi all,
with the advent of Org 8.0, a special effort needs to be made
to keep the manual and Worg updated.
I thought it would be nice to gather on IRC and focus on this
together for a few hours, so here is a doodle:
http://doodle.com/s7fhueeifaex54t8
Also, I'll to discuss with people I only k
Julien Cubizolles writes:
> David Engster writes:
>> No, it's not defined in ox-icalendar. I guess it must be generated by
>> the new exporter first, probably through some additional require.
>
> I have the following definition in ox-icalendar.el.
>
> (defgroup org-export-icalendar nil
> "Optio
Suvayu Ali writes:
> On Wed, Mar 06, 2013 at 12:52:24AM +0100, Nicolas Goaziou wrote:
>>
>> I think this kind of control should really belong to specific latex
>> code.
>>
>> A TOC limited to current section sure sounds seducing, but I'm not sure
>> how to achieve this in LaTeX.
>
> I think yo
David Engster writes:
> After skimming through the new exporter, it also seems that
> org-combined-agenda-icalendar-file was replaced with
> org-icalendar-combined-agenda-file. Is that correct?
>
> I'm also using org-icalendar-timezone, org-icalendar-store-UID, and
> org-icalendar-date-time-forma
Hi Andreas and all,
Andreas Leha writes:
> Eric suggested/uses this format (thanks for sharing, Eric):
> [[cite:jones-etal-2000][Jones et al., 2000]]
> ^^^ ^^
> key displayed in org
I'd suggest to treat org-link-abbrev-alist and loc
Hello,
Bastien writes:
> Hi Andreas and all,
>
> Andreas Leha writes:
>
>> Eric suggested/uses this format (thanks for sharing, Eric):
>> [[cite:jones-etal-2000][Jones et al., 2000]]
>> ^^^ ^^
>> key displayed in org
>
> I'd suggest
Thanks John. I was a little nervous about upgrading org version. I use
Vince Goulet's version of emacs with ESS built-in, and he removed
org-mode from his latest release (24.2.1)
http://vgoulet.act.ulaval.ca/pub/emacs/NEWS-windows
But I downloaded and installed the newer emacs anyway, and got org
Here is a quick patch. Not meant to be applied but meant for testing
purpose only.
So there is a html backend which doesn't add divs and there is a HTML
backend that adds divs. (The difference is between html and HTML, in
capslock).
The `org-export-dispatch' uses HTML backend, while you can c
Hi Nicolas,
I'm still waiting for feedback from Karl Voit over in the other thread,
but here's the amended patch for you to review:
>From c49b4ab5afda4d223cbcf97cb8c7ac0f9cc8e39b Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Wed, 27 Feb 2013 22:55:26 +0100
Subject: [PATCH] ob-core: do not ask
Well, with the little test file I initially posted, things worked OK
with org version 7.9.3f. But things are bit more complicated:
---
* goodbye
foo foo
* Hello
:PROPERTIES:
:EXPORT_FILE_NAME: TestMyBabelSetup
:EXPORT_TITLE: foobar
:EXPORT_AUTHOR: Christopher W.
Andreas Leha writes:
> And while I still think, that setting the #+LANGUAGE in org should
> ideally be reflected in the export -- also for the date formatting -- I
> found a solution to my problem that I use now: It does not use orgmode's
> date and date-formatting facilities, but moves the work to
Hi all,
I have a beamer presentation in org-mode that contains a line like
#+LaTeX_HEADER: \subtitle{foo}
This prevents me from using 'org-preview-latex-fragment' as that one --
naturally, as it uses the article class -- fails with
'Failed to create dvi file from /tmp/orgtex49760oq.tex'
due to
,
Eric S Fraga writes:
>> No, nothing complete yet. Here's what I have so far, some autoload
>> definitions might still be there, but will error out due to the fact
>> that their target files are not in load-path anymore.
>
> Thanks for this. I've incorporated it into my emacs startup. It should
>
Nicolas Goaziou writes:
[...]
> A TOC limited to current section sure sounds seducing, but I'm not sure
> how to achieve this in LaTeX.
Something like this?
\tableofcontents[sectionstyle=show/hide, subsectionstyle=show/show/hide]
Full example:
#+begin_src org
#+TITLE: Something
#+LaTeX_CLAS
Achim Gratz writes:
> I'm still waiting for feedback from Karl Voit over in the other thread,
> but here's the amended patch for you to review:
Thanks. I haven't much to say wrt to the internals since the only thing
needed to make use of this patch is to set
`org-babel--suppress-confirm-evaluate
Nicolas Goaziou writes:
> Hello,
>
> Bastien writes:
>
>> Hi Andreas and all,
>>
>> Andreas Leha writes:
>>
>>> Eric suggested/uses this format (thanks for sharing, Eric):
>>> [[cite:jones-etal-2000][Jones et al., 2000]]
>>> ^^^ ^^
>>> key
Hello Jambunathan,
I admire your energy and coding skill, but I wish you would stop
occupying our time with replies like this. Your tone is insulting, and
seems deliberately so, and none of this response is helpful to the
original thread.
I won't reply to more of your posts like this, so if you
Nicolas Goaziou writes:
> David Engster writes:
>
>> After skimming through the new exporter, it also seems that
>> org-combined-agenda-icalendar-file was replaced with
>> org-icalendar-combined-agenda-file. Is that correct?
>>
>> I'm also using org-icalendar-timezone, org-icalendar-store-UID, and
Hello Jambunathan,
Jambunathan K writes:
> Is there a way your specific problem could be solved if we were to use
> CSS counters for numbering various things? Would you like to submit a
> patch to ox-html.el that uses CSS-based counters rather than counters
> computed with hand.
No.
I'm not s
On Wed, Mar 6, 2013 at 1:33 PM, Christopher W. Ryan
wrote:
> Thanks John. I was a little nervous about upgrading org version. I use
> Vince Goulet's version of emacs with ESS built-in, and he removed
> org-mode from his latest release (24.2.1)
>
> http://vgoulet.act.ulaval.ca/pub/emacs/NEWS-window
Achim Gratz writes:
> Andreas Leha writes:
>> And while I still think, that setting the #+LANGUAGE in org should
>> ideally be reflected in the export -- also for the date formatting -- I
>> found a solution to my problem that I use now: It does not use orgmode's
>> date and date-formatting facil
Nicolas Goaziou writes:
> `org-babel--suppress-confirm-evaluate-answer-no' to t from
> `org-export-async-start'. I would suggest a shorter variable name,
I've dropped the "suppress-" as it is redundant, but kept the
"confirm-evaluate".
>> -;;; ob-core.el --- working with code blocks in org-mode
>
Thanks for considering the changes.
Achim Gratz writes:
> + (org-babel-call-process-region-original
> + (if (org-bound-and-true-p
> org-babel-call-process-region-original)
> + (symbol-function 'call-process-region)))
I think you mean (or () (...
Andreas Leha writes:
> Nicolas Goaziou writes:
>
> [...]
>
>> A TOC limited to current section sure sounds seducing, but I'm not sure
>> how to achieve this in LaTeX.
>
> Something like this?
> \tableofcontents[sectionstyle=show/hide, subsectionstyle=show/show/hide]
Actually, I am looking for
Hello Jambunathan,
You are not welcome on this list anymore, please ban yourself.
Thanks,
--
Bastien
Nicolas Goaziou writes:
> I think you mean (or () ())
Yes of course, thanks for catching that. This also means that the
testsuite isn't picking upon that.
> I will wait for this patch to be committed.
When and if Eric chimes in and Karl confirms that his earlier problem
with this change
Hello,
Andreas Leha writes:
> I have a beamer presentation in org-mode that contains a line like
> #+LaTeX_HEADER: \subtitle{foo}
>
> This prevents me from using 'org-preview-latex-fragment' as that one --
> naturally, as it uses the article class -- fails with
> 'Failed to create dvi file from
Hi Nicolas,
Nicolas Goaziou writes:
> If we're not going to provide a multi-backend solution, I suggest to
> keep things simple and write LaTeX code directly (or use the solution
> provided by Eric). Unless you have something else in mind with these
> link abbrevs, of course.
Can you resend me
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I have a beamer presentation in org-mode that contains a line like
>> #+LaTeX_HEADER: \subtitle{foo}
>>
>> This prevents me from using 'org-preview-latex-fragment' as that one --
>> naturally, as it uses the article class -- fails wi
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> Nicolas Goaziou writes:
>>
>> [...]
>>
>>> A TOC limited to current section sure sounds seducing, but I'm not sure
>>> how to achieve this in LaTeX.
>>
>> Something like this?
>> \tableofcontents[sectionstyle=show/hide, subsectionstyle=show/
Hi Bastien,
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> If we're not going to provide a multi-backend solution, I suggest to
>> keep things simple and write LaTeX code directly (or use the solution
>> provided by Eric). Unless you have something else in mind with these
>> lin
1 - 100 of 115 matches
Mail list logo
