Carsten,
I took a closer look at column view today and really liked what I saw.
It seems to have gotten a lot better since I tried it on 5.01, but it
may just be that I understood the implementation this time around.
I think it works very well and I am very surprised it hasn't gotten
more use. I
On 10/11/07, Carsten Dominik <[EMAIL PROTECTED]> wrote:
> Changes in Version 5.12
> ---
>- The variable `org-ellipsis' now defaults to `org-link'.
What are your thoughts on making this clickable, with RET and mouse? I
don't know, the link face makes it looks like it should
Hi,
Can/should we add more options to org-log-done, or maybe create a new
variable org-log-state, to specify what state changes need to be logged.
I have very fixed TODO state settings for all my org files and wish to
avoid using in-buffer options for that. I just wonder how many people
feel
On Oct 12, 2007, at 19:20, Richard G Riley wrote:
I have a possible bug here (5.12). When embedding the CATEGORY as a
property e.g in my org file
Yes, logging state changes is broken in 5.12, *#$&*&#&$.
Fixed in 5.12c, thanks.
,
| '(org-agenda-custom-commands
|(quote (
| (
Carsten Dominik <[EMAIL PROTECTED]> writes:
> On Oct 12, 2007, at 17:04, Richard G Riley wrote:
>>
>> Yes. The concept of not having to worry about where things are in the
>> org file doesn't really work for me. I like things having a certain
>> category in that category section - otherwise there
Rainer Stengele <[EMAIL PROTECTED]> writes:
> I also do not expect to grow Org into anything near a "full" PM.
> But I do would be more than glad to get some basic (trigger or blocker)
> functionality to model dependencies between todos.
I would think that setting these up initially would require
On Oct 12, 2007, at 17:04, Richard G Riley wrote:
Yes. The concept of not having to worry about where things are in the
org file doesn't really work for me. I like things having a certain
category in that category section - otherwise there seems little point
in having lines like
,
| * Emac
pete phillips <[EMAIL PROTECTED]> writes:
> org-mode developed as a means of maintaining lists, and it excels at
> this. Just because the GTD methodology uses the term Project doesn't
> mean that we should turn org-mode into a fully fledged project
> planning application. If you need project plann
About TODO state, tags and properties in Org-mode
In a recent message to emacs-orgmode, Richard G Riley asked for
more background about the concept of properties and their
relation to tags. Let me try to take a step back and explain
these concepts together.
Every node in an Org-mode ou
Hi all,
I keep getting the following error after performing a M-x remember,
entering some text in the new buffer and pressing C-c C-c. The
following error occurs on the final C-c C-c.
(error "Invalid search bound (wrong side of point)")
As far as I know I have the configuration setup as spe
Richard G Riley <[EMAIL PROTECTED]> writes:
> Completion doesnt work for me. Possibly this is a result of using
> icicles? You just TAB to completion?
Can you please provide more details:
What version of Org-mode?
What did you do?
What did you expect?
What did you get instead?
> This might
Carsten Dominik <[EMAIL PROTECTED]> writes:
> You can add a category property to the entry, and that will overrule the
> category that might be inherited from above. With the latest org-mode
> 5.12,
> press `C-c C-x p'. This will prompt you for a property name, enter
> CATEGORY
> (using completi
On Oct 12, 2007, at 16:12, Richard G Riley wrote:
Bastien <[EMAIL PROTECTED]> writes:
Richard G Riley <[EMAIL PROTECTED]> writes:
The CATEGORY property does the same job than the old #+CATEGORY,
except
that its scope is well defined, i.e. we don't need to bother
anymore on
where #+CATEGOR
Bastien <[EMAIL PROTECTED]> writes:
> Richard G Riley <[EMAIL PROTECTED]> writes:
>
>>> The CATEGORY property does the same job than the old #+CATEGORY, except
>>> that its scope is well defined, i.e. we don't need to bother anymore on
>>> where #+CATEGORY has to be.
>>
>> Did you before?
>
> IIR
Richard G Riley <[EMAIL PROTECTED]> writes:
>> The CATEGORY property does the same job than the old #+CATEGORY, except
>> that its scope is well defined, i.e. we don't need to bother anymore on
>> where #+CATEGORY has to be.
>
> Did you before?
IIRC this was a recurrent issue on this list.
>> ,
Stuart McLean <[EMAIL PROTECTED]> writes:
> I think this might be a typo in the file `org-install.el', line 56:
>
> (autoload 'org-show-toc "org-toc" "Create and display a table of contents"
> t)
>
> Shouldn't this be `org-toc-show'?
Yes, it should. Thanks!
--
Bastien
Hi,
firstly, thanks for Org-mode, I live in this mode, so to speak ;-)
I think this might be a typo in the file `org-install.el', line 56:
(autoload 'org-show-toc "org-toc" "Create and display a table of contents" t)
Shouldn't this be `org-toc-show'?
Regards,
Stuart
__
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> I can't say I have any plans to use triggers, but will they really
> hurt anything? I mean if it makes the code a mess then that wouldn't
> be good. But frankly, I have no need for the GTD 'find a stuck
> project' stuff, and it hasn't been a proble
Gijs Hillenius <[EMAIL PROTECTED]> writes:
> But maybe I should not :-). But here goes: I plan to start working on
> an item by date X -> schedule stamp. The item has a deadline, so ->
> deadline.
For that I use `org-deadline-warning-days'. I start the deadline when
it shows up in my agenda. Th
Richard G Riley <[EMAIL PROTECTED]> writes:
>> You could set a :CATEGORY: property for entry.
>>
> How do you do that?
Please check (info "(Org)Property syntax") to know more about
properties.
> | #+CATEGORY: Emacs
Although this is still supported, you can now use this:
,
| * A headline h
On 12 Oct 2007, Bastien wrote:
>> Or should I maybe simply not use both stamps for the same item?
>
> I don't see why you need both of them. Can you answer that?
Yes.
But maybe I should not :-). But here goes: I plan to start working on
an item by date X -> schedule stamp. The item has a deadli
Gijs Hillenius <[EMAIL PROTECTED]> writes:
> I have a TODO item with both a schedule and a deadline and this
> results in the item appearing twice after the deadline passes in
> my Org weekly Agenda.
Meaning you have to blame yourself twice :)
> Or should I maybe simply not use both stamps for
Carsten Dominik <[EMAIL PROTECTED]> writes:
> First, let me say that I was surprised that quite a few people are so keen
> to see this kind of features. I myself would worry a lot about spending
> more time to set up and maintain these connections, than I would be saving
> by using them. And I a
Bastien <[EMAIL PROTECTED]> writes:
>> * Hardware
>> ** TODO Install
>> * Software
>> ** TODO Install :ADDRESSTHISONE:
>> * Patches
>> ** TODO Install
>>
>> Thats why I thought a GUID property would be required.
>
> I a sense, that shows that having a proper GUID system will only be
> useful in ca
Hi,
"Eddward DeVilla" <[EMAIL PROTECTED]> writes:
> You could set a :CATEGORY: property for entry.
>
> Edd
>
This is different from a tag how?
How do you do that?
At the moment my org file has sections like this:
,
| * Emacs
|
| #+CATEGORY: Emacs
|
|
| * Register
|
| #+CATEGORY: Reg
25 matches
Mail list logo
