Re: [Orgmode] org export html with header and footer option

2008-02-21 Thread Xin Shi
Hi Will,

I've tried that and it works pretty well!

There are still one minor issue bother me:

I would like to turn off the Author and Date at the end of the page. And 
instead add my own style footer:

org-export-html-postamble: "   
Updated February 20, 2008


And I don't know how to put a variable for the date format. (In the muse case, 
it is 

 
Updated (muse-publishing-directive "date")



Thanks!

Xin




___
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] org export html with header and footer option

2008-02-21 Thread William Henney
Hi Xin

On 21 Feb 2008 10:35:02 -0500, Xin Shi <[EMAIL PROTECTED]> wrote:
>  There are still one minor issue bother me:
>
>  I would like to turn off the Author and Date at the end of the page. And 
> instead add my own style footer:
>
>  org-export-html-postamble: "  
>  Updated February 20, 2008
>  
>
>  And I don't know how to put a variable for the date format. (In the muse 
> case, it is
>
>  
>  Updated (muse-publishing-directive "date")
>  
>

As far as I know, you can only include static text in the
header/footer. Maybe Bastien's new exporter will include this
functionality.

Cheers

Will

-- 

 Dr William Henney, Centro de Radioastronomía y Astrofísica,
 Universidad Nacional Autónoma de México, Campus Morelia


___
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] Highlighting Sparse Tree Leaves

2008-02-21 Thread Carsten Dominik


On Feb 18, 2008, at 4:19 PM, Wanrong Lin wrote:



Using "PROJECT" as a TODO keyword certainly can work, however, my  
work flow usually is first quickly mark anything that needs action  
with "TODO" and later I may add more sub-items to it. Following this  
approach I will need to remember to change "TODO" to "PROJECT" once  
a TODO item starts to have sub-items. Also, if all sub-actions of a  
"PROJECT" are marked as "DONE", I need to remember to turn the  
"PROJECT" back to "TODO", as I need the sparse tree to remind me to  
double check this TODO/PROJECT item to see whether it is really all  
done, or I need to add more sub-actions to it (and turn it back to  
"PROJECT" again).


As you can see, that is a lot of manually actions and mistakes can  
be easily made. Maybe my workflow has some problem here, but I can  
not think of anything else that works better. The difficulty to me  
is, an item can be either PROJECT or TODO depending on how detailed  
your plan is, which keeps changing.


I think if we can have the *option* of selecting a different face  
for highlighting sparse tree leaves, the above can be solved  
elegantly. You can still see the whole sparse tree, but the leaves  
will stand out.


Just trying to push my case a little bit. :-)   Thanks a lot.


That is fine, but it does not work in this case... :-(

- Carsten




Wanrong

Carsten Dominik wrote:

Hi Wanrong,

No, I think you need to find a different way around this.
For example by using a different keyword for the headings that  
contain the true TODO items.  I use PROJECT or something similar.

When you then search for TODO, the true tasks will be highlighted.

- Carsten

On Feb 15, 2008, at 12:36 AM, Wanrong Lin wrote:


Hi,

Is it possible to highlighting only the sparse tree leaves, or  
even better, highlighting the whole sparse tree but with leaves in  
a special face?


The motivation for such a feature is this:

Suppose I have a task tree like this:

* TODO Task A
*** TODO Task A.1
* TODO Task A.1.1
* TODO Task B
*** TODO Task B.1
* TODO Task B.1.1
* TODO Task B.1.2

If I do a "org-sparse-tree", all those lines are highlighted,  
giving an impression that I have a lot of open tasks, but in  
reality I only have three tasks: A.1.1, B.1.1 and B.1.2, as the  
higher level tasks are automatically done if those are done. So it  
would be nice to highlight those leaves in a special face. Also,  
suppose both B.1.1 and B.1.2 are done, then Task B.1 should be  
highlighted as a leaf.


Hope the above makes some sense. Thank you very much for giving it  
a thought.


Wanrong






___
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] Highlighting Sparse Tree Leaves

2008-02-21 Thread Wanrong Lin


Hi, Carsten,

I hacked a patch that does what I need. Just in case you change your 
mind in the future, or anyone else has the same need as I, here is the 
patch (against org.el in 5.22a. I did not get time to learn git yet). 
Thanks.


Wanrong



15082c15082,15085
< (org-highlight-new-match (match-beginning 0) (match-end 0)))
---
> ;; 
> (if (and org-highlight-sparse-tree-leaf (not 
(org-has-match-in-subtree-p regexp)))
> (org-highlight-new-match (match-beginning 0) (match-end 
0) 'org-sparse-tree-leaf)

>   (org-highlight-new-match (match-beginning 0) (match-end 0
15141,15145c15144,15149
< (defun org-highlight-new-match (beg end)
<   "Highlight from BEG to END and mark the highlight is an occur headline."
<   (let ((ov (org-make-overlay beg end)))
< (org-overlay-put ov 'face 'secondary-selection)
< (push ov org-occur-highlights)))
---
>   replaced with my own version to support highlighting sparse 
tree leaves

> ;; (defun org-highlight-new-match (beg end)
> ;;   "Highlight from BEG to END and mark the highlight is an occur 
headline."

> ;;   (let ((ov (org-make-overlay beg end)))
> ;; (org-overlay-put ov 'face 'secondary-selection)
> ;; (push ov org-occur-highlights)))
28233a28238,28265
> ;;  my own extension to org to show sparse tree leaves in 
different face ;

>
> ;; highlighting sparse tree leaves
>
> ;; 
> (defvar org-highlight-sparse-tree-leaf t
>   "Whether to highlight sparse tree leaves")
> (defface org-sparse-tree-leaf '((t (:background "#cdb38b")))
>   "Face for highlighting sparse tree leaves.")
>
> ;; 
> (defun org-highlight-new-match (beg end &optional highlight-face)
>   "Highlight from BEG to END and mark the highlight is an occur 
headline."

>   (let ((ov (org-make-overlay beg end)))
> (if highlight-face
> (org-overlay-put ov 'face highlight-face)
>   (org-overlay-put ov 'face 'secondary-selection))
> (push ov org-occur-highlights)))
>
> ;; 
> (defun org-has-match-in-subtree-p(regexp)
>   "Returns non-nil if there is a match for regexp in current subtree."
>   (save-match-data
> (save-excursion
>   (let ((beg (point)) (end-of-tree (org-end-of-subtree t)))
> (goto-char beg)
> (re-search-forward regexp end-of-tree t)
>
28240d28271
<

---

Carsten Dominik wrote:


On Feb 18, 2008, at 4:19 PM, Wanrong Lin wrote:



Using "PROJECT" as a TODO keyword certainly can work, however, my 
work flow usually is first quickly mark anything that needs action 
with "TODO" and later I may add more sub-items to it. Following this 
approach I will need to remember to change "TODO" to "PROJECT" once a 
TODO item starts to have sub-items. Also, if all sub-actions of a 
"PROJECT" are marked as "DONE", I need to remember to turn the 
"PROJECT" back to "TODO", as I need the sparse tree to remind me to 
double check this TODO/PROJECT item to see whether it is really all 
done, or I need to add more sub-actions to it (and turn it back to 
"PROJECT" again).


As you can see, that is a lot of manually actions and mistakes can be 
easily made. Maybe my workflow has some problem here, but I can not 
think of anything else that works better. The difficulty to me is, an 
item can be either PROJECT or TODO depending on how detailed your 
plan is, which keeps changing.


I think if we can have the *option* of selecting a different face for 
highlighting sparse tree leaves, the above can be solved elegantly. 
You can still see the whole sparse tree, but the leaves will stand out.


Just trying to push my case a little bit. :-)   Thanks a lot.


That is fine, but it does not work in this case... :-(

- Carsten




Wanrong

Carsten Dominik wrote:

Hi Wanrong,

No, I think you need to find a different way around this.
For example by using a different keyword for the headings that 
contain the true TODO items.  I use PROJECT or something similar.

When you then search for TODO, the true tasks will be highlighted.

- Carsten

On Feb 15, 2008, at 12:36 AM, Wanrong Lin wrote:


Hi,

Is it possible to highlighting only the sparse tree leaves, or even 
better, highlighting the whole sparse tree but with leaves in a 
special face?


The motivation for such a feature is this:

Suppose I have a task tree like this:

* TODO Task A
*** TODO Task A.1
* TODO Task A.1.1
* TODO Task B
*** TODO Task B.1
* TODO Task B.1.1
* TODO Task B.1.2

If I do a "org-sparse-tree", all those lines are highlighted, 
giving an impression that I have a lot of open tasks, but in 
reality I only have three tasks: A.1.1, B.1.1 and B.1.2, as the 
higher level tasks are automatically done if those are done. So it 
would be nice to highlight those leaves in a special face. Also, 
suppose both B.1.1 and B.1.2 are done, then Task B.1 should be 
highlighted as a leaf.


Hope the above makes some sense. Thank you very much for giving it 
a thought.


Wanrong

Re: [Orgmode] Agenda publishing

2008-02-21 Thread lanas
Le Jeudi, 21 Février 2008 01:09:40 +,
Bastien <[EMAIL PROTECTED]> a écrit :

>> I'm trying this but org saves the content of the agenda (for
>> instance generated with 'C-c a L') as plain text, even though I
>> specify a file name of: test.html.  Do I need to add any other
>> package to emacs to have this functionality ?

> Yes, you need htmlize.el:

> http://www.emacswiki.org/cgi-bin/wiki/Htmlize

At first it still did not work, even with htmlize.  But then I was
using Orgmode that came with emacs 22.1.  I got the latest, and put it
in the site-list directory while removing the two org files in 22.1/.

With the latest Orgmode, it works.  It works even too well.  I mean, is
there a way to produce a somewhat sober output than an actual emacs
'screenshot' (in my case with the blue background I'm using in
emacs) ?  Something like the regular html output of an org file done
with org-export-as-html.  The blue background and the actual emacs
fonts are nice in html but are a bit too colorful for regular use.

The latest Orgmode works nicely, but a bit on the slow side for loading
times.  I think there's a way to compile .el files to accelerate
processing.  Could you tell me what command is used to compile Orgmode ?

Thanks,

Al



___
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] Agenda publishing

2008-02-21 Thread Manish
On Fri, Feb 22, 2008 at 6:11 AM, lanas <[EMAIL PROTECTED]> wrote:
> Le Jeudi, 21 Février 2008 01:09:40 +,
>
> Bastien <[EMAIL PROTECTED]> a écrit :
>
>
> >> I'm trying this but org saves the content of the agenda (for
>  >> instance generated with 'C-c a L') as plain text, even though I
>  >> specify a file name of: test.html.  Do I need to add any other
>  >> package to emacs to have this functionality ?
>
>  > Yes, you need htmlize.el:
>
>  > http://www.emacswiki.org/cgi-bin/wiki/Htmlize
>
>  At first it still did not work, even with htmlize.  But then I was
>  using Orgmode that came with emacs 22.1.  I got the latest, and put it
>  in the site-list directory while removing the two org files in 22.1/.
>
>  With the latest Orgmode, it works.  It works even too well.  I mean, is
>  there a way to produce a somewhat sober output than an actual emacs
>  'screenshot' (in my case with the blue background I'm using in
>  emacs) ?  Something like the regular html output of an org file done
>  with org-export-as-html.  The blue background and the actual emacs
>  fonts are nice in html but are a bit too colorful for regular use.
>
>  The latest Orgmode works nicely, but a bit on the slow side for loading
>  times.  I think there's a way to compile .el files to accelerate
>  processing.  Could you tell me what command is used to compile Orgmode ?
>

Just a `make' in org directory should do it.

-- 
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] Agenda publishing

2008-02-21 Thread Bastien Guerry
Manish <[EMAIL PROTECTED]> writes:

>>  At first it still did not work, even with htmlize.  But then I was
>>  using Orgmode that came with emacs 22.1.  I got the latest, and put it
>>  in the site-list directory while removing the two org files in
>>  22.1/.

Yes.  Sorry, I often wrongly assume people are using a recent Org.

>>  With the latest Orgmode, it works.  It works even too well.  I mean, is
>>  there a way to produce a somewhat sober output than an actual emacs
>>  'screenshot' (in my case with the blue background I'm using in
>>  emacs) ?  Something like the regular html output of an org file done
>>  with org-export-as-html.  The blue background and the actual emacs
>>  fonts are nice in html but are a bit too colorful for regular use.

This has been previously requested, as long with some code to export in
a TeX file.  I am working on code that will help do this. 

>>  The latest Orgmode works nicely, but a bit on the slow side for loading
>>  times.  I think there's a way to compile .el files to accelerate
>>  processing.  Could you tell me what command is used to compile Orgmode ?
>>
>
> Just a `make' in org directory should do it.

Alternatively, if for one reason or another you want to compile .el
files by hand, go to a directory with `C-x d', mark .el files with 
`% m \.el RET", then try to byte-compile them all with `B'.

HTH,

-- 
Bastien


___
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] appt-delete

2008-02-21 Thread Richard G Riley

Should appt-delete not also remove a diary entry from the agenda view?


___
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] Agenda publishing

2008-02-21 Thread lanas
From: lanas <[EMAIL PROTECTED]>
To: Bastien Guerry <[EMAIL PROTECTED]>
Subject: Re: [Orgmode] Agenda publishing
Date: Thu, 21 Feb 2008 21:14:39 -0500
X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.13; x86_64-redhat-linux-gnu)

Le Vendredi, 22 Février 2008 01:35:31 +,
Bastien Guerry <[EMAIL PROTECTED]> a écrit :

(sorry for the private reply as sometimes for some reason 
sylpheed uses the private e-mail instead of the mailing lists')

> Manish <[EMAIL PROTECTED]> writes:  

>> Just a `make' in org directory should do it.  
> 
> Alternatively, if for one reason or another you want to compile .el
> files by hand, go to a directory with `C-x d', mark .el files with 
> `% m \.el RET", then try to byte-compile them all with `B'.  

Thanks a lot for your help, it's appreciated.  The make works but one
thing is left out: emacs is still referring to the previous (4.67) info
pages.  Doing a 'make install' has created /usr/local/info/.  Then I had
to copy the file to /usr/local/share/info/ which is where the otehr
info files are on a Fedora Core 6 system.

Cheers,

Al


___
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] Highlighting Sparse Tree Leaves

2008-02-21 Thread Carsten Dominik

Hi Wanrong, thanks for the code. It looks good, I will put it into
my trickler to reconsider a some time in the future.

- Carsten

On Feb 21, 2008, at 11:53 PM, Wanrong Lin wrote:



Hi, Carsten,

I hacked a patch that does what I need. Just in case you change your  
mind in the future, or anyone else has the same need as I, here is  
the patch (against org.el in 5.22a. I did not get time to learn git  
yet). Thanks.


Wanrong



15082c15082,15085
< (org-highlight-new-match (match-beginning 0) (match-end 0)))
---
> ;; 
> (if (and org-highlight-sparse-tree-leaf (not (org-has- 
match-in-subtree-p regexp)))
> (org-highlight-new-match (match-beginning 0) (match- 
end 0) 'org-sparse-tree-leaf)
>   (org-highlight-new-match (match-beginning 0) (match-end  
0

15141,15145c15144,15149
< (defun org-highlight-new-match (beg end)
<   "Highlight from BEG to END and mark the highlight is an occur  
headline."

<   (let ((ov (org-make-overlay beg end)))
< (org-overlay-put ov 'face 'secondary-selection)
< (push ov org-occur-highlights)))
---
>   replaced with my own version to support highlighting  
sparse tree leaves

> ;; (defun org-highlight-new-match (beg end)
> ;;   "Highlight from BEG to END and mark the highlight is an occur  
headline."

> ;;   (let ((ov (org-make-overlay beg end)))
> ;; (org-overlay-put ov 'face 'secondary-selection)
> ;; (push ov org-occur-highlights)))
28233a28238,28265
> ;;  my own extension to org to show sparse tree leaves in  
different face ;

>
> ;; highlighting sparse tree leaves
>
> ;; 
> (defvar org-highlight-sparse-tree-leaf t
>   "Whether to highlight sparse tree leaves")
> (defface org-sparse-tree-leaf '((t (:background "#cdb38b")))
>   "Face for highlighting sparse tree leaves.")
>
> ;; 
> (defun org-highlight-new-match (beg end &optional highlight-face)
>   "Highlight from BEG to END and mark the highlight is an occur  
headline."

>   (let ((ov (org-make-overlay beg end)))
> (if highlight-face
> (org-overlay-put ov 'face highlight-face)
>   (org-overlay-put ov 'face 'secondary-selection))
> (push ov org-occur-highlights)))
>
> ;; 
> (defun org-has-match-in-subtree-p(regexp)
>   "Returns non-nil if there is a match for regexp in current  
subtree."

>   (save-match-data
> (save-excursion
>   (let ((beg (point)) (end-of-tree (org-end-of-subtree t)))
> (goto-char beg)
> (re-search-forward regexp end-of-tree t)
>
28240d28271
<

---

Carsten Dominik wrote:


On Feb 18, 2008, at 4:19 PM, Wanrong Lin wrote:



Using "PROJECT" as a TODO keyword certainly can work, however, my  
work flow usually is first quickly mark anything that needs action  
with "TODO" and later I may add more sub-items to it. Following  
this approach I will need to remember to change "TODO" to  
"PROJECT" once a TODO item starts to have sub-items. Also, if all  
sub-actions of a "PROJECT" are marked as "DONE", I need to  
remember to turn the "PROJECT" back to "TODO", as I need the  
sparse tree to remind me to double check this TODO/PROJECT item to  
see whether it is really all done, or I need to add more sub- 
actions to it (and turn it back to "PROJECT" again).


As you can see, that is a lot of manually actions and mistakes can  
be easily made. Maybe my workflow has some problem here, but I can  
not think of anything else that works better. The difficulty to me  
is, an item can be either PROJECT or TODO depending on how  
detailed your plan is, which keeps changing.


I think if we can have the *option* of selecting a different face  
for highlighting sparse tree leaves, the above can be solved  
elegantly. You can still see the whole sparse tree, but the leaves  
will stand out.


Just trying to push my case a little bit. :-)   Thanks a lot.


That is fine, but it does not work in this case... :-(

- Carsten




Wanrong

Carsten Dominik wrote:

Hi Wanrong,

No, I think you need to find a different way around this.
For example by using a different keyword for the headings that  
contain the true TODO items.  I use PROJECT or something similar.

When you then search for TODO, the true tasks will be highlighted.

- Carsten

On Feb 15, 2008, at 12:36 AM, Wanrong Lin wrote:


Hi,

Is it possible to highlighting only the sparse tree leaves, or  
even better, highlighting the whole sparse tree but with leaves  
in a special face?


The motivation for such a feature is this:

Suppose I have a task tree like this:

* TODO Task A
*** TODO Task A.1
* TODO Task A.1.1
* TODO Task B
*** TODO Task B.1
* TODO Task B.1.1
* TODO Task B.1.2

If I do a "org-sparse-tree", all those lines are highlighted,  
giving an impression that I have a lot of open tasks, but in  
reality I only have three tasks: A.1.1, B.1.1 and B.1.2, as the  
higher level tasks are automatically done if those are done. So  
it would be nice to hi