when doing an org-remember, is there a way to get the C-c C-q tags
dialog for tag entry when creating the new entry using an
org-remember-template? I only see tags from completion candidates.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to
Similar to the variable: org-todo-state-tags-triggers // triggers
on|off when gets active...
Is there also something that triggers my tag menu when a gets
active.
Example: When NEXT (todo state) gets active ...I get prompted for one of my
context tags (radio group menu: @home(h), @errands(e),
Andreas Burtzlaff writes:
> Hello everyone,
>
> the idea is now implemented as an extension to org-mode.
>
> Available here: http://www.burtzlaff.de/org-fstree/org-fstree.el
>
> org-fstree inserts the filesystem subtree for a given directory.
> Each file/directory is formatted as a headline, provi
On Sun, Mar 29, 2009 at 12:54:15AM +0100, Andreas Burtzlaff wrote:
> Hello everyone,
>
> the idea is now implemented as an extension to org-mode.
>
> Available here: http://www.burtzlaff.de/org-fstree/org-fstree.el
>
> org-fstree inserts the filesystem subtree for a given directory.
> Each file/
Karl Maihofer writes:
> Hi,
>
> thanks for your answer!
>
> Sebastian Rose schrieb:
>> Yes, this is possible. By default only the first three levels are
>> exported as headlines. Any headline that is deeper nested, is exported
>> as a list item.
>>
>> The variable in question is
>>
>>`org-ex
Changed that variable... works great again.
I remember reading about a setting to auto-indent description text.
On Sun, Mar 29, 2009 at 01:32, Matthew Lundin wrote:
> Bernt Hansen writes:
>
> > Eraldo Helal writes:
> >
> >> I just found out that there is a newline before each headline in the
Bernt Hansen writes:
> Eraldo Helal writes:
>
>> I just found out that there is a newline before each headline in the recent
>> version of org-mode (6.24).
>>
>> Is there a post explaining why this change was made?
>>
>> I have troubles with that, for example:
>>
>> when adding a new headline w
Eraldo Helal writes:
> The problem is that the LOGBOOK item does not move with the headline...
>
> example:
>
> BEFORE
> **
> :LOGBOOK:
> - Created from
> :END:
>
>
> AFTER
>
> :LOGBOOK:
> - Created from
> :END:
>
>
> It does when created by changing to state
> But I
Eraldo Helal writes:
> I just found out that there is a newline before each headline in the recent
> version of org-mode (6.24).
>
> Is there a post explaining why this change was made?
>
> I have troubles with that, for example:
>
> when adding a new headline while looking at the overview...
>
The problem is that the LOGBOOK item does not move with the headline...
example:
BEFORE
**
:LOGBOOK:
- Created from
:END:
AFTER
:LOGBOOK:
- Created from
:END:
It does when created by changing to state
But I did also find out that this is a general problem! (not reme
Evening,
On 28 Mar 09, Eraldo Helal wrote:
>
> If I create it with my remember template however...
>
> ("inbox" ?i "* %^{topic}%i\n:LOGBOOK:\n- Created: %U from
> %a\n:END:\n%?" "inbox.org" "stuff")
>
> then it is all the way in the left margin (first char)
> and it does not move when the
Hey there,
I just switched to using the development version of org-mode (rather than
the synaptic package), and now have an issue with org-agenda. Whenever I
filter the agenda by tag and then refresh the agenda or move to a new view
(functionally, refreshing it) the filter is no longer applied. In
Hello everyone,
the idea is now implemented as an extension to org-mode.
Available here: http://www.burtzlaff.de/org-fstree/org-fstree.el
org-fstree inserts the filesystem subtree for a given directory.
Each file/directory is formatted as a headline, provides links back
to all headlines that ar
I just found out that there is a newline before each headline in the recent
version of org-mode (6.24).
Is there a post explaining why this change was made?
I have troubles with that, for example:
when adding a new headline while looking at the overview...
the newline does not get made...
and th
Karl Maihofer schrieb:
> #+HTML:
>
> I think, this should work for me.
>
> The only problem now is to exclude the TODO from the HTML-generated
> Table of Contents. Using "#+EXPORT_EXCLUDE_TAGS: exclude" does not work.
> Perhaps a bug in the html-export?
Sorry, no bug, of course. When I mark the
If the :LOGBOOK: property gets created via TODO state change...
; log state changes into a drawer (introduced in Orgmode 6.23)
(setq org-log-into-drawer "LOGBOOK")
> the :LOGBOOK: item is indented (has as many spaces to the left as the
headline) and gets moved(left right) together with the headli
Hi Carsten,
When I export a footnote that begins with emphasis/italics markup, the
markup is not converted to \emph in the LaTeX output.
E.g., the following source...
--8<---cut here---start->8---
#+title: Test
This is a footnote.[fn:footnote]
[fn:footnote]
Hi,
thanks for your answer!
Sebastian Rose schrieb:
> Yes, this is possible. By default only the first three levels are
> exported as headlines. Any headline that is deeper nested, is exported
> as a list item.
>
> The variable in question is
>
>`org-export-headline-levels'
OK, I see. But
I can't think of a good way to make the TODO items inline for HTML
export, as the result is a list. Note, that the element has to be
closed to have valid XHTML (wich means we can't use a CSS selector
`p ul' here to make it inline):
=> --->8->8-
Karl Maihofer writes:
> Perhaps it is possible to define TODOs as a very deep-level heading,
> that isn't needed, like "** TODO text" and change the export
> function that this level isn't exported as a heading but as a
> "div"-Container? Or every heading that contains "TODO" is not expor
Hi,
I write some articles in Org-Mode and use the html and latex export
function. I'm wondering about how to define TODOs within the text the
best way. I hope my bad english lasts to explain what I mean exactly:
I'd like to define a TODO like in the example below. When there is a
task somewhere i
Hi Eraldo,
Eraldo Helal writes:
> Mike Newman newmanfamily.me.uk> writes:
>
>> When you use the standard commands to add/removes files from the
>> agenda, it will write a definition for the variable org-agenda-files to
>> the custom section of your .emacs file.
>
> That would still mean remov
Mike Newman newmanfamily.me.uk> writes:
> When you use the standard commands to add/removes files from the
> agenda, it will write a definition for the variable org-agenda-files to
> the custom section of your .emacs file.
That would still mean removing every org-file in the tree manually when
23 matches
Mail list logo