Hi, Org people.
The manual, section "8.3.2 Repeated tasks", says:
Some tasks need to be repeated again and again. Org mode helps to
organize such tasks using a so-called repeater in a DEADLINE, SCHEDULED,
or plain timestamp.
Examples and directions given in the page are related to DEAD
On 15.9.2013, at 21:06, Sebastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>>> When moving with C-c C-v C-n (or p) from one code block to the next (or
>>> previous), it's much better if the code block gets centered (vs hidden,
>>> forcing the user to scroll down, as it currently i
On 2013-09-14 13:42 , Jambunathan K wrote:
(add-hook 'org-mode-hook
(lambda nil
(local-unset-key [menu-bar Org])))
Thanks, if I do this for my derived mode, it does exactly what I need!
Christian
--
Christian Wittern, Kyoto
Hi,
consider the following very simple org file:
* TODO Thing1[]
where "[]" marks where the point is. Now if I C-S-RET to insert a new
TODO heading, I get
* TODO Thing1
* TODO []
Note that there is a trailing space at the end of the last line, as
expected. The problem is that if I now press C-
Julien Cubizolles writes:
> How can I change the default packages used in the latex file generated
> by org-preview-latex-fragment ?
>
They are produced by the function org-create-formula--latex-header,
which uses the variables
org-latex-default-packages-alist
org-latex-packages-al
"Sebastien Vauban"
writes:
> Paul Rudin,
>
> Paul Rudin wrote:
>> I'm not clear on how these two are intended to be used. The former
>> prefixes the timestamp with "SCHEDULED:" but I'm not sure what practical
>> consequences this has. Items appear in the agenda either way.
>
> You should absolute
Paul Rudin,
Paul Rudin wrote:
> I'm not clear on how these two are intended to be used. The former
> prefixes the timestamp with "SCHEDULED:" but I'm not sure what practical
> consequences this has. Items appear in the agenda either way.
You should absolutely read the chapter 8 ("Dates and Times"
Julien Cubizolles wrote:
> org-src-fontify-natively doesn't fontify quoted LaTeX code like
>
> #+BEGIN_LaTeX
> #+END_LaTeX
>
> the same as it does for LaTeX src blocks like
>
> #+BEGIN_SRC latex
> #+END_SRC
>
> Why is that, and is there a way to get fontification for both ?
Yes, you have different
Hi Carsten,
Carsten Dominik wrote:
>> When moving with C-c C-v C-n (or p) from one code block to the next (or
>> previous), it's much better if the code block gets centered (vs hidden,
>> forcing the user to scroll down, as it currently is).
>>
>> This is the purpose of this easy patch.
>
> I don
I'm not clear on how these two are intended to be used. The former
prefixes the timestamp with "SCHEDULED:" but I'm not sure what practical
consequences this has. Items appear in the agenda either way.
Updated patch. Tiny commit message format fix.
>From c46db11ffe0cc0f9b4fbd5a1ede2b4be0175 Mon Sep 17 00:00:00 2001
From: Ian Kelling
Date: Sun, 15 Sep 2013 00:32:08 -0700
Subject: [PATCH] Make the point visible when jumping to the mark
* lisp/org.el: advise `pop-global-mark', `exchange-point
Updated patch, fixed commit message format.
>From 0c23ccb9b00fd42f830f5a7472e2980b93c6040f Mon Sep 17 00:00:00 2001
From: Ian Kelling
Date: Sun, 15 Sep 2013 08:03:24 -0700
Subject: [PATCH] Fix incorrect time calculation for `org-extend-today-until'
* lisp/org-clock.el (org-clock-get-sum-start):
Hi List,
I now got a first working version of code that transforms the parse-tree
produced by `org-element-parse-buffer' into a normalized form - in the
sense that special Emacs Lisp syntax is converted into plain standard
Lisp syntax:
The transformation steps can be seen in this code excerpt fr
During the extra hours of org-extend-today-until, when
org-clock-mode-line-total is 'today, the clocked time shown in the
modeline is wrong. It ignores all previously clocked time, when it
should add them starting from the past day beyond
org-extend-today-until hours. This also affects clock tabl
On Sun, Sep 15, 2013 at 5:57 AM, Suvayu Ali wrote:
> On Sat, Sep 14, 2013 at 09:49:18PM -0500, John Hendy wrote:
>>
>> In any case, I'm mostly in agreement that Org's changed and thus the
>> file structure should change... but not all of us use the git and/or
>> snapshot Org version with regular f
2013/9/15 Carsten Dominik :
>
> Does anyone know about conflicts arising from loading wrapfig and rotating?
>
Not that I know of.
How can I change the default packages used in the latex file generated
by org-preview-latex-fragment ?
Julien.
On Sat, Sep 14, 2013 at 10:28 AM, Eric S Fraga wrote:
> Matt Price writes:
>> Unfortunatey, I'm exporting to HTML (deck.js) not Beamer. I guess I
>> still on't understand how to use beamer -- I tried it just now and it
>> seemed to produce a very plain pdf, not a slideshow at all. sigh.
>
> It
Hi Christoph and others,
On Sun, Sep 15, 2013 at 01:41:32PM +0200, Carsten Dominik wrote:
>
> On 15.9.2013, at 13:07, Christoph LANGE wrote:
>
> > Dear all,
> >
> > many thanks for your extensive feedback. You more than answered my
> > question: I conclude for myself that it is not a good ide
aditya siram writes:
> I've included new versions of both patches with most of the changes you
> suggested. I guess you'll apply the longer one when you've been notified by
> the FSF?
>
Once you receive your confirmation from the FSF please let Bastien or
Carsten know, and they'll add you to the
aditya siram writes:
> Thanks for your feedback and your work on org-babel!
>
I'm happy you're finding it useful.
>
> Oops, the maintain-point was a hold-over and isn't actually used in the
> code. I'll remove it.
>
> I will incorporate your suggestions.
>
> However, regarding the cascading if
On 15.9.2013, at 13:07, Christoph LANGE wrote:
> Dear all,
>
> many thanks for your extensive feedback. You more than answered my
> question: I conclude for myself that it is not a good idea to use Org
> tree entries if one wants list items. This was "accidentally" supported
> by the old expo
Dear all,
many thanks for your extensive feedback. You more than answered my
question: I conclude for myself that it is not a good idea to use Org
tree entries if one wants list items. This was "accidentally" supported
by the old exporter, but with the new exporter it makes sense to
manually (or
On Sat, Sep 14, 2013 at 09:49:18PM -0500, John Hendy wrote:
>
> In any case, I'm mostly in agreement that Org's changed and thus the
> file structure should change... but not all of us use the git and/or
> snapshot Org version with regular frequency and thus I expect a fair
> amount of trickling i
An example of the problem:
* headline-1
** one of many headlines I want to remain folded...
** headline
*** headline
The point starts here. I set a mark on this line.
Then I fold headline-1. This becomes invisible.
* headline-2
I move the point here. After I'm done here, I want to go back to my
m
25 matches
Mail list logo
