[Orgmode] Key maps for remember?
I have about used up all the letters in the alphabet on org-remember keybindings. Now I'm using numbers. Is there any way to assign sequences upon a single key? Like a keymap? Alan Davis "An inviscid theory of flow renders the screw useless, but the need for one non-existent." ---Lord Raleigh (John William Strutt), or else his son, who was also a scientist. It is undesirable to believe a proposition when there is no ground whatsoever for supposing it is true. Bertrand Russell ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: Project definition (WAS: [Orgmode] Re: Emacs-orgmode Digest, Vol 37, Issue 121--)
Hello: On Mon, Mar 30, 2009 at 1:39 AM, Eraldo Helal wrote: >> An interesting question would be how to generalize this to update >> remember templates accordingly. Possibly the best approach would be to >> have a defining form that would define a project in a single >> s-expression, adding both remember templates and agenda entries, and >> then that form could be removed all at once. Something like >> >> (org-add-project newproj >> "A sample new project to show the greatness of org-add-project." >> (agenda-files (find-lisp-find-files "~/newproj/" "\.org$")) >> (remember-templates >> )) >> [The generic subject line made it difficult to find again] This idea has great possibilities. I have wanted some way to define a project that would insert a link in a master file. Alan ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] html export: row/column dividers in tables
Hi Bill, If I understand your post correctly, I think this section of the manual will help to accomplish what you are looking for---i.e., the creation of special vertical lines in tables: http://orgmode.org/manual/Column-groups.html#Column-groups Also you change the appearance of tables using css. Best, Matt Bill White writes: > I recently found a need for visible dividers (or "rules") between the > rows and columns of an org table exported to html. The most recent > discussion of this that I could find on gmane was > http://article.gmane.org/gmane.emacs.orgmode/1709/match=table+rules+html > from 2007, which concluded that such rules weren't supported, so here's > a kludgey workaround I found today: > > #+BEGIN_HTML > > |+++| > | a0 | b0 | c0 | d0 | > |+++| > | a1 | b1 | c1 | d1 | > |+++| > | a2 | b2 | c2 | d2 | > |+++| > > #+END_HTML > > It isn't pretty, but it works when you really need visual separation of > rows and columns. Here's what it looks like in real life: > > http://members.wolfram.com/billw/VerbatimTables.html > > BTW, here's how I got the org-mode code sample onto the webpage: > > #+begin_src org > #+BEGIN_HTML > > |+++| > | a0 | b0 | c0 | d0 | > |+++| > | a1 | b1 | c1 | d1 | > |+++| > | a2 | b2 | c2 | d2 | > |+++| > > #+END_HTML > #+end_src > > Cheers - > > bw ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] html export: row/column dividers in tables
I recently found a need for visible dividers (or "rules") between the rows and columns of an org table exported to html. The most recent discussion of this that I could find on gmane was http://article.gmane.org/gmane.emacs.orgmode/1709/match=table+rules+html from 2007, which concluded that such rules weren't supported, so here's a kludgey workaround I found today: #+BEGIN_HTML |+++| | a0 | b0 | c0 | d0 | |+++| | a1 | b1 | c1 | d1 | |+++| | a2 | b2 | c2 | d2 | |+++| #+END_HTML It isn't pretty, but it works when you really need visual separation of rows and columns. Here's what it looks like in real life: http://members.wolfram.com/billw/VerbatimTables.html BTW, here's how I got the org-mode code sample onto the webpage: #+begin_src org #+BEGIN_HTML |+++| | a0 | b0 | c0 | d0 | |+++| | a1 | b1 | c1 | d1 | |+++| | a2 | b2 | c2 | d2 | |+++| #+END_HTML #+end_src Cheers - bw -- Bill White . bi...@wolfram.com . http://members.wolfram.com/billw "No ma'am, we're musicians." ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] XEmacs complains about a few define-key sequences in org-mouse.el
XEmacs complains about a few define-key sequences in org-mouse.el. For example: (define-key org-agenda-keymap [C-mouse-4] 'org-agenda-earlier) These sequences are using a GNU emacs form that XEmacs does not support. I've patched it like this, which stopped the errors at least: (define-key org-agenda-keymap (if (featurep 'xemacs) [(control mouse-4)] [C-mouse-4]) 'org-agenda-earlier) Here is full set: org-mouse.pat Description: org-mouse.pat thanks --tony ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: How to define TODOs within continuous text the best way?
Carsten Dominik writes: > Fixed, thanks. Awesome! Thanks!! -Bernt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Sorting TODOs with time-up
On Mar 30, 2009, at 11:03 PM, David Engster wrote: Carsten Dominik writes: On Mar 30, 2009, at 4:46 PM, David Engster wrote: Thanks for the clarification. This is a bit confusing, since sorting by priority works in the todo list, but sorting with date does not. Also, since I call the function 'org-agenda', it is a bit unexpected that when I press 't' afterwards I don't really get an agenda but a TODO list, which seems to behave differently in some aspects from the normal agenda view I get when pressing 'a'. Yes, this is bad terminology, which evolved historically. "org-agenda" is a dispatcher for the different views that we call "agenda views". One of the "agenda views" is the global todo list (on `t'), another one is the "daily/weekly agenda" (on `'a), which is a list of what is due today or this week. I always try to call it explicitly "daily/weekly agenda" to avoid some of that confusion, but I agree, if I'd get a chance to start again I would use better terms. Now these are so engrained in our mailing list culture and into tutorials etc that I do not dare to change them anymore. Thank you for the explanation. Maybe this situation could be cleared up a bit in the manual. While browsing through chapter 10, I got the impression that the different views are just different filters, but that I'm always dealing with the same agenda mode, where each entry carries the same information. Actually, I think this is so, entries always do carry the same information in all these views. remember that, a Matt said, time-up is time-of-day only. Maybe one could explicitly mention which commands and sorting strategies only apply to the daily/weekly agenda? I'd also say that the doc- string of org-agenda-sorting-strategy does not make this point clear enough. I will see what I can do. - Carsten Yes can use the text property on a, `org-hd-marker', which is a marker pointing to the original location of the item. You can make your function go back to get this information. For example with (org-entry-get (get-text-property 0 'org-hd-marker a) "SCHEDULED") I will try that. Thank you for your help! -David ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
On Mar 30, 2009, at 9:55 PM, Sebastian Rose wrote: Carsten Dominik writes: Still, if it is "common practice" to call this outermost container "container" instead of "content", I would not object to rename it. "content" (see some drupal templates and Org-mode) or "wrapper" (see OP) or "wrap" (see some CMSs, e.g. typolight) or ... ??? I think, we will just leave things the way they are. Issue closed - as far as I am concerned. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Sorting TODOs with time-up
Carsten Dominik writes: > On Mar 30, 2009, at 4:46 PM, David Engster wrote: >> Thanks for the clarification. This is a bit confusing, since sorting >> by priority works in the todo list, but sorting with date does >> not. Also, since I call the function 'org-agenda', it is a bit >> unexpected that when I press 't' afterwards I don't really get an >> agenda but a TODO list, which seems to behave differently in some >> aspects from the normal agenda view I get when pressing 'a'. > > Yes, this is bad terminology, which evolved historically. > > "org-agenda" is a dispatcher for the different views that we call > "agenda views". > > One of the "agenda views" is the global todo list (on `t'), another > one is the "daily/weekly agenda" (on `'a), which is a list of what is > due today or this week. > I always try to call it explicitly > "daily/weekly agenda" to avoid some of that confusion, but I agree, if > I'd get a chance to start again I would use better terms. Now these > are so engrained in our mailing list culture and into tutorials etc > that I do not dare to change them anymore. Thank you for the explanation. Maybe this situation could be cleared up a bit in the manual. While browsing through chapter 10, I got the impression that the different views are just different filters, but that I'm always dealing with the same agenda mode, where each entry carries the same information. Maybe one could explicitly mention which commands and sorting strategies only apply to the daily/weekly agenda? I'd also say that the doc-string of org-agenda-sorting-strategy does not make this point clear enough. > Yes can use the text property on a, `org-hd-marker', which is a marker > pointing to the original location of the item. You can make your > function go back to get this information. > > For example with > (org-entry-get (get-text-property 0 'org-hd-marker a) "SCHEDULED") I will try that. Thank you for your help! -David ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: How to define TODOs within continuous text the best way?
Fixed, thanks.
- Carsten
On Mar 30, 2009, at 10:18 PM, Bernt Hansen wrote:
Carsten Dominik writes:
Sometimes, miracles do happen.
:)
Fool the user, not Org!
We will make them just normal outline nodes with stars,
metadata and all the rest. Full citizens. But then we treat
them specially in just two situations:
1. For visibility cycling: We disqualify these tasks from being
recognized during visibility cycling. Simply by setting a
limit for the outline depth to be seen by cycling, treating
any deeper levels as normal text. So if the parent opens, all
these "disqualified" nodes are treated as text and open as
well.
2. During export: We treat the node and its meta data as special
and export it as some inline construct, and we do this in the
export *preprocessor* already, so that the backends never know
there was an outline node at all. This fixes any issues with
section numbering, text and list continuation etc.
3. As icing on the cake we introduce special fontification which
make inline tasks look deeply indented.
I have put these features into a new add-on, org-inlinetask.el.
Just (require 'org-inlinetask) should turn it on for you, and
any headline with a level 15 or deeper (30 if you use odd levels
only) will then be subject to the special treatment.
I just pushed this file into the git repository. Read the file
commentary for explanations and try it out - I think the
mechanism work surprisingly well.
I simply cannot believe that after all those years, we might be
able to close this task.
I think there's a bug here. I have started using
(setq org-odd-levels-only t)
again and org-cycle() complains about 'limit' not having a value.
,[ org.el line 4533 ]
| (and limit-level (1- (* limit 2)))
` ^
All I did was update to the latest version in git and did not make any
other changes to my setup (ie. I'm not using the
(require 'org-inlinetask)
stuff)
I'm not sure what this is supposed to be..
Here's the backtrace.
-Bernt
Debugger entered--Lisp error: (void-variable limit)
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...)
limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-
special ...) (org-cycle-hook ...) (pos ...)) (if (or bob-
special ...) (setq arg t)) (cond (... ... ...) (... ... ...)
(... ...) (... ...) (... ...) (... ...) (... ... ...) (buffer-read-
only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=!ÈÉÊ\"ËÉ!A@)¢Ì=!ÈÍÊ\"Î !Ï Ð!\fcÑed\"
VWebÒ
¥y` dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊ ÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-
lines -1 debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-
buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n"
message "%s" buffer-string kill-emacs "" nil recursive-edit
middlestart buffer-read-only standard-output] 4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...)
limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-
special ...) (org-cycle-hook ...) (pos ...)) (if (or bob-
special ...) (setq arg t)) (cond (... ... ...) (... ... ...)
(... ...) (... ...) (... ...) (... ...) (... ... ...) (buffer-read-
only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=!ÈÉÊ\"ËÉ!A@)¢Ì=!ÈÍÊ\"Î !Ï Ð!\fcÑed\"
VWebÒ
¥y` dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊ ÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-
lines -1 debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-
buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n"
message "%s" buffer-string kill-emacs "" nil recursive-edit
middlestart buffer-read-only standard-output] 4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...)
limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-
special ...) (org-cycle-hook ...) (pos ...)) (if (or bob-
special ...) (setq arg t)) (cond (... ... ...) (... ... ...)
(... ...) (... ...) (... ...) (... ...) (... ... ...) (buffer-read-
only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
yas/expand()
call-interactively(yas/expand)
[Orgmode] Re: Filtering for effort in org-agenda
Carsten Dominik writes:
> On Mar 30, 2009, at 8:01 PM, Matthew Lundin wrote:
>
>>
>> A quick question. Sometimes during the day, when my effort is
>> flagging,
>> I like to see all items that have an effort of, say, < 0:10, so I
>> can do
>> a bunch of quick tasks in succession. When I apply the agenda filter
>> ( /
>> < 0:10 ), however, the resulting list includes all items that do not
>> have a
>> defined effort. Would it be possible to create an option to exclude
>> items where effort is nil from the filtered list?
>>
>> I had a quick look at org-agenda-compare-effort in org-agenda.el (line
>> 4734), and if I'm reading the function correctly, it gives items
>> without
>> a defined effort the value of 0. Is this correct?
>
> Correct.
>
> I guess we could define a variable to put a different default or so.
> Or we could apply org-sort-agenda-noeffort-is-high also in this case
> and supply a large number instead of 0.
>
> - Carsten
>
>>
>> Any advice would be greatly appreciated.
I think I changed that behaviour originally in commit dc43885
I was looking for a way to select tasks with no effort so I could define
an effort before working on them.
I'd like to retain the ability to find tasks with no effort easily.
There's probably a better solution that the one I came up with.
-Bernt
commit dc438851021ba340bbff3462671e2b142ff6bdbf
Author: Carsten Dominik
Date: Tue Nov 11 06:56:32 2008 +0100
Treat no effort defined as 0 minutes.
Bernt Hanses writes:
This changes the default value for Effort during agenda filtering so
that an undefined Effort value is treated as 0 instead of nil. Tasks
with no effort defined now return zero effort when selecting tasks for
the filter.
There was effectively no way to select 'tasks with no effort defined'
using the agenda effort filter. The '<' operator is interpreted as
'<=' and the default effort selection defined in
org-agenda-filter-by-tag starts with zero ("0 0:10 ...") so this
change just treats tasks with no effort defined the same as tasks with
an effort of 0.
This allows fast selection of NEXT tasks with no effort defined.
Column view with follow-mode active in the agenda is great for quickly
filling in the agenda estimated effort values for tasks. Just display
your Next tasks, then / 0 to select tasks with no effort and enter
column mode (C-c C-x C-c) and fill in your effort values with the
quick keys (0-9) for all of the tasks that have blanks in the effort
column.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: How to define TODOs within continuous text the best way?
Carsten Dominik writes:
> Sometimes, miracles do happen.
:)
> Fool the user, not Org!
>
> We will make them just normal outline nodes with stars,
> metadata and all the rest. Full citizens. But then we treat
> them specially in just two situations:
>
> 1. For visibility cycling: We disqualify these tasks from being
>recognized during visibility cycling. Simply by setting a
>limit for the outline depth to be seen by cycling, treating
>any deeper levels as normal text. So if the parent opens, all
>these "disqualified" nodes are treated as text and open as
>well.
>
> 2. During export: We treat the node and its meta data as special
>and export it as some inline construct, and we do this in the
>export *preprocessor* already, so that the backends never know
>there was an outline node at all. This fixes any issues with
>section numbering, text and list continuation etc.
>
> 3. As icing on the cake we introduce special fontification which
>make inline tasks look deeply indented.
>
> I have put these features into a new add-on, org-inlinetask.el.
> Just (require 'org-inlinetask) should turn it on for you, and
> any headline with a level 15 or deeper (30 if you use odd levels
> only) will then be subject to the special treatment.
>
> I just pushed this file into the git repository. Read the file
> commentary for explanations and try it out - I think the
> mechanism work surprisingly well.
>
> I simply cannot believe that after all those years, we might be
> able to close this task.
I think there's a bug here. I have started using
(setq org-odd-levels-only t)
again and org-cycle() complains about 'limit' not having a value.
,[ org.el line 4533 ]
| (and limit-level (1- (* limit 2)))
` ^
All I did was update to the latest version in git and did not make any
other changes to my setup (ie. I'm not using the
(require 'org-inlinetask)
stuff)
I'm not sure what this is supposed to be..
Here's the backtrace.
-Bernt
Debugger entered--Lisp error: (void-variable limit)
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=! ÈÉÊ\"ËÉ!A@)¢Ì=! ÈÍÊ\"Î !Ï Ð!\fc Ñed\"
VW ebÒ
¥y` dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊ ÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1
debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode
debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string
kill-emacs "" nil recursive-edit middlestart buffer-read-only standard-output]
4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=! ÈÉÊ\"ËÉ!A@)¢Ì=! ÈÍÊ\"Î !Ï Ð!\fc Ñed\"
VW ebÒ
¥y` dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊ ÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1
debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode
debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string
kill-emacs "" nil recursive-edit middlestart buffer-read-only standard-output]
4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
yas/expand()
call-interactively(yas/expand)
_
Re: [Orgmode] Re: Export as HTML
Carsten Dominik writes: > Still, if it is "common practice" to call this outermost > container "container" instead of "content", I would not > object to rename it. "content" (see some drupal templates and Org-mode) or "wrapper" (see OP) or "wrap" (see some CMSs, e.g. typolight) or ... ??? - Sebastian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: filtering org-agenda by tag
It works for me too. (I can't reproduce it either) -Bernt Carsten Dominik writes: > Hi > > I cannot reproduce this, refreshing keeps the filter for me. > > - Carsten > > On Mar 28, 2009, at 11:16 PM, shaunalynn duffy wrote: > >> 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. Internet searching turned up the promisingly named >> variable "org-agenda-filter-preset," but it isn't recognized by my >> emacs. >> >> I guess my questions are: Was switching to the dev version the cause >> of this change? AND Is there a straightforward way to get the filter >> to be applied through a reload, or is this something I should write >> a solution to for myself? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Filtering for effort in org-agenda
Nick Dokos wrote: > Matthew Lundin wrote: > > > > > A quick question. Sometimes during the day, when my effort is flagging, > > I like to see all items that have an effort of, say, < 0:10, so I can do > > a bunch of quick tasks in succession. When I apply the agenda filter ( / > > < 0:10 ), however, the resulting list includes all items that do not have a > > defined effort. Would it be possible to create an option to exclude > > items where effort is nil from the filtered list? > > > > I had a quick look at org-agenda-compare-effort in org-agenda.el (line > > 4734), and if I'm reading the function correctly, it gives items without > > a defined effort the value of 0. Is this correct? > > > > Any advice would be greatly appreciated. > > > > Take a look at org-sort-agenda-noeffort-is-high - it should be t by default > which should do what you want, but maybe you have changed it? > > Nick > Never mind !-) I should have waited for Carsten's mail, then I wouldn't have to get foot out of mouth... Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Export as HTML
Hi Carsten, Carsten Dominik wrote: > On Mar 30, 2009, at 4:45 PM, Matthew Lundin wrote: >> Carsten Dominik writes: >>> I would not object to renaming the outer div to "container" or whatever >>> other name we can find a consensus for. >> >> Completely agreed. This is not an important problem. Anyone who chooses to >> use org-mode for publishing a web site should know a little bit about >> hacking css. > > Yes. > > Still, if it is "common practice" to call this outermost container > "container" instead of "content", I would not object to rename it. >From my (very) small experience, this last assumption seems to be the case. So, for me, if we keep a global DIV in the body, we'd better name it `container'. Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Filtering for effort in org-agenda
Matthew Lundin wrote: > > A quick question. Sometimes during the day, when my effort is flagging, > I like to see all items that have an effort of, say, < 0:10, so I can do > a bunch of quick tasks in succession. When I apply the agenda filter ( / > < 0:10 ), however, the resulting list includes all items that do not have a > defined effort. Would it be possible to create an option to exclude > items where effort is nil from the filtered list? > > I had a quick look at org-agenda-compare-effort in org-agenda.el (line > 4734), and if I'm reading the function correctly, it gives items without > a defined effort the value of 0. Is this correct? > > Any advice would be greatly appreciated. > Take a look at org-sort-agenda-noeffort-is-high - it should be t by default which should do what you want, but maybe you have changed it? Nick ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] move subtree down bug?
Fixed, thanks. - Carsten On Mar 30, 2009, at 9:22 AM, Rustom Mody wrote: The last two lines of my org file are *** Vishnu Sahasranam *** Ram Navami without a newline at the end Trying to reorder these two lines I do a M-S-down on second last line I get *** Ram Navami*** Vishnu Sahasranam ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Filtering for effort in org-agenda
On Mar 30, 2009, at 8:01 PM, Matthew Lundin wrote: A quick question. Sometimes during the day, when my effort is flagging, I like to see all items that have an effort of, say, < 0:10, so I can do a bunch of quick tasks in succession. When I apply the agenda filter ( / < 0:10 ), however, the resulting list includes all items that do not have a defined effort. Would it be possible to create an option to exclude items where effort is nil from the filtered list? I had a quick look at org-agenda-compare-effort in org-agenda.el (line 4734), and if I'm reading the function correctly, it gives items without a defined effort the value of 0. Is this correct? Correct. I guess we could define a variable to put a different default or so. Or we could apply org-sort-agenda-noeffort-is-high also in this case and supply a large number instead of 0. - Carsten Any advice would be greatly appreciated. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
On Mar 30, 2009, at 8:12 PM, Matthew Lundin wrote:
Hi Carsten,
I think I figured out the problem. I reset
org-emphasis-regexp-components to the new default (I had customized
it)
and everything now works fine.
Ah, yes, that explains it.
- Carsten
Thanks,
Matt
Carsten Dominik writes:
Hi Matt,
well, if I export that exact same document, then I get
---
\title{Test}
\author{Carsten Dominik}
\date{30 March 2009}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
This is a footnote.\footnote{\emph{Test.} }
\end{document}
- Carsten
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
Hi Carsten,
I think I figured out the problem. I reset
org-emphasis-regexp-components to the new default (I had customized it)
and everything now works fine.
Thanks,
Matt
Carsten Dominik writes:
> Hi Matt,
>
> well, if I export that exact same document, then I get
>
> ---
> \title{Test}
> \author{Carsten Dominik}
> \date{30 March 2009}
>
> \begin{document}
>
> \maketitle
>
> \setcounter{tocdepth}{3}
> \tableofcontents
> \vspace*{1cm}
>
> This is a footnote.\footnote{\emph{Test.} }
>
>
>
> \end{document}
>
>
> - Carsten
>
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Filtering for effort in org-agenda
A quick question. Sometimes during the day, when my effort is flagging, I like to see all items that have an effort of, say, < 0:10, so I can do a bunch of quick tasks in succession. When I apply the agenda filter ( / < 0:10 ), however, the resulting list includes all items that do not have a defined effort. Would it be possible to create an option to exclude items where effort is nil from the filtered list? I had a quick look at org-agenda-compare-effort in org-agenda.el (line 4734), and if I'm reading the function correctly, it gives items without a defined effort the value of 0. Is this correct? Any advice would be greatly appreciated. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Sorting TODOs with time-up
On Mar 30, 2009, at 4:46 PM, David Engster wrote:
Matthew Lundin writes:
David Engster writes:
I guess this should be simple but somehow it's not working for me. I
want to generate a todo list which is sorted according to the
scheduled
date. Consider the following test.org file:
[...]
This minimal setup
(setq org-agenda-files '("~/orgtest/test.org"))
(setq org-agenda-sorting-strategy
'((agenda time-up priority-down category-keep)
(todo time-up priority-down category-keep)
(tags priority-down category-keep)
(search category-keep)))
should sort TODOs according to time, right? But when I do
As far as I understand it, time-up sorts only by time of day in the
agenda view. I.e., it will place items that have been scheduled for a
particular hour at the top of the agenda.
Here's some info from the docstring:
,
| time-upPut entries with time-of-day indications
first, early first
| time-down Put entries with time-of-day indications
first, late first
|
| Pull out all entries having a specified time of day and sort them,
| in order to make a time schedule for the current day the first
thing in the
| agenda listing for the day.
`
Thanks for the clarification. This is a bit confusing, since sorting
by
priority works in the todo list, but sorting with date does not. Also,
since I call the function 'org-agenda', it is a bit unexpected that
when
I press 't' afterwards I don't really get an agenda but a TODO list,
which seems to behave differently in some aspects from the normal
agenda
view I get when pressing 'a'.
Yes, this is bad terminology, which evolved historically.
"org-agenda" is a dispatcher for the different views that we call
"agenda views".
One of the "agenda views" is the global todo list (on `t'), another
one is the
"daily/weekly agenda" (on `'a), which is a list of what is due today
or this week. I always try to call it explicitly "daily/weekly
agenda" to avoid some of that confusion, but I agree, if I'd get a
chance to start again I would use better terms. Now these are so
engrained in our mailing list culture and into tutorials etc that I do
not dare to change them anymore.
There is the possibility of using a user-defined function. Perhaps
you
could use that to sort by date.
,
| user-defined-upSort according to `org-agenda-cmp-user-
defined', high last.
| user-defined-down Sort according to `org-agenda-cmp-user-
defined', high first.
`
Unfortunately, this does not help, since there is no time
information in
the entries 'a' and 'b' to sort by; it seems the timestamps are simply
not extracted when building TODO lists.
Yes can use the text property on a, `org-hd-marker', which is a marker
pointing to the original location of the item. You can make your
function go back to get this information.
For example with
(org-entry-get (get-text-property 0 'org-hd-marker a) "SCHEDULED")
The most efficient implementation would be to first check if there is
a `scheduled-time' or so property on the items. If yes, use it. If
not, get the property and store it in a text property. This will be
efficient because each item will probably be tested several times
during the sorting.
The information is not extracted by default because that would take
extra parsing time and it is usually not needed.
- Carsten
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
On Mar 30, 2009, at 4:45 PM, Matthew Lundin wrote: Carsten Dominik writes: I would not object to renaming the outer div to "container" or whatever other name we can find a consensus for. I think I would object to removing it alltogether, I cannot see the benefit of doing that. On the other hand, I cannot really see ths issue here, because the name in the templates could be changed as well, and I would suspect that this is a common issue name clashes when using templates. Completely agreed. This is not an important problem. Anyone who chooses to use org-mode for publishing a web site should know a little bit about hacking css. And as Sebastian R. suggests, we should certainly *not* change org-export because of some random css template! Yes. Still, if it is "common practice" to call this outermost container "container" instead of "content", I would not object to rename it. - Carsten Let me clarify that I am perfectly happy with the current behavior. And I have a vested interest in *not* having it changed, since I'm lazy and don't want to have to change my css file again. :) - Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
Hi Matt,
well, if I export that exact same document, then I get
---
\title{Test}
\author{Carsten Dominik}
\date{30 March 2009}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
This is a footnote.\footnote{\emph{Test.} }
\end{document}
- Carsten
On Mar 30, 2009, at 4:56 PM, Matthew Lundin wrote:
Hi Carsten,
Carsten Dominik writes:
Fixed, thanks.
- Carsten
I installed the most recent org from the git repo and footnotes that
begin with italics markup are still not converted to \emph in LaTeX.
(See example below.)
Thanks,
Matt
On Mar 28, 2009, at 7:29 PM, Matthew Lundin wrote:
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] /Test./
--8<---cut here---end--->8---
Is exported as (some of preamble omitted):
,
| \title{Test}
| \author{Matthew Lundin}
| \date{March 28, 2009}
|
| \begin{document}
|
| \maketitle
|
| \setcounter{tocdepth}{3}
| \tableofcontents
| \vspace*{1cm}
|
|
| This is a footnote.\footnote{/Test./ }
|
|
|
| \end{document}
`
Any advice would be greatly appreciated.
Thanks,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] footnote bug
Hi Samuel, caching stuff for the agenda would mean rewriting the agenda code. Do you have more detailed pointers what operations exactly are slow? Maybe we can profile and improve these without resorting to cacheing. - Carsten On Mar 26, 2009, at 9:21 PM, Samuel Wales wrote: The following source produces the following output. * sorting speed The agenda is wonderful for other stuff, but for me it is not an editing mode per se. I have never been able to use the agenda for full control over the org file, as some people are able to do. For me (at least on my computer) it is slow. What is "slow". Maybe we can improve things? You could use cached values for agenda files whose last update time is earlier than the last agenda scan. That could lead to significant speedups for people who have several agenda files.[fn:15] [fn:15] It wouldn't help with people who have a single agenda file, and it wouldn't help with people who very frequently use all of their agenda files. For those use cases, something much more complicated and brittle would probably be necessary Output: You could use cached values for agenda files whose last update time is earlier than the last agenda scan. That could lead to significant speedups for people who have several agenda files.[1] [fn:15] It wouldn't help with people who have a single agenda file, and it wouldn't help with people who very frequently use all of their agenda files. For those use cases, something much more complicated and brittle would probably be necessary [1] [fn:15] -- Myalgic encephalomyelitis denialism is causing death (decades early; Jason et al. 2006) and severe suffering (worse than nearly all other diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting science. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] embedded/inherited tags
Hi Kostya! I am still pretty new to emacs and org-mode, but from what I have read until now... Could you use the tag hook to automatically assign the :tech: tag along with :firefox: and|or :emacs: etc... This is still not exactly what you wished afaics, but it may make things a little more convenient. On Mon, Mar 30, 2009 at 16:47, Konstantin Antipin < antipin.konstan...@googlemail.com> wrote: > Hi, > > Manish - thank you for the reply. > > Here is what I want in details: > For example, I have following tags :tech: :firefox: :emacs: :orgmode: > In agenda I usually ask only for TODO with :tech: tags, in order to see > actions, related to technical stuff. > > clearly, :firefox: and :emacs: are related to :tech: tag. It would be > convenient to introduce tag hierarchy: > every todo-item with :emacs: (or :firefox: ) tag only should show up in > agenda, when I query for :tech: tag. > I understand, that every time I assign :emacs: tag I can assign :tech: tag > as well, and this will do the work, but it is not convenient. > > > Is such mechanism exists? > > My todo's are scatterd over the files, thus I can not use usual tag > hierarchy, that is controlled by, for example, "org-use-tag-inheritance". > > thanks, > Kostya > > > On Mon, Mar 30, 2009 at 1:09 PM, Manish wrote: > >> On Sat, Mar 28, 2009 at 6:59 PM, Konstantin Antipin wrote: >> > Dear org-users, >> > Is there any way to make tags inherited from another tag? >> > For example, I have following tags: >> > :tech: >> > :emacs: >> > :orgmode: >> > :ubuntu: >> > >> > :other: >> >> Could you please a little elaborate more on this? Also please take a >> look at variable "org-use-tag-inheritance". >> >> -- >> Manish >> > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
Hi Carsten,
Carsten Dominik writes:
> Fixed, thanks.
>
> - Carsten
>
I installed the most recent org from the git repo and footnotes that
begin with italics markup are still not converted to \emph in LaTeX.
(See example below.)
Thanks,
Matt
> On Mar 28, 2009, at 7:29 PM, Matthew Lundin wrote:
>
>> 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] /Test./
>> --8<---cut here---end--->8---
>>
>> Is exported as (some of preamble omitted):
>>
>> ,
>> | \title{Test}
>> | \author{Matthew Lundin}
>> | \date{March 28, 2009}
>> |
>> | \begin{document}
>> |
>> | \maketitle
>> |
>> | \setcounter{tocdepth}{3}
>> | \tableofcontents
>> | \vspace*{1cm}
>> |
>> |
>> | This is a footnote.\footnote{/Test./ }
>> |
>> |
>> |
>> | \end{document}
>> `
>>
>> Any advice would be greatly appreciated.
>>
>> Thanks,
>> Matt
>>
>>
>> ___
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] embedded/inherited tags
Hi, Manish - thank you for the reply. Here is what I want in details: For example, I have following tags :tech: :firefox: :emacs: :orgmode: In agenda I usually ask only for TODO with :tech: tags, in order to see actions, related to technical stuff. clearly, :firefox: and :emacs: are related to :tech: tag. It would be convenient to introduce tag hierarchy: every todo-item with :emacs: (or :firefox: ) tag only should show up in agenda, when I query for :tech: tag. I understand, that every time I assign :emacs: tag I can assign :tech: tag as well, and this will do the work, but it is not convenient. Is such mechanism exists? My todo's are scatterd over the files, thus I can not use usual tag hierarchy, that is controlled by, for example, "org-use-tag-inheritance". thanks, Kostya On Mon, Mar 30, 2009 at 1:09 PM, Manish wrote: > On Sat, Mar 28, 2009 at 6:59 PM, Konstantin Antipin wrote: > > Dear org-users, > > Is there any way to make tags inherited from another tag? > > For example, I have following tags: > > :tech: > > :emacs: > > :orgmode: > > :ubuntu: > > > > :other: > > Could you please a little elaborate more on this? Also please take a > look at variable "org-use-tag-inheritance". > > -- > Manish > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Sorting TODOs with time-up
Matthew Lundin writes:
> David Engster writes:
>> I guess this should be simple but somehow it's not working for me. I
>> want to generate a todo list which is sorted according to the scheduled
>> date. Consider the following test.org file:
[...]
>> This minimal setup
>>
>> (setq org-agenda-files '("~/orgtest/test.org"))
>> (setq org-agenda-sorting-strategy
>> '((agenda time-up priority-down category-keep)
>> (todo time-up priority-down category-keep)
>> (tags priority-down category-keep)
>> (search category-keep)))
>>
>> should sort TODOs according to time, right? But when I do
> As far as I understand it, time-up sorts only by time of day in the
> agenda view. I.e., it will place items that have been scheduled for a
> particular hour at the top of the agenda.
>
> Here's some info from the docstring:
>
> ,
> | time-upPut entries with time-of-day indications first, early
> first
> | time-down Put entries with time-of-day indications first, late
> first
> |
> | Pull out all entries having a specified time of day and sort them,
> | in order to make a time schedule for the current day the first thing in the
> | agenda listing for the day.
> `
Thanks for the clarification. This is a bit confusing, since sorting by
priority works in the todo list, but sorting with date does not. Also,
since I call the function 'org-agenda', it is a bit unexpected that when
I press 't' afterwards I don't really get an agenda but a TODO list,
which seems to behave differently in some aspects from the normal agenda
view I get when pressing 'a'.
> There is the possibility of using a user-defined function. Perhaps you
> could use that to sort by date.
>
> ,
> | user-defined-upSort according to `org-agenda-cmp-user-defined', high
> last.
> | user-defined-down Sort according to `org-agenda-cmp-user-defined', high
> first.
> `
Unfortunately, this does not help, since there is no time information in
the entries 'a' and 'b' to sort by; it seems the timestamps are simply
not extracted when building TODO lists.
Thanks for your help,
-David
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
Carsten Dominik writes: > I would not object to renaming the outer div to "container" or > whatever other name we can find a consensus for. > > I think I would object to removing it alltogether, I cannot see the > benefit of doing that. > > On the other hand, I cannot really see ths issue here, because the > name in the templates could be changed as well, and I would suspect > that this is a common issue name clashes when using templates. Completely agreed. This is not an important problem. Anyone who chooses to use org-mode for publishing a web site should know a little bit about hacking css. And as Sebastian R. suggests, we should certainly *not* change org-export because of some random css template! Let me clarify that I am perfectly happy with the current behavior. And I have a vested interest in *not* having it changed, since I'm lazy and don't want to have to change my css file again. :) - Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] bug in "simple dependencies" handling (?)
Hi Daniel, looks that your modification do the right thing - almost. It does not check if the parent itself is a TODO, and I think this would be necessary as well. Because it would allow to have do-able subtasks in the list without too much blocking. So "write hopping list" would not be blocked in this case: * organize party :PROPERTIES: :ORDERED: t :END: ** TODO send invitations *** TODO send invitation to Paul *** TODO send invitation to Nicole *** ect. ** Buy meals and drinks :PROPERTIES: :ORDERED: t :END: *** TODO write shopping list *** TODO get money from my bank account *** TODO buy food *** TODO buy drinks Would you agree? - Carsten On Mar 28, 2009, at 3:52 AM, Daniel wrote: Oh my god! I think I've found a good solution :) Can you please tell me, whether it's crap or not? Only 4 lines differ from the original org-block-todo-from-children-or-siblings hook. I've marked the lines with "comment lines", they are before and after the ORDERED-property check, at the end of the function. (defun org-block-todo-from-children-or-siblings-or-parent (change- plist) "Block turning an entry into a TODO, using the hierarchy. This checks whether the current task should be blocked from state changes. Such blocking occurs when: 1. The task has children which are not all in a completed state. 2. A task has a parent with the property :ORDERED:, and there are siblings prior to the current task with incomplete status." (catch 'dont-block ;; If this is not a todo state change, or if this entry is already DONE, ;; do not block (when (or (not (eq (plist-get change-plist :type) 'todo-state- change)) (member (plist-get change-plist :from) (cons 'done org-done-keywords)) (member (plist-get change-plist :to) (cons 'todo org-not-done-keywords))) (throw 'dont-block t)) ;; If this task has children, and any are undone, it's blocked (save-excursion (org-back-to-heading t) (let ((this-level (funcall outline-level))) (outline-next-heading) (let ((child-level (funcall outline-level))) (while (and (not (eobp)) (> child-level this-level)) ;; this todo has children, check whether they are all ;; completed (if (and (not (org-entry-is-done-p)) (org-entry-is-todo-p)) (throw 'dont-block nil)) (outline-next-heading) (setq child-level (funcall outline-level)) ;; Otherwise, if the task's parent has the :ORDERED: property, and ;; any previous siblings are undone, it's blocked (save-excursion (save-match-data (ignore-errors (while t (save-excursion (org-back-to-heading t) (when (save-excursion (ignore-errors (org-up-heading-all 1) (org-entry-get (point) "ORDERED"))) (let* ((this-level (funcall outline-level)) (current-level this-level)) (while (and (not (bobp)) (>= current-level this-level)) (outline-previous-heading) (setq current-level (funcall outline-level)) (if (= current-level this-level) ;; This is a younger sibling, check if it is completed (if (and (not (org-entry-is-done-p)) (org-entry-is-todo-p)) (throw 'dont-block nil))) ;; (org-back-to-heading t) (org-up-heading-all 1) ;; t)) (add-hook 'org-blocker-hook 'org-block-todo-from-children-or- siblings-or-parent) Carsten Dominik wrote: Hi Daniel, one problem might have been a bug I just fixed. Another problem is that the way you wrote your code, a child on an ordered sequence will block the parent, and the parent will block the child. I'd like to come around an fix this, just not clear yet how, and how to do it efficiently. - Carsten On Mar 27, 2009, at 1:24 AM, Daniel wrote: Hello Carsten, thanks for your reply. Hi Daniel, yes, this could be seen as a bug. However, the implementation does not work by scanning the entire buffer and marking tasks that should be blocked. Rather, it goes to each task and then scans around to see locally what the dependencies are. In this case it looks only at the parent, not at the grand parent. Wouldn't it be enough to check whether the parent is blocked. Wouldn't that generate a blocking-chain? However, the todo dependencies are simple hook functions, and an interested programmer could relatively easily extend them, I believe. I've tried to write a custom org-blocker-hook but it doesn't work, unfortunately. Can you (or someone else) tell me please what's wrong with my code? (defun org-block-todo-with-blocked-parent (change-plist) ;; check whether we are in a endless loop: (if (plist-get change-plist :org-block-todo-with-blocked-parent) ;; We are in a endless loop: don't block (return t) t ;; We are not in a endless loop: go to the parent heading (save-excursion (org-back-to-heading t) (ignore-errors (org-up-heading-a
[Orgmode] Re: embedded/inherited tags
Konstantin Antipin writes: > Is there any way to make tags inherited from another tag? > For example, I have following tags: > :tech: > :emacs: > :orgmode: > :ubuntu: > > :other: No, tags cannot inherit from one another, but you can achieve a similar effect by structuring your headings in the same fashion. Org has tag inheritance, but in this case it just means that a heading will inherit the tags from its parent heading: * Technology :tech: ** Emacs :emacs: *** Org Mode :orgmode: TODO Turn on tag inheritance The TODO heading from above will have the following tags (if tag inheritance is enabled): :tech:emacs:orgmode: -- Peter Jones, http://pmade.com pmade inc. Louisville, CO US ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
Sébastien Vauban writes: > I took a free CSS template at: > > http://www.free-css.com/free-css-templates/page2/minisite-pro.php Why don't you adjust the template??? Why should anyone Org-mode to match an arbitrary freely available CSS-template? Sebastian ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Sorting TODOs with time-up
David Engster writes:
>
> I guess this should be simple but somehow it's not working for me. I
> want to generate a todo list which is sorted according to the scheduled
> date. Consider the following test.org file:
>
> ** TODO: first SCHEDULED: <2009-04-01 Wed>
> ** TODO: second SCHEDULED: <2009-04-23 Thu>
> ** TODO: third SCHEDULED: <2009-04-16 Thu>
>
> This minimal setup
>
> (setq org-agenda-files '("~/orgtest/test.org"))
> (setq org-agenda-sorting-strategy
> '((agenda time-up priority-down category-keep)
> (todo time-up priority-down category-keep)
> (tags priority-down category-keep)
> (search category-keep)))
>
> should sort TODOs according to time, right? But when I do
>
As far as I understand it, time-up sorts only by time of day in the
agenda view. I.e., it will place items that have been scheduled for a
particular hour at the top of the agenda.
Here's some info from the docstring:
,
| time-upPut entries with time-of-day indications first, early first
| time-down Put entries with time-of-day indications first, late first
|
| Pull out all entries having a specified time of day and sort them,
| in order to make a time schedule for the current day the first thing in the
| agenda listing for the day.
`
There is the possibility of using a user-defined function. Perhaps you
could use that to sort by date.
,
| user-defined-upSort according to `org-agenda-cmp-user-defined', high last.
| user-defined-down Sort according to `org-agenda-cmp-user-defined', high
first.
`
Best,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
On Mar 30, 2009, at 2:46 PM, Matthew Lundin wrote: Sebastian Rose writes: Could you describe here what's the problem with the element? This was put in recently on a users request. If you don't want to use it for you're CSS styling, just don't. In my opinion, a minor issue with the new default is that it is used used to wrap the entire body of the page. Though there are no hard and fast rules, I believe it is a common convention to use the id of "wrapper" or "container" for such a div and to use the id "content" for a div that begins after a preamble/menu and ends before a postamble/menu. In other words in this order. ... I would not object to renaming the outer div to "container" or whatever other name we can find a consensus for. I think I would object to removing it alltogether, I cannot see the benefit of doing that. On the other hand, I cannot really see ths issue here, because the name in the templates could be changed as well, and I would suspect that this is a common issue name clashes when using templates. - Carsten Let me repeat that the new behavior of org-export is not really a problem for me, as I simply adapted my css stylings to match it (I had been using the id "content" for everything after the preamble). But the new behavior could cause *minor* confusion for people trying to adapt a generic css for use with org-export. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Sorting TODOs with time-up
Hi all,
I guess this should be simple but somehow it's not working for me. I
want to generate a todo list which is sorted according to the scheduled
date. Consider the following test.org file:
** TODO: first SCHEDULED: <2009-04-01 Wed>
** TODO: second SCHEDULED: <2009-04-23 Thu>
** TODO: third SCHEDULED: <2009-04-16 Thu>
This minimal setup
(setq org-agenda-files '("~/orgtest/test.org"))
(setq org-agenda-sorting-strategy
'((agenda time-up priority-down category-keep)
(todo time-up priority-down category-keep)
(tags priority-down category-keep)
(search category-keep)))
should sort TODOs according to time, right? But when I do
M-x org-agenda RET t
I get:
Global list of TODO items of type: ALL
Available with `N r': (0)ALL (1)TODO (2)DONE
test: TODO: first SCHEDULED: <2009-04-01 Wed>
test: TODO: second SCHEDULED: <2009-04-23 Thu>
test: TODO: third SCHEDULED: <2009-04-16 Thu>
Same with org-todo-list. Also, doing 'C-u C-x =' on one of the lines shows
that the time-of-day property is nil, so it seems that there's just no
information for sorting according to date. What am I missing? (I'm using
org-mode snapshot from today with latest Emacs 23 pretest).
Thanks for your help.
-David
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
Sebastian Rose writes: > Could you describe here what's the problem with the element? > > This was put in recently on a users request. If you don't want to use it > for you're CSS styling, just don't. In my opinion, a minor issue with the new default is that it is used used to wrap the entire body of the page. Though there are no hard and fast rules, I believe it is a common convention to use the id of "wrapper" or "container" for such a div and to use the id "content" for a div that begins after a preamble/menu and ends before a postamble/menu. In other words in this order. ... Let me repeat that the new behavior of org-export is not really a problem for me, as I simply adapted my css stylings to match it (I had been using the id "content" for everything after the preamble). But the new behavior could cause *minor* confusion for people trying to adapt a generic css for use with org-export. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
Could you describe here what's the problem with the element? This was put in recently on a users request. If you don't want to use it for you're CSS styling, just don't. One way to gear the export results to your needs exactly might be the usage of XSL (which you could use with the XHTML or DocBook export). Since the ideas about layout differ so much, I think it's not worth it to change the XHTML export, but to put more effort into creating a template based export instead. Or into what was already called the `generic exporter' here, and I think some people are already working on it. Sebastian Sébastien Vauban writes: > Hi Roc Lee, > > Roc lee wrote: >> 2009/3/30 roc lee Could you remove that line, and its closing tag from `(insert "\n\n\n\n"))' (in function `org-export-as-html') so that we have a completely naked BODY, that the user can fill at its own freedom via the preamble/postamble? >> >> There is no such a div on my exported files. The version I am using is >> 6.17a. > > See lines 3584: > > > > > and line 4205: > > > (insert "\n\n\n\n")) > > in my Org-mode version 6.24trans. > > Seb ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Export as HTML
2009/3/30 Sébastien Vauban > > Hi Carsten, > > Carsten Dominik wrote: > > On Mar 30, 2009, at 10:55 AM, Sébastien Vauban wrote: > >> Hello, > >> > >> Trying to use free CSS templates for some Web site, I have layout problems > >> with the current export to HTML, as a first `' is > >> hard-coded > >> into the resulting Web page. > >> > >> Could you remove that line, and its closing tag from `(insert > >> "\n\n\n\n"))' (in function `org-export-as-html') so > >> that > >> we have a completely naked BODY, that the user can fill at its own freedom > >> via > >> the preamble/postamble? > > > > Why and how is this limiting what you can do? > > I took a free CSS template at: > > http://www.free-css.com/free-css-templates/page2/minisite-pro.php > > If I want to use it without modifying it, I have to follow such a construct > (taken from their live demo): > > --8<---cut here---start->8--- > > > > > Free CSS > Free CSS Templates, CSS Layouts & More! > > http://www.free-css.com/"; title="Free CSS">Home > Contact > Us > Advertise > > title="Recommend Free CSS">Recommend Us > Submit > Search > > > > type="text/javascript"> > > > > > You Are Here > » > Free CSS > » > Free CSS > Templates > » > CSS Templates Page 2 > > » > title="Minisite Pro Template">Minisite Pro > > > > --8<---cut here---end--->8--- > > Having directly under the BODY tag messes up everything. > > > > It was recently introduce precisely to aid CSS formatting > > of the entire body. > > For me, it seems easier to have a completely naked body, by default, and let > the user decide, follow or copy a guideline to implement the nice CSS he wants > to. > > Currently, I had to modify the source code to get the same effect as the one I > want. This is the basic structure for your intended html files : And "content" div has its special format in your style sheet. When a unexpected "content" div comes in, it messes up everything: I agree with you. To give user a nacked body should be better. Or use a long, no-conflict name is also OK :) BR > > Sebasian (Rose) and Richard, you helped making getting > > the outer div into place, would you care to comment? > > Best regards, > Seb > > -- > Sébastien Vauban > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Custom entry IDs in HTML export
El dv, mar 27 2009, Sebastian Rose va escriure: > > What we have now, just as Carstens said: > > # <> > * Section B > > Creates this headline in HTML: > > 2 Section B > > > This is enough for all the use cases I can think of. > Yes, this is enough except for two things: 1. The TOC still links to #sec-2 and the user can't change that 2. Your syntax doesn't fold very well in the outliner. I mean: if you use > # <> > * Section B then the comment appears at the end of the previous section, and you can miss it when you are viewing the heading „Section B“. I would swap both lines (solution 1): > * Section B > # <> But since there are already LOGBOOK drawers under the heading, it would be a lot clearer to use a property, like EXPORT_ID (solution 2): > * Section B > :PROPERTIES: > :EXPORT_ID: human-readable > :END: In this way, the TOC can reliably find the EXPORT_ID, and then generate: > 2 Section B > (You could also leave *just* the human-readable id, but having two is not bad. I would prefer solution 1, but I don't because I'm not sure that the TOC can find the ID if it is written as a comment anywhere under the heading (and together with other things). Solution 2 involves thus: a new property to specify the human-readable entry ID, which will be used to link to the entry. The automatic ID (#sec-2) will still work for all entrys. > > * Distinguishing automatic and human readable IDs > > One thing I like is, that we now _can_ distinguish the > `human-readable-target' (human readable) from the `sec-2' (not human > readable and not context related) using a regular expression. > > In org-info.js, I can now prefere the human readable ID in from an > automatic created one, and thus use that to create the links for `l' > and `L'. The same holds true for other programming languages and > parsers. > > If we open the 's ID for user defined values (bad), we can not > distinguish those ID's using a regular expression and there is no way > to detect the human readable one. There will be no way to _know_ that > the 's ID is the prefered one used for human readable links. > Solution 2 doesn't break the parsing techniques you use; in fact it can also make clearer which ID is the human readable one and which one not. This is not extremely important; just useful: - for pages with many incoming links from external sites - to ensure link integrity (now you can't assure that links will still work in 1 year ... or in some weeks) - to avoid that HTML visitors get directed to a wrong section and can't find what they searched Greetings, Daniel ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] How to define TODOs within continuous text the best way?
On Mar 28, 2009, at 3:23 PM, Karl Maihofer wrote: I'd like to define a TODO like in the example below. When there is a task somewhere in my text (I want to look something up etc.) I want to define this task at the relevant position in my text. So I can lookup all TODOs using the agenda-view and jump directly to the position in my text. The problem is that a TODO is always a new heading and so it is exported in my html(latex)-version as a heading. Sometimes, miracles do happen. The question about non-outline tasks is, really, a FAQ. We have been over this question again and again, though not recently. Each time this question came up I thought it over again, each time with the same result: that this is not possible in a reasonable clean way in the framework of Org's hierarchical document structure. The ideas that were contemplated usually were things like adding a new syntax which is "only" for task management treated as a headline, but not otherwise. I remember proposals like #*** TODO my task or finding a way to add metadata it plain list items, or many other similar ideas. The trouble is, task management is much of Org, so new syntax would be a lot of work. It would destroy he cleanness of much of Org. So always the answer was it cannot be done. That is not to say that I do not appreciate the wish for such a structure. In an outline/list driven setting, one can always re-arrange things to make tasks a separate section. However, when writing a book or extensive notes, the text becomes dominant over the density of outline nodes, and then getting a task into the right place becomes an issue. This new thread, first greeted with a sigh on my side, somehow has changed the perception by focussing on *export* handling of nodes. And it is now clear to me that, in fact, there is a reasonable clean pass to "inline" tasks: Fool the user, not Org! We will make them just normal outline nodes with stars, metadata and all the rest. Full citizens. But then we treat them specially in just two situations: 1. For visibility cycling: We disqualify these tasks from being recognized during visibility cycling. Simply by setting a limit for the outline depth to be seen by cycling, treating any deeper levels as normal text. So if the parent opens, all these "disqualified" nodes are treated as text and open as well. 2. During export: We treat the node and its meta data as special and export it as some inline construct, and we do this in the export *preprocessor* already, so that the backends never know there was an outline node at all. This fixes any issues with section numbering, text and list continuation etc. 3. As icing on the cake we introduce special fontification which make inline tasks look deeply indented. I have put these features into a new add-on, org-inlinetask.el. Just (require 'org-inlinetask) should turn it on for you, and any headline with a level 15 or deeper (30 if you use odd levels only) will then be subject to the special treatment. I just pushed this file into the git repository. Read the file commentary for explanations and try it out - I think the mechanism work surprisingly well. I simply cannot believe that after all those years, we might be able to close this task. - Carsten I would prefer to format a TODO as a text box or at least to exclude it from the html(latex)-export so that it is only visible in org-mode - not in the exported version. But when I exclude the TODO so that it isn't exported anymore, not only the TODO itself but also the text below the TODO isn't exported until there is a new heading - because the TODO itself is a heading, too. I know that this is because Org-Mode is an outliner-mode, TODOs always have to be defined with a beginning "*". But is there any possibility to solve the problem? How do you define TODOs within the text when you use Org-Mode as an authoring tool? 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 exported as a heading but as a div-container? What is the best way to handle TODOs within continuous text? Kind regards, Karl --- * Heading 1 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. * TODO Check again (or ** TODO text?) This paragraph still belongs to heading 1. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At
Re: [Orgmode] Footnotes bug
Hi Carsten, Carsten Dominik writes: >> When I call org-footnote-action, footnotes are entered inline, as >> expected. But when I call org-footnote-action with an argument and >> then >> select "sort," footnote definitions are created at the bottom of the >> section (as expected), > > > I believe this expectation is wrong for inline footnotes which > should be left alone when only sorting footnotes. That was a > bug which I fixed now. Let me know if I am missing something here. Thanks so much for fixing this. Yes, I see that it is much better *not* to have inline footnotes sorted, since they are, after all, inline. The great thing is that one can always convert them by using normalize. By the way, I can't tell you how much I appreciate the elegance of your solution to footnotes in org-mode. As a historian who uses footnotes all the time, I've found org-mode's footnote features to be the most convenient and flexible I've ever used. Best, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Export as HTML
Hi Carsten, Carsten Dominik wrote: > On Mar 30, 2009, at 10:55 AM, Sébastien Vauban wrote: >> Hello, >> >> Trying to use free CSS templates for some Web site, I have layout problems >> with the current export to HTML, as a first `' is >> hard-coded >> into the resulting Web page. >> >> Could you remove that line, and its closing tag from `(insert >> "\n\n\n\n"))' (in function `org-export-as-html') so that >> we have a completely naked BODY, that the user can fill at its own freedom >> via >> the preamble/postamble? > > Why and how is this limiting what you can do? I took a free CSS template at: http://www.free-css.com/free-css-templates/page2/minisite-pro.php If I want to use it without modifying it, I have to follow such a construct (taken from their live demo): --8<---cut here---start->8--- Free CSS Free CSS Templates, CSS Layouts & More! http://www.free-css.com/"; title="Free CSS">Home Contact Us Advertise Recommend Us Submit Search You Are Here » Free CSS » Free CSS Templates » CSS Templates Page 2 » Minisite Pro --8<---cut here---end--->8--- Having directly under the BODY tag messes up everything. > It was recently introduce precisely to aid CSS formatting > of the entire body. For me, it seems easier to have a completely naked body, by default, and let the user decide, follow or copy a guideline to implement the nice CSS he wants to. Currently, I had to modify the source code to get the same effect as the one I want. > Sebasian (Rose) and Richard, you helped making getting > the outer div into place, would you care to comment? Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] todo state trigger tag options
On Sun, Mar 29, 2009 at 7:55 AM, Eraldo Helal wrote: > 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), > etc). > > It's not a matter of speed... but rather a way to make sure I > never forget to give my next actions a context as well! May be org-trigger-hook [1] can be made to trigger org-set-tags-command function somehow when state changes to NEXT? Sorry I do not know enough elisp to be able to code that. HTH -- Manish 1. http://orgmode.org/worg/org-configs/org-hooks.php#sec-1.12 ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] embedded/inherited tags
On Sat, Mar 28, 2009 at 6:59 PM, Konstantin Antipin wrote: > Dear org-users, > Is there any way to make tags inherited from another tag? > For example, I have following tags: > :tech: > :emacs: > :orgmode: > :ubuntu: > > :other: Could you please a little elaborate more on this? Also please take a look at variable "org-use-tag-inheritance". -- Manish ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Effort_all
On Mon, Mar 30, 2009 at 1:38 PM, Rustom Mody wrote: > I am quoting from Charles Cave's "How I use emacs and org to > implement GTD" > > He showshas two configuration lines: > > #+PROPERTY: Effort_ALL 0:10 0:20 0:30 1:00 2:00 4:00 6:00 8:00 > #+PROPERTY: Effort_ALL 0 0:10 0:20 0:30 1:00 2:00 3:00 4:00 8:00 > with one#+COLUMNS: line in between > > Can someone throw some light on this? I believe this is just a remnant of some experimentation done while writing the article. The first line will be in effect if you have both defined. In fact, if you were to refresh the setup in the file, only the first one takes effect (the second one is ignored, unless removed.) And #+COLUMNS being in between the two has no significance. -- Manish ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] move subtree down bug?
--- Lun 30/3/09, Rustom Mody ha scritto: > The last two lines of my org file are > > *** Vishnu Sahasranam > *** Ram Navami > > without a newline at the end > > Trying to reorder these two lines I do a M-S-down on > second last line I get > > *** Ram Navami*** Vishnu Sahasranam then press ;-) 1 keystroke. cheers, Giovanni ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Export as HTML
On Mar 30, 2009, at 10:55 AM, Sébastien Vauban wrote: Hello, Trying to use free CSS templates for some Web site, I have layout problems with the current export to HTML, as a first `' is hard-coded into the resulting Web page. Could you remove that line, and its closing tag from `(insert "\n\n\n\n"))' (in function `org-export-as-html') so that we have a completely naked BODY, that the user can fill at its own freedom via the preamble/postamble? Why and how is this limiting what you can do? It was recently introduce precisely to aid CSS formatting of the entire body. Sebasian (Rose) and Richard, you helped making getting the outer div into place, would you care to comment? - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
Fixed, thanks.
- Carsten
On Mar 28, 2009, at 7:29 PM, Matthew Lundin wrote:
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] /Test./
--8<---cut here---end--->8---
Is exported as (some of preamble omitted):
,
| \title{Test}
| \author{Matthew Lundin}
| \date{March 28, 2009}
|
| \begin{document}
|
| \maketitle
|
| \setcounter{tocdepth}{3}
| \tableofcontents
| \vspace*{1cm}
|
|
| This is a footnote.\footnote{/Test./ }
|
|
|
| \end{document}
`
Any advice would be greatly appreciated.
Thanks,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
On Mar 30, 2009, at 11:27 AM, Scot Becker wrote:
I can confirm this.
Another related issue is that italics and bold do not mix in latex
export. You can't do something like this:
/An italicized sentence with a *bold* bit./ or *vice /versa/*.
Nested emphasis is indeed not possible.
However, as a LaTeX user, I think you can do
/An italicized sentence with a \textbf{bold} bit./
Also, and this may be unavoidable without adding significant
complexity to the export engine.
Indeed.
But you can't, e.g.
/carry your emphasis on until after the punctuation is over./
(It's been a while since I tested this. I'll check it out again
today).
This does work, I think.
For LaTeX export in particular, it would be nice to have finer
control over just where the emphasis goes. For periods it's not
generally an issue :-), but some of the taller punctuation get into
fistfights with their text if they aren't allowed to be italicized
too.
Emphasis is one of the nightmares, and I will only work
on this at gun point :-)
- Carsten
Scot
On Sat, Mar 28, 2009 at 7:29 PM, Matthew Lundin
wrote:
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] /Test./
--8<---cut here---end--->8---
Is exported as (some of preamble omitted):
,
| \title{Test}
| \author{Matthew Lundin}
| \date{March 28, 2009}
|
| \begin{document}
|
| \maketitle
|
| \setcounter{tocdepth}{3}
| \tableofcontents
| \vspace*{1cm}
|
|
| This is a footnote.\footnote{/Test./ }
|
|
|
| \end{document}
`
Any advice would be greatly appreciated.
Thanks,
Matt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export - footnotes and emphasis
I can confirm this.
Another related issue is that italics and bold do not mix in latex export.
You can't do something like this:
/An italicized sentence with a *bold* bit./ or *vice /versa/*.
Also, and this may be unavoidable without adding significant complexity to
the export engine. But you can't, e.g.
/carry your emphasis on until after the punctuation is over./ (It's been a
while since I tested this. I'll check it out again today).
For LaTeX export in particular, it would be nice to have finer control over
just where the emphasis goes. For periods it's not generally an issue :-),
but some of the taller punctuation get into fistfights with their text if
they aren't allowed to be italicized too.
Scot
On Sat, Mar 28, 2009 at 7:29 PM, Matthew Lundin wrote:
> 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] /Test./
> --8<---cut here---end--->8---
>
> Is exported as (some of preamble omitted):
>
> ,
> | \title{Test}
> | \author{Matthew Lundin}
> | \date{March 28, 2009}
> |
> | \begin{document}
> |
> | \maketitle
> |
> | \setcounter{tocdepth}{3}
> | \tableofcontents
> | \vspace*{1cm}
> |
> |
> | This is a footnote.\footnote{/Test./ }
> |
> |
> |
> | \end{document}
> `
>
> Any advice would be greatly appreciated.
>
> Thanks,
> Matt
>
>
> ___
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Export as HTML
Hi Roc Lee, Roc lee wrote: > 2009/3/30 roc lee >>> Could you remove that line, and its closing tag from `(insert >>> "\n\n\n\n"))' (in function `org-export-as-html') so >>> that we have a completely naked BODY, that the user can fill at its own >>> freedom via the preamble/postamble? > > There is no such a div on my exported files. The version I am using is > 6.17a. See lines 3584: --8<---cut here---start->8--- --8<---cut here---end--->8--- and line 4205: --8<---cut here---start->8--- (insert "\n\n\n\n")) --8<---cut here---end--->8--- in my Org-mode version 6.24trans. Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Footnotes bug
Hi Matt, On Mar 28, 2009, at 4:34 AM, Matthew Lundin wrote: Hi Carsten, I would like to report a bug in org-footnote. I have set org-footnote-define-inline to t. I also have the following settings: --8<---cut here---start->8--- (setq org-footnote-section nil) (setq org-footnote-auto-label nil) --8<---cut here---end--->8--- When I call org-footnote-action, footnotes are entered inline, as expected. But when I call org-footnote-action with an argument and then select "sort," footnote definitions are created at the bottom of the section (as expected), I believe this expectation is wrong for inline footnotes which should be left alone when only sorting footnotes. That was a bug which I fixed now. Let me know if I am missing something here. - Carsten but the inline footnote definition is not removed, leading to duplicate definitions. If I sort again, a duplicate set of definitions is created at the bottom of the file. The following progession should help to illustrate what I mean. 1. Inline footnotes , | #+startup: fninline | | * Test | | Footnote one.[fn:one: This is a footnote.] Footnote two.[fn:two: This | is another footnote.] ` 2. After the first sort , | #+startup: fninline | | * Test | | Footnote one.[fn:one: This is a footnote.] Footnote two.[fn:two: This | is another footnote.] | | [fn:one] This is a footnote. | | [fn:two] This | is another footnote. ` 3. After a second sort. , | #+startup: fninline | | * Test | | Footnote one.[fn:one: This is a footnote.] Footnote two.[fn:two: This | is another footnote.] | | [fn:one] This is a footnote. | | [fn:two] This | is another footnote. | | [fn:one] This is a footnote. | | [fn:two] This | is another footnote. ` Thanks, Matt ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Export as HTML
2009/3/30 roc lee > in org-exp.el, line 3858: > (insert "\n") > > 2009/3/30 Sébastien Vauban > > Hello, >> >> Trying to use free CSS templates for some Web site, I have layout problems >> with the current export to HTML, as a first `' is >> hard-coded >> into the resulting Web page. >> >> Could you remove that line, and its closing tag from `(insert >> "\n\n\n\n"))' (in function `org-export-as-html') so >> that >> we have a completely naked BODY, that the user can fill at its own freedom >> via >> the preamble/postamble? > > Sorry for not throughly understanding your question. In first sight, I think you mean the "table-of-contents". There is no such a div on my exported files. The version I am using is 6.17a. >> >> Thanks, >> Seb >> >> -- >> Sébastien Vauban >> >> >> ___ >> Emacs-orgmode mailing list >> Remember: use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> > > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Fwd: Re: Fully featured Web publishing
Hi Taru,
> Here is a simple solution, have a menu like:
>
>
>Navigation
>
> Home
> CV
> Contact Me
>
>
>
> And simply have inside curriculum-vitae.org:
> #+STYLE: a#navigation-cv { color: red }
>
> inside contact-me.org:
> #+STYLE: a#navigation-contact-me { color: red }
This is more a work around than a real solution, but I think it will cover my
urgent needs. Thanks for this...
> Setting the correct style can also be automated with suitable
> Javascript.
I try to avoid JavaScript for many reasons, such as I'm not at all fluent in
it, and I like my pages to be read within text browsers (like w3m).
Thanks a lot for your answer,
Seb
--
Seb
Sébastien Vauban
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Export as HTML
in org-exp.el, line 3858: (insert "\n") 2009/3/30 Sébastien Vauban > Hello, > > Trying to use free CSS templates for some Web site, I have layout problems > with the current export to HTML, as a first `' is > hard-coded > into the resulting Web page. > > Could you remove that line, and its closing tag from `(insert > "\n\n\n\n"))' (in function `org-export-as-html') so > that > we have a completely naked BODY, that the user can fill at its own freedom > via > the preamble/postamble? > > Thanks, > Seb > > -- > Sébastien Vauban > > > ___ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export as HTML
Hello, Trying to use free CSS templates for some Web site, I have layout problems with the current export to HTML, as a first `' is hard-coded into the resulting Web page. Could you remove that line, and its closing tag from `(insert "\n\n\n\n"))' (in function `org-export-as-html') so that we have a completely naked BODY, that the user can fill at its own freedom via the preamble/postamble? Thanks, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Effort_all
I am quoting from Charles Cave's "How I use emacs and org to implement GTD" He shows has two configuration lines: #+PROPERTY: Effort_ALL0:10 0:20 0:30 1:00 2:00 4:00 6:00 8:00 #+PROPERTY: Effort_ALL 0 0:10 0:20 0:30 1:00 2:00 3:00 4:00 8:00 with one #+COLUMNS: line in between Can someone throw some light on this? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Handling org-file agenda dependenncies?
On Mar 27, 2009, at 10:46 PM, Mike Newman wrote: 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. If you want to deal with trees of files, you might be better off removing the variable from the custom section, defining it yourself and updating it manually. I would find it useful to be able to switch to an "*Org Agenda Files Buffer*", edit this and save it to update - but I don't suppose anyone would think it worth the effort of coding. This is already possible. If org-agenda-files points to a single file instead of a list, that file should contain the list of agenda files, one per line. - Carsten As an interesting aside - if in Dired I rename a file that I am currently visiting, the buffer's name will be changed automatically. However, org-agenda-files will not be updated in this case. On Fri, 27 Mar 2009 01:31:19 +0100 Eraldo Helal wrote: I have projects with non-text files. Many of them having sub-,subsub-projects etc. (nested) Therefore I made directories for them using the project name. ///etc Each having it's own <(sub-)project name>.org file in it. My question: How can I add|remove a whole project from the agenda? e.g. If I remove project1.org file from the agenda... /project1/subprojectX.org would still be in there! Or is there a way to assign and then set a group of org.files to inactive(=remove from agenda)? Any other suggestions|methods for solving this problem? ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] tags when entering a new task
On Mar 29, 2009, at 4:37 AM, Richard Riley wrote: 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. How about pressing `C-c C-q' ? - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] move subtree down bug?
The last two lines of my org file are *** Vishnu Sahasranam *** Ram Navami without a newline at the end Trying to reorder these two lines I do a M-S-down on second last line I get *** Ram Navami*** Vishnu Sahasranam ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
