Re: [O] Zotero csl file that uses parenthetical style for citations

Aloha Vaidheeswaran C, Vaidheeswaran C writes: > On Sunday 08 March 2015 11:04 PM, Thomas S. Dye wrote: > >> Thankfully, Richard demonstrated to his satisfaction that an >> off-the-shelf CSL style could be made to handle this situation. If this >> is the only potential problem you see, then thi

Re: [O] Zotero csl file that uses parenthetical style for citations

On Sunday 08 March 2015 11:04 PM, Thomas S. Dye wrote: > Thankfully, Richard demonstrated to his satisfaction that an > off-the-shelf CSL style could be made to handle this situation. If this > is the only potential problem you see, then this gives me hope that > Richard will succeed in implement

Re: [O] Plotting in Python block won't over-write existing file

> Date: Fri, 06 Mar 2015 14:21:54 -0500 > From: Nick Dokos > To: emacs-orgmode@gnu.org > Subject: Re: [O] Plotting in Python block won't over-write existing > file > Message-ID: <87sidi9bjh@alphaville.usersys.redhat.com> > Content-Type: text/plain; charset=utf-8 > > Richard Stanton wri

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Aloha Richard, Richard Lawrence writes: > Hi Tom and all, > > t...@tsdye.com (Thomas S. Dye) writes: > >> As I see it, the choice boils down to the relative benefit of citation >> shortcuts vs. the limitation of requiring authors to configure the >> citation manager so it doesn't produce a key e

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Hi Tom and all, t...@tsdye.com (Thomas S. Dye) writes: > As I see it, the choice boils down to the relative benefit of citation > shortcuts vs. the limitation of requiring authors to configure the > citation manager so it doesn't produce a key ending in punctuation (or > your solution that uses d

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Gregor Zattler writes: > Sadly no: I reapplied `org-repair-property-drawers' on my org > file with no customisation at all: > > emacs-snapshot -Q -nw -L /home/grfz/src/org-mode/lisp/ file.org > ~/src/org-mode/etc/ORG-NEWS > > I loaded `org-repair-property-drawers' from > ~/src/org-mode/etc/ORG-N

Re: [O] Bleeding edge in elpa

Rasmus writes: >> You can use a tarball and the support for manual builds, described in: >> http://orgmode.org/worg/dev/org-build-system.html#sec-7 > > I have no desire to use anything more than what comes with emacs-24-nox on > this system. You can download any git commit directly from orgmode.or

Re: [O] Bleeding edge in elpa

Achim Gratz writes: > Rasmus writes: >> I agree. I have the same problem when I build documents (via CI) on a >> remote Debian server where I don't want to mess around with anything more >> than what comes with Emacs by default. > > You can use a tarball and the support for manual builds, descri

Re: [O] Bleeding edge in elpa

Rasmus writes: > I agree. I have the same problem when I build documents (via CI) on a > remote Debian server where I don't want to mess around with anything more > than what comes with Emacs by default. You can use a tarball and the support for manual builds, described in: http://orgmode.org/wor

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Hi Nicolas, * Nicolas Goaziou [08. Mar. 2015]: > Unfortunately it doesn't ring a bell. > > Running `org-repair-property-drawers' on your file repairs it. Would it > be related to `org-inlinetask' (i.e., different behaviour if the library > is loaded or not)? Sadly no: I reapplied `org-repair-pr

Re: [O] Bleeding edge in elpa

Hi, tftor...@tftorrey.com (T.F. Torrey) writes: > I want to collaborate on Org files with my wife and parents, ^^^ Do you? It sounds cool! > In a real-world situation, I want to collaborate on Org files with my > wife and parents, and I want to use the current best version of Org >

Re: [O] Bleeding edge in elpa

A major benefit of an ELPA version of the "bleeding edge" version of Org is that it enables those of us who run Emacs and Org on machines where we can not install git (or just do not want to) to have the latest version of Org nonetheless. In a real-world situation, I want to collaborate on Org fil

Re: [O] Bleeding edge in elpa

Nikolai Weibull writes: >> Having both a stable and >> an unstable version of Org avilable via ELPA is a non-starter for the >> simple reason that the package manager can't deal with the versioning >> problems this would introduce. > > This could, I assume, and was sort of implied in my original

Re: [O] Bleeding edge in elpa

On Sun, Mar 8, 2015 at 6:59 PM, Achim Gratz wrote: > Nikolai Weibull writes: >> Is trying to manage it via git+make oneself less likely to cause >> incidents? > There's a bunch of people who seem to manage it just fine. Did I say otherwise? Does this preclude making an alternative available, on

Re: [O] Bleeding edge in elpa

Nikolai Weibull writes: > Is trying to manage it via git+make oneself less likely to cause > incidents? There's a bunch of people who seem to manage it just fine. > From the FAQ: > > The master branch of the git repository always contains the bleeding > edge development code. This is important fo

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

t...@tsdye.com (Thomas S. Dye) writes: Bibtex.el is not that hard to configure. I think I have something like this to configure FIRSTAUTHOR-YY (without the hyphen): (setq bibtex-autokey-titlewords 0 bibtex-autokey-titlewords-stretch 0 bibtex-autokey-titleword-length 0 b

Re: [O] Zotero csl file that uses parenthetical style for citations

Aloha Vaidheeswaran C, Vaidheeswaran C writes: > On Sunday 08 March 2015 09:29 AM, Thomas S. Dye wrote: > >> Is your doubt about his eventual success founded in a general >> skepticism about predicting the future (certainly warranted), >> or in some particular knowledge about the difficulty of t

Re: [O] Bleeding edge in elpa

On Sun, Mar 8, 2015 at 3:17 PM, Aaron Ecay wrote: > IMO this is a bad idea. The bleeding edge version is expected to be > somewhat unstable, and exposing it via ELPA will lead to foot-shooting > incidents. Is trying to manage it via git+make oneself less likely to cause incidents? >From the FA

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Aloha Rasmus, Rasmus writes: > t...@tsdye.com (Thomas S. Dye) writes: > >> Rasmus writes: >> >>> Nicolas Goaziou writes: >>> > I'm asking because I haven't fully grasped uses for the shorthand. What > is the use case? More readable, I guess. >>> >>> I agree. In time, "org-r

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Hello, Gregor Zattler writes: > I invoked org-repair-property-drawers on a fairly large org-mode > file. It did sort some PROPERTIES drawers in front of LOGBOOK > ones but not all. Since I do not understand the logic of > org-repair-property-drawers I prepared a file with the structure > of th

Re: [O] Bug: org-habit treats all repeat tasks as ".+" type [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]

Leo He writes: > On the other hand, I am writing a shell script to move each entry's > PROPERTIES drawer to its beginning. Though I think elisp can handle this > more easily, I am not familiar with it (still learning :-) ). I wonder if > there is an existing function or script to do this. See OR

Re: [O] [ox-ascii, bug] TOC-keyword doesn't work

Hello, Rasmus writes: > Consider the following file: > > #+OPTIONS: toc:nil author:nil > * h1 > #+TOC: headlines 2 > * h2 > ** h3 > > Expected output includes the TOC. Actual output is > > 1 h1 > > > Table of Contents > ─ > > > 2 h2 > > > 2.1 h3 > ── > > The

[O] [ox-ascii, bug] TOC-keyword doesn't work

Hi, Consider the following file: #+OPTIONS: toc:nil author:nil * h1 #+TOC: headlines 2 * h2 ** h3 Expected output includes the TOC. Actual output is 1 h1 Table of Contents ─ 2 h2 2.1 h3 ── The TOC is there when #+OPTIONS: toc:t, but then you can't decid

Re: [O] Multicite syntax

Vaidheeswaran C writes: >> Note that, as a consequence, the new object is incompatible with the >> previous one, since every citation is a multi-cite citation. See >> commit message for details. > > Just a quick feedback. > > (:parenthetical nil :begin 807 :post-blank 0 :end 843 :references >

Re: [O] [ox-ascii, bug?] aligning text withing footnotes

Rasmus writes: > What I want to do is simpler. I want to subtract the length between [1] > and [fn:1] from every line between :begin and :end of the > footnote-definition. Differences other than the three character > difference between [fn:1] and [1] I don't care about. This is not simpler. Ex

Re: [O] Beamer Hello World Help Request

FWIW, I was a complete noob and was exporting to a Latex PDF (C-c C-e l p) instead of a Beamer PDF (C-c C-e l P). Sorry for spamming the list! On Sat, Mar 7, 2015 at 7:50 PM, Matthew Gidden wrote: > Hi folks, > > I've been trying to follow the getting started tutorials >

Re: [O] Bleeding edge in elpa

Hi Nikolai, IMO this is a bad idea. The bleeding edge version is expected to be somewhat unstable, and exposing it via ELPA will lead to foot-shooting incidents. On the other hand, it would be nice to have more regular releases from master to maint. AFAIK the last one was a year and a half ago

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

t...@tsdye.com (Thomas S. Dye) writes: > Rasmus writes: > >> Nicolas Goaziou writes: >> I'm asking because I haven't fully grasped uses for the shorthand. What is the use case? >>> >>> More readable, I guess. >> >> I agree. In time, "org-reftex" would insert @key if no notes are >> r

Re: [O] Multicite syntax

I have fixed up ox-jabref.el to support multicites. Only common prefixes and suffixes are handled. I don't know how to handle per-key prefix/suffix-es. If someone has any complaints about the output, please write to me. Attaching files that I have used for testing. (Author-Date file lacks yea

Re: [O] Small bug? org-narrow-to-subtree and open file link

James K. Lin writes: > By default, Org mode does not work well with indirect buffers. You could get > around this by rolling your own version of functions on your own to ignore > the base buffer. This is no small feat because the link navigation commands > are nested. I understand... thanks for

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence writes: > Like I said, this seems like an edge case, and I don't see that it > is necessarily Org's responsibility to accommodate the keys produced > by Zotero in such edge cases. And there is a significant benefit to > *not* accommodating such keys: namely, you can use in-text c