I have no idea if it relates to what you describe with cask and
dependencies, but I had the same error and found several old threads
stating that it's caused by installing org when it's already initialized.
I solved it by Emacs -q and reinstalling from elpa. If you search for the
old threads
Hello List,
I just converted my init file to an init.org to load with babel. I
prefer to view the source blocks with font lock
(org-src-fontify-natively). My problem is that certain parts of the
file don't show the fontification.
I had a lot of trouble narrowing down my init to provide a good
The MWE (with native fontification - t) looks ok for me,
Thanks for taking time to check this. I should note that if I find a new
file (test.org) and yank the MWE, it is fontified correctly, but if I save
and kill the buffer and then find the file again, that is when the problem
occurs. In
Hi List,
I only became aware of literate programming through org and have been
looking for a chance to try it out. I need to write a small command
line utility that parses through a plain text log file and performs
some operations, which I think is a reasonably simple use case for me
to try out
On Thu, Jul 10, 2014 at 6:28 PM, Thorsten Jolitz tjol...@gmail.com wrote:
When I call M-: (outorg-convert-org-to-outshine) on this Org-mode buffer:
Thanks for this suggestion. It seems outorg/outshine are not distributed
with org and must be added separately? I have to watch the size of bites I
Is it possible to configure the exporter to stop and throw an error for a
bad link?
I found this old thread
http://comments.gmane.org/gmane.emacs.orgmode/55912 with a patch to make
the format configurable, but I'd rather receive an explicit warning.
Thanks,
Jake
I have a lengthy command customization that I want to include in LaTeX
export. Since it must appear in the preamble,
#+BEGIN_LATEX
...
#+END_LATEX
didn't work. I had to prepend
#+LATEX_HEADER:
to each line in order to achieve my result.
I found C-h v org-format-latex-header RET:
The document
On Sun, Jul 27, 2014 at 10:08 PM, Ken Mankoff mank...@gmail.com wrote:
Hi Jacob,
#+LATEX_HEADER: does work on export (when else would it work?)
Agreed. If I said otherwise it was a mistake.
2) From Aaron Ecay, put your header in a #+BEGIN_SRC latex section, and
then run a bit of lisp to
This keeps coming up, and while the answers are there if you search in the
right place or ask the list, I wonder if there is a better way.
Would it be feasible to include some sort of test function in the elpa
version of org that checks for the correct installation conditions and
throws an error
On Sun, Jul 27, 2014 at 7:27 AM, Bastien b...@gnu.org wrote:
Hi Jacob,
Jacob Gerlach jacobgerl...@gmail.com writes:
Is it possible to configure the exporter to stop and throw an error
for a bad link?
No. But what is really a bad link? Is it bad because it cannot be
exported
I am making heavy use of latex strikeout for a report I'm preparing in org
mode. I defined a macro for the necessary latex snippet, but the argument
gets truncated on export.
MWE:
* Section
{{{stk(The argument for this macro is several lines long. It seems
that after a certain length, the
Ah, of course. Right under my nose, but since I knew I only had one
argument, I didn't even think about it.
Thanks for the quick reply.
On Sun, Sep 21, 2014 at 9:40 PM, Thomas S. Dye t...@tsdye.com wrote:
Aloha Jacob,
Jacob Gerlach jacobgerl...@gmail.com writes:
I am making heavy use
After writing a detailed report in org-mode and submitting it via
latex/pdf, I've found out that for the next version of the report, I am
required to use track changes in MS Word.
I thought my best way to approximate this is to submit two versions: one
with removed text in strikeout and new text
While I expect that there's no code overlap with macro expansion, I asked
about similar stop on unresolved content behavior with respect to links
here: http://article.gmane.org/gmane.emacs.orgmode/90010/
That discussion died off so I thought I'd bring up the topic again here.
Would it be
Hi list,
I'm having trouble with LaTeX export of a table that uses some footnotes.
It seems that export by default uses combinations of \footnotemark inside
the table and \footnotetext after the table.
This gets me in to trouble when the table is pushed to the next page - the
footnotes are left
On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles j.cubizol...@free.fr
wrote:
Bracket links (like link) create a \texttt{} \hypertarget{} pair
instead of a \label{} \ref{} pair in the latex file. Should I go with
explicit \label{} \ref{} in the org file ?
The \texttt{} is probably because
On Wed, Nov 5, 2014 at 9:11 AM, Sebastien Vauban sva-n...@mygooglest.com
wrote:
Jacob Gerlach wrote:
On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles wrote:
Bracket links (like link) create a \texttt{} \hypertarget{} pair
instead of a \label{} \ref{} pair in the latex file. Should I go
Hello list,
I'm starting writing my thesis, for which I hope to remain in org-mode
rather than regular LaTeX.
I am working on adapting a thesis LaTeX template into org-mode. The
template is set up with a main.tex having several individual files
(chapters, appendices, etc) \include'd.
I believe
(pdf) export to fail if it includes a link
that is out of scope. Nevertheless, I may come back to this and adjust
the behavior if I end up having problems with export time.
On Thu, Nov 27, 2014 at 2:51 AM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote:
On Wednesday, 26 Nov 2014 at 19:00, Jacob
Hi List,
I am using a custom Latex class that requires some code between
\begin{document} and \maketitle.
It seems from looking at ox-latex.el that there is nothing between document
start and title command available for me to customize.
I suppose I could customize the title command to include
On Wed Feb 11 2015 at 4:01:47 PM Rasmus ras...@gmx.us wrote:
Maybe something like AfterPreamble, AfterEndPreamble, AtEndPreamble etc.
from etoolbox?
Ah, a Latex solution to an Org problem. I was looking for a final filter
and didn't realize it, but used your approach before I saw Chuck's
names?
Regards,
Jake
[1] http://permalink.gmane.org/gmane.emacs.orgmode/91935
From f1166d30ccabdb208b0263d87fd9366fa9a2f325 Mon Sep 17 00:00:00 2001
From: Jacob Gerlach jacobgerl...@gmail.com
Date: Wed, 18 Mar 2015 09:58:00 -0400
Subject: [PATCH] Add support to link to named elements
* lisp
On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote:
Hi
I got an error as follow when I tried to export:
,
| org-babel-exp process R at line 5495...
| Evaluation of this R code-block is disabled.
| user-error: Unable to resolve link *uLELFit
`
I thought OK -
On Sat, Mar 21, 2015 at 7:34 PM, Alexis flexibe...@gmail.com wrote:
On 2015-03-21T01:59:07+1100, Richard Lawrence
richard.lawre...@berkeley.edu said:
RL I am not sure if this counts as a bug or not, so someone else
RL should still address this question. Maybe this is the desired
RL
org-show-context-detail may also be relevant:
org-show-context-detail is a variable defined in `org.el'.
Its value is ((isearch . lineage)
(bookmark-jump . lineage)
(default . ancestors))
Documentation:
Alist between context and visibility span when revealing a location.
Some actions may
be
`user-error' instead of `error'.
OK.
Updated fuzzy link patch attached.
Regards,
Jake
[1] http://thread.gmane.org/gmane.emacs.orgmode/96017
From a9221500b721a501f7b7f05519dfc0d6f30f23d0 Mon Sep 17 00:00:00 2001
From: Jacob Gerlach jacobgerl...@gmail.com
Date: Wed, 11 Mar 2015 22:39:11 -0400
Subject
Hi List,
I'd like to re-raise the issue discussed here
http://comments.gmane.org/gmane.emacs.orgmode/79902. In short, storing
and inserting an internal link to a headline containing spaces using
org-store-link and org-insert-link causes export to fail because the space
is hexified into %20.
It
On Mon, Mar 9, 2015 at 10:38 AM, Leo Ufimtsev lufim...@redhat.com wrote:
On the side, if of any help:
I generally use ID's for linking to headings.
The benefit is that headings can be re-named safley and links still work.
A great suggestion. I wasn't aware of the feature, and renaming safety
On Tue, Mar 10, 2015 at 3:47 PM, Jacob Gerlach jacobgerl...@gmail.com wrote:
After finally getting this function to work, I discovered that I had
the same problem as when I used org-id: the link description causes
exported latex references to use the headline text instead of the
\label
Hi List,
I'm trying to write a patch and getting test failures from `make test'. The
backtrace on the command line is hard for me to parse.
If I try running ert interactively by:
M-x load-file org-test.el
M-x load-file test-ox.el
M-x ert RET applicable/test
It reports that the test passes.
Do
for this?
On Mon, Mar 9, 2015 at 4:50 PM, Jacob Gerlach jacobgerl...@gmail.com wrote:
When exploring this, I found the function org-id-store-link. This
seemed like what I wanted - it creates a custom ID if one doesn't
exist, but it doesn't actually store a link (or at least, it wasn't
available when I
On Tue, Mar 10, 2015 at 12:12 PM, John Kitchin jkitc...@andrew.cmu.edu wrote:
As far as I know you have only two options to use refs to a headline in
Latex export.
1) Use a CUSTOM_ID property on a heading and then use [[#your-custom-id]] as
your link. You have to put relevant text in like:
provide a similar patch for
org-export-resolve-id-link.
Example, foo.org:
[[id:points-nowhere]]
[[id:this-one-too][also bad]]
Exports (latex) to:
\url{foo.org}
\href{foo.org}{also bad}
Regards,
Jake
From 20f84420a84997fc0e15df5af2e65b3cfde87ac1 Mon Sep 17 00:00:00 2001
From: Jacob Gerlach
On Wed, Mar 11, 2015 at 10:17 AM, Nicolas Goaziou
m...@nicolasgoaziou.fr wrote:
This is where I don't follow you. You can insert links without
description, using `org-insert-link'. What makes you think you cannot?
I thought that I had tested `(org-insert-link nil nil )' and found
that a
Hi,
On Wed, Mar 11, 2015 at 9:41 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
I'm not sure to understand the problem you're trying to solve. Would you
mind giving a simple example and motivation?
(Did I break the thread by adding [PATCH] to the subject? Apologies
if so, original thread was
On Sun, Mar 29, 2015 at 4:05 PM, Kyle Meyer k...@kyleam.com wrote:
With org-use-speed-commands set to t, this could be C-c C-p p p.
Well, this is much better. Should have thought to check the info, of
course there's already something like this built in...
On Sun, Mar 29, 2015 at 4:09 PM, John
On Fri, Mar 27, 2015 at 6:53 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
:ignoreheading: is a feature implemented in ox-beamer.el only. This is
not a common feature for all back-ends.
IIUC, this question is about performance of the filter shown in the
OP, not about the built in feature in
Hi List,
I often find myself wanting to move up by several headings:
C-c C-p, C-c C-p, C-c C-p...
(I don't usually know ahead of time how many I want to move, so I
can't use a numeric prefix arg)
I like how `set-mark-command' works with non-nil `set-mark-repeat-pop'
to avoid the need to repeat
On Mon, Mar 23, 2015 at 8:45 AM, Rainer M Krug rai...@krugs.de wrote:
First I must say it makes sense to give the error message, although I
was quite surprised.
But the message should contain a string one can easily search for. And I
guess the most used search function is C-s I think the
Hi List,
I want to include a literal underscore in LaTeX export, like FOO_BAR. Right
now I get:
FOO$_{\text{BAR}}$
Contrary to this stackexchange question
http://stackoverflow.com/a/12753930/3371623, if I try to escape the
underscore with a backslash, I get:
FOO$\backslash$$_{\text{BAR}}
I've
On Tue, Mar 17, 2015 at 6:38 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
(re unresolved ID links)
See e0b19dedb99d3c01199a159a2da8f9aa4adb2f6f
Updated fuzzy link patch attached.
Applied (with minor tweaks). Thank you.
Thanks for the changes.
I had some issues using the error messages to
Hello,
A link in a caption:
#+CAPTION: [[link]]
Initially receives org-link face when I type it. After some action (moving
to the next line or saving the buffer), it is redrawn with org-block face.
In neither case does [[ and ]] receive the invisibility attribute typically
given to links.
In
Hello,
--
#+OPTIONS: ':t
\begin{myenvironment}
Foo
\end{myenvironment}
--
Exports Foo rather than ``foo''. Is this expected?
I tried this instead:
--
#+Latex:\begin{myenvironment}
Foo
On Mon, Apr 27, 2015 at 4:29 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
No, it is a genuine bug from parser. This should be fixed in
eb77fed33fa0306ebed2224f7895b688320847b2.
Confirmed that it is fixed. Thank you.
Regards,
Jake
Hello,
Is it required by org syntax to separate short captions from body text?
In the following example:
* ECM
Some text that introduces this table.
#+CAPTION[Short caption]:
#+CAPTION: Longer caption
| Foo |
Latex export
Hello,
Latex export explicitly specifies the footnote number when using
\footnotetext for a footnote in a table:
---
| One[fn:1] |
* Footnotes
[fn:1] Footnote in the table
---
becomes:
---
Hello,
I thought I had successfully used this variable, but after restarting
emacs, I can no longer reproduce the documented behavior.
Given the following org file:
--
#+BEGIN_SRC sh :exports code
echo Hello
#+END_SRC
# Local Variables:
# org-latex-listings: t
#
Hello,
On Sun, May 24, 2015 at 3:43 PM, Charles C. Berry ccbe...@ucsd.edu wrote:
Currently, :wrap allows this:
#+begin_src emacs-lisp :wrap src latex :wrap my-verbatim :exports results
...
This is sufficient for my use case. Thanks for the tip.
A special block :raw parameter, as Rasmus
Hello,
I want to use a one of several custom environments for some babel
results using, for example, :wrap myverbatim as a header argument.
(Since I have several possible environments, I think I need to use
:wrap rather than, say, replacing verbatim using an export filter).
However, since this
Hello,
I'd like to export a source block and it's results together in one latex
environment. I came up with a solution using the final filter below.
Is there a better way?
Thanks,
Jake
#+BEGIN_SRC emacs-lisp :exports none :results silent
(defun combine-verb-final-filter (s backend info)
Hello,
On Tue, May 19, 2015 at 11:29 AM, Rasmus ras...@gmx.us wrote:
If I explicitly eval:
(org-babel-do-load-languages 'org-babel-load-languages '((sh . t)))
(setq org-latex-custom-lang-environments '((sh myverbatim))
org-latex-listings t)
And export
#+BEGIN_SRC sh
51 matches
Mail list logo
