+1.
No hurry.
Yours,
Christian
On 7/26/11 5:15 PM, Thomas S. Dye wrote:
Bastien writes:
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
Aloha all,
Perhaps they are [[tag:boxed][already]] here with org-add-link-type? It
seems to me that all that's missing is a way to specify a function t
Bastien writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> Perhaps they are [[tag:boxed][already]] here with org-add-link-type? It
>> seems to me that all that's missing is a way to specify a function to
>> determine on screen display. But, I might be missing som
Bastien writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> Perhaps they are [[tag:boxed][already]] here with org-add-link-type? It
>> seems to me that all that's missing is a way to specify a function to
>> determine on screen display. But, I might be missing som
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> Perhaps they are [[tag:boxed][already]] here with org-add-link-type? It
> seems to me that all that's missing is a way to specify a function to
> determine on screen display. But, I might be missing something.
just as a quick foll
t...@tsdye.com (Thomas S. Dye) writes:
> Bastien writes:
>
>> Hi Florian,
>>
>> Florian Beck writes:
>>
>>> Actually, I meant »tags« in the HTML sense. For example
>>> would call a function during export, which returns, say, its LaTeX
>>> interpretation, another function would be called by font
Bastien writes:
> Hi Florian,
>
> Florian Beck writes:
>
>> Actually, I meant »tags« in the HTML sense. For example
>> would call a function during export, which returns, say, its LaTeX
>> interpretation, another function would be called by font lock (or
>> whatever you use) to determine its on
Hi Florian,
Florian Beck writes:
> Actually, I meant »tags« in the HTML sense. For example
> would call a function during export, which returns, say, its LaTeX
> interpretation, another function would be called by font lock (or
> whatever you use) to determine its on screen display.
Well, I'm
Hi Sébastien,
"Sebastien Vauban" writes:
> Any idea about the reason to make the first asterisk shine with face
> `org-warning'? Could it be `org-hide' face as well?
I guess using the `org-warning' face for the first asterisk of an inline
task helps distinguishing it from normal task.
I'd say
"Sebastien Vauban"
writes:
>>>
>>> 1. people want inline tasks with possibly no TODO keyword
>>
>> This is often how I use them --- to insert a "drawer" of notes that is
>> visible but will not be exported.
>
> Why do you say it wouldn't be exported just because it has no TODO keyword?
> At least
Hi Matt,
Matt Lundin wrote:
> In my experience, most of the asterisks are made invisible by
> org-hide-face. E.g.,
>
> *** TODO A task
> Some notes about the task that are not part of the text.
> *** END
Any idea about the reason to make the first asterisk sh
Hi Matt,
Matt Lundin wrote:
> Bastien writes:
>> "Sebastien Vauban" writes:
>>
* !TODO This would be an inline task, not a headline
>>>
>>> I've no clear cut opinion on this right now. Maybe yes, maybe not.
>>> Though, there are differences between inline tasks and headlines:
>>
>> I'm talk
Bastien writes:
> "Sebastien Vauban" writes:
>
>>> * !TODO This would be an inline task, not a headline
>>
>> I've no clear cut opinion on this right now. Maybe yes, maybe not.
>> Though, there are differences between inline tasks and headlines:
>
> I'm talking about the way they _look_. So man
Hi all,
Nicolas Goaziou writes:
>> 1. people want inline tasks with possibly no TODO keyword
>> 2. people prefer to detect them *very easily*
>> 3. changing the syntax of inline tasks from changing todos
>>(like !TODO) is too complicated code-wise
>
> 4. people do not want to break the main
Florian Beck writes:
> Bastien writes:
>
>>> 2. Tags are SLOW (no doubt due to my 8.5M file). Completion takes
>>> minutes. I fixed that by adding all my (hundreds of) tags to
>>> `org-tag-alist' and restricting capture to »%g«, checking only the
>>> current file. `org-id-find' is slow as we
Bastien writes:
>> 2. Tags are SLOW (no doubt due to my 8.5M file). Completion takes
>> minutes. I fixed that by adding all my (hundreds of) tags to
>> `org-tag-alist' and restricting capture to »%g«, checking only the
>> current file. `org-id-find' is slow as well and so will be property
>>
John Hendy writes:
> I posted something similar a bit back. I do use org for todos, but
> also write papers/reports, and take notes on things I'm reading. You
> might want to check out that thread. [1] In particular, there were
> some great comments about using inline tasks with custom export
>
Hello,
Bastien writes:
> I'm talking about the way they _look_. So many asterisks looks
> cumbersome to mee, and I'd favor a non-intrusive syntax like the
> one proposed above.
>
> My question was: what is the rationale behind using so many asterisks?
>
> I can think of three things:
>
> 1. pe
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" writes:
>>> * !TODO This would be an inline task, not a headline
>>
>> I've no clear cut opinion on this right now. Maybe yes, maybe not.
>
> :)
>
>> Though, there are differences between inline tasks and headlines:
>
> Yep, I know the differences.
Hi Sébastien,
"Sebastien Vauban" writes:
>> * !TODO This would be an inline task, not a headline
>
> I've no clear cut opinion on this right now. Maybe yes, maybe not.
:)
> Though, there are differences between inline tasks and headlines:
Yep, I know the differences.
I'm talking about the wa
Hi Bastien,
Bastien wrote:
> As suggested, you want to check inline tasks.
>
> I really don't like the current syntax for inline tasks, I would much
> prefer something like special TODO keywords:
>
> * !TODO This would be an inline task, not a headline
I've no clear cut opinion on this right now.
Hi Florian,
Florian Beck writes:
> A couple of questions and observations, first impressions really:
>
> 2. Tags are SLOW (no doubt due to my 8.5M file). Completion takes
> minutes. I fixed that by adding all my (hundreds of) tags to
> `org-tag-alist' and restricting capture to »%g«, checking
Florian Beck writes:
Hi, Florian,
My org version is:
Org-mode version 7.5 311b09d92644f39040087327d6a1dbeb09a9ab6e
> I don't want to see todo-keywords and TAGs in
> the output. How do I get rid of them?
In the manual,
Export options.
#+OPTIONS: todo: nil
manual explanation:
#+OPTIONS:
On Mon, Jul 11, 2011 at 2:55 PM, Florian Beck wrote:
> [My main goal is to take research notes and write texts. I have little
> interest in the todo/agenda part of org-mode, which I understand is its
> main focus, so bear this in mind.]
Snipped 1-4, as I don't have anything to add...
> 5. Accor
[My main goal is to take research notes and write texts. I have little
interest in the todo/agenda part of org-mode, which I understand is its
main focus, so bear this in mind.]
Previously I have been using muse-mode for publishing and a home brew
system for organising my notes. Now I thought, I w
24 matches
Mail list logo
