Re: [O] org-ref code
On Wednesday, 14 May 2014 at 16:35, John Kitchin wrote: [...] I wonder if you are adding another cite link later that overrides my cite link. do the other citation links export ok, e.g. autocite, citeyear, etc...? The problem is not how links are handled but the fact that implicit links, i.e. those not surrounded by [[...]], are not recognised as links on export. This applies to all citation links but not, for instance, http:. There has to be something in org that I need to set or that I have set that affects this behaviour but I just do not seem to find it. I am now bisecting my initialisation code to see if it is me setting something but I do wonder if there is something you have set to tell org to recognise implicitly defined links? In any case, would it be possible to have org-ref insert proper links, i.e. [[cite:joe-2014]], maybe as an option? I often use superscripts for citation references and a space before the superscript looks ugly! And my problem would be solved... :) thanks again, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] *text* in headlines and export to latex
On Wednesday, 14 May 2014 at 19:28, Seb Frank wrote: Yes -- but that changes it to emph (instead of alert) in beamer export. Ah, there was no mention of beamer in your original question. I cannot help then other than to suggest you embed actual LaTeX in your headline. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] org-ref code
John, I am in the process of bisecting my initialisation. Something I have set definitely stops org (whether 8.2.5c which comes with emacs 24.4.50.2 or 8.2.6-958) from recognising cite:... etc. as links. However, I have been re-building up from no initialisation bit by bit. Right from the start, I get the error I posted yesterday: --8---cut here---start-8--- Debugger entered--Lisp error: (wrong-type-argument stringp nil) re-search-forward(nil 10001 t) tex-main-file() reftex-TeX-master-file() reftex-tie-multifile-symbols() reftex-access-scan-info((16)) reftex-parse-all() (and (buffer-file-name) (file-exists-p (buffer-file-name)) (global-auto-revert-mode t) (reftex-parse-all)) org-mode-reftex-setup() run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook) apply(run-hooks (change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook)) run-mode-hooks(org-mode-hook) org-mode() set-auto-mode-0(org-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil t) find-file-noselect-1(#buffer t.org ~/s/test/t.org nil nil ~/synced/test/t.org (10095713 2055)) find-file-noselect(~/s/test/t.org nil nil t) find-file(~/s/test/t.org t) call-interactively(find-file nil nil) command-execute(find-file) --8---cut here---end---8--- This happens when I try to visit any org file *once* I have loaded org-ref the first time. It doesn't happen before org-ref is loaded. I am starting to despair, I must admit! I wonder if there is a conflict between Emacs 24.4.50 and org-ref? Or do you have some other setting for reftex that is not the default? Anyway, I have to get some work done so I will do without org-ref for the time being. I'll revisit later. thanks again for all your time, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] Using Emacs, Org-mode and R for Research Writing in Social Sciences
Am 15.05.2014 um 06:49 schrieb Vikas Rawal vikasli...@agrarianresearch.org:
I removed explicit inclusion of these packages from this document and the
instructions, because I wanted to reduce the work in terms of setting
things up.
You achieved the opposite.
Now a user *has* to enable the config file.
Otherwise it would be clear that additional packages may be needed which may
not be part of a minimal TeX Live installation.
May be I should specify the packages that are being called, so the user can
make sure those are installed or modify the config file. But I prefer the
basic set of LaTeX packages being called by default rather than being added
in every file.
This will be a problem when one of your collaborators doesn't use your config
files.
There are many packages for tabular/table environments.
Having them in the document gives a strong hint that there is something
different that may collide with the packages another user prefers. (No-one can
agree on a basic set of LaTeX packages:-)
If you keep them in the configuration file, the user has to extract the
relevant information
(setq org-latex-default-packages-alist …)
from your configuration and add it to their configuration file.
You can always supply a template file with all the relevant
+LaTeX_HEADER
definitions.
You can even have lines like
#+LaTeX_HEADER: \usepackage{tabulary} % provides column specification LCRJ
#+LaTeX_HEADER: \usepackage{threeparttable} % A table with cation and notes
#+LaTeX_HEADER: \renewcommand{\TPTminimum}{\linewidth} % configure
threeparttable
#+Latex_HEADER: %\usepackage{tgschola} % enable to use the Schola font
#+Latex_HEADER: %\usepackage{tgbonum} % enable to use the Bonum font
#+Latex_HEADER: %\usepackage{tgpagella} % enable to use the Pagella font
#+Latex_HEADER: \usepackage[urw-garamond]{mathdesign} \linespread{1.0609}
and let the user decide which to use instead of hiding this in an option which
requires modifications of the latex exporter.
(My Latex template has several pages of commented preamble. I activate only
what I need but I have everything available, including common usage examples.)
But in the end this is your decision, you know what works best for your users
and I know how to modify the configuration to suit my needs.
Axel
[O] Ragged Left in Beamer Export?
Hi,
I am trying the following:
#+BEGIN_QUOTE
Getting ragged-left text in a Beamer presentation exported from Org does not
seem as easy as I expected.
#+END_QUOTE
#+BEGIN_LaTeX
\begin{raggedleft}
From Loris' Adventures in Orgland
\end{raggedleft}
#+END_LaTeX
This seems to get exported to the latex file OK, but the text after the
quote is justified left in the final Beamer PDF.
What am I doing wrong?
Cheers,
Loris
--
This signature is currently under construction.
Re: [O] Using Emacs, Org-mode and R for Research Writing in Social Sciences
May be I should specify the packages that are being called, so the user can
make sure those are installed or modify the config file. But I prefer the
basic set of LaTeX packages being called by default rather than being added
in every file.
This will be a problem when one of your collaborators doesn't use your config
files.
There are many packages for tabular/table environments.
Having them in the document gives a strong hint that there is something
different that may collide with the packages another user prefers. (No-one
can agree on a basic set of LaTeX packages:-)
If you keep them in the configuration file, the user has to extract the
relevant information
(setq org-latex-default-packages-alist …)
from your configuration and add it to their configuration file.
You can always supply a template file with all the relevant
+LaTeX_HEADER
definitions.
You can even have lines like
#+LaTeX_HEADER: \usepackage{tabulary} % provides column specification LCRJ
#+LaTeX_HEADER: \usepackage{threeparttable} % A table with cation and notes
#+LaTeX_HEADER: \renewcommand{\TPTminimum}{\linewidth} % configure
threeparttable
#+Latex_HEADER: %\usepackage{tgschola} % enable to use the Schola font
#+Latex_HEADER: %\usepackage{tgbonum} % enable to use the Bonum font
#+Latex_HEADER: %\usepackage{tgpagella} % enable to use the Pagella font
#+Latex_HEADER: \usepackage[urw-garamond]{mathdesign} \linespread{1.0609}
This may be a better solution. We could even provide a separate file with
sample lines that need to go at the top, which can be modified if needed, to be
called in using #+INCLUDE: into a document.
Since Suvayu has offered to have a go at modifying the document for Worg, I
would wait for him to do what he thinks may be best.
Vikas
[O] Spurious elements in HTML export
Hi, Using the HTML exporter, I easily get spurious empty elements. Example: Org-mode: * Section [2014-05-15 jeu. 10:29] ** Subsection 1 [2014-05-15 jeu. 10:28] Foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar ** Subsection 2 [2014-05-15 jeu. 10:29] Foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar After C-c C-e C-s C-b h H, HTML: div id=table-of-contents h2Table of Contents/h2 div id=text-table-of-contents ul lia href=#sec-11. Subsection 1/a/li lia href=#sec-22. Subsection 2/a/li /ul /div /div div class=figure p /p /div div id=outline-container-sec-1 class=outline-2 h2 id=sec-1span class=section-number-21/span Subsection 1/h2 div class=outline-text-2 id=text-1 div class=figure p /p /div p Foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar /p /div /div div id=outline-container-sec-2 class=outline-2 h2 id=sec-2span class=section-number-22/span Subsection 2/h2 div class=outline-text-2 id=text-2 div class=figure p /p /div p Foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar foo bar /p /div /div My questions: - is this what is expected ? - why those 3 p/p ? - why are they surrounded by those divs ? I don't see the point in generating those empty p/p elements, and even less in wrapping them with figure class. If I remove the empty lines following the date/time stamps, then I get only the first of those empty blocks. However, doing this, I trigger what i think is inconsistent between the HTML and the LaTeX exporter: if there is no empty line after the date stamp, the LaTeX exporter exports the date stamp. The HTML exporter doesn't. Thanks for clarifications on this topic. -- Fabrice
[O] Tag setting mode creates two additional windows
Hello, I am trying to enter the tag setting mode by pressing C-c C-c for the following org file: #+TAGS: @work(w) @home(h) @tennisclub(t) * some test I have noticed that if the frame is large enough, when entering the tag setting mode Org will split the frame horizontally first and then will split the top window vertically. I end up with two windows with my org file and the other *Org tags* window. Is this done on purpose? Couldn’t find any information about this behavior. I am using the latest nightly build of emacsformacosx, the latest org-mode and an .emacs with only org-mode enabled. Thanks, Dima
Re: [O] Spurious elements in HTML export
Hi Fabrice, Fabrice Popineau fabrice.popin...@gmail.com writes: Using the HTML exporter, I easily get spurious empty elements. I can't reproduce this. Do you have a recipe with a minimal configuration ? Also mention your Org and Emacs version. Thanks, -- Bastien
Re: [O] Tag setting mode creates two additional windows
Hi Dmitry, Dmitry Gorbik dgor...@me.com writes: I am trying to enter the tag setting mode by pressing C-c C-c for the following org file: #+TAGS: @work(w) @home(h) @tennisclub(t) * some test I have noticed that if the frame is large enough, when entering the tag setting mode Org will split the frame horizontally first and then will split the top window vertically. I end up with two windows with my org file and the other *Org tags* window. Is this done on purpose? Nope. Couldn’t find any information about this behavior. I can't reproduce this. I am using the latest nightly build of emacsformacosx, the latest org-mode and an .emacs with only org-mode enabled. M-x org-version RET to tell us about the version -- I don't know what version comes with emacsformacosx. Maybe show us how you enable Org. This is probably a bug specific to this version, since setting tags from Org-mode does not do anything fancy with the window creation. Perhaps other emacsformacosx can try to reproduce this as well. HTH, -- Bastien
Re: [O] Bug: Activating org-mode in any buffer recenters (unrelated) selected window. [8.2.6 (release_8.2.6-6-gfc37d1 @ /home/youngfrog/sourcetrees/org-mode/lisp/)]
Hi Nicolas, I removed the call to `recenter' and to `goto-char'. Thanks for reporting this, -- Bastien
Re: [O] Abbreviating filtered tags in mode line
Hi Thomas, thanks for the patch, it looks good. We can only accept it if you sign the FSF copyright assignment here: http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt Thanks in advance for doing so, and let's commit your change when the FSF confirm your assignment (it may take one month or so.) Best, -- Bastien
Re: [O] Spurious elements in HTML export
2014-05-15 10:55 GMT+02:00 Bastien b...@gnu.org: Hi Fabrice, Fabrice Popineau fabrice.popin...@gmail.com writes: Using the HTML exporter, I easily get spurious empty elements. I can't reproduce this. Do you have a recipe with a minimal configuration ? This is already good to know! I'll try to bisect my emacs config. Recipe : the sole org fragment from my message in an org buffer, and export the subtree in an html buffer with C-c C-e C-s C-b h H Also mention your Org and Emacs version. Org: git latest (from today). Emacs 24.4 (trunk devel, under Windows, yeah I know ...). I suspect the problem might come from org-html-standalone-image-p (incorrectly finding an image for an empty paragraph) or even from org-string-nw-p. What org-string-nw-p should return on a string with the single EOL character? BTW, I wonder if org-html-standalone-image-p does actually what is documented. It is documented as returning non-nil in one of two cases: element is of type paragraph or of type link. But its code starts with: (and (eq (org-element-type paragraph) 'paragraph) ...) which seems to prevent the second case. That is certainly unrelated to my problem. Fabrice
Re: [O] Tag setting mode creates two additional windows
This is my org-mode version: Org-mode version 8.2.6 (release_8.2.6-961-g089a13 @ /Users/dgorbik/.emacs.d/org-mode/) I could reproduce this in both Emacs 24.4.5 with emacsformacosx and Emacs 24.3.1 in console. And here is the .emacs file: (add-to-list 'load-path ~/.emacs.d/org-mode/) (require 'org) Thanks, Dima On May 15, 2014, at 1:59 AM, Bastien b...@gnu.org wrote: Hi Dmitry, Dmitry Gorbik dgor...@me.com writes: I am trying to enter the tag setting mode by pressing C-c C-c for the following org file: #+TAGS: @work(w) @home(h) @tennisclub(t) * some test I have noticed that if the frame is large enough, when entering the tag setting mode Org will split the frame horizontally first and then will split the top window vertically. I end up with two windows with my org file and the other *Org tags* window. Is this done on purpose? Nope. Couldn’t find any information about this behavior. I can't reproduce this. I am using the latest nightly build of emacsformacosx, the latest org-mode and an .emacs with only org-mode enabled. M-x org-version RET to tell us about the version -- I don't know what version comes with emacsformacosx. Maybe show us how you enable Org. This is probably a bug specific to this version, since setting tags from Org-mode does not do anything fancy with the window creation. Perhaps other emacsformacosx can try to reproduce this as well. HTH, -- Bastien
Re: [O] still seeing semi-regular lockups
Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: After Nicolas made the last round of improvements to the caching mechanism I got far fewer hangs with Org, but they are still happening. Maybe once a day or so, on average, editing something in an Org buffer causes emacs to hang, and my fans to spin up, and there we are until I kill emacs. I've seen hiccups here and there, but generally, what happens is an error, not an infinite hanging. It happens often enough that I guess it's worth running emacs under some kind of debugger -- at least, I assume that's the best way of catching the bug. I'm not really sure how to go hunting, though, so if anyone had any advice in this direction, that would be great. I'd hunt for some infloop in parsing -- but cannot detail more than that, problably Nicolas could. In the meantime, is there any way of interrupting emacs so it quits whatever its doing, without having to kill it? I've played around with sending different signals using kill, just for fun, but everything I've tried either does nothing, or kills emacs altogether. I have no suggestion here either, sorry :/ -- Bastien
Re: [O] Clock-in in agenda makes some headings with links disappear
Hi Thomas, thanks for the bug report. This bug has been showing up and disappearing as this used to be quite an unstable area. But I think I fixed this for good in maint. One use that still needs careful check is when the agenda is filtered, so perhaps you can hunt things from there. Thanks, -- Bastien
Re: [O] Spurious elements in HTML export
BTW, I wonder if org-html-standalone-image-p does actually what is documented. It is documented as returning non-nil in one of two cases: element is of type paragraph or of type link. But its code starts with: (and (eq (org-element-type paragraph) 'paragraph) ...) which seems to prevent the second case. That is certainly unrelated to my problem. Sorry. I misread the code. Forget about this false interpretation. Fabrice
Re: [O] Ragged Left in Beamer Export?
On Thursday, 15 May 2014 at 10:27, Loris Bennett wrote:
Hi,
I am trying the following:
#+BEGIN_QUOTE
Getting ragged-left text in a Beamer presentation exported from Org does not
seem as easy as I expected.
#+END_QUOTE
#+BEGIN_LaTeX
\begin{raggedleft}
From Loris' Adventures in Orgland
\end{raggedleft}
#+END_LaTeX
This seems to get exported to the latex file OK, but the text after the
quote is justified left in the final Beamer PDF.
What am I doing wrong?
The ragged left only takes place when a paragraph ends so simply put
\par before the end:
#+begin_src org
,#+BEGIN_LaTeX
\begin{raggedleft}
From Loris' Adventures in Orgland
\par\end{raggedleft}
,#+END_LaTeX
#+end_src
Your code might look better this way, by the way:
#+begin_src org
,#+latex: \begin{raggedleft}
From Loris' Adventures in Orgland
,#+latex: \par\end{raddedleft}
#+end_src
as you can then use org syntax on the text elements.
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] still seeing semi-regular lockups
Bastien b...@gnu.org writes: Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: After Nicolas made the last round of improvements to the caching mechanism I got far fewer hangs with Org, but they are still happening. Maybe once a day or so, on average, editing something in an Org buffer causes emacs to hang, and my fans to spin up, and there we are until I kill emacs. I've seen hiccups here and there, but generally, what happens is an error, not an infinite hanging. It happens often enough that I guess it's worth running emacs under some kind of debugger -- at least, I assume that's the best way of catching the bug. I'm not really sure how to go hunting, though, so if anyone had any advice in this direction, that would be great. I'd hunt for some infloop in parsing -- but cannot detail more than that, problably Nicolas could. In the meantime, is there any way of interrupting emacs so it quits whatever its doing, without having to kill it? I've played around with sending different signals using kill, just for fun, but everything I've tried either does nothing, or kills emacs altogether. I have no suggestion here either, sorry :/ I have also semi-regular lockup with org-mode. I have opened a bug on debbugs and here is what Stefan told me to try to debug this: You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun rest args) (with-local-quit (apply fun args Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. I'll try to see what I can find this week end and report back. By the way, if you want to see in which part the infloop occurs, you can attach a gdb debugger to the running emacs, source the path-to-emacs-source/src/.gdbinit file and use the `xbacktrace' command. $ gdb path-to-emacs-executable emacs-pid gdb) source path-to-emacs-source/src/.gdbinit ... gdb) xbacktrace You can also use the `bt' command but it contains much more noise. -- Daimrod/Greg signature.asc Description: PGP signature
Re: [O] gnus-summary-move-article and org-store-link
Hi Esben, Esben Stien b...@esben-stien.name writes: Any way I could do this? You can use this in .gnus.el: (gnus-registry-initialize) (setq gnus-refer-article-method '(current (nnregistry))) this way, following Gnus links will find the message-id based on the registry, and you can safely move articles around. -- Bastien
Re: [O] Tag setting mode creates two additional windows
Dmitry Gorbik dgor...@me.com writes: This is my org-mode version: Thanks -- maybe try to define large enough from your previous report, so that other emacsformacosx users have more infos on how to reproduce the bug. -- Bastien
Re: [O] Spurious elements in HTML export
Let's first try to safely reproduce the problem before pointing fingers on some functions -- bisecting your config will surely help! -- Bastien
Re: [O] still seeing semi-regular lockups
Daimrod daim...@gmail.com writes: I'll try to see what I can find this week end and report back. Great -- thanks for the guidance! -- Bastien
Re: [O] Is it possible to name tables programmatically?
Joon Kwon joon.k...@ens-lyon.org writes: Is there a way? Hélas, no, sorry. -- Bastien
[O] bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Daimrod daim...@gmail.com writes: I wonder if it is because `org-adaptive-fill-function' doesn't mix well with `adaptive-wrap-prefix-mode'... (Nicolas has been doing some rewrite for filling functions in the master branch, maybe it's worth checking whether this bug affects the master branch too, not just the Emacs-24 version of Org.) -- Bastien
Re: [O] Tag setting mode creates two additional windows
I have found interesting email threads related to exactly same issue. But it looks like it was fixed since then, not sure why it reproduces for me again: http://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00443.html http://article.gmane.org/gmane.emacs.orgmode/34802 Dima On May 15, 2014, at 2:49 AM, Dmitry Gorbik dgor...@me.com wrote: It reproduces in console for me as well. Here is a screenshot to demonstrate the frame size and the issue: Screen Shot 2014-05-15 at 2.18.52 AM.png Thanks, Dima On May 15, 2014, at 2:44 AM, Bastien b...@gnu.org wrote: Dmitry Gorbik dgor...@me.com writes: This is my org-mode version: Thanks -- maybe try to define large enough from your previous report, so that other emacsformacosx users have more infos on how to reproduce the bug. -- Bastien
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Hi, Achim Gratz strom...@nexgo.de writes: That breaks the tests for Octave and Maxima; since you're intentionally not keeping backwards compatibility here this should be fixed in the tests, I'd think. Agreed. Aaron, can you take care of this? Also, I'd think you should be using user-error instead of error to generate the messages. Agreed too. -- Bastien
Re: [O] org-review-schedule
Hi Alan, Alan Schmitt alan.schm...@polytechnique.org writes: I need to learn how to do this. In the meantime, I've put the code on github: https://github.com/brabalan/org-review Since the big secret plan to move contrib/ files to Org ELPA is not yet to happen, and since it may take time for you to add org-review to GNU ELPA, I simply suggest you add this file to contrib/. It will get exposure when we announce it for the upcoming 8.3 release. Up to you! Thanks, -- Bastien
Re: [O] org-ref code
Hi John, John Kitchin jkitc...@andrew.cmu.edu writes: I would prefer to keep org-ref where it is until it stabilizes. I hope it will stabilize before Org 8.3 so that we can add org-ref to contrib/ and give it exposure in the release notes. Thanks, -- Bastien
Re: [O] Schedule for the World Cup in org format
Hi Rafael, Rafael rvf0...@gmail.com writes: Following https://github.com/djcb/org-euro2012 as a template, I have produced a schedule for the upcoming world cup in org format, which can be obtained from https://github.com/rvf0068/org-wc2014 This is great, thanks! We should build a community website where people can contribute various Org calendars and users subscribe to them, as these calendar are so much easier to produce than others. -- Bastien
[O] bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Bastien b...@gnu.org writes: Daimrod daim...@gmail.com writes: I wonder if it is because `org-adaptive-fill-function' doesn't mix well with `adaptive-wrap-prefix-mode'... (Nicolas has been doing some rewrite for filling functions in the master branch, maybe it's worth checking whether this bug affects the master branch too, not just the Emacs-24 version of Org.) I am using the master branch, I didn't check if it also happens in the Emacs-24 version of Org. Sorry, I should have mentioned that in my initial report. :( -- Daimrod/Greg
Re: [O] Bug report (the hard way!)
Hi Dave, Dave Pawson dave.paw...@gmail.com writes: Section 4.2 Internal links intimates (not clearly IMHO) that the target for a link in same file is marked as target yet a bad link offers to create one as * #target It is either wrong or unclear? regards DaveP dave.paw...@gmail.com The manual says this in Org 8.2.6: - one item - targetanother item Here we refer to item [[target]]. and hitting C-c C-o when point is on [[target]] works fine here. As far as I remember, this is also the case in Org 7.9.3f. -- Bastien
Re: [O] Bug report (the hard way!)
On 15 May 2014 11:15, Bastien b...@gnu.org wrote: Hi Dave, Dave Pawson dave.paw...@gmail.com writes: Section 4.2 Internal links intimates (not clearly IMHO) that the target for a link in same file is marked as target yet a bad link offers to create one as * #target It is either wrong or unclear? regards DaveP dave.paw...@gmail.com The manual says this in Org 8.2.6: - one item - targetanother item Here we refer to item [[target]]. and hitting C-c C-o when point is on [[target]] works fine here. As far as I remember, this is also the case in Org 7.9.3f. I've recently upgraded to 8, I'll try again. The report was with 7.9, It was quite confusing though. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk
Re: [O] Ragged Left in Beamer Export?
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Thursday, 15 May 2014 at 10:27, Loris Bennett wrote:
Hi,
I am trying the following:
#+BEGIN_QUOTE
Getting ragged-left text in a Beamer presentation exported from Org does not
seem as easy as I expected.
#+END_QUOTE
#+BEGIN_LaTeX
\begin{raggedleft}
From Loris' Adventures in Orgland
\end{raggedleft}
#+END_LaTeX
This seems to get exported to the latex file OK, but the text after the
quote is justified left in the final Beamer PDF.
What am I doing wrong?
The ragged left only takes place when a paragraph ends so simply put
\par before the end:
#+begin_src org
,#+BEGIN_LaTeX
\begin{raggedleft}
From Loris' Adventures in Orgland
\par\end{raggedleft}
,#+END_LaTeX
#+end_src
Your code might look better this way, by the way:
#+begin_src org
,#+latex: \begin{raggedleft}
From Loris' Adventures in Orgland
,#+latex: \par\end{raddedleft}
#+end_src
as you can then use org syntax on the text elements.
HTH,
eric
Thanks, Eric, that did the trick.
The hint regarding
#+LaTeX:
is also useful - I had forgotten about that possibility and your point
about being able to use Org syntax on the text is a good one.
I tried searching for some relevant documentation on #+LaTeX:, but
failed to find anything other that the Easy Template (Google's
verbatim search seems to use a different definition of verbatim to
mine). Maybe it should be mentioned in the manual somewhere in the
chapter Embedded LaTeX.
Cheers,
Loris
--
This signature is currently under construction.
Re: [O] Bug: Literal Example does not work [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Hi Hisao, KURODA Hisao kur...@msi.co.jp writes: A very simple literal example below seems not work with M-x org-export-as-html. #+BEGIN_SRC emacs-lisp (save-excursion (goto-char (point-min))) #+END_SRC The HTML output is class=example not emacs-lisp as follows. pre class=example(save-excursion (goto-char (point-min))) /pre It also reproducible on 8.2.6. I can't reproduce this with 8.2.6. In Org 8, `org-export-as-html' does not exist anymore, you need to try `org-html-export-as-html'. Can you test again, making sure you are using Org 8 ? Test this with M-x org-version RET Thanks, -- Bastien
[O] bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Daimrod daim...@gmail.com writes: Bastien b...@gnu.org writes: Daimrod daim...@gmail.com writes: I wonder if it is because `org-adaptive-fill-function' doesn't mix well with `adaptive-wrap-prefix-mode'... (Nicolas has been doing some rewrite for filling functions in the master branch, maybe it's worth checking whether this bug affects the master branch too, not just the Emacs-24 version of Org.) I am using the master branch, I didn't check if it also happens in the Emacs-24 version of Org. Okay, then it would be good to know if it happens in the Org version included in the Emacs pretest, as this is the one that needs heavy testing right now :) -- Bastien
Re: [O] Archive subtree with parent structure
Am 18.04.2014 13:36, schrieb Bastien: Hi Florian, Florian Lindner mailingli...@xgm.de writes: is it possible to org-archive-subtree a subtree and keep the entire parent structure? e.g. * A ** AA ** AB ** AC AB will be archived to: * A ** AB No, but each subtree can contain an :ARCHIVE: property that will help you come close to this. For example: * A :PROPERTIES: :ARCHIVE: basement_archive::* A :END ** AA ** AB ** AC then C-c $ on AA AB and AC will archive them under the * A subtree of the basement_archive file. Hey, sorry for that reply after a long time. Problem is that this kind of archivement does not fit my workflow. I tend to archive small pieces of a project's subtree long before I'm ready to archive the entire project. This way I build (want to build) an archived mirror of the project's subtree bit by bit. Do you know what is the appropriate place to file such an feature as a whishlist item? M-x org-submit-bug-report RET ? Thx, Florian
Re: [O] still seeing semi-regular lockups
Daimrod daim...@gmail.com writes: Bastien b...@gnu.org writes: Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: After Nicolas made the last round of improvements to the caching mechanism I got far fewer hangs with Org, but they are still happening. Maybe once a day or so, on average, editing something in an Org buffer causes emacs to hang, and my fans to spin up, and there we are until I kill emacs. [...] I have also semi-regular lockup with org-mode. I have opened a bug on debbugs and here is what Stefan told me to try to debug this: You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun rest args) (with-local-quit (apply fun args Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. I'll try to see what I can find this week end and report back. By the way, if you want to see in which part the infloop occurs, you can attach a gdb debugger to the running emacs, source the path-to-emacs-source/src/.gdbinit file and use the `xbacktrace' command. $ gdb path-to-emacs-executable emacs-pid gdb) source path-to-emacs-source/src/.gdbinit ... gdb) xbacktrace You can also use the `bt' command but it contains much more noise. Thanks! This is the sort of thing I assumed I'd have to do, and it's good to have an actual recipe. If you're on it, I might take the lazy option and spectate for now... :)
Re: [O] still seeing semi-regular lockups
Eric Abrahamsen e...@ericabrahamsen.net writes: Daimrod daim...@gmail.com writes: Bastien b...@gnu.org writes: Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: After Nicolas made the last round of improvements to the caching mechanism I got far fewer hangs with Org, but they are still happening. Maybe once a day or so, on average, editing something in an Org buffer causes emacs to hang, and my fans to spin up, and there we are until I kill emacs. [...] I have also semi-regular lockup with org-mode. I have opened a bug on debbugs and here is what Stefan told me to try to debug this: You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun rest args) (with-local-quit (apply fun args Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. I'll try to see what I can find this week end and report back. By the way, if you want to see in which part the infloop occurs, you can attach a gdb debugger to the running emacs, source the path-to-emacs-source/src/.gdbinit file and use the `xbacktrace' command. $ gdb path-to-emacs-executable emacs-pid gdb) source path-to-emacs-source/src/.gdbinit ... gdb) xbacktrace You can also use the `bt' command but it contains much more noise. Thanks! This is the sort of thing I assumed I'd have to do, and it's good to have an actual recipe. If you're on it, I might take the lazy option and spectate for now... :) No problem, but could you attach gdb during a lockup, source .gdbitinit and use the `xbacktrace' command to see if the lockup happens at the same place? -- Daimrod/Greg
Re: [O] Tag setting mode creates two additional windows
Dmitry Gorbik dgor...@me.com writes: I have found interesting email threads related to exactly same issue. But it looks like it was fixed since then, not sure why it reproduces for me again: http://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00443.html http://article.gmane.org/gmane.emacs.orgmode/34802 Can you try the attached patch against the master's HEAD? diff --git a/lisp/org.el b/lisp/org.el index 2661686..06c2b56 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -14877,7 +14877,7 @@ Returns the new tags string, or nil to not change the current settings. (if expert (set-buffer (get-buffer-create *Org tags*)) (delete-other-windows) - (split-window-vertically) + (set-window-buffer (split-window-vertically) *Org tags*) (org-switch-to-buffer-other-window (get-buffer-create *Org tags*))) (erase-buffer) (org-set-local 'org-done-keywords done-keywords) -- Bastien
Re: [O] still seeing semi-regular lockups
Daimrod daim...@gmail.com writes: Eric Abrahamsen e...@ericabrahamsen.net writes: Daimrod daim...@gmail.com writes: Bastien b...@gnu.org writes: Hi Eric, Eric Abrahamsen e...@ericabrahamsen.net writes: After Nicolas made the last round of improvements to the caching mechanism I got far fewer hangs with Org, but they are still happening. Maybe once a day or so, on average, editing something in an Org buffer causes emacs to hang, and my fans to spin up, and there we are until I kill emacs. [...] I have also semi-regular lockup with org-mode. I have opened a bug on debbugs and here is what Stefan told me to try to debug this: You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun rest args) (with-local-quit (apply fun args Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. I'll try to see what I can find this week end and report back. By the way, if you want to see in which part the infloop occurs, you can attach a gdb debugger to the running emacs, source the path-to-emacs-source/src/.gdbinit file and use the `xbacktrace' command. $ gdb path-to-emacs-executable emacs-pid gdb) source path-to-emacs-source/src/.gdbinit ... gdb) xbacktrace You can also use the `bt' command but it contains much more noise. Thanks! This is the sort of thing I assumed I'd have to do, and it's good to have an actual recipe. If you're on it, I might take the lazy option and spectate for now... :) No problem, but could you attach gdb during a lockup, source .gdbitinit and use the `xbacktrace' command to see if the lockup happens at the same place? Most definitely. Saving the instructions now...
Re: [O] [PATCH] org.el (org-offer-links-in-entry): Remove code duplication
Hi Albert, Achim Gratz strom...@nexgo.de writes: Albert Krewinkel writes: Done. As an aside: I did sign the copyright assignment papers to be able to contrivute to Gnus, but that probably wouldn't help much, as Org is a different project. Is that correct? If you assigned copyright just for Gnus, then you'd have to do it again for Org. I've just checked and yes, Albert's assignment is made for EMACS/GNUS. So I'm afraid Albert you have to go through the process of assigning your copyright again for Emacs :/ You can use the form here: http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt HTH, -- Bastien
Re: [O] Tag setting mode creates two additional windows
This one didn’t work, I modified it like this to make it work: tags-split-windows.patch Description: Binary data Dima On May 15, 2014, at 3:37 AM, Bastien b...@gnu.org wrote: Dmitry Gorbik dgor...@me.com writes: I have found interesting email threads related to exactly same issue. But it looks like it was fixed since then, not sure why it reproduces for me again: http://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00443.html http://article.gmane.org/gmane.emacs.orgmode/34802 Can you try the attached patch against the master's HEAD? split-window.patch -- Bastien
Re: [O] Spurious elements in HTML export
Hello, Fabrice Popineau fabrice.popin...@gmail.com writes: Using the HTML exporter, I easily get spurious empty elements. Example: Org-mode: * Section [2014-05-15 jeu. 10:29] ** Subsection 1 [2014-05-15 jeu. 10:28] [...] div id=table-of-contents h2Table of Contents/h2 div id=text-table-of-contents ul lia href=#sec-11. Subsection 1/a/li lia href=#sec-22. Subsection 2/a/li /ul /div /div div class=figure p /p /div This should be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou
Re: [O] Using Emacs, Org-mode and R for Research Writing in Social Sciences
Am 15.05.2014 um 06:49 schrieb Vikas Rawal vikasli...@agrarianresearch.org: I think starter-kit is a good choice. You will be up and running in no time. Just put it in place. Well, time moves differently around here. Since I use Aquamacs it took me over a day to get it working. A google sear gave me: The starter kit is designed to be used with GNU Emacs. Version 24 or later is required, and the current released version (24.3) is recommended. It will not work with Aquamacs without modification. Seriously? That it? No Here are the necessary modifications? It seems to work now. I write a separate article to describe what I did. Axel
[O] emacs24-starter-kit and Aquamacs 3.0
I never wanted to learn Emacs. But hearing about Org-mode got me interested, so far I like what I see. The next step is exporting from Org-mode. There was a post by Vikas Rawal, Using Emacs, Org-mode and R for Research Writing in Social Sciences which looked like a simple step by step manual. I failed at the first step: Installing starter-kit. Asking Google for help I got: The starter kit is designed to be used with GNU Emacs. Version 24 or later is required, and the current released version (24.3) is recommended. It will not work with Aquamacs without modification. Here are the modifications I did: * The init.el file GNUEmacs uses .emacs.d/init.el as the init file. Everything works fine with GNUEmacs. Aquamacs uses ~/Library/Preferences/Aquamacs Emacs/Preferences.el and ~/.emacs. With this information it was easy: just link ~/.emacs.d/init.el to ~/.emacs. Now starter-kit loads * There is no place like $HOME (or rather starter-kit-dir) Starter-kit remembers the directory of the init.el file: (setq starter-kit-dir ,(file-name-directory (or load-file-name (buffer-file-name Sadly this is now ~ and not ~/emacs.d. I solved this with brute force, replacing the command with (setq starter-kit-dir /Users/axel/.emacs.d/) Now it seems to work. There is probably a more elegant way to add a /.emacs.d to the path when the editor is Aquamacs, but I have to learn some elisp for that. Or a way to tell Aquamacs to use a different init file. Any suggestions are appreciated. Axel
Re: [O] [PATCH] Add author and title to exported PDF properties
Marcel van der Boom wrote:
On wo 14-mei-2014 14:48
Nicolas Goaziou n.goaz...@gmail.com wrote:
[...]
How do they differ from, say 'subject'?
subject, which refers to :description property, only contains a
single string, no Org syntax. OTOH, TITLE and AUTHOR keywords have
their contents parsed and, as such, can contain parsed objects. E.g.,
| keyword | value | property value |
|-+-+|
| DESCRIPTION | some *text* | some *text* |
| TITLE | some *text* | (some (bold ... text)) |
See also `org-element-document-properties'.
Thanks, this section made the click for me.
I think I sort of assumed that 'LateX codes' in author and title were
just going to be dropped by the hyperref package itself to produce the
properties.
For example, a complex author property which I sometimes have:
#+AUTHOR:\href{mailto:m...@myself.com}{My name} --
\href{mailto:collea...@gmail.com}{My colleague}
Best regards,
Seb
--
Sebastien Vauban
[O] bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Bastien b...@altern.org writes: Daimrod daim...@gmail.com writes: Bastien b...@gnu.org writes: Daimrod daim...@gmail.com writes: I wonder if it is because `org-adaptive-fill-function' doesn't mix well with `adaptive-wrap-prefix-mode'... (Nicolas has been doing some rewrite for filling functions in the master branch, maybe it's worth checking whether this bug affects the master branch too, not just the Emacs-24 version of Org.) I am using the master branch, I didn't check if it also happens in the Emacs-24 version of Org. Okay, then it would be good to know if it happens in the Org version included in the Emacs pretest, as this is the one that needs heavy testing right now :) So far I haven't manage to reproduce it with the Org bundled with the Emacs pretest. I'll continue to use it for a while and see what happens. Best, -- Daimrod/Greg
Re: [O] Spurious elements in HTML export
This should be fixed. Thank you for reporting it. Thanks for fixing it (and so quickly). I have seen what went wrong in org-html-standalone-image-p albeit I don't know what triggered it in my setup. It has been an opportunity to remove a huge pile of old stuff from my Org config :-) Best regards, Fabrice
Re: [O] *text* in headlines and export to latex
Seb Frank wrote: On Wed, May 14, 2014 at 7:19 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote: On Wednesday, 14 May 2014 at 18:00, Seb Frank wrote: Latex export converts *text* to \textbf -- this doesn't work well for headlines that get turned into section titles as these appear to be bold by default. Is there a way to change this to \emph in headlines that get converted to (sub)sections? Silly question but: can you not simply use /text/ instead in the headlines? Mind you, I think that bold + emph is not pretty... but that's a personal taste issue! Yes -- but that changes it to emph (instead of alert) in beamer export. As a side note, as both \alert and \textbf do exist in Beamer, I do think *text* should never be translated to \alert. That's because of that different translation between the two backends that you see that problem only in one backend. Best regards, Seb -- Sebastien Vauban
Re: [O] emacs24-starter-kit and Aquamacs 3.0
On 2014-05-15 07:59, Axel Kielhorn wrote: I never wanted to learn Emacs. There is probably a more elegant way to add a /.emacs.d to the path when the editor is Aquamacs, but I have to learn some elisp for that. Or a way to tell Aquamacs to use a different init file. Any suggestions are appreciated. Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. IMHO, there is no longer any compelling reason to use aquamacs. It was started at a time when the core gnu emacs did not support os x, this is no longer the case. The nextstep build of emacs runs as a native app, supports anti-aliased fonts, etc. Personally, i find that the keyboard rebinding in aquamacs just make it it harder to use/learn emacs, as all the documentation, etc, is based on the standard, cross-platform bindings. Once you learn them, you will be able to use emacs on any platform -- mac, windows, unix. Also, your configuration will be portable across all the same platforms. rick
Re: [O] org-ref code
That is pretty strange. I used this to get a minimally working install of org-ref. I deleted ~/.emacs.d, and ran emacs -q and then executed this code block. * installation You need the dash package. Use these repositories, and install dash. #+BEGIN_SRC emacs-lisp (require 'package) (setq package-archives '((org . http://orgmode.org/elpa/;) (gnu . http://elpa.gnu.org/packages/;) (melpa . http://melpa.milkbox.net/packages/;) )) (package-refresh-contents) (package-install 'dash) (org-babel-load-file ~/Dropbox/kitchingroup/jmax/org-ref.org) ;; this function is normally run as a hook. we run it manually here to ;; get started. (org-mode-reftex-setup) #+END_SRC #+RESULTS: : org-ref-insert-cite-link After that, it works like I expect. Your error seems to be coming from reftex. I wonder if you have something set that is making it look for a TeX-master or something, which eventually results in nil, which is failing here: re-search-forward(nil 10001 t). Or maybe you need to set something to turn that off. Perhaps some default changed? John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, May 15, 2014 at 4:17 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: John, I am in the process of bisecting my initialisation. Something I have set definitely stops org (whether 8.2.5c which comes with emacs 24.4.50.2 or 8.2.6-958) from recognising cite:... etc. as links. However, I have been re-building up from no initialisation bit by bit. Right from the start, I get the error I posted yesterday: --8---cut here---start-8--- Debugger entered--Lisp error: (wrong-type-argument stringp nil) re-search-forward(nil 10001 t) tex-main-file() reftex-TeX-master-file() reftex-tie-multifile-symbols() reftex-access-scan-info((16)) reftex-parse-all() (and (buffer-file-name) (file-exists-p (buffer-file-name)) (global-auto-revert-mode t) (reftex-parse-all)) org-mode-reftex-setup() run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook) apply(run-hooks (change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook)) run-mode-hooks(org-mode-hook) org-mode() set-auto-mode-0(org-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil t) find-file-noselect-1(#buffer t.org ~/s/test/t.org nil nil ~/synced/test/t.org (10095713 2055)) find-file-noselect(~/s/test/t.org nil nil t) find-file(~/s/test/t.org t) call-interactively(find-file nil nil) command-execute(find-file) --8---cut here---end---8--- This happens when I try to visit any org file *once* I have loaded org-ref the first time. It doesn't happen before org-ref is loaded. I am starting to despair, I must admit! I wonder if there is a conflict between Emacs 24.4.50 and org-ref? Or do you have some other setting for reftex that is not the default? Anyway, I have to get some work done so I will do without org-ref for the time being. I'll revisit later. thanks again for all your time, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] org-ref code
On Thursday, 15 May 2014 at 09:05, John Kitchin wrote: [...] Your error seems to be coming from reftex. I wonder if you have something set that is making it look for a TeX-master or something, which eventually results in nil, which is failing here: re-search-forward(nil 10001 t). Or maybe you need to set something to turn that off. Perhaps some default changed? Yes, that is my feeling as well but I am totally unable to find what may be causing it. I haven't yet looked to see whether there have been any changes in reftex itself in the latest emacs. I continue to investigate! thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] org-ref code
I can see the desire to avoid the space with a superscript, but that is a latex specific formatting issue, that is probably taken care of with some package. In the packages we use (usually natmove), citations are moved to the correct side of punctuation, for example, so we always put them on the left where the logically make sense (eg because it is grouped in the sentence being cited. the latex package moves the superscripts to the right. I think it also works on spaces In org-mode some text[[cite:yoo-2014-theor-analy]] is also ugly ;) and harder to read. That gives us the best of both worlds (org and latex) I don't think I have done anything to make the naked links work. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, May 15, 2014 at 2:58 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: On Wednesday, 14 May 2014 at 16:35, John Kitchin wrote: [...] I wonder if you are adding another cite link later that overrides my cite link. do the other citation links export ok, e.g. autocite, citeyear, etc...? The problem is not how links are handled but the fact that implicit links, i.e. those not surrounded by [[...]], are not recognised as links on export. This applies to all citation links but not, for instance, http:. There has to be something in org that I need to set or that I have set that affects this behaviour but I just do not seem to find it. I am now bisecting my initialisation code to see if it is me setting something but I do wonder if there is something you have set to tell org to recognise implicitly defined links? In any case, would it be possible to have org-ref insert proper links, i.e. [[cite:joe-2014]], maybe as an option? I often use superscripts for citation references and a space before the superscript looks ugly! And my problem would be solved... :) thanks again, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] org-ref code
On Thursday, 15 May 2014 at 09:05, John Kitchin wrote: Your error seems to be coming from reftex. Well, it seems that if you are going to use reftex in emacs 24.4.x, you need to define some variables. I put the following in your org-mode-reftex-setup function: (setq-local tex-start-of-header %\\*\\*start of header) (setq-local tex-end-of-header %\\*\\*end of header) immediately after loading reftex and things work better (I haven't checked whether everything works yet). The problem is that tex-mode assumes that it is active in a mode that has been derived from tex-mode (such as latex-mode or plain-tex-mode) and those modes define the variables above. Org-mode doesn't! This may be a change in tex-mode for the latest emacs versions? I cannot verify this. Am I correct in believing that you are using emacs 24.3? -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] Abbreviating filtered tags in mode line
Hi, Bastien, Thanks -- I've got the assignment form and will send it in. Best regards, Thomas
[O] inserting new heading
Hi everybody! I recently found the joy of using Emacs and Org-mode. I'm using it to organize a lot of stuff and just now I notice something that bothers me a lot. Whenever I am inserting a new heading, via Ctrl-return or alt-return , the new heading skips a line. Is this the default behavior? If yes, is there a variable that I can change somewhere? Thanks a lot! my specs: MB air GNU Emacs 24.3.50.1 (x86_64-apple-darwin13.0.0, NS apple-appkit-1265.00)-- org-mode 8.2.5c Ralph Bacolod,MT(AMT),MLS(ASCP)
Re: [O] org-ref code
yes, I am using emacs 24.3. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, May 15, 2014 at 9:30 AM, Eric S Fraga e.fr...@ucl.ac.uk wrote: On Thursday, 15 May 2014 at 09:05, John Kitchin wrote: Your error seems to be coming from reftex. Well, it seems that if you are going to use reftex in emacs 24.4.x, you need to define some variables. I put the following in your org-mode-reftex-setup function: (setq-local tex-start-of-header %\\*\\*start of header) (setq-local tex-end-of-header %\\*\\*end of header) immediately after loading reftex and things work better (I haven't checked whether everything works yet). The problem is that tex-mode assumes that it is active in a mode that has been derived from tex-mode (such as latex-mode or plain-tex-mode) and those modes define the variables above. Org-mode doesn't! This may be a change in tex-mode for the latest emacs versions? I cannot verify this. Am I correct in believing that you are using emacs 24.3? -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] emacs24-starter-kit and Aquamacs 3.0
Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I recommend a homebrew-based install of emacs. I like the version available from railwaycat/emacsmacport tap (https://github.com/railwaycat/emacs-mac-port). Vikas
Re: [O] org-ref code
On Thursday, 15 May 2014 at 10:19, John Kitchin wrote: yes, I am using emacs 24.3. Can you have a look at tex-mode.el and see if the variables: (setq-local tex-start-of-header %\\*\\*start of header) (setq-local tex-end-of-header %\\*\\*end of header) are (a) used and (b) defined somewhere other than in the definitions of derived modes? By the way, I have no idea how these are being used but maybe they could be adapted to org syntax (# start of header, say)? In any case, some good news! I have tracked down the problem with citations not being picked up by the exporter. If I load ox-latex *before* org-ref, cite: and other new links are not picked up. If I load org-ref before ox-latex, everything seems to work fine. It would seem that ox-latex is defining the links that are valid and this is not being updated subsequently? I've not tracked this down yet but maybe Nicolas should have a look? We're getting there! thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
Re: [O] emacs24-starter-kit and Aquamacs 3.0
Am 15.05.2014 um 15:01 schrieb Rick Frankel r...@rickster.com: Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I should have asked earlier, but everyone was suggesting Aquamacs. Since I'm starting from scratch I don't mind switching and it will be easier to share my configuration with the Unix machine I sometimes telnet to. Thanks for the suggestion. Axel
Re: [O] beamer columns and printout
I've solved the first problem, using a something similar to what has been
suggested here:
http://stackoverflow.com/questions/10295177/is-there-an-equivalent-of-org-modes-b-ignoreheading-for-non-beamer-documents
The solution is to define
#+begin_src emacs-lisp
(defun sf-ignore-headline (contents backend info)
Ignore headlines with tags `ignoreheading or `columns'.
(when (and (org-export-derived-backend-p backend 'latex 'html 'ascii)
(string-match \\`.*\\(ignoreheading\\|columns\\).*\n
(downcase contents)))
(replace-match nil nil contents)))
(add-to-list 'org-export-filter-headline-functions 'sf-ignore-headline)
#+end_src emacs-lisp
This removes headlines with tags columns (or ignoreheading, for that
matter), which is what I wanted. Any ideas for the second problem? I.e.,
how to get rid of the BMCOL in export to latex/html/etc. while keeping the
headlines/content?
On Wed, May 14, 2014 at 5:51 PM, Seb Frank sebsfr...@gmail.com wrote:
Hi,
I'm interested in using org-mode to generate beamer slides and an
article-like printout (using the article class, usepackage{beamerarticle}
and latex export) from the same source, and I am running into two problems
with the export to article when there are multiple columns.
1.) I often use an empty headline with B_columns tag to allow me to
specify top alignment. E.g.,
#+begin_src org
* :B_columns:
:PROPERTIES:
:BEAMER_env: columns
:BEAMER_opt: T
:END:
** Column 1 :BMCOL:
:PROPERTIES:
:BEAMER_col: 0.35
:END:
** Column 2:BMCOL:
:PROPERTIES:
:BEAMER_COL: 0.6
:END:
#+end_src org
In the printout, this yields an ugly empty section with a number if num:t.
Is there a better way to pass [T] to the title-less columns environment, or
(less preferably) a way to specify a title for the section without it
appearing on the beamer slide?
2.) In the above example, the B_columns and BMCOL tags get exported to the
latex file for the printout (with an error because the underscore is used
outside of math mode). Can these be suppressed?
Thanks,
Seb
[O] Centering graphics in LaTeX export
Hi,
Here's a small patch that enables centering graphics in LaTeX exports
(as it already exists for tables).
Currently, the only way to center images is by adding a caption (which
is not always needed) or by adding #+begin_center / #+end_center around
images (but it must be done for every image as we cannot define
a default behavior for centering images).
Thanks to this patch:
- an image can be centered by adding the ':center t' attribute in
a '#+ATTR_LATEX' directive (as for tables);
- default centering of images can be achieved by setting the
'org-latex-images-centered' variable to t.
Could you please apply this patch?
Thanks.
Best regards,
Francesco Pizzolante
---
C:\Users\fpz\Documents\home\.emacs.d\elpa\org-plus-contrib-20140512\ox-latex.el
2014-05-15 17:09:08.0 +0200
+++ C:\Users\fpz\Documents\home\.emacs.d\elpa\org-plus-contrib-20140505 -
Copy\ox-latex.el 2014-05-15 17:11:25.0 +0200
@@ -401,12 +401,17 @@
Default option for images.
:group 'org-export-latex
:version 24.4
:package-version '(Org . 8.0)
:type 'string)
+(defcustom org-latex-images-centered t
+ When non-nil, images are exported in a center environment.
+ :group 'org-export-latex
+ :type 'boolean)
+
(defcustom org-latex-image-default-width .9\\linewidth
Default width for images.
This value will not be used if a height is provided.
:group 'org-export-latex
:version 24.4
:package-version '(Org . 8.0)
@@ -1710,12 +1715,15 @@
((eq float 'figure)
(format [%s] org-latex-default-figure-position))
(t
(comment-include (if (plist-get attr :comment-include) % ))
;; It is possible to specify width and height in the
;; ATTR_LATEX line, and also via default variables.
+(centerp (if (plist-member attr :center)
+ (plist-get attr :center)
+ org-latex-images-centered))
(width (cond ((plist-get attr :width))
((plist-get attr :height) )
((eq float 'wrap) 0.48\\textwidth)
(t org-latex-image-default-width)))
(height (cond ((plist-get attr :height))
((or (plist-get attr :width)
@@ -1749,18 +1757,21 @@
;; - include the image with \includegraphics.
(when (org-string-nw-p width)
(setq options (concat options ,width= width)))
(when (org-string-nw-p height)
(setq options (concat options ,height= height)))
(setq image-code
- (format \\includegraphics%s{%s}
+ (format %s\\includegraphics%s{%s}%s
+(if centerp {\\centering\n )
(cond ((not (org-string-nw-p options)) )
((= (aref options 0) ?,)
(format [%s](substring options 1)))
(t (format [%s] options)))
- path))
+ path
+(if centerp \\par}\n )
+))
(when (equal filetype svg)
(setq image-code (replace-regexp-in-string ^includegraphics
\\includesvg
image-code
nil t))
(setq image-code (replace-regexp-in-string \\.svg}
Re: [O] Centering graphics in LaTeX export
On Thu, May 15, 2014 at 10:25 AM, Francesco Pizzolante f...@missioncriticalit.com wrote: Hi, Here's a small patch that enables centering graphics in LaTeX exports (as it already exists for tables). Currently, the only way to center images is by adding a caption (which is not always needed) or by adding #+begin_center / #+end_center around images (but it must be done for every image as we cannot define a default behavior for centering images). Thanks to this patch: - an image can be centered by adding the ':center t' attribute in a '#+ATTR_LATEX' directive (as for tables); - default centering of images can be achieved by setting the 'org-latex-images-centered' variable to t. Sounds cool to me! I'm already always using an #+attr_latex line for setting the width; being able to center it with the same line would be pretty cool. That said, I'm guessing someone's going to point you in this direction for the patch submission itself (I guess that someone is me in this case). - http://orgmode.org/worg/org-contribute.html#sec-4 [patch snipped] Best regards, John
Re: [O] org-ref code
On Thursday, 15 May 2014 at 15:31, Eric S Fraga wrote: [...] If I load ox-latex *before* org-ref, cite: and other new links are not picked up. If I load org-ref before ox-latex, everything seems to work fine. It would seem that ox-latex is defining the links that are valid and this is not being updated subsequently? I've not tracked this down yet but maybe Nicolas should have a look? Following up on myself: org-ref has to be loaded *before* ox.el which means also before any ox-*.el files. I thought the problem was that the link types regexps used by org were not being updated but invoking org-make-link-regexps after loading org-ref had no effect. Oh well. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-958-g7c8559-git
[O] Issue when using cache property set to yes
Hi, I'm having issues using the cache property set to yes. The problem is the following (please see http://screencast.com/t/8sIMfL0YHAj): I've added a few directives (center, width, caption) in order to customize the output of my R code block. As soon as I change my code block and execute it, everything that was between the code block and the 'results' line gets lost (losing all customizations and breaking the centering). Thanks a lot for your help. Regards, Francesco
Re: [O] emacs24-starter-kit and Aquamacs 3.0
On 2014-05-15 10:31, Vikas Rawal wrote: Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I recommend a homebrew-based install of emacs. I like the version available from railwaycat/emacsmacport tap (https://github.com/railwaycat/emacs-mac-port [1]). Not familiar w/ emacsports, will take a look at it this weekend. My problem w/ the homebrew install (and i'm a homebrew fan) is that i prefer the all-in-one (--with-ns) package and not having the app spread around /usr/local in unix fashion the way the homebrew install works. Personally, i used homebrew to install the build dependencies (autoconf, automake, imagemagick, etc) and the git mirror of the emacs trunk (http://git.sv.gnu.org/emacs.git) YMMV. rick
Re: [O] emacs24-starter-kit and Aquamacs 3.0
On Thu, 15 May 2014 10:28:13 -0400, Axel Kielhorn org-m...@axelkielhorn.de wrote: I should have asked earlier, but everyone was suggesting Aquamacs. Since I'm starting from scratch I don't mind switching and it will be easier to share my configuration with the Unix machine I sometimes telnet to. Yes. Because emacs predates all the modern consumer keyboard interfaces by a decade or more, and because vanilla emacs is available for just about every platform except possibly Babbage's original Analytical Engine, it really makes sense to avoid grandly localised versions of emacs. In my view Aquamacs is the cure for which there is no disease. To gild refined gold; to paint the lily. --Shakespeare', King John.
Re: [O] emacs24-starter-kit and Aquamacs 3.0
Aloha all, Macports has an emacs-app that bundles all the files in /Applications/MacPorts/Emacs.app/ We use this at work and find it convenient. All the best, Tom Rick Frankel r...@rickster.com writes: On 2014-05-15 10:31, Vikas Rawal wrote: Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I recommend a homebrew-based install of emacs. I like the version available from railwaycat/emacsmacport tap (https://github.com/railwaycat/emacs-mac-port [1]). Not familiar w/ emacsports, will take a look at it this weekend. My problem w/ the homebrew install (and i'm a homebrew fan) is that i prefer the all-in-one (--with-ns) package and not having the app spread around /usr/local in unix fashion the way the homebrew install works. Personally, i used homebrew to install the build dependencies (autoconf, automake, imagemagick, etc) and the git mirror of the emacs trunk (http://git.sv.gnu.org/emacs.git) YMMV. rick -- Thomas S. Dye http://www.tsdye.com
Re: [O] [Latex Export] Influence placement of \maketitle command
On 2014-05-14 21:01 Nick Dokos wrote:
Alexander Baier alexander.ba...@mailbox.org writes:
[...]
Is there a way for me to influence the placement of =\maketitle= and
thus be able to order those commands the right way?
If \institute can be placed in the preamble, then using #+LATEX_HEADER
instead of #+LATEX is probably the way to go.
If it has to be in the document body, one way to do it is to redefine
the variable org-latex-title-command in a file-local-variable section
added to the end of your file:
# Local Variables:
# org-latex-title-command: \\institute{Foo}\\maketitle
# End:
See
(info (emacs) File variables)
While we are on the topic of placing stuff: I also need to insert
citations for which I use bibtex. I use #+LATEX:
\bibliographystyle{plain} and #+LATEX: \bibliography{literatur} under my
last header for the bibliography to be placed at the very end.
I find this to be a somewhat lacking solution as moving my last subtree
would move my bibliography, too.
Is there a way to make it make it appear at the bottom of my document no
matter what?
Regards,
--
Alexander Baier
Re: [O] emacs24-starter-kit and Aquamacs 3.0
This thread is rather off-topic for this list. Isn’t it? But since we have a hugely tolerant community, it is perhaps okay. I have a homebrew install, with a symbolic link to /Applications/Emacs.app. Works just fine. Vikas On 15-May-2014, at 8:51 pm, Thomas S. Dye t...@tsdye.com wrote: Aloha all, Macports has an emacs-app that bundles all the files in /Applications/MacPorts/Emacs.app/ We use this at work and find it convenient. All the best, Tom Rick Frankel r...@rickster.com writes: On 2014-05-15 10:31, Vikas Rawal wrote: Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I recommend a homebrew-based install of emacs. I like the version available from railwaycat/emacsmacport tap (https://github.com/railwaycat/emacs-mac-port [1]). Not familiar w/ emacsports, will take a look at it this weekend. My problem w/ the homebrew install (and i'm a homebrew fan) is that i prefer the all-in-one (--with-ns) package and not having the app spread around /usr/local in unix fashion the way the homebrew install works. Personally, i used homebrew to install the build dependencies (autoconf, automake, imagemagick, etc) and the git mirror of the emacs trunk (http://git.sv.gnu.org/emacs.git) YMMV. rick -- Thomas S. Dye http://www.tsdye.com
Re: [O] [Latex Export] Influence placement of \maketitle command
On Thursday, 15 May 2014 at 21:02, Alexander Baier wrote:
[...]
While we are on the topic of placing stuff: I also need to insert
citations for which I use bibtex. I use #+LATEX:
\bibliographystyle{plain} and #+LATEX: \bibliography{literatur} under my
last header for the bibliography to be placed at the very end.
I find this to be a somewhat lacking solution as moving my last subtree
would move my bibliography, too.
Is there a way to make it make it appear at the bottom of my document no
matter what?
I put it under its own heading with an :ignoreheading: tag and use the
filter that was posted on this list (today in fact):
#+begin_src org
,* references :ignoreheading:
\bibliographystyle{acm}
\bibliography{papers.bib}
#+end_src
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-966-g6cdf1b
Re: [O] [Latex Export] Influence placement of \maketitle command
On 2014-05-15 21:57 Eric S Fraga wrote: I put it under its own heading with an :ignoreheading: tag and use the filter that was posted on this list (today in fact): I can't find the filter you are referring to. I guess it is in the org-ref thread? I did not follow that thread as org-ref seems to be a somewhat full-fledged solution including a lot of things I do not need. I looked through the thread but wasn't lucky to find said filter. Could you kindly post a link? (if that's not to much to ask) Thanks, -- Alexander Baier
Re: [O] *text* in headlines and export to latex
Is this customizable at all? I've seen some old threads where people used @ for alert (and a hack to replace it with something else if the \alert command didn't exist, see http://lists.gnu.org/archive/html/emacs-orgmode/2010-01/msg00614.html and http://lists.gnu.org/archive/html/emacs-orgmode/2010-01/msg00754.html ), but the solutions mentioned there don't seem to work with the current version of org. On 5/15/14, Sebastien Vauban sva-n...@mygooglest.com wrote: Seb Frank wrote: On Wed, May 14, 2014 at 7:19 PM, Eric S Fraga e.fr...@ucl.ac.uk wrote: On Wednesday, 14 May 2014 at 18:00, Seb Frank wrote: Latex export converts *text* to \textbf -- this doesn't work well for headlines that get turned into section titles as these appear to be bold by default. Is there a way to change this to \emph in headlines that get converted to (sub)sections? Silly question but: can you not simply use /text/ instead in the headlines? Mind you, I think that bold + emph is not pretty... but that's a personal taste issue! Yes -- but that changes it to emph (instead of alert) in beamer export. As a side note, as both \alert and \textbf do exist in Beamer, I do think *text* should never be translated to \alert. That's because of that different translation between the two backends that you see that problem only in one backend. Best regards, Seb -- Sebastien Vauban
Re: [O] emacs24-starter-kit and Aquamacs 3.0
brew linkapps does this for you. Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi gret...@acm.org | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Thu, May 15, 2014 at 2:41 PM, Vikas Rawal vikasli...@agrarianresearch.org wrote: This thread is rather off-topic for this list. Isn’t it? But since we have a hugely tolerant community, it is perhaps okay. I have a homebrew install, with a symbolic link to /Applications/Emacs.app. Works just fine. Vikas On 15-May-2014, at 8:51 pm, Thomas S. Dye t...@tsdye.com wrote: Aloha all, Macports has an emacs-app that bundles all the files in /Applications/MacPorts/Emacs.app/ We use this at work and find it convenient. All the best, Tom Rick Frankel r...@rickster.com writes: On 2014-05-15 10:31, Vikas Rawal wrote: Probably not the answer you want, but as a long-time mac and emacs user, my suggestion would be to use the vanilla os x version of emacs. The nextstep build of emacs runs as a native app, You are suggesting to a Mac user to build his own Emacs? Do you know what that takes? About 10 minutes :-) I just realized that it is even possible to download it prebuilt. I recommend a homebrew-based install of emacs. I like the version available from railwaycat/emacsmacport tap (https://github.com/railwaycat/emacs-mac-port [1]). Not familiar w/ emacsports, will take a look at it this weekend. My problem w/ the homebrew install (and i'm a homebrew fan) is that i prefer the all-in-one (--with-ns) package and not having the app spread around /usr/local in unix fashion the way the homebrew install works. Personally, i used homebrew to install the build dependencies (autoconf, automake, imagemagick, etc) and the git mirror of the emacs trunk (http://git.sv.gnu.org/emacs.git) YMMV. rick -- Thomas S. Dye http://www.tsdye.com
[O] [PATCH] Empty inline tasks in latex export
If the body if the inline task is empty, org-latex-inlinetask writes nil in the exported document. This patch skips including contents (and the bar above it) if it's nil. Michael 0001-Handle-empty-tasks-without-printing-nil-in-org-latex.patch Description: Binary data
Re: [O] Clock-in in agenda makes some headings with links disappear
Hi, Bastien, Here is a recipe for what might be another manifestation of this bug. I'm using the maint branch: Org-mode version 8.2.6 (release_8.2.6-21-g3b9419 @ /src/org-mode/lisp/). Files `setup.el' and `test-case.org' are attached. The directory added to the load path in `setup.el' will probably need to be customized. Steps: 1. Run Emacs: `emacs -Q -l setup.el'. 2. Open the agenda: `M-x org-agenda RET a'. 3. Add a tag filter: `/ TAB foo RET'. 4. Move point to the agenda line containing the TODO item: `C-s TODO RET'. 5. Move point to the end of the line with `C-e'. It does apparently move to the end of the line. However, `C-x =' reports that it is in column 0. I expected it to be in column 108 or 109. 6. Try to move point to the beginning of the line with `C-a'. It appears to move one column to the left. I expected it to move to the left edge of the window. `C-x =' says it is in column 108. 7. Try again to move to the beginning of line with `C-a'. This works. 8. Clock in with `I'. Parts of the line change color but in column 0 `C-u C-x =' does not list any face. I expected the whole line to be highlighted with face `org-agenda-clocking'. 9. Now try to go to the item in the source Org file: `TAB'. I see this error: `Command not allowed in this line'. Best, Thomas setup.el Description: application/emacs-lisp * TODO Buckle my shoe :foo: SCHEDULED: 2014-05-15 Thu +1d :PROPERTIES: :STYLE:habit :END: * TODO Open the door SCHEDULED: 2014-05-15 Thu +1d :PROPERTIES: :STYLE:habit :END:
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Hi Achim, 2014ko maiatzak 14an, Achim Gratz-ek idatzi zuen: That breaks the tests for Octave and Maxima; since you're intentionally not keeping backwards compatibility here this should be fixed in the tests, I'd think. Fixed. (It actually required changes to the code, not the tests, since my commit made org-babel-graphical-output-file stricter). Also, I'd think you should be using user-error instead of error to generate the messages. Good catch (especially since I recently pushed a patch changing some errors to user-errors *blush*). Fixed. Thanks, -- Aaron Ecay
[O] export to org, header args disappear
I have code blocks such as #+BEGIN_SRC emacs-lisp :tangle no ... #+END_SRC and when I export the file to org, it becomes #+BEGIN_SRC emacs-lisp ... #+END_SRC Is there an option to include the header args on export? Thank you, Brady
Re: [O] [Latex Export] Influence placement of \maketitle command
Alexander Baier alexander.ba...@mailbox.org writes: On 2014-05-15 21:57 Eric S Fraga wrote: I put it under its own heading with an :ignoreheading: tag and use the filter that was posted on this list (today in fact): I can't find the filter you are referring to. I guess it is in the org-ref thread? I did not follow that thread as org-ref seems to be a somewhat full-fledged solution including a lot of things I do not need. I looked through the thread but wasn't lucky to find said filter. Could you kindly post a link? (if that's not to much to ask) I don't have a link, but I have the following in an example file (which afaik still works fine): --8---cut here---start-8--- #+LATEX_CLASS: article #+include: ch1.org #+include: ch2.org :minlevel 1 #+include: ch3.org :minlevel 1 #+include: ch4.org :minlevel 1 #+include: ch5.org :minlevel 1 #+include: bib.org * Code :noexport: Suvayu's filter to get rid of :ignoreheading: tagged headlines - used in bib.org #+BEGIN_SRC emacs-lisp :results silent (defun sa-ignore-headline (contents backend info) Ignore headlines with tag `ignoreheading'. (when (and (org-export-derived-backend-p backend 'latex 'html 'ascii) (string-match \\`.*ignoreheading.*\n (downcase contents))) (replace-match nil nil contents))) (add-to-list 'org-export-filter-headline-functions 'sa-ignore-headline) #+END_SRC --8---cut here---end---8--- Using #+include also largely resolves your original concern I think and is invaluable for larger files. HTH, -- Nick
