[O] ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Dear all, I have started using ox-koma-letter from the contrib directory. Very nice. Thanks Nicolas, Alan, Viktor, and Rasmus! Everything works well so far except for one minor niggle: I would like to introduce, sometimes, LaTeX specific inline directives in #+ lines. E.g. for LaTeX export, I would use @@latex:\\@@ to get a line break in a title or author entry. I had expected the same to work with ox-koma-letter given that it is a latex /derived/ backend and does work in normal text, just not in #+ lines. I guess the processing of #+ lines is handled directly by ox-koma-letter. Would it be possible to extend @@...@@ processing to those lines? Or am I doing something silly? Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-1216-gb856f6
[O] helm-bibtex questions
Hi Titus I have been exploring helm-bibtex a bit today and have some questions. btw is this the preferred way to make requests/ask questions or is github preferred? in any case i was wondering a few things: 1. is it possible to have custom sorting? i want all views to sort by Author, year, month 2. i would really like a way to have stored smart groups (like the jabref dynamic groups if your aware of that). that is for example create a group that auto selects all publications i have (by my first/last name) and shows the count (in numbers) of these publications. Another example is a group to keep track of all the papers im working on or invloved with by matching keyword author and prep/*other key word 3.is it possible to ass an option to auto generate a bibkey for a selected citation based on user criteria such as author(date)short-title? thx so much in advance, you and john have given me confidence to finally dive into the whole latex/bibteX world best Z
Re: [O] Links, exporter
2015-06-17 12:42 GMT+02:00 Nicolas Goaziou m...@nicolasgoaziou.fr: Hello, Fabrice Popineau fabrice.popin...@gmail.com writes: If I try to export the Second Blog entry subtree by C-C C-e C-s C-b h H, I get a user-error because the exporter can't resolve the link which points outside of the exported subtree. Is this expected? Yes, unresolved links/footnotes/whatever throw errors instead of leaving broken links. Ok. I was surprised because months ago, it went unnotified. It makes sense, even if it is pretty restrictive. Errors could have been postponed to html/latex processing but that wouldn't help either to fix them. Thanks. Best regards,
[O] issues with publishing to LaTeX using #INCLUDE
Hi,
when publishing a project (to LaTeX) where each file has a #INCLUDE: of
the same file, some files get mixed up on export to LaTeX, but _only_
the stuff from the #INCLUDE gets mixed up.
Below is an excerpt of a correct export, one of a mixed up export and
the corresponding part from the #INCLUDEd file.
Currently I don't have the slightest idea what to do about this.
Any advice is highly appreciated.
Thank you very much for your help.
Best regards
Robert
A correct export looks like:
#+begin_src latex
\newcommand{\mySubtitle}{}
\newcommand{\myProducer}{org-mode / pdflatex}
\newcommand{\myTitle}{Common Software}
\newcommand{\myAuthor}{Robert Klein}
\newcommand{\myDate}{}
\newcommand{\myCreator}{Emacs 24.5.1 (Org mode 8.3beta)}
\newcommand{\myKeywords}{}
\newcommand{\mySubject}{}
\usepackage{scrhack}
% standard font is Linux Libertine, but may want to have different
% tt font. Scale is for 10pt, probably also Ok for others.
%\usepackage[ttscale=.875]{libertine} % scale by roklein
\usepackage[osf]{libertine} % standardfont Linux Libertine
\usepackage[libertine]{newtxmath}
\renewcommand*\oldstylenums[1]{{\fontfamily{fxlj}\selectfont #1}}
\usepackage[scaled=0.9,zerostyle=c]{newtxtt} % TX typewriter, scale ok by
roklein
% have to load ams packages before symbol packages, so some things aren't
% already defined. (amsmath doesn't cope)
\usepackage{amstext} % text in a math display
\usepackage[rgb,svgnames,table]{xcolor} % enable color, also for tables
\usepackage[most]{tcolorbox}
\usepackage{overpic} % put LaTeX or grid over graphics
\usepackage{colortbl} % colored tables
\usepackage{tabu} % enhanced tables using above packages
\usepackage{booktabs} % beautiful table formatting
\usepackage{tikz}
\usetikzlibrary{matrix,arrows,decorations.pathmorphing}
\usepackage{paralist}
\usepackage{xfrac} % nice fractions $\sfrac{1}{2}$
\usepackage{calc} % infix notation arithmetic
\usepackage{ifthen}% if...then for LaTeX
\usepackage{alltt} % like verbatim but \, {, and } work
\usepackage[a4paper]{geometry}
\usepackage{relsize} % relative font sizing (\smaller)
\lstset{
basicstyle=\ttfamily,
frame=single,
% frame=leftline,
backgroundcolor=\color{Gainsboro},
% spacing normal, wie in verbatim:
columns=fullflexible,
keepspaces=true,
% Umlaute
inputencoding=utf8,
extendedchars=true,
literate={Ä}{{\A}}1 {ä}{{\a}}1 {Ö}{{\O}}1 {ö}{{\o}}1 {Ü}{{\U}}1
{ü}{{\u}}1 {ß}{{\ss}}1,
}
...
#+end_src
For some other files, however the export looks like:
#+begin_src latex
\newcommand{\mySubtitle}{}
\newcommand{\myProducer}{org-mode / pdflatex}
\newcommand{\myTitle}{Mathematical Software}
\newcommand{\myAuthor}{Robert Klein}
\newcommand{\myDate}{}
\newcommand{\myCreator}{Emacs 24.5.1 (Org mode 8.3beta)}
\usepackage{scrhack}
% standard font is Linux Libertine, but may want to have different
% tt font. Scale is for 10pt, probably also Ok for others.
% tt font. Scale is for 10pt, probably also Ok for others.
%\usepackage[ttscale=.875]{libertine} % scale by roklein
\usepackage[osf]{libertine} % standardfont Linux Libertine
\usepackage[libertine]{newtxmath}
\renewcommand*\oldstylenums[1]{{\fontfamily{fxlj}\selectfont #1}}
\usepackage[scaled=0.9,zerostyle=c]{newtxtt} % TX typewriter, scale ok by
roklein
% already defined. (amsmath doesn't cope)
% already defined. (amsmath doesn't cope)
\usepackage{amstext} % text in a math display
\usepackage[rgb,svgnames,table]{xcolor} % enable color, also for tables
\usepackage[rgb,svgnames,table]{xcolor} % enable color, also for tables
\usepackage[most]{tcolorbox}
\usepackage[most]{tcolorbox}
\usepackage{overpic} % put LaTeX or grid over graphics
\usepackage{colortbl} % colored tables
\usepackage{tabu} % enhanced tables using above packages
\usepackage{tabu} % enhanced tables using above packages
\usepackage{booktabs} % beautiful table formatting
\usetikzlibrary{matrix,arrows,decorations.pathmorphing}
\usetikzlibrary{matrix,arrows,decorations.pathmorphing}
\usepackage{paralist}
\usepackage{xfrac} % nice fractions $\sfrac{1}{2}$
\usepackage{xfrac} % nice fractions $\sfrac{1}{2}$
\usepackage{calc} % infix notation arithmetic
\usepackage{ifthen}% if...then for LaTeX
\usepackage{ifthen}% if...then for LaTeX
\usepackage{alltt} % like verbatim but \, {, and } work
\usepackage{alltt} % like verbatim but \, {, and } work
\usepackage[a4paper]{geometry}
\usepackage{relsize} % relative font sizing (\smaller)
\usepackage{relsize} % relative font
[O] Emacs/ESS/org freezes/hangs on big data/ RAM(~256GB) processes when run in org/babel
Hi all im not sure if this is absolutely the correct forum to raise this and if not would be also happy to get input on where to persue this issue. i recently dived into using orgmode, ESS, Babel etc to run code and im really love it. The problem i have (and im not sure if its a org,Emacs or ess issue) is that emacs sometimes (and mostly when dealing with R processes involving HUGE databases) will just hang/freeze. I do alot of modeling work that involves using huge datasets and run process intensive R processes (such as complex mixed models, Gamms etc). in R studio all works well yet when i use the orgmode eval on R code blocks it works well for small simple process but 90% of the time when dealing with complex models and bug data (up to 256GB) it will just freeze emacs/ess. sometimes i can C-c or C-g it and other times i need to physically kill emacs. here is an example of such process that hangs lmer run the lmer part regressing stage 2 pred Vs mean pm #+BEGIN_SRC R :session Rorg :results none m2.smooth = lme(pred.m2 ~ meanPM25,random = list(aodid= ~1 + meanPM25),control=lmeControl(opt = optim), data= mod2 ) #correlate to see everything from mod2 and the mpm works mod2[, pred.t31 := predict(m2.smooth)] mod2[, resid := residuals(m2.smooth)] print(summary(lm(pred.m2~pred.t31,data=mod2))$r.squared) #+END_SRC i usually issue org-babel-execute-subtree to eval several subsections under a main header. again i dont know if its an org mode isse perse but would love to hear from people that have experience using R/org with big data/RAM and maybe point me to where to raise these issues best Z
Re: [O] Emacs/ESS/org freezes/hangs on big data/ RAM(~256GB) processes when run in org/babel
On 17 June 2015, Xebar Saram wrote: I do alot of modeling work that involves using huge datasets and run process intensive R processes (such as complex mixed models, Gamms etc). in R studio all works well yet when i use the orgmode eval on R code blocks it works well for small simple process but 90% of the time when dealing with complex models and bug data (up to 256GB) it will just freeze emacs/ess. sometimes i can C-c or C-g it and other times i need to physically kill emacs. I've been having the same problem for a while, but wasn't able to isolate it any more than large data sets, lack of memory, and heavy CPU usage. Sometimes everything hangs and I need to power cycle the computer. :( Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
[O] no org-export-to-html-and-open since distribution switch
Hi List, since I have switched distributions from Mint to Arch, I have lost one of my most-loved Org features: Export to HTML and open. When I choose to export something, I type C-c C-e C-s h o as I usually do. But now the HTML opens in my agenda buffer, and not in my browser anymore. When I right-click on http links in my org document, the browser correctly opens them. When I command M-x org-export-to-html-and-open, it says [No match]. The symptoms are very much like described in http://emacs.stackexchange.com/questions/2387/browser-not-opening-when-exporting-html-from-org-mode , but unfortunately there is no documented solution. My org version reports as „Org-mode version 8.2.10 (8.2.10-41-g42228a-elpaplus @ /home/ehret/.emacs.d/elpa/org-plus-contrib-20150615/)“. I tried moving the elpa installation out of the way and installing a distribution package, aur/emacs-org-mode, but the result is the same. Emacs will likely always feel alien to me, but my love to org mode is bitter swt. Any help or hints are greatly appreciated! Best, Sven. -- Sven Ehret I2P: das unsichtbare Internet. Erreicht mich mit via I2P-Bote als vDe1o-Y0SS6JYDLUInq1O~1ryC0~Gx48~px7bb5iVDgoC1PRJf8OKG3PVeYGRqilnKn8k14KYBzp4FZ3FVnLklZNsHI62N8ieeexgU~SwJZ1pl6sucy24X8uU39T0aWf7egwrwfyI34rXEb7uBhWlkKf https://geti2p.net/de/ :: http://i2pbote.i2p.us/
Re: [O] ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Eric S Fraga e.fr...@ucl.ac.uk writes: Dear all, I have started using ox-koma-letter from the contrib directory. Very nice. Thanks Nicolas, Alan, Viktor, and Rasmus! Everything works well so far except for one minor niggle: I would like to introduce, sometimes, LaTeX specific inline directives in #+ lines. E.g. for LaTeX export, I would use @@latex:\\@@ to get a line break in a title or author entry. I had expected the same to work with ox-koma-letter given that it is a latex /derived/ backend and does work in normal text, just not in #+ lines. I guess the processing of #+ lines is handled directly by ox-koma-letter. Would it be possible to extend @@...@@ processing to those lines? Or am I doing something silly? It also doesn't work with ox-beamer: #+subtitle: subtitle @@latx:\LaTeX@@ @@beamer:BEAMER@@ I guess it's a feature. Or a bug at a higher level than ox-koma-letter. You can use the koma-letter snippet: #+subject: test @@koma-letter:\LaTeX@@ You can use a macro to combine several snippet types (not tested): #+macro: latex @@latex:$1beamer:$1koma-letter:$1@@ Rasmus -- . . . The proofs are technical in nature and provides no real understanding
Re: [O] ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Hello, Rasmus ras...@gmx.us writes: Eric S Fraga e.fr...@ucl.ac.uk writes: Dear all, I have started using ox-koma-letter from the contrib directory. Very nice. Thanks Nicolas, Alan, Viktor, and Rasmus! Everything works well so far except for one minor niggle: I would like to introduce, sometimes, LaTeX specific inline directives in #+ lines. E.g. for LaTeX export, I would use @@latex:\\@@ to get a line break in a title or author entry. I had expected the same to work with ox-koma-letter given that it is a latex /derived/ backend and does work in normal text, just not in #+ lines. I cannot reproduce it. koma-letter back-ends explicitly allows latex export snippets, e.g., #+title: @@latex:\something@@ produces the expected \something. It also doesn't work with ox-beamer: #+subtitle: subtitle @@latx:\LaTeX@@ @@beamer:BEAMER@@ I guess it's a feature. Or a bug at a higher level than ox-koma-letter. This is a feature. If @@latex:...@@ is supported in beamer export, you have no way to insert latex-only code in a document that you plan to export using both beamer and latex back-ends. However, this doesn't apply in koma-letter. Regards, -- Nicolas Goaziou
Re: [O] org-publish-project yields Eager macro-expansion failure
Nick, Thanks for the feedback. I ultimately fixed this problem by moving my org-mode customizations in my emacs initialization file after the package initialization of orgmode.org/elpa. I somehow think this problem is related to having two versions of org floating around, one from emacs itself and the other from orgmode.org/elpa. (My emacs initialization file is done via tangle/org-babel so I have to have org available from the start, I presume.) BTW, this problem would occur in several situations. For example, when I was trying to get an agenda view. At any rate, the issue is resolved for now. Thanks again for your suggestions. On Wed, Jun 17, 2015 at 7:47 AM, Nick Dokos ndo...@gmail.com wrote: Julien Chastang chast...@ucar.edu writes: Hello. Frequently, when I try to org-publish-project, I get a Eager macro-expansion failure The message buffer and backtrace are available here: https://gist.github.com/julienchastang/98b268e9601882d8d81c Indeed, I can simply reproduce this problem by calling (load-with-code-conversion path/elpa/org-20150615/ox-html.el path/elpa/org-20150615/ox-html.el nil t) which gets called somewhere in the org-publish-project invocation (see backtrace). So I am concluding the error has nothing to do with my project. What can I do to publish my project again? Many thanks. Can you try with uncompiled code? See (info (org) Feedback) for how to do that. There are two possibilities: o you'll still get the error, but the backtrace will be much more informative. o you will not get the error - IME, problems that disappear when run with uncompiled code are harder to debug. But that would still be interesting information. In the latter case, a minimal example that triggers the error would be useful. -- Nick -- Julien Chastang Scientific Software Developer Unidata-UCAR
[O] export to HTML with nbsp
Greetings. I tried searching for this, because I think I've seen it before, but searching for nbsp brings up dozens of false-positives. So my underlying problem is that I'd like to combine markups ~commandname option1 /option2/~ and end up with options2 being both monospace and italic. I couldn't get the borders and prematch and postmatch working correctly. I also failed to figure out how to create my own monospace-and-italic markup style. So I eventually gave up and settled for ~commandname option1 /option2/ \nbsp~ which works great inside emacs, and works with export to ASCII. But when I export to HTML, the \nbsp is not being converted to like the docs say it should. It is just being left as \nbsp . I just noticed this comment in the doc Text in the code and verbatim string is not processed for Org mode specific syntax, it is exported verbatim. However, again, \nbsp is properly processed when I export to ASCII. So I'm confused as to why it's different for export to HTML. Am I doing something wrong? Or is there something I need to do to make this export correctly? Thanks. --hymie!
Re: [O] ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Nicolas Goaziou m...@nicolasgoaziou.fr writes: I cannot reproduce it. koma-letter back-ends explicitly allows latex export snippets, e.g., #+title: @@latex:\something@@ produces the expected \something. I agree. I cannot reproduce either. Typo. Thanks. Rasmus -- Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] org-ref helm-bibtex notes
On 2015-06-16 Tue 18:28, Titus von der Malsburg wrote: On 2015-06-16 Tue 17:39, Julian Burgos wrote: Dear list, I have been using org-ref for a while, using reftex to insert citations in my org documents. Now I am switching to helm-bibtex, which is pretty awesome. I have a couple of question about the note files. Org-ref uses a single file to keep notes (e.g. notes.org), but helm-bibtex assumes that notes are kept in separate files, one per article. My questions are: a) Do you have a preference in the single file vs multiple files question? Are advantages/disadvantages? I tend to prefer the single file option, it makes search easy and also I can add TODO items that later I can pull out in the agenda view. With multiple files this would not be as easy. Do you agree? Hi, I’m the author of helm-bibtex. There was recently a discussion about this on Github: https://github.com/tmalsburg/helm-bibtex/issues/40 Someone convinced me that storing all notes in one file is better and there is an experimental (and incomplete) implementation in a topic branch: https://github.com/tmalsburg/helm-bibtex/tree/note-files Update: I worked on the note-files branch and as far as I’m concerned it is ready to be merged into master. There are several changes: When one big notes file is used: - The new default template for notes is simpler than what org-ref uses but it should be compatible because it uses the Custom_ID property to store the key. - Note templates can be defined in `helm-bibtex-notes-template`. - The list of publications now shows a mark if notes are available for a publication. - Finding the correct entry is now robust because the code looks for `Custom_ID: key` not just for the key. Multiple note files (one for each publication): - The template for notes is used to populate new note files. (Previously it was only used in the case with one big notes file.) Julian, if you could test this branch, that would be fantastic! Here is the code: https://github.com/tmalsburg/helm-bibtex/tree/note-files Titus (Multiple note files will still be possible for users who prefer that.) b) Helm-bibtex identifies which references have a note file, adding a symbol on the reference list. Can we make helm-bibtex look into a single file (say the notes.org file), look for the :Custom_ID: properties of the entries, and use that to mark the reference list? I am teaching myself emacs-lisp but this is above my capacity right now. Yes, something like that needs to be included. The unresolved question is how BibTeX keys should be stored in the notes file. I find property drawers incredibly clunky and in my experience they can considerably slow down Emacs in large org files (that’s the reason why I don’t use org-contacts as much as a would like). My current favorite format for entries in the notes file is the following: * Author: Title (year) :BibTeXkey: Here are the notes … The only problem I see with this is that BibTeX allows keys to contain colons, and a key with a colon would break org’s tag syntax. Suggestions welcome. Titus Many thanks, Julian signature.asc Description: PGP signature
Re: [O] helm-bibtex questions
On 2015-06-17 Wed 11:08, Xebar Saram wrote: Hi Titus I have been exploring helm-bibtex a bit today and have some questions. btw is this the preferred way to make requests/ask questions or is github preferred? Helm-bibtex is not part of org (although it tries to work well with org). So I’m not sure whether this list is the best place for discussing it. For now the issue tracker on Github might be a better option: https://github.com/tmalsburg/helm-bibtex/issues in any case i was wondering a few things: 1. is it possible to have custom sorting? i want all views to sort by Author, year, month I prefer to see the entries in the (inverse) order in which they appear in the BibTeX file. This way, recent additions show up at the top. However, I agree that sorting would be useful (see issues #5 and #21); it just doesn’t have high priority for me. Pull requests welcome. 2. i would really like a way to have stored smart groups (like the jabref dynamic groups if your aware of that). that is for example create a group that auto selects all publications i have (by my first/last name) and shows the count (in numbers) of these publications. I’m not familiar with smart groups but it seems that all helm-bibtex is doing is giving you very flexible smart groups defined by your search expressions. For example, if you want a list of your publications, you can simple enter your name. And if you want a list of your articles, you can enter your name + “article”. If you want all your articles from 2010, enter your name + “articles 2010”. And so on. The number of matches will be displayed in the mode line. If you don’t want to type these search expressions, you could create a command that invokes helm-bibtex with a default search expression and that command could be bound to a keyboard shortcut. Another example is a group to keep track of all the papers im working on or invloved with by matching keyword author and prep/*other key word I use two BibTeX fields to tag entries: “keywords” for keywords describing the content of the paper (as usual) and “tags” for meta data. Values that I use in tags are “own”, “manuscript”, “poster”, “talk”, … So if I want a list of all articles in progress, I search for “own manuscript”. Since the tags field is non-standard, it has to be added to `helm-bibtex-additional-search-fields`. Another solution would be to use the pubstate field and to search for your name and “forthcoming” (add pubstate to helm-bibtex-additional-search-fields for this to work). 3.is it possible to ass an option to auto generate a bibkey for a selected citation based on user criteria such as author(date)short-title? Maintaining the content of the BibTeX file not really in the scope of helm-bibtex (I prefer to write my BibTeX entries by hand). Perhaps org-ref or ebib can help here? Once you have a function that generates a new key and inserts it in the BibTeX file, you can easily add it to the list of actions in helm-bibtex. Hope that helps. Titus thx so much in advance, you and john have given me confidence to finally dive into the whole latex/bibteX world best Z signature.asc Description: PGP signature
[O] org-babel-lob-ingest and debug-init
Hi all, I have two lines like this in my .emacs: --8---cut here---start-8--- (org-babel-lob-ingest ~/path/to/library-of-babel.org) (org-babel-lob-ingest ~/path/to/custom-library-of-babel.org) --8---cut here---end---8--- All works fine usually. But when I start emacs using the --debug-init option, these lines result in , | Debugger entered--Lisp error: (error Before first heading) ` Not sure whether this is relevant, but these are basically my first lines in .emacs: --8---cut here---start-8--- (add-to-list 'load-path ~/path/to/org-mode-from-git/) (require 'org-loaddefs) --8---cut here---end---8--- Why do I get this error? Many thanks in advance, Andreas
Re: [O] org-babel-lob-ingest and debug-init
Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: Andreas Leha andreas.l...@med.uni-goettingen.de writes: Hi all, I have two lines like this in my .emacs: (org-babel-lob-ingest ~/path/to/library-of-babel.org) (org-babel-lob-ingest ~/path/to/custom-library-of-babel.org) All works fine usually. But when I start emacs using the --debug-init option, these lines result in , | Debugger entered--Lisp error: (error Before first heading) ` Not sure whether this is relevant, but these are basically my first lines in .emacs: (add-to-list 'load-path ~/path/to/org-mode-from-git/) (require 'org-loaddefs) Why do I get this error? Many thanks in advance, Andreas Sorry, this was the wrong diagnosis. I get 'Before first heading' now quite often with Org mode files (visiting the file, global visibility cycling, etc.) I got myself into this by upgrading emacs [1]. I also upgraded Org mode [2] to no avail. What am I missing? Dunno. A backtrace with an uncompiled Org would help. Regards, -- Nicolas Goaziou
Re: [O] org-babel-lob-ingest and debug-init
Andreas Leha andreas.l...@med.uni-goettingen.de writes: Hi all, I have two lines like this in my .emacs: (org-babel-lob-ingest ~/path/to/library-of-babel.org) (org-babel-lob-ingest ~/path/to/custom-library-of-babel.org) All works fine usually. But when I start emacs using the --debug-init option, these lines result in , | Debugger entered--Lisp error: (error Before first heading) ` Not sure whether this is relevant, but these are basically my first lines in .emacs: (add-to-list 'load-path ~/path/to/org-mode-from-git/) (require 'org-loaddefs) Why do I get this error? Many thanks in advance, Andreas Sorry, this was the wrong diagnosis. I get 'Before first heading' now quite often with Org mode files (visiting the file, global visibility cycling, etc.) I got myself into this by upgrading emacs [1]. I also upgraded Org mode [2] to no avail. What am I missing? Thanks, Andreas [1] GNU Emacs 25.0.50.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 10.9.5 (Build 13F1077)) [2] Org-mode version 8.3beta (release_8.3beta-1264-g365c19)
Re: [O] allow italic quote marks? org-emphasis-regexp-components
And Steven, You need to insert that same char between , and / in /then,/ On Wed, Jun 17, 2015 at 11:19 PM Kaushal kaushal.m...@gmail.com wrote: The solution is simpler than you think; you simply need to add ZERO WIDTH SPACE unicode char between / and (beginning) and and / (end). The default way to do it is C-x 8 RET zero width space RET or C-x 8 RET 200b RET But I need to use this priceless unicode char to escape stuff like this in org-mode and so I have bound 0 in C-x 8 map to insert this char. Here is how I do it in my init: https://github.com/kaushalmodi/.emacs.d/blob/f3c44e933f45dfdb760540e9f86acc91b55ab94a/setup-files/setup-editing.el#L637 Thus I simply need to do C-x 8 0 to insert the ZERO WIDTH SPACE. To elaborate more, 0 below is where you insert the 200b unicode characters: I would like to see /0these surrounding quotes in italics0/. On Wed, Jun 17, 2015 at 10:46 PM Steven Arntson ste...@stevenarntson.com wrote: I am not helpful here, but would simply like to add that I would also love an answer to this, as well as times when italics don't seem to work around periods and commas, like and /then,/ well, ... (which does not italicize for me on emacs 24.5.1, org 8.2.1). Myles English mylesengl...@gmail.com writes: Hello, Can anyone tell me what to set org-emphasis-regexp-components to in order to allow italic quote marks? i.e. /like this/ I don't understand the documentation and am just not in the mood to spend the next hour or so working it out. (That is a rule of thumb for me; if it involves a regular expression, it will take at least an hour, and three cups of tea.) Thanks, Myles
Re: [O] How do I specify the font attributes in org - odt exports?
The specific sequence of steps you need to follow) are documented in the Org manual. Note that the node mentions 'Stylist'. (Search for it in LibreOffice help) See https://www.gnu.org/software/emacs/manual/html_node/org/Applying-custom-styles.html If you have further SPECIFIC questions (and if it is of wider interest), I can help. That said, if I were you, I would talk to the University librarian/archivist and suggest/insist that THEY provide LibreOffice templates that ALL students can use. Talking to them is a good way to let them know that some (and hopefully more and more) of their students rely on Free Software tools like LibreOffice. On Monday 15 June 2015 07:55 AM, Kaushal wrote: Hi, I require the ox-odt package and I set this variable to export to doc (MS Word 97) format by default: (setq org-odt-preferred-output-format doc) I have to do this as I need to submit a paper in Word. The export works fine but can someone help me how to write the style ott/xml file so that the export to .doc adheres to the below rules? Title Page (must fit on first page only): Title (bold, centered) – *Times New Roman 18 pt* Author Names (centered) - Times New Roman 16 pt Company/Location/Country/Website (centered) - Times New Roman 14 pt Abstract (left-justified; italicized; not to exceed 150 words) – Times New Roman 12 pt Table of Contents/Figures/Tables*: Header (bold, centered): *Times New Roman 14 pt* Listing (left-justified): Times New Roman 12 pt Body Page and Margins: - One-inch margins; top, bottom, right and left - No headers - Chapter headings (numbered, bold, left justified): *Times New Roman 14 pt* - Chapter body (left justified): Times New Roman 12 pt References (numbered): Times New Roman 11 pt - Use embedded footer, Times New Roman 12 pt (Update ‘Paper Title’) - Script/code examples: Courier New 12 pt -- Kaushal Modi
Re: [O] allow italic quote marks? org-emphasis-regexp-components
I am not helpful here, but would simply like to add that I would also love an answer to this, as well as times when italics don't seem to work around periods and commas, like and /then,/ well, ... (which does not italicize for me on emacs 24.5.1, org 8.2.1). Myles English mylesengl...@gmail.com writes: Hello, Can anyone tell me what to set org-emphasis-regexp-components to in order to allow italic quote marks? i.e. /like this/ I don't understand the documentation and am just not in the mood to spend the next hour or so working it out. (That is a rule of thumb for me; if it involves a regular expression, it will take at least an hour, and three cups of tea.) Thanks, Myles
Re: [O] Emacs/ESS/org freezes/hangs on big data/ RAM(~256GB) processes when run in org/babel
On Wed, 17 Jun 2015, William Denton wrote: On 17 June 2015, Xebar Saram wrote: I do alot of modeling work that involves using huge datasets and run process intensive R processes (such as complex mixed models, Gamms etc). in R studio all works well yet when i use the orgmode eval on R code blocks it works well for small simple process but 90% of the time when dealing with complex models and bug data (up to 256GB) it will just freeze emacs/ess. sometimes i can C-c or C-g it and other times i need to physically kill emacs. I've been having the same problem for a while, but wasn't able to isolate it any more than large data sets, lack of memory, and heavy CPU usage. Sometimes everything hangs and I need to power cycle the computer. :( And you (both) have `ess-eval-visibly' set to nil, right? I do statistical genomics, which can be compute intensive. Sometimes processes need to run for a while, and I get impatient having to wait. I wrote (and use) ox-ravel[1] to speed up my write-run-revise cycle in org-mode. Basically, ravel will export Org mode to a format that knitr (and the like) can run - turning src blocks into `code chunks'. That allows me to set the cache=TRUE chunk option, etc. I run knitr on the exported document to initialize objects for long running computations or to produce a finished report. When I start a session, I run knitr in the R session, then all the cached objects are loaded in and ready to use. If I write a src block I know will take a long time to export, I export from org mode to update the knitr document and re-knit it to refresh the cache. Mostly, I work in org-mode adding src blocks, revising existing ones, or editing text and graphics. If you decide to try ravel I recommend the `ravel-lang' branch[2] as that will soon replace master. HTH, Chuck [1] https://github.com/chasberry/orgmode-accessories [2] https://github.com/chasberry/orgmode-accessories/tree/ravel-lang
Re: [O] allow italic quote marks? org-emphasis-regexp-components
The solution is simpler than you think; you simply need to add ZERO WIDTH SPACE unicode char between / and (beginning) and and / (end). The default way to do it is C-x 8 RET zero width space RET or C-x 8 RET 200b RET But I need to use this priceless unicode char to escape stuff like this in org-mode and so I have bound 0 in C-x 8 map to insert this char. Here is how I do it in my init: https://github.com/kaushalmodi/.emacs.d/blob/f3c44e933f45dfdb760540e9f86acc91b55ab94a/setup-files/setup-editing.el#L637 Thus I simply need to do C-x 8 0 to insert the ZERO WIDTH SPACE. To elaborate more, 0 below is where you insert the 200b unicode characters: I would like to see /0these surrounding quotes in italics0/. On Wed, Jun 17, 2015 at 10:46 PM Steven Arntson ste...@stevenarntson.com wrote: I am not helpful here, but would simply like to add that I would also love an answer to this, as well as times when italics don't seem to work around periods and commas, like and /then,/ well, ... (which does not italicize for me on emacs 24.5.1, org 8.2.1). Myles English mylesengl...@gmail.com writes: Hello, Can anyone tell me what to set org-emphasis-regexp-components to in order to allow italic quote marks? i.e. /like this/ I don't understand the documentation and am just not in the mood to spend the next hour or so working it out. (That is a rule of thumb for me; if it involves a regular expression, it will take at least an hour, and three cups of tea.) Thanks, Myles
Re: [O] no org-export-to-html-and-open since distribution switch
Sven Ehret s...@ehlu.name writes: Hi List, since I have switched distributions from Mint to Arch, I have lost one of my most-loved Org features: Export to HTML and open. ... When I command M-x org-export-to-html-and-open, it says [No match]. That function might have existed in org 7.9.x and earlier, but the exporter underwent major restructuring in the org 8.0 release and a lot of things were changed/renamed. The current version does this for C-c C-e h o: (org-open-file (org-html-export-to-html args)) org-html-export-to-html writes an HTML file and org-open-file opens it. See the doc string for the latter: C-h f org-open-file RET You might have to customize org-file-apps to override the default for the HTML file type (although see below first). For me, the default is mailcap (determined through the system specific variable org-file-apps-defaults-gnu - the default is the t entry), so it uses the entry in ~/.mailcap or /etc/mailcap (if it exists). Mine says: text/html; /usr/bin/google-chrome %s so it opens it in chrome. The problem here is that there are too many cooks in the kitchen. I prefer to leave things at default as far as org is concerned and use mailcap (which is used by other applications as well). Other people prefer to hardwire things into org-file-apps which is fine for org but of course it is not used by any other applications. Other people prefer to route everything through their desktop environment's Open function (e.g xdg-open for Gnome) which uses its own routing mechanism (generally different from mailcap). I suggest you pick *one* method and stick with it through thick and thin: ignore everything else. Using more than one leads to madness. The path of least resistance is probably customizing org-file-apps. The symptoms are very much like described in http://emacs.stackexchange.com/questions/2387/browser-not-opening-when-exporting-html-from-org-mode , but unfortunately there is no documented solution. My org version reports as „Org-mode version 8.2.10 (8.2.10-41-g42228a-elpaplus @ /home/ehret/.emacs.d/elpa/org-plus-contrib-20150615/)“. I tried moving the elpa installation out of the way and installing a distribution package, aur/emacs-org-mode, but the result is the same. Emacs will likely always feel alien to me, but my love to org mode is bitter swt. Any help or hints are greatly appreciated! Best, Sven. HTH, Nick
[O] org version numbers in file - WAS: Tangling takes long - profiling and calling R
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Rainer M Krug r.m.k...@gmail.com writes: We can check for that in Org Lint and warn the user. That would be a really good idea! Done. Great - thanks. Before deleting it, one should get a warning that a certain feature is deprecated. At the moment, it is only mentioned in the help (as far as I am aware). It has been mentioned in the manual for the last two years. See footnote in (info (org)Header arguments in Org mode properties). Yes - that's true. But who of the longer org users reads the manual of features they use regularly? org-lint seems to become the place where these changes can be marked and the user be notified - that is really brilliant. I could imagine the following automatic workflow to enable automatic linting of org files upon opening when they were saved under an older (or unknown) version of org: 1) a new argument is introduced : #+FILE_ORG_VERSION: 8.3beta 2) when opening an org file, this version is checked. The following cases are possible: - parameter not present: assume that file version is older and run org-lint - file version older then org version: run org-lint - file version identical to org version: just open - file version newer: run org-lint 3) after reviewing the results, org-lint could offer to update the file version (#+FILE_ORG_VERSION) to the version of org-mode. This should be, by the way, possible to do even when running org-lint manually. 4) this behavior should be possible to disabled by an additional header #+ORG_FILE_VERSION_CHECK: f but not via emacs.el as this should be the standard behavior. One could go even one step further, to define a minimum and maximum org version so that one get's a warning that the file requires a different org version than used: #+REQUIRED_ORG_VERSION: min:8.0 would require org newer and including than 8.0 #+REQUIRED_ORG_VERSION: max:8.0 would require org older and including than 8.0 #+REQUIRED_ORG_VERSION: min:8.0 max:8.9.9 a version between and including 8.0 and 8.9.9 because e.g. a feature used was only present during these releases or #+REQUIRED_ORG_VERSION: min:8.0 max:8.0 require version exactly version 8.0 where the warning comes when the version is different to the ones specified. I really think that org files should have the org-versions that was used to write them and the org version required to run them. Even though that org-documents are documents, I kind of see them as *add-ons* to org, because they can contain code to be execute, variables to be set, and added functionality to the standard org. So to make this more robust, to store the org version used to create the file version and the required org versions would make perfect sense to me. This should obviously only include release, alpha, beta, rc and not git checkout values. Cheers, Rainer Regards, -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: [O] Why navigating in Org mode is so slow in overview mode?
Hi Nicolas, * Nicolas Goaziou m...@nicolasgoaziou.fr [17. Jun. 2015]: Hello, Q godbles...@gmail.com writes: I am view this file http://doc.norang.ca/org-mode.org It's a prettey long document, when it all folded up, navigating to previous line and next line takes about 2 seconds. When the sub heading is shown, it's more responsive. Is this a bug? I don't know. What Org version are you using? Could you use a profiler and report results? I thought this is a known problem which gets worse with the amount of hidden text. The workaround is to use a „#+STARTUP: showeverything“ directive. I use this in order to make a longish org file with many clocking lines in drawers usable. It would be great if this could be fixed. I would like to help but need help myself on how to produce profiler reports. My org mode version is 8.3beta (release_8.3beta-1228-gd1f9aa @ /home/grfz/src/org-mode/lisp/) but I have this problem since months or years. Regards, Gregor
Re: [O] org-ref helm-bibtex notes
Hi Titus, I think a very simple template for the notes file would suffice. I am using org ref and had originally modified the template by removing the TODO, simplifying the properties drawer (no need to duplicate all the biblatex info here) and adding a link to the pdf file, which is very handy when reading my notes file. * [[/path/to/pdf/files/BibTeXkey.pdf][BibTeXkey]] Title :PROPERTIES: :Custom_ID: BibTeXkey :END: Recently I upgraded org-ref and instead of using my own link to the pdf file, I use a cite statement, which gives me all the goodies from org-ref (opening the pdf file, accesing Google Scholar, etc.etc.). * cite:BibTeXkey Title :PROPERTIES: :Custom_ID: BibTeXkey :END: I have no choice between using drawers or tags. I have not experienced slow downs because of using drawers, although tags would make the notes file look cleaner. The issue with keys containing colons could be solved by replacing the colon with some other acceptable character on the tag, like @ or _. So a reference with BibTeXkey Smith,Jones 2008 would get a tag Smith@Jones2008 or Smith_Jones2008. Julian On 2015-06-16 Tue 17:39, Julian Burgos wrote: Dear list, I have been using org-ref for a while, using reftex to insert citations in my org documents. Now I am switching to helm-bibtex, which is pretty awesome. I have a couple of question about the note files. Org-ref uses a single file to keep notes (e.g. notes.org), but helm-bibtex assumes that notes are kept in separate files, one per article. My questions are: a) Do you have a preference in the single file vs multiple files question? Are advantages/disadvantages? I tend to prefer the single file option, it makes search easy and also I can add TODO items that later I can pull out in the agenda view. With multiple files this would not be as easy. Do you agree? Hi, I’m the author of helm-bibtex. There was recently a discussion about this on Github: https://github.com/tmalsburg/helm-bibtex/issues/40 Someone convinced me that storing all notes in one file is better and there is an experimental (and incomplete) implementation in a topic branch: https://github.com/tmalsburg/helm-bibtex/tree/note-files (Multiple note files will still be possible for users who prefer that.) b) Helm-bibtex identifies which references have a note file, adding a symbol on the reference list. Can we make helm-bibtex look into a single file (say the notes.org file), look for the :Custom_ID: properties of the entries, and use that to mark the reference list? I am teaching myself emacs-lisp but this is above my capacity right now. Yes, something like that needs to be included. The unresolved question is how BibTeX keys should be stored in the notes file. I find property drawers incredibly clunky and in my experience they can considerably slow down Emacs in large org files (that’s the reason why I don’t use org-contacts as much as a would like). My current favorite format for entries in the notes file is the following: * Author: Title (year) :BibTeXkey: Here are the notes … The only problem I see with this is that BibTeX allows keys to contain colons, and a key with a colon would break org’s tag syntax. Suggestions welcome. Titus Many thanks, Julian
Re: [O] org-ref helm-bibtex notes
Thanks John. You are right, although I think having to read too many org files would make the agenda run slower. And creates a lot of buffers (one per file) which makes navigation more complicated. I always wished that the agenda would close those buffers. Anyway, I think that having a single file is the best option. Julian Burgos writes: Dear list, I have been using org-ref for a while, using reftex to insert citations in my org documents. Now I am switching to helm-bibtex, which is pretty awesome. I have a couple of question about the note files. Org-ref uses a single file to keep notes (e.g. notes.org), but helm-bibtex assumes that notes are kept in separate files, one per article. My questions are: a) Do you have a preference in the single file vs multiple files question? Are advantages/disadvantages? I tend to prefer the single file option, it makes search easy and also I can add TODO items that later I can pull out in the agenda view. I prefer the single file, for the reasons you describe. With multiple files this would not be as easy. Do you agree? This is not totally true. You can add your directory of org notes to your org-agenda-files, e.g. (setq org-agenda-files '(~/path/to/org-notes)) and it will add all org files in that directory to your agenda. If you use helm, it is probably easy to search all of the files too. -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] exporting images in latex with a relative path
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
I'm fetching images using org-download, which creates links of the form:
[[~/work/talks/Formal_JavaScript/images/Adobe_logo_2015-06-17_12:22:02.gif]]
Unfortunately these links are not exported when I export to latex, I get
this output:
\url{file:///Users/schmitta/work/talks/Formal_JavaScript/images/Adobe_logo_2015-06-17_12:22:02.gif}
Is there a way to get an inline image instead? I see the manual requires
the link to start with file: or with ., could it also work with
~?
It already works with ~, but .gif is not recognized, by default, as
a valid extension for images. You can configure
`org-latex-inline-image-rules'.
Regards,
--
Nicolas Goaziou
Re: [O] [feature request] org-capture-window-setup to stop capture window taking up whole frame
On Monday, 8 Jun 2015 at 16:46, Kaushal wrote: `org-capture` does not take up the full frame for me by default; I just tried that in an emacs -Q session. Okay, I have finally found some time to get back to this (been marking exam scripts, for my sins... ;-). If the capture template prompts for information, the whole frame is cleared and only the bare capture buffer is shown in the frame while the prompts are processed. This is my main problem: I often want to include some information from the existing buffers in my org capture and all the information is hidden just when I want it. Once the prompts have been answered, the windows shown in the frame change with the original window present as well as the capture window. This is too late. All of the above confirmed with emacs -Q. The question, I guess, is why does org-capture need to take over the whole frame while processing the prompts in the capture template? If it needs to display the capture buffer while handling the prompts, why not display it as it will once the prompts have been processed? Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-1216-gb856f6
Re: [O] Bug with label names in beamer export
On Tue, Jun 16, 2015 at 09:36:26PM +0200, Rasmus wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
The attached patch should fix the issue.
Pushed, thanks. I changed the commit message slightly.
* lisp/ox-beamer.el (org-beamer--get-label): wrap labels in {..}
You don't need the lisp/ prefix. Capitalize after the colon. Should
end with period.
Thank you!
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Links, exporter
Hello,
Fabrice Popineau fabrice.popin...@gmail.com writes:
If I try to export the Second Blog entry subtree by C-C C-e C-s C-b h H,
I get a user-error because the exporter can't resolve the link which points
outside of the exported subtree.
Is this expected?
Yes, unresolved links/footnotes/whatever throw errors instead of leaving
broken links.
Maybe that is a bad idea, but I was thinking that the link could be
resolved as if we were exporting the whole file rather than error
it.
It could work for HTML export but it cannot be generalized (e.g., you
cannot have a dangling \ref{something} without a corresponding
\label{...} in LaTeX). So, it is consistent.
Regards,
--
Nicolas Goaziou
[O] exporting images in latex with a relative path
Hello,
I'm fetching images using org-download, which creates links of the form:
[[~/work/talks/Formal_JavaScript/images/Adobe_logo_2015-06-17_12:22:02.gif]]
Unfortunately these links are not exported when I export to latex, I get
this output:
\url{file:///Users/schmitta/work/talks/Formal_JavaScript/images/Adobe_logo_2015-06-17_12:22:02.gif}
Is there a way to get an inline image instead? I see the manual requires
the link to start with file: or with ., could it also work with ~?
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Weekly CO₂ average (2015-05-30, Mauna Loa Observatory): 403.41 ppm
signature.asc
Description: PGP signature
[O] Links, exporter
Hi, I have another problem/question with links related to the exporter. I lost track of what was the behavior months ago. Assume I have something like this : * BAR :PROPERTIES: :PAGE: bar.html :END: ** First link :first: :PROPERTIES: :CUSTOM_ID: First%20link :END: Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor. Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum. Nam vestibulum accumsan nisl. ** Second link *** Third level - [[#First%20link][First link]] foo bar - [[file:sample.org][sample.org]] - [[http://www.google.com][Google]] * BLOG ** DONE BLOG Entry :blog:foo: CLOSED: [2015-06-17 mer. 10:15] Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor. Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum. Nam vestibulum accumsan nisl. ** DONE Second Blog entry :blog:bar: CLOSED: [2015-06-17 mer. 11:17] [[#First%20link][First link again]] See if this will work. If I try to export the Second Blog entry subtree by C-C C-e C-s C-b h H, I get a user-error because the exporter can't resolve the link which points outside of the exported subtree. Is this expected? Maybe that is a bad idea, but I was thinking that the link could be resolved as if we were exporting the whole file rather than error it. Thanks for enlighting me. Fabrice
Re: [O] Links
Hello, Suvayu Ali fatkasuvayu+li...@gmail.com writes: Would it make sense to promote these kind of encoded links to almost their own sub-types? I would guess, almost no one enters these encoded links by hand. It's either via copy paste in the prompt from org-insert-link, or by entering [[encoded-link][description]] by hand. I think it is a reasonable inconvenience to ask the user to prefix it with something like uri:. I mostly see advantages for a minor inconvenience. I don't think we should go as far as changing link syntax for this. Actually, the problem lies in internal links, since external ones are expected to be url-encoded when necessary. Internal links only require url-encoding when they contain square brackets. So, we can make a guess: if a string either doesn't contain %5B or %5D, or contains any character in `org-link-escape-chars' (with the exception of the percent sign), it cannot be encoded. Otherwise, we can assume it is encoded. In this case, there are false positives, but those are sufficiently rare (i.e., an internal link with either %5B or %5D and no space in it) this should not be a problem in practice. There is an important drawback however, as in the prefix proposal: currently encoded internal links (e.g. Headline%201) will break. Although, you still have to handle the ambiguous case for existing Org files. Unless this double maintenance is cumbersome, I would vote for introducing such a scheme. The double maintenance is not possible. Either we take into consideration the prefix or the heuristic rule above, and some links are going to break, or we allow to bypass it and it doesn't improve the situation. Regards, -- Nicolas Goaziou
Re: [O] org-publish-project yields Eager macro-expansion failure
Julien Chastang chast...@ucar.edu writes: Hello. Frequently, when I try to org-publish-project, I get a Eager macro-expansion failure The message buffer and backtrace are available here: https://gist.github.com/julienchastang/98b268e9601882d8d81c Indeed, I can simply reproduce this problem by calling (load-with-code-conversion path/elpa/org-20150615/ox-html.el path/elpa/org-20150615/ox-html.el nil t) which gets called somewhere in the org-publish-project invocation (see backtrace). So I am concluding the error has nothing to do with my project. What can I do to publish my project again? Many thanks. Can you try with uncompiled code? See (info (org) Feedback) for how to do that. There are two possibilities: o you'll still get the error, but the backtrace will be much more informative. o you will not get the error - IME, problems that disappear when run with uncompiled code are harder to debug. But that would still be interesting information. In the latter case, a minimal example that triggers the error would be useful. -- Nick
Re: [O] exporting images in latex with a relative path
On 2015-06-17 13:54, Nicolas Goaziou m...@nicolasgoaziou.fr writes: It already works with ~, but .gif is not recognized, by default, as a valid extension for images. You can configure `org-latex-inline-image-rules'. Ah, thank you. Org was doing the smart thing here: including gifs in a latex document is not a great idea … Thanks again, Alan -- OpenPGP Key ID : 040D0A3B4ED2E5C7 Weekly CO₂ average (2015-05-30, Mauna Loa Observatory): 403.41 ppm signature.asc Description: PGP signature
Re: [O] Why navigating in Org mode is so slow in overview mode?
Hi Gregor, Gregor Zattler telegr...@gmx.net writes: Hi Nicolas, * Nicolas Goaziou m...@nicolasgoaziou.fr [17. Jun. 2015]: Hello, Q godbles...@gmail.com writes: I am view this file http://doc.norang.ca/org-mode.org It's a prettey long document, when it all folded up, navigating to previous line and next line takes about 2 seconds. When the sub heading is shown, it's more responsive. Is this a bug? I don't know. What Org version are you using? Could you use a profiler and report results? I thought this is a known problem which gets worse with the amount of hidden text. The workaround is to use a „#+STARTUP: showeverything“ directive. I use this in order to make a longish org file with many clocking lines in drawers usable. It would be great if this could be fixed. I would like to help but need help myself on how to produce profiler reports. My org mode version is 8.3beta (release_8.3beta-1228-gd1f9aa @ /home/grfz/src/org-mode/lisp/) but I have this problem since months or years. Shot in the dark: Do have linum-mode enabled? That is always my first candidate when I experience slowdowns. Best, Andreas
Re: [O] Why navigating in Org mode is so slow in overview mode?
Gregor Zattler telegr...@gmx.net writes: I would like to help but need help myself on how to produce profiler reports. M-x profiler-start Do something slow M-x profiler-report Regards,
Re: [O] Why navigating in Org mode is so slow in overview mode?
Hi Andreas, * Andreas Leha andreas.l...@med.uni-goettingen.de [17. Jun. 2015]: Shot in the dark: Do have linum-mode enabled? That is always my first candidate when I experience slowdowns. No I don’t use linum-mode. Thanks, Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: [O] Links
Hi Nicolas, Fabrice, On Tue, Jun 16, 2015 at 11:30:06PM +0200, Nicolas Goaziou wrote: Fabrice Popineau fabrice.popin...@gmail.com writes: Ideally, url encoded links should have been prefixed with some kind of uri syntax. This way, you could know what to decode and what not. The encoded link could be copied from somewhere else. Also, there are numerous links in the wild without this prefix. Would it make sense to promote these kind of encoded links to almost their own sub-types? I would guess, almost no one enters these encoded links by hand. It's either via copy paste in the prompt from org-insert-link, or by entering [[encoded-link][description]] by hand. I think it is a reasonable inconvenience to ask the user to prefix it with something like uri:. I mostly see advantages for a minor inconvenience. Although, you still have to handle the ambiguous case for existing Org files. Unless this double maintenance is cumbersome, I would vote for introducing such a scheme. What do others think? -- Suvayu Open source is the future. It sets us free.
Re: [O] Why navigating in Org mode is so slow in overview mode?
Hello, Q godbles...@gmail.com writes: I am view this file http://doc.norang.ca/org-mode.org It's a prettey long document, when it all folded up, navigating to previous line and next line takes about 2 seconds. When the sub heading is shown, it's more responsive. Is this a bug? I don't know. What Org version are you using? Could you use a profiler and report results? Regards, -- Nicolas Goaziou
Re: [O] [feature request] org-capture-window-setup to stop capture window taking up whole frame
Quickie patch, maybe I'll work it up as per comments later submit but this will fix things for you (no guarantees, not widely tested) Modify: ,org-cpature.el In org-capture-fill-template ** (save-window-excursion ;; simplistic modification to avoid the capture-fill-template from ;; taking over the whole frame. It just moves to next window in cycling ;; order and uses that ;; proper patch would want configuration variable, more intelligent window choice, ;; and option to pop up new frame and destroy after capture-flll-template ;; (or use with template as well? ;; (delete-other-windows) don't delete other windows SMT 2015-06-17 (other-window 1) ;;stupid version, just go to next window in cycling order (org-pop-to-buffer-same-window (get-buffer-create *Capture*)) * -Original Message- From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On Behalf Of Eric S Fraga Sent: Wednesday, June 17, 2015 1:25 AM To: Kaushal Cc: emacs-orgmode@gnu.org; Charles Millar Subject: Re: [O] [feature request] org-capture-window-setup to stop capture window taking up whole frame On Monday, 8 Jun 2015 at 16:46, Kaushal wrote: `org-capture` does not take up the full frame for me by default; I just tried that in an emacs -Q session. Okay, I have finally found some time to get back to this (been marking exam scripts, for my sins... ;-). If the capture template prompts for information, the whole frame is cleared and only the bare capture buffer is shown in the frame while the prompts are processed. This is my main problem: I often want to include some information from the existing buffers in my org capture and all the information is hidden just when I want it. Once the prompts have been answered, the windows shown in the frame change with the original window present as well as the capture window. This is too late. All of the above confirmed with emacs -Q. The question, I guess, is why does org-capture need to take over the whole frame while processing the prompts in the capture template? If it needs to display the capture buffer while handling the prompts, why not display it as it will once the prompts have been processed? Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-1216-gb856f6 This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
