Hello Jonhn, hello the list,
I have already used org-bibtex (and ox-bibtex) and I have just tried to use
org-ref . Is it possible that a conflict exists between the former(s) and
the latter?
My links for example are not clickable and the link to the default
bibliography does not work at all... But
On 2014-06-26 20:44, Matt Lundin writes:
> Alan Schmitt writes:
>
>> On 2014-06-26 16:39, Matt Lundin writes:
>>
>>> By contrast, ox-bibtex.el runs citations through bibtex2html, which is
>>> pretty much limited to the "old-fashioned" bibtex formats.
>>
>> What would be required for bibtex2html
Hi all
off topic a bit again. im an academic (asst. prof) in Epidemiology and have
been using org-mode for about a year now. i love using org but im really
not very technical at all. it has always been a dream for me to ditch word
and move over to Latex and even better orgmode to write my scientif
Thorsten Jolitz writes:
> Hi List,
>
> what about adding one more option for WHICH
>
> ,[ C-h f org-entry-properties RET ]
> | org-entry-properties is a compiled Lisp function in `org.el'.
> |
> | (org-entry-properties &optional POM WHICH SPECIFIC)
> | [...]
> | If WHICH is nil or `all', ge
Forwarding to list. Somehow reply-all did not actually reply to all
-- Forwarded message --
From: "Jonathan Leech-Pepin"
Date: Jun 26, 2014 4:05 PM
Subject: Re: [O] How to identify all headings that won't be exported?
To: "Thomas S. Dye"
Cc:
Hello Thomas
On 26 June 2014 15:09,
Aloha all,
Answering myself ...
t...@tsdye.com (Thomas S. Dye) writes:
> Is there a practical way to identify descendants for my use
> case?
>
> (defun tsd-get-names-labels-and-headings ()
> (interactive)
> (save-excursion
> (goto-char (point-min))
> (let ((matches))
>
Hi Rainer,
Rainer M Krug writes:
> Hi
>
> there seems to be a bug in the table transfer. The org file below
> evaluates as shown, i.e. the TABLE_BLOCK contains one column less then
> it should as the first column is discarded and the second one used as
> the row names. This only occurs when ther
Hi John,
Thanks for sharing. My students and I love it.
Cheers,
M
Hi List,
what about adding one more option for WHICH
,[ C-h f org-entry-properties RET ]
| org-entry-properties is a compiled Lisp function in `org.el'.
|
| (org-entry-properties &optional POM WHICH SPECIFIC)
| [...]
| If WHICH is nil or `all', get all properties. If WHICH is
| `special'
Samuel Wales writes:
> in recent maint, it seems that refiling an entry will put that entry
> into the kill ring. perhaps it should leave the kill ring intact?
I think this has been the behavior for a very long time. E.g., I went
back to a version of org-refile from 2010 and it invokes
org-copy
Aloha all,
Inspired by John Kitchin's org-ref, I'm working on a little function that
returns all the pieces of an Org mode file that are candidates for cross
referencing. The helm package lets me choose from among the candidates
and then another little function inserts the chosen link.
This all w
Thibaut Verron writes:
> Would changing the last lines of `orgtbl-to-latex` to something like this
> work as a long-term solution?
>
> (require 'ox-latex)
> (let* ((*orgtbl-verbatim* (plist-get params :verbatim))
>(backend (if *orgtbl-verbatim* nil 'latex)))
> (orgtbl-to
Alan Schmitt writes:
> On 2014-06-26 16:39, Matt Lundin writes:
>
>> By contrast, ox-bibtex.el runs citations through bibtex2html, which is
>> pretty much limited to the "old-fashioned" bibtex formats.
>
> What would be required for bibtex2html to take biblatex input? I thought
> the backend for
Org-verbatim syntax is '=STRING=' ,but the equal symbol makes it look
not distinguishing ('=' itself looks like it seems to be a part of
STRING). I misread them often.
So, I think maybe Org-mode can add a new face for equal symbol itself? I
mean, user can dim the face of '=' to avoid confusion.
Achim Gratz writes:
> Nick Dokos writes:
>> After last night's git pull, org-version returns "beta_8.3" which
>> broke the major-version calculation above. I hardwired the org version
>> major number above, but I was wondering if we could agree on some
>> convention/method that will not break in
On 2014-06-26 18:14 Nick Dokos wrote:
> I have some backward-compat code that does this:
>
> (setq major-version (string-to-number (nth 0 (split-string
> (org-version) "[.]"
It does not work in this situation, because "beta_8.3" is not a valid
version string, but "version<" might be interestin
Nick Dokos writes:
> After last night's git pull, org-version returns "beta_8.3" which
> broke the major-version calculation above. I hardwired the org version
> major number above, but I was wondering if we could agree on some
> convention/method that will not break in the future - maybe an
> org
Aloha Onur,
Onur Solmaz writes:
> I followed the instructions on this website:
> http://orgmode.org/worg/org-contrib/babel/examples/article-class.html
>
> and tried to tangle article-class.org to obtain the class file
> org-article.cls that is to be used when exporting LaTeX files. The file is
>
El Thu, 26 Jun 2014 12:36:47 -0400 Eric Schulte va escriure:
> > #+BEGIN_SRC python :results output
> > print "x"
> > #+END_SRC
> >
> > It prints:
> >
> > #+RESULTS:
> > : None
> >
> > I expected to see "x". This worked some days ago.
> >
>
> This works for me using the latest version of Org-mode
On 2014-06-26 16:39, Matt Lundin writes:
> By contrast, ox-bibtex.el runs citations through bibtex2html, which is
> pretty much limited to the "old-fashioned" bibtex formats.
What would be required for bibtex2html to take biblatex input? I thought
the backend format was similar or the same (as y
Aloha Rainer,
Rainer M Krug writes:
> Hi
>
> I use #+NAME to define some parameters for my analysis, which works
> quite nice for tables. but I would now like to use the same apprioach
> for values, e.g. a single number, but I don't manage. Is this possible?
> For illustration a short example:
>
Daniel Clemente writes:
> Hi, this babel code recently stopped working on my system:
>
> #+BEGIN_SRC python :results output
> print "x"
> #+END_SRC
>
> It prints:
>
> #+RESULTS:
> : None
>
> I expected to see "x". This worked some days ago.
>
This works for me using the latest version of Org-mod
John Kitchin writes:
> Some features could be merged, but there is an important difference in that
> org-ref uses bibtex as the backend database, and reftex for searching, and
> org-bibtex uses org-mode headings as the backend database, and tag/property
> searches (I think). It is like the diffe
Hi, this babel code recently stopped working on my system:
#+BEGIN_SRC python :results output
print "x"
#+END_SRC
It prints:
#+RESULTS:
: None
I expected to see "x". This worked some days ago.
If I use a command like os.system("xeyes"), I see it running.
In addition I don't see the Python bl
I have some backward-compat code that does this:
--8<---cut here---start->8---
;;(setq major-version (string-to-number (nth 0 (split-string (org-version)
"[.]"
(setq major-version 8)
(if (< major-version 8)
(progn
(require 'org-latex)
...
>
> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> print(u'é')
> #+END_SRC
>
I also see the same problem here. Even if you include # -*- coding: utf-8 -*-
as the first line.
Shouldn't org-babel already be using utf-8 instead of ASCII for input/output?
By the way, w
Grant Rettke writes:
> On Thu, Jun 26, 2014 at 9:08 AM, Matt Lundin wrote:
>> I think the key in any possible feature merge is to remember citation
>> management is idiosyncratic.
>
> Off topic:
>
> How do people choose today?
>
> Why choose bibtex over biblatex?
Thanks to inertia, bibtex still
Grant Rettke writes:
> How do people choose today?
>
> Why choose bibtex over biblatex?
For journal submission. With BibTeX you only have to copy paste at the
end of your LaTeX file the contents of the generated .bbl file.
Moreover, journals provide a default style for BibTeX, not biblatex. And
On 2014-06-26 at 10:11, Grant Rettke wrote:
> Why choose bibtex over biblatex?
People choose bibtex because that is how it has been done and is well
supported/documented and still popular on Google results. People choose
biblatex because that appears to be the new under-development
with-bells-and
On Thu, Jun 26, 2014 at 9:08 AM, Matt Lundin wrote:
> I think the key in any possible feature merge is to remember citation
> management is idiosyncratic.
Off topic:
How do people choose today?
Why choose bibtex over biblatex?
Where do people discuss such questions like this in real life?
Matt Lundin writes:
> John Kitchin writes:
>
>> Some features could be merged, but there is an important difference in
>> that org-ref uses bibtex as the backend database, and reftex for
>> searching, and org-bibtex uses org-mode headings as the backend
>> database, and tag/property searches (I
John Kitchin writes:
> Some features could be merged, but there is an important difference in
> that org-ref uses bibtex as the backend database, and reftex for
> searching, and org-bibtex uses org-mode headings as the backend
> database, and tag/property searches (I think). It is like the
> dif
2014-06-26 15:17 GMT+02:00 Nicolas Goaziou :
> Thibaut Verron writes:
>
> >> Now, are these "limitations of Org" really preventing it from exporting
> a
> >> string verbatim? That would seem like the most logical default in this
> >> situation, wouldn't it?
>
> I disagree in the general case. The
Thibaut Verron writes:
>> Now, are these "limitations of Org" really preventing it from exporting a
>> string verbatim? That would seem like the most logical default in this
>> situation, wouldn't it?
I disagree in the general case. The most logical default for Org is to
treat contents as plain
2014-06-26 12:38 GMT+02:00 Nicolas Goaziou :
> Hello,
>
> Thibaut Verron writes:
>
> > I'm forwarding this question asked on stackexchange:
> > http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
> > that-braces-and-dollars-are-not-escaped
> >
> > After some investigation, it
>
> Now, are these "limitations of Org" really preventing it from exporting a
> string verbatim? That would seem like the most logical default in this
> situation, wouldn't it? (Disclaimer: I don't "understand the limitations of
> Org", so these last questions may be ridiculous to someone who does)
Some features could be merged, but there is an important difference in that
org-ref uses bibtex as the backend database, and reftex for searching, and
org-bibtex uses org-mode headings as the backend database, and tag/property
searches (I think). It is like the difference between org-contacts and
Aaron Ecay writes:
> 2014ko ekainak 25an, Rainer M Krug-ek idatzi zuen:
>>
>> Hi
>>
>> I want to add many variables to a subtree. But it seems
>> that :header-args: only allows one line - is this true? In my case, this
>> line would be exceedingly long and very difficult to debug.
>>
>> Is the
Hi
I use #+NAME to define some parameters for my analysis, which works
quite nice for tables. but I would now like to use the same apprioach
for values, e.g. a single number, but I don't manage. Is this possible?
For illustration a short example:
--8<---cut here---start---
+1 for org-bibtex (and ox-bibtex) that I'm using for a couple of years.
But org-ref seems to go further (video is convincing).
It would be really nice to merge org-ref and org-bibtex before they split
too far apart.
Wishful thinking from me because I don't see that I'm in position to do it.
Fabri
On 2014-06-26 09:35, Alan Schmitt writes:
> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> print(u'∀')
> #+END_SRC
I see that somewhere the email did not get through, the character above
is a "forall" character. I have the same problem with a simpler accent
#+BEGIN_SRC pyt
On 2014-06-26 03:38, Alan L Tyree writes:
> I have the following expression in my manuscript:
>
> /Caltex Oil (Aust) Pty Ltd v The Dredge 'Willemstad'/ [1976] HCA 65
>
> I want the /.../ part to be italicised on export, but (of course) it isn't.
>
> The variable org-emphasis-regexp-components was
Hello,
Thibaut Verron writes:
> I'm forwarding this question asked on stackexchange:
> http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
> that-braces-and-dollars-are-not-escaped
>
> After some investigation, it seems that the behavior is hidden deep in the
> export rou
Hello,
I'm forwarding this question asked on stackexchange:
http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
that-braces-and-dollars-are-not-escaped
After some investigation, it seems that the behavior is hidden deep in the
export routines, and I was wisely suggested to
David Rose jeppesen.com> writes:
>
> Hi,
>
> I am not sure if this is an actual bug or if I am just missing some
> new setting/configuration option, but when in a graphical emacs window
> org-mode table alignments are way off, yet when in a 'terminal' window
> emacs session tables are shown as
Thank you Peter.
I have to admit I do feel stupid for missing the font differences.
That did take care of it.
Cheers,
David Rose
Linux Systems Administrator
Information Technology Services
Jeppesen
A Boeing Company
ph: +46 31 722 62 25 | mobile: +46 73
Hi David,
On 26 Jun 2014, at 08:54, David Rose wrote:
> I am not sure if this is an actual bug or if I am just missing some
> new setting/configuration option, but when in a graphical emacs window
> org-mode table alignments are way off, yet when in a 'terminal' window
> emacs session tables are
I followed the instructions on this website:
http://orgmode.org/worg/org-contrib/babel/examples/article-class.html
and tried to tangle article-class.org to obtain the class file
org-article.cls that is to be used when exporting LaTeX files. The file is
weirdly empty.
Does anybody have an idea why
Hello,
I'm having trouble with the babel evaluation of python blocks containing
utf-8 encoded characters (which is the encoding of my org file).
I tried the approach suggested in this message
https://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00086.html
in the following block
#+BEGIN_SR
Hello Charles,
On 2014-06-24 18:37, Charles Berry writes:
> ,
> | #+NAME: prin-block
> | #+BEGIN_SRC emacs-lisp :var a="abc"
> | (defun foo (blk)
> | (save-excursion
> | (org-babel-goto-named-src-block blk)
> | (nth 1 (org-babel-get-src-block-info 'light
> |
> | #+EN
50 matches
Mail list logo
