Hi,
I was just trying the same thing (prompted by the recent discussion).
It turned out I had to
#+begin_src emacs-lisp
(bibtex-set-dialect)
#+end_src
first.
Regards,
Sean
On Thu, Nov 21, 2013 at 3:55 AM, Marvin Doyley marvin...@gmail.com wrote:
Hi there,
I have decided to give
I have found that opening a (any) bibtex file fixes this for the session. I
have no idea why though.
Chris.
On 21 November 2013 09:25, Sean O'Halpin sean.ohal...@gmail.com wrote:
Hi,
I was just trying the same thing (prompted by the recent discussion).
It turned out I had to
#+begin_src
Hello Eric,
IIRC, some time ago, a bug involving the computation of the hash (when option
cache is enabled) and NoWeb code blocks. I remember that it had been fixed.
However, the following example shows it's not (true anymore):
--8---cut here---start-8---
On Thu, Nov 21, 2013 at 08:11:50AM +0700, Eric Abrahamsen wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20, 2013 at 09:15:43PM +, Luke Crook wrote:
That works. But that means I need both #+HTML:
Hi, Eric,
You can derive a new back-end from existing ones. Please consult org
export reference
documentationhttp://orgmode.org/worg/dev/org-export-reference.html
.
Yujie
2013/11/22 Eric Schulte schulte.e...@gmail.com
Hi,
I'd like to add a new option to the LaTeX backend from a contrib/
Hi, Jambunathan and Nick
Yes, I prefer the separated org files be exported to several HTMLs, but
with continuous heading numbering. Not that re-including them and export
into one HTML. :) Thanks for your suggestions.
Yujie
2013/11/21 Nick Dokos ndo...@gmail.com
Yujie Wen yjwen...@gmail.com
Hello,
Christian Moe m...@christianmoe.com writes:
The two examples below illustrate an odd ODT export failure that occurs in
restricted circumstances: only when the target of the link is on a
higher level of the tree than the link.
* This fails
** A subheader
This paragraph is
Hello,
Eric Schulte schulte.e...@gmail.com writes:
I'd like to add a new option to the LaTeX backend from a contrib/
package so that it can be set with a #+ keyword. Is this possible? If
so how would one go about making this change. If not what's the best
way to add a new optional value
Hi,
Is there a way to evaluate imaxima source code in org-mode to display
the latex output inline in the org-buffer? I have found in [1] how to
evaluate maxima code, but I don't understand if and how to adopt it to
get the nice latex/pdf output. Any pointers appreciated, or just whether
it is
TeX output is a feature of Maxima. See
(info (maxima) Functions and Variables for TeX Output)
E.g.
#+name: solve-maxima
#+header: :exports results
#+begin_src maxima :results output
tex(exp(-x)/x);
#+end_src
#+RESULTS: solve-maxima
: $${{e^ {- x }}\over{x}}$$
On Thursday 21 November 2013
Hi, Dan,
Is this the message you get?
No such file: /[path]/OpenDocument export failed: FIXME?
Does the error always occur when you have my filter set, and never when
you don't?
Does it matter whether you're restricting export to subtrees?
After some more testing, I'm seeing the above error
Hi Bastien,
The patch doesn't work unfortunately. I stepped through
x-get-selection-value in w32-common-fns.el and the correct value from the
clipboard gets assigned to x-last-selected-text but then the function just
returns nil (line 120). I would say x-last-selected text needs to be used
Thanks everyone! Much appreciated. I think I can get what I want by
fiddling with these. Thomas, I'm not sure why but yours comes out with
weird indentation which makes the first line not part of the list. Eric,
yours doesn't seem to create a proper numbered list at all, but is
otherwise just
noo...@noorul.com writes:
Christopher Allan Webber cweb...@dustycloud.org writes:
Hello,
I'd like to have a habit-only agenda view, if possible, that looks a bit
like:
Morning habits
--
life: TODO Shave [ * * ** !] habit::morning:
rsi:
On Thu, Nov 21, 2013 at 11:34:55AM -0500, Dan Griswold wrote:
On Wed, Nov 20, 2013 at 4:33 PM, Christian Moe m...@christianmoe.comwrote:
Well, here's one way to get those page references, using filters:
(defun my-odt-filter-pagerefs (text backend info)
Make page references, not
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Thu, Nov 21, 2013 at 08:11:50AM +0700, Eric Abrahamsen wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20, 2013 at 09:15:43PM +, Luke Crook wrote:
Eric Abrahamsen e...@ericabrahamsen.net writes:
Emacs already has the concept of the page-delimiter (defaults to ^L),
for page-related commands. I once floated the idea of making a
page-break a full org element, that could be handled differently by
different backends.
You are not alone.
The
Nick Dokos ndo...@gmail.com writes:
Bastien b...@gnu.org writes:
Looks good, please push!
Pushed to master (I hope...) Let me know if there is a problem.
Thanks Nick. After a pull this morning, my file's local variables aren't
lost when I refresh buffer properties.
All the best,
Tom
--
Luke Crook l...@balooga.com writes:
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Luke Crook luke at balooga.com writes:
Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version.
OK. Then could you provide an ECM? I'm unable to reproduce the problem.
Regards,
Bastien b...@gnu.org writes:
Looks good, please push!
Pushed to master (I hope...) Let me know if there is a problem.
--
Nick
Hi, there,
I am wondering whether it is possible to define the starting number of
headings when exporting org-mode files.
The problem is that, I had a long Org file that I want to separate it
into several small ones, each will be exported to a HTML file. But if so,
every exported HTML will
Nicolas Goaziou n.goaz...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Updated patch.
I've been using this patch without issues for at least two week. I
haven't experienced any slowdowns over wcheck other than that
associated with the design of Flyspell (e.g.
Marvin Doyley marvin...@gmail.com writes:
Symbol's function definition is void: bibtex-beginning-of-entry
Whenever you get an error, do
M-x toggle-debug-on-error
and post the *Backtrace* buffer.
I am still surprised why (even) regulars in this list fail to do it.
Hi there,
I found the bug.
It turned out that an old copy of bibtex.el was the culprit, deleting this
fixed the problem.
Thanks again for all your help.
Cheers,
M
On Thu, Nov 21, 2013 at 10:12 AM, Marvin Doyley marvin...@gmail.com wrote:
Hi Chris,
That didn't work either.
When I did
Dear list,
I am currently very happy to use orgmode and org-reveal [0] to create slide
for my lessons about programming.
I enjoy using src block to have automatic syntax highlighting for the code
fragments.
However, I now have the joy to teach a lisp variant (Clojure) for which I
have some
(info (org) Include files)
Yujie Wen yjwen...@gmail.com writes:
Hi, there,
I am wondering whether it is possible to define the starting number of
headings when exporting org-mode files.
The problem is that, I had a long Org file that I want to separate it
into several small ones, each
On 20/11/13 17:27, Jambunathan K wrote:
Alan L Tyree alanty...@gmail.com writes:
What I mean is to enter something like \cite{mann82} in the text and
have it spit out (Mann 1982) in each and every export as well as
constructing an entry for the bibliography.
(For benefit of others)
Hi Bernard,
Org-mode uses htmlize.el [1] to fontify source code blocks. Htmlize
directly converts an Emacs buffer to HTML, so if you are exporting from
a buffer in which parenthesis are colorized, then the exported HTML
should be colorized as well. If not then this is a question for htmlize
The two examples below illustrate an odd ODT export failure that occurs in
restricted circumstances: only when the target of the link is on a
higher level of the tree than the link.
* This fails
** A subheader
This paragraph is bookmarked. target1
When I try to export this subtree to ODT
Hi Chris,
That didn't work either.
When I did
#+begin_src emacs-lisp
(bibtex-set-dialect)
#+end_src
I got the following error
Debugger entered--Lisp error: (void-function bibtex-set-dialect)
(bibtex-set-dialect)
(progn (bibtex-set-dialect))
eval((progn (bibtex-set-dialect)))
Alan L Tyree alanty...@gmail.com writes:
What I mean is to enter something like \cite{mann82} in the text and
have it spit out (Mann 1982) in each and every export as well as
constructing an entry for the bibliography.
(For benefit of others)
ox-jabref.el and JabRef can spit things out in
Yujie Wen yjwen...@gmail.com writes:
I am wondering whether it is possible to define the starting number
of headings when exporting org-mode files.
The problem is that, I had a long Org file that I want to separate
it into several small ones, each will be exported to a HTML file. But
if
Eric Schulte schulte.eric at gmail.com writes:
Org-mode uses htmlize.el [1] to fontify source code blocks. Htmlize
directly converts an Emacs buffer to HTML, so if you are exporting from
a buffer in which parenthesis are colorized, then the exported HTML
should be colorized as well.[…]
Hi,
I'd like to add a new option to the LaTeX backend from a contrib/
package so that it can be set with a #+ keyword. Is this possible? If
so how would one go about making this change. If not what's the best
way to add a new optional value to an existing backend (to be used by a
new link
Marvin Doyley marvin...@gmail.com writes:
Hi Chris,
That didn't work either.
When I did
#+begin_src emacs-lisp
(bibtex-set-dialect)
#+end_src
I got the following error
Debugger entered--Lisp error: (void-function bibtex-set-dialect)
(bibtex-set-dialect)
Try
(require
Well, as you can see with my exchange with Suvayu I got past the error. Yet
I still have a strange problem. Your solution works on a small test file,
but not on my large (~ 13k words) document. The conversion of text to
page just doesn't happen.
I do have a special style file, so I thought that
Dan Griswold writes:
Well, as you can see with my exchange with Suvayu I got past the error. Yet
I still have a strange problem. Your solution works on a small test file,
but not on my large (~ 13k words) document. The conversion of text to
page just doesn't happen.
Odd. The document I
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Luke Crook luke at balooga.com writes:
Hi Nicolas, I'm definitely using 8.2.2, as reported by org-version.
OK. Then could you provide an ECM? I'm unable to reproduce the problem.
Regards,
Hi Nicolas,
The first two work
Richard Lawrence richard.lawre...@berkeley.edu writes:
Eric Schulte schulte.e...@gmail.com writes:
Ian Barton li...@wilkesley.net writes:
On 19/11/13 01:40, Christopher W. Ryan wrote:
Not sure citational is even a word, but hopefully it conveys my meaning!
I've been using LaTeX for
On Thu, Nov 21, 2013 at 11:38 AM, Suvayu Ali fatkasuvayu+li...@gmail.comwrote:
First I would check the Output buffer. That should have more
information on why the export failed.
Thanks Suvayu. There was no Output buffer, only a few error messages in the
*Messages* buffer (and these are of
On Wed, Nov 20, 2013 at 4:33 PM, Christian Moe m...@christianmoe.comwrote:
Well, here's one way to get those page references, using filters:
(defun my-odt-filter-pagerefs (text backend info)
Make page references, not textual references in ODT export.
(when
Yujie Wen yjwen...@gmail.com writes:
Hi, Eric,
You can derive a new back-end from existing ones. Please consult org
export reference
documentationhttp://orgmode.org/worg/dev/org-export-reference.html
.
Yujie
Yes, I've done this before, however I'm hoping to modify an existing
backend.
Changing :results output to :results output latex in Rüdiger's nice
example below would probably be an improvement.
Best,
Rüdiger Sonderfeld ruedi...@c-plusplus.de writes:
TeX output is a feature of Maxima. See
(info (maxima) Functions and Variables for TeX Output)
E.g.
#+name:
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric Schulte schulte.e...@gmail.com writes:
I'd like to add a new option to the LaTeX backend from a contrib/
package so that it can be set with a #+ keyword. Is this possible? If
so how would one go about making this change. If not
Alan L Tyree alanty...@gmail.com writes:
On 20/11/13 17:27, Jambunathan K wrote:
Alan L Tyree alanty...@gmail.com writes:
What I mean is to enter something like \cite{mann82} in the text and
have it spit out (Mann 1982) in each and every export as well as
constructing an entry for the
In the mean time I just pushed up a small change to this file which
will resolve cite: links and export them correctly to LaTeX.
I just reverted my addition to org-bibtex-extras.el as it looks like
ox-bibtex.el (also in contrib) already handles cite: links on export.
Best,
--
Eric Schulte
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
In html export include todo state words in table of contents.
Would the following patch do the job?
It does for me! Thanks
Applied then.
Regards,
Hi
On 22/11/13 15:04, Eric Schulte wrote:
Alan L Tyree alanty...@gmail.com writes:
On 20/11/13 17:27, Jambunathan K wrote:
Alan L Tyree alanty...@gmail.com writes:
What I mean is to enter something like \cite{mann82} in the text and
have it spit out (Mann 1982) in each and every export as well
Eric Abrahamsen e...@ericabrahamsen.net writes:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Thu, Nov 21, 2013 at 08:11:50AM +0700, Eric Abrahamsen wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20,
49 matches
Mail list logo
