Hello,
I didn't know that I could log things like that. Thanks for that hint!
Unfortunately, I would prefer to have only one entry and be sure that it wont
be overwrited by mistake.
Alan
On July 10, 2009 01:36:45 pm Nicolas Goaziou wrote:
> Alan Boudreault writes:
>
>
> Hello,
>
> It's maybe
At Fri, 10 Jul 2009 19:48:20 +0200,
Nicolas Goaziou wrote:
> [...]
> Then again, as someone said, a DEADLINE with an appropriate warning
> delay would be fine in that case too.
I have tasks that have deadlines months in the future and which need
tackling from now until the deadline, although obvio
At Fri, 10 Jul 2009 12:32:59 -0400,
Nick Dokos wrote:
> Quite likely it's a failure of imagination on my part, but I still
> don't see why you would both schedule and deadline an item. Could
> you provide a scenario where that would be useful?
Well, to use an example that I think the OP (Andrew) w
Nick Dokos writes:
> Quite likely it's a failure of imagination on my part, but I still
> don't see why you would both schedule and deadline an item. Could
> you provide a scenario where that would be useful?
I think the OP has a time frame to execute some task. He doesn't want to
be bugged abou
"Andrew M. Nuxoll" writes:
> 1. When I view my agenda for a day it displays TODO items twice if they
> are both SCHEDULED and DEADLINEd (a common occurrence for me). Can this
> be avoided? Here's a generic example snippet from my agenda:
>Thursday9 July 2009
> nux:Schedule
Alan Boudreault writes:
Hello,
It's maybe not what you're looking for, but you can leave org-log-done
to nil and simply define org-todo-keywords with something like :
(setq org-todo-keywords '(sequence "TODO(t)" "|" "FIXED(f!)"))
Nothing should be overwritten then.
HTH,
--
Nicolas Goaziou
Eric S Fraga wrote:
> At Thu, 09 Jul 2009 21:08:31 -0700,
> Andrew M. Nuxoll wrote:
> > In my mind, there is no conflict between scheduling and deadlining.
>
> I agree with you on this point but, in this case, it makes sense for
> both aspects to be highlighted in the agenda view. I would sugge
At Thu, 09 Jul 2009 21:08:31 -0700,
Andrew M. Nuxoll wrote:
> In my mind, there is no conflict between scheduling and deadlining.
I agree with you on this point but, in this case, it makes sense for
both aspects to be highlighted in the agenda view. I would suggest
that you might wish to change (
Stefan Vollmar writes:
> Dear Sebastian,
>
> On 09.07.2009, at 20:25, Sebastian Rose wrote:
>
>> this works here with `emacs -Q'
>>
>> we forgot the load path
>> The function is likely to change some more. I just send this version, so
>> you can compile this way (hopefully).
>
>
> EXCELL
Dear Sebastian,
On 09.07.2009, at 20:25, Sebastian Rose wrote:
this works here with `emacs -Q'
we forgot the load path
The function is likely to change some more. I just send this
version, so
you can compile this way (hopefully).
EXCELLENT - we now have an up-to-date org-mode e
"Holst Thomas (DS-ET/ECF1)" writes:
>
> yes I have transient-mark-mode enabled.
>
> Here is a simpler example to reproduce the bug:
> --8<---cut here---start->8---
> * Kapitel 1
>dingens
>foo bar
> * Kapitel 2
> bar foo
> --8<---cut here---
Hi,
Is it possible to lock the CLOSED tag ? It may happen that I set back a FIXED
tag to TODO by mistake, The problem is that when I re-set it to FIXED, the
closed tag is overwrited. I would like to lock the closed tag as soon as it is
set to a done tag.
Best regards,
Alan
--
Alan Boudreaul
Peter Frings writes:
> On 09 Jul 2009, at 23:32, Matthew Lundin wrote:
>
>> I found it easiest to install the new org files directly to the
>> Emacs.app directory.
>
> I've seen this approach mentioned several times, but I think it makes
> things more complicated then they should be. By keeping t
Hello Matt,
> Von: Matthew Lundin [mailto:m...@imapmail.org]
> Betreff: Re: Bug in LaTeX export
>
> "Holst Thomas (DS-ET/ECF1)" writes:
>> [Problem exporting a subtree with no further subsubtrees]
> Do you have transient-mark-mode enabled? I tested this with Emacs 22
> and when transient-mark-m
"Holst Thomas (DS-ET/ECF1)" writes:
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the end.
>
> He
Karl Maihofer writes:
> Others may correct me but I think this is the same issue I had yesterday. The
> reason is that the two versions of Org - the one shipped with your Emacs and
> the
> latest one you installed by yourself conflict in some way. Some time ago the
> lisp-file for LaTeX export wa
"Holst Thomas (DS-ET/ECF1)" writes:
> Hello,
>
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the
Karl Maihofer writes:
> Others may correct me but I think this is the same issue I had yesterday. The
> reason is that the two versions of Org - the one shipped with your Emacs and
> the
> latest one you installed by yourself conflict in some way. Some time ago the
> lisp-file for LaTeX export w
Hello,
I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
and then export it to LaTeX with C-c C-e L.
If the subtree has no further subtrees the LaTeX-file not only contains
the region, but also the rest of the document to the end.
Here is an example:
,[ test.org ]
| * K
Others may correct me but I think this is the same issue I had
yesterday. The reason is that the two versions of Org - the one shipped
with your Emacs and the latest one you installed by yourself conflict in
some way. Some time ago the lisp-file for LaTeX export was renamed -
perhaps this is wh
Hi
I've only just spotted this error as I don't use the Latex export very
often. When I export as Latex either to file or buffer, I get the
following error:
org-export-latex-lists: Wrong number of arguments: #[(list)
"\"" [list org-list-to-generic (:splicep nil :ostart
"\\begin{enumerate}" :oend
Hi Giovanni,
Giovanni Ridolfi wrote:
> --- Gio 9/7/09, Ulf Stegemann ha scritto:
>> When writing documentations I often
>> come across expressions like
>>
>> doMagic('myVariable')
>>
>> In an ideal world the HTML code for this after exporting the org file
>> would look like this:
>>
>> doMagic
On 09 Jul 2009, at 23:32, Matthew Lundin wrote:
Karl Maihofer writes:
Until now I used Org with Debian GNU/Linux. Today I bought a MacBook
Pro 13" and I spent the evening making my first steps with MacOS. I
installed the Carbon Emacs package and configured Emacs to use the
latest Org-Version
Andrew M. Nuxoll wrote:
Nick Dokos wrote:
Just an FYI (a nice one since Carsten said so :-): Carsten is the first
name, Dominik (no c) is the surname of the creator of Org-mode. And I
promise we'll be nice even after he comes back :-)
Err, whoops!
So let me turn the question around: why do
24 matches
Mail list logo
