Hello all,
I have recently started using pabbrev again. However, I found that
using orgstruct mode within Message buffers (in gnus) caused pabbrev to
not work properly. Not sure why (something to pursue later).
So I decided to not enable orgstruct mode. However, by doing so, I get
the followin
Hello,
Christopher Culver writes:
> I am running org-mode 8.2.10 from elpa on Emacs 24.4. When I try to
> export to ODT format with the keystrokes described here:
>
> http://orgmode.org/manual/ODT-export-commands.html
>
> I get an error. Indeed, when I press C-c C-e, ODT is not even mentioned
Christopher Culver writes:
> I am running org-mode 8.2.10 from elpa on Emacs 24.4. When I try to
> export to ODT format with the keystrokes described here:
>
> http://orgmode.org/manual/ODT-export-commands.html
>
> I get an error. Indeed, when I press C-c C-e, ODT is not even mentioned
> among th
On Mon, Nov 10, 2014 at 3:04 PM, Grant Rettke wrote:
> On Mon, Nov 10, 2014 at 11:03 AM, Ista Zahn wrote:
>> On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry wrote:
>>> On Mon, 10 Nov 2014, Andreas Leha wrote:
>>
>> [snip]
>>
>>>
>>
>> Nonetheless, from a literate programming perspecti
I am running org-mode 8.2.10 from elpa on Emacs 24.4. When I try to
export to ODT format with the keystrokes described here:
http://orgmode.org/manual/ODT-export-commands.html
I get an error. Indeed, when I press C-c C-e, ODT is not even mentioned
among the formats that I can export to, I am offe
On Mon, Nov 10, 2014 at 2:45 PM, Thomas S. Dye wrote:
> Grant Rettke writes:
>
>>
>> My approach here has been to use "hidden" source blocks that aren't
>> exported but make it
>> really easy to see the result during development. These settings
>> should work on any configuration,
>> so I didn't
Grant Rettke writes:
>
> My approach here has been to use "hidden" source blocks that aren't
> exported but make it
> really easy to see the result during development. These settings
> should work on any configuration,
> so I didn't include mine here.
I think you've set the :session header argum
On Mon, Nov 10, 2014 at 11:03 AM, Ista Zahn wrote:
> On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry wrote:
>> On Mon, 10 Nov 2014, Andreas Leha wrote:
>
> [snip]
>
>>
>
> Nonetheless, from a literate programming perspective, I think that
> replaceable (and raw) inline results are
* Dominic Surano wrote:
>
> be able to quickly pull up an agenda view that shows each entry on the day /
> time it was created.
I am using (org-expiry-insinuate) from the org-expiry.el and have
those CREATED properties within my capture templates.[1]
HTH
[1] https://github.com/novoid/dot-emacs
Hi Xavier,
Xavier Garrido writes:
> I'm trying to move to =org-agenda= and I'm converting some of my
> Google Calendar entries into Org agenda entries. I'm facing an issue
> with repeated tasks and how to properly stop the event. Consider the
> following entry :
>
> * [Master 1] Nuclear & partic
Dear Orgers,
I'm trying to move to =org-agenda= and I'm converting some of my Google
Calendar entries into Org agenda entries. I'm facing an issue with
repeated tasks and how to properly stop the event. Consider the
following entry :
* [Master 1] Nuclear & particle class
<2015-01-21 mer. 14:
On Mon, Nov 10, 2014 at 11:23 AM, Charles C. Berry wrote:
> On Mon, 10 Nov 2014, Andreas Leha wrote:
[snip]
>
Nonetheless, from a literate programming perspective, I think that
replaceable (and raw) inline results are definitely desirable.
Regardless of the state of their imp
With the error, I had installed emacs like this:
brew reinstall emacs --HEAD --cocoa --srgb
That built Emacs on my yosemite mac.
Just verified that this build corrects the issue. So the issue could be
with core emacs.
http://emacsformacosx.com/builds
FileVersionDateArchitectureBuilt OnSizeEmacs-
Org-mode version 8.2.3c (release_8.2.3c-249-g85d28b.dirty @
/Users/justin/forks/org-mode/lisp/)
GNU Emacs 25.0.50.1 (x86_64-apple-darwin14.0.0, NS appkit-1343.14 Version
10.10 (Build 14A389)) of 2014-11-10 on JustinMbp-2.local
To reproduce:
1. Open up org file
2. export to markdown, buffer
Debugg
On Mon, 10 Nov 2014, Andreas Leha wrote:
Hi Sebastien,
Sebastien Vauban writes:
Andreas Leha wrote:
Sebastien Vauban writes:
Andreas Leha wrote:
For me, that's the correct behavior, as inline code blocks are
*only expected to be evaluated during export*.
I disagree here.
[snip]
N
Brett Witty writes:
> Seems like a good solution. Although how about HEADLINE_LEVEL,
> OUTLINE_LEVEL or some abbreviation to make it more unlikely to clash with
> user defined properties?
I stripped all meta-data from "ITEM" special property in master.
However, I kept the stars as they inform ab
Nick Dokos writes:
> Sharon Kimble writes:
>
>> I am able to 'remember' text with highlighting the text required, and
>> copying it to the clipboard, and then "C-c r" remembers it, and shows in
>> its popup buffer that I need to "C-c C-c" to copy/move it to my remember
>> storage file. Except, t
On 10/11/14 14:18, Ian Barton wrote:
On 06/11/14 20:20, Dominic Surano wrote:
I'm a huge fan of Org-mode and have been using it daily for a little
over a
year. I've been following this list for about 8 months and really benefit
from
the level of technical discussion. I've finally encountered a m
On 06/11/14 20:20, Dominic Surano wrote:
I'm a huge fan of Org-mode and have been using it daily for a little over a
year. I've been following this list for about 8 months and really benefit
from
the level of technical discussion. I've finally encountered a methodology
problem that I haven't quit
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> Isn't that somehow duplicate with `org-indent-mode' (which I don't
>> enable either)?
>
> `org-indent-mode' sets `org-adapt-indentation' to nil _and_ indents
> virtually (no modification to the document) body as if
> `org-adapt-indentation' was
Sebastien Vauban
writes:
> Isn't that somehow duplicate with `org-indent-mode' (which I don't
> enable either)?
`org-indent-mode' sets `org-adapt-indentation' to nil _and_ indents
virtually (no modification to the document) body as if
`org-adapt-indentation' wasn't nil.
There's no duplication
Hi Sebastien,
Sebastien Vauban writes:
> Andreas Leha wrote:
>> Sebastien Vauban writes:
>>> Andreas Leha wrote:
> For me, that's the correct behavior, as inline code blocks are
> *only expected to be evaluated during export*.
I disagree here.
>>>
>>> Though, this is what Eric
Andreas Leha wrote:
> Sebastien Vauban writes:
>> Andreas Leha wrote:
For me, that's the correct behavior, as inline code blocks are
*only expected to be evaluated during export*.
>>>
>>> I disagree here.
>>
>> Though, this is what Eric Schulte wrote:
>>
>> ┌
>> │ Currently inlin
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> It does work perfectly on the "meta-stuff" (SCHEDULED, DEADLINE,
>> etc.). Though, it moves as well the "body" text -- while I'm not using
>> `org-indent-mode'.
>>
>> * New section
>>
>> * The SCHED will be moved
>> SCHEDULED: <2011-08-18 Thu
Hi,
Sebastien Vauban writes:
> Andreas Leha wrote:
>>> For me, that's the correct behavior, as inline code blocks are *only
>>> expected to be evaluated during export*.
>>
>> I disagree here. As limiting the use of inline code to
>> eval-on-export-only renders all the org-babel-execute-subtree a
Hello,
Up to recently, with the following customization:
--8<---cut here---start->8---
(setq org-todo-keywords
'((sequence "NEW(n!)" "TODO(t!)" "STRT(s!)" "WAIT(w!)" "SDAY(y!)"
"|" "DONE(d!)" "CANX(x!)")
(sequence "QTE(q!
Sebastien Vauban
writes:
> It does work perfectly on the "meta-stuff" (SCHEDULED, DEADLINE,
> etc.). Though, it moves as well the "body" text -- while I'm not using
> `org-indent-mode'.
>
> * New section
>
> * The SCHED will be moved
> SCHEDULED: <2011-08-18 Thu>
>
> ** This one won't be move
Andreas Leha wrote:
>> For me, that's the correct behavior, as inline code blocks are *only
>> expected to be evaluated during export*.
>
> I disagree here. As limiting the use of inline code to
> eval-on-export-only renders all the org-babel-execute-subtree and
> related functionality useless.
T
Hello Nicolas,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> One question, now that this syntax is stabilized, can the following
>> long-standing bug be fixed: sometimes the SCHEDULED line (or
>> DEADLINE, or ...) is moved synchronously with the heading when
>> promoting/demoting, sometim
Christian Moe writes:
>>> Going by the documentation of org-odt-use-date-fields, the data styles
>>> "OrgDate1" and "OrgDate2" are supposed to be mapped from
>>> org-time-stamp-custom-formats, rather than
>>> org-export-date-timestamp-format.
>>
>> Yeah, I saw that, but the description of
>> `or
Hi
Sebastien Vauban writes:
> Nicolas Goaziou wrote:
>> Hello,
>>
>> mcg writes:
>>
>>> I use inline code for simple calculations to insert numeric results into
>>> text apart from "normal" code blocks for more complex calculations and
>>> graphics (all in R).
>>>
>>>
>>> The :results replace op
Nicolas Goaziou wrote:
> Hello,
>
> mcg writes:
>
>> I use inline code for simple calculations to insert numeric results into
>> text apart from "normal" code blocks for more complex calculations and
>> graphics (all in R).
>>
>>
>> The :results replace option is not working for inline code, even
Richard Kim writes:
> Thanks for your feedback. I agree that using the same link type is better.
> Hence I took an alternate approach as detailed in the attached patch.
> Enhanced org-info-follow-link to attempt index lookup if node lookup fails.
> Following is my check in message found in the
El Mon, 10 Nov 2014 08:08:51 +0100 Bernhard Pröll va escriure:
>
> I have been curious too and found this file:
>
> https://bitbucket.org/blais/beancount/src/tip/examples/tutorial/example.beancount
Exactly. The first line defines org mode:
;; -*- mode: org; mode: beancount; -*-
[Forgot to "reply all", so part of the below discussion happened
off-list. Sorry. Back on track now. CM]
Rasmus writes:
> Hi Christian,
>
> Thanks for the helpful email. Note that you did not sent it to the
> ML, though.
>
> Christian Moe writes:
>
>> Going by the documentation of org-odt-use-
Sharon,
a reference to another possibly useful tutorial was posted to the ledger
newsgroup a while ago:
From: Simon Michael
Subject: Re: ledger basics and habits
Newsgroups: gmane.comp.finance.ledger.general
To: ledger-cli-/jypxa39uh5tlh3mboc...@public.gmane.org
Date: Sun, 22
36 matches
Mail list logo
