FR: date marking in calendar

FR: date marking in calendar

[Wanrong Lin]

Hi,

If I have (setq mark-holidays-in-calendar t), the calendar window will 
mark all holidays. I am thinking it will be great if we can mark 
appointments in org-files. Maybe we can have a command to do the following:

1. Find a subset of headlines using the usual todo, or tag-todo search 
syntax
2. Extract all active timestamps from those selected headlines and mark 
them in the calendar

Or we can have a function that simply extract all active time stamps 
from the headlines in an todo/tag-todo search result buffer and mark 
them in the calendar. We can then do the marking in two steps:

1. Find the headlines using existing org-mode commands
2. In the result buffer, invoke the "org-mark-calendar" function to mark 
the calendar

The marked calendar gives a better overview of things we are interested 
(appointment in my case), and make it easier to avoid conflicted schedules.

Wanrong

Re: FR: date marking in calendar

[Bastien]

Wanrong Lin <wanrong.lin@gmail.com> writes:

> If I have (setq mark-holidays-in-calendar t), the calendar window will
> mark all holidays. I am thinking it will be great if we can mark
> appointments in org-files. 

(require 'diary-lib)
(add-hook 'diary-display-hook 'fancy-diary-display)

Adding this in your ~/.diary file should do it:

%%(org-diary :scheduled :timestamp :deadline)

HTH,

-- 
Bastien

time lag in re-scheduling the item in Agenda buffer

[Xin Shi]

Hi,

I'm using the 5.22a version.  When I view the agenda in the buffer, I 
use keyboard C-c C-s to re-schedule some items. It first gives a "nil" 
in the min-buffer, and after about 2 or 3 seconds gives me the calendar 
to choose. It looks like slow compared with doing the same thing in the 
.org file on those items. Are there any reason for that or to make it a 
little bit faster?

Thanks!

Xin

Re: time lag in re-scheduling the item in Agenda buffer

[Bastien]

Xin Shi <xs32@cornell.edu> writes:

> I'm using the 5.22a version.  When I view the agenda in the buffer, I use
> keyboard C-c C-s to re-schedule some items. It first gives a "nil" in the
> min-buffer, and after about 2 or 3 seconds gives me the calendar to
> choose. It looks like slow compared with doing the same thing in the .org
> file on those items. Are there any reason for that or to make it a little
> bit faster?

This was a bug -- fixed, thanks.

-- 
Bastien

export-latex beamer

[Xin Shi]

Hi,

I'm wondering if it's possible to export org file to latex beamer 
format, to make pdf slides.  Or are there any thoughts?

Xin

Re: export-latex beamer

[Bastien]

Xin Shi <xs32@cornell.edu> writes:

> I'm wondering if it's possible to export org file to latex beamer
> format, to make pdf slides.  

You can export to LaTeX and work from here.  Direct export to beamer is
not supported right now.  I hope it will be someday, but it won't happen
before a while...

The list have been pretty busy these days (partly because of me) and
maybe we should slow down a bit on the [Feature request] side -- let's
concentrate on bugs before the next release!

-- 
Bastien

Re: export-latex beamer

[Xin Shi]

All right. Thank you!

Xin



Bastien wrote:
> Xin Shi <xs32@cornell.edu> writes:
>
>   
>> I'm wondering if it's possible to export org file to latex beamer
>> format, to make pdf slides.  
>>     
>
> You can export to LaTeX and work from here.  Direct export to beamer is
> not supported right now.  I hope it will be someday, but it won't happen
> before a while...
>
> The list have been pretty busy these days (partly because of me) and
> maybe we should slow down a bit on the [Feature request] side -- let's
> concentrate on bugs before the next release!
>
>   

Re: export-latex beamer

[Nick Dokos]

Hi Bastien,

I have a quick-n-dirty patch to export an org file as a beamer
document. It has been tested on one very simple org file only, so
YMMV. I hope I have not broken anything else in the process but if I
have, please let me know.  It takes level 1 headlines and makes them
into frametitles for a frame, starts an itemize environment and includes
all level 2 subordinates as items. At the end, it closes the itemize
enviroment and the frame. It's just barely enough to cover the simplest
conversion, but I hope it's useful nevertheless.

I *did* change the format of org-export-latex-classes. Instead of pairs,
I use lists: the third element of the list, if present, is the string to
use to close any environment(s) opened by the first or second elements
of the list. So if this variable has been customized, things are going
to break.

HTH,
Nick

PS. I see I also added a second clause to some conditionals, checking
whether the subcontent is null and avoiding the function call in that
case. That's only a small optimization that I introduced to simplify
the tracing that I was doing when trying to understand the code. I
don't think it hurts anything to leave it in, however if it causes
problems, it can be ripped out.

--- a/lisp/org-export-latex.el
+++ b/lisp/org-export-latex.el
@@ -89,31 +89,39 @@
 \\usepackage[utf8]{inputenc}
 \\usepackage[T1]{fontenc}
 \\usepackage{hyperref}"
-     ("\\section{%s}" . "\\section*{%s}")
-     ("\\subsection{%s}" . "\\subsection*{%s}")
-     ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
-     ("\\paragraph{%s}" . "\\paragraph*{%s}")
-     ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
+     ("\\section{%s}"  "\\section*{%s}")
+     ("\\subsection{%s}"  "\\subsection*{%s}")
+     ("\\subsubsection{%s}"  "\\subsubsection*{%s}")
+     ("\\paragraph{%s}"  "\\paragraph*{%s}")
+     ("\\subparagraph{%s}"  "\\subparagraph*{%s}"))
     ("report"
      "\\documentclass[11pt,a4paper]{report}
 \\usepackage[utf8]{inputenc}
 \\usepackage[T1]{fontenc}
 \\usepackage{hyperref}"
-     ("\\part{%s}" . "\\part*{%s}")
-     ("\\chapter{%s}" . "\\chapter*{%s}")
-     ("\\section{%s}" . "\\section*{%s}")
-     ("\\subsection{%s}" . "\\subsection*{%s}")
-     ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
+     ("\\part{%s}"  "\\part*{%s}")
+     ("\\chapter{%s}"  "\\chapter*{%s}")
+     ("\\section{%s}"  "\\section*{%s}")
+     ("\\subsection{%s}"  "\\subsection*{%s}")
+     ("\\subsubsection{%s}"  "\\subsubsection*{%s}"))
     ("book"
      "\\documentclass[11pt,a4paper]{book}
 \\usepackage[utf8]{inputenc}
 \\usepackage[T1]{fontenc}
 \\usepackage{hyperref}"
-     ("\\part{%s}" . "\\part*{%s}")
-     ("\\chapter{%s}" . "\\chapter*{%s}")
-     ("\\section{%s}" . "\\section*{%s}")
-     ("\\subsection{%s}" . "\\subsection*{%s}")
-     ("\\subsubsection{%s}" . "\\subsubsection*{%s}")))
+     ("\\part{%s}"  "\\part*{%s}")
+     ("\\chapter{%s}"  "\\chapter*{%s}")
+     ("\\section{%s}"  "\\section*{%s}")
+     ("\\subsection{%s}"  "\\subsection*{%s}")
+     ("\\subsubsection{%s}"  "\\subsubsection*{%s}"))
+    ("beamer"
+     "\\documentclass{beamer}
+\\usepackage[utf8]{inputenc}
+\\usepackage[T1]{fontenc}
+\\usepackage{hyperref}"
+     ("\\frame{\\frametitle{%s}\\begin{itemize}"  "\\frame{\\frametitle{%s}\\begin{itemize}" "\\end{itemize}}")
+     ("\\item{%s}"  "\\item*{%s}")
+     (""  "")))
   "Alist of LaTeX classes and associated header and structure.
 If #+LaTeX_CLASS is set in the buffer, use its value and the
 associated information.  Here is the structure of each cell:
@@ -567,11 +575,14 @@ and its content."
      ;; Normal conversion
      ((<= level org-export-latex-sectioning-depth)
       (let ((sec (nth (1- level) org-export-latex-sectioning)))
-	(insert (format (if num (car sec) (cdr sec)) heading) "\n"))
-      (insert (org-export-latex-content content))
-      (cond ((stringp subcontent) (insert subcontent))
-            ((null subcontent))
-	    ((listp subcontent) (org-export-latex-sub subcontent))))
+	(insert (format (if num (car sec) (cadr sec)) heading) "\n")
+        (insert (org-export-latex-content content))
+        (cond ((stringp subcontent) (insert subcontent))
+              ((null subcontent))
+              ((listp subcontent) (org-export-latex-sub subcontent)))
+        (let ((closing (caddr sec)))
+          (if closing
+              (insert closing "\n")))))
      ;; At a level under the hl option: we can drop this subsection
      ((> level org-export-latex-sectioning-depth)
       (cond ((eq org-export-latex-low-levels 'description)

Re: export-latex beamer

[Pete Phillips]

>>>>> "Nick" == Nick Dokos <nicholas.dokos@hp.com> writes:

    Nick> Hi Bastien, I have a quick-n-dirty patch to export an org file
    Nick> as a beamer document. 

Cool. I use lyx to edit beamer presentations which I export as pdf
files. Do you have plans to add other beamer support such as inserting
images etc ? Whilst I like lyx a lot, I prefer editing in emacs for
speed.

Would be great if it supported some sort of localisation file (so I can
include the usual bunch of stuff that gives me blue background, yellow
text, etc etc).

Pete

Re: export-latex beamer

[Nick Dokos]

Pete Phillips <pete@smtl.co.uk> wrote:

> >>>>> "Nick" == Nick Dokos <nicholas.dokos@hp.com> writes:
> 
>     Nick> Hi Bastien, I have a quick-n-dirty patch to export an org file
>     Nick> as a beamer document. 
> 

NB: the original patch was wrong and it does not apply cleanly. I sent
an updated patch to the list yesterday.

> Cool. I use lyx to edit beamer presentations which I export as pdf
> files. Do you have plans to add other beamer support such as inserting
> images etc ? Whilst I like lyx a lot, I prefer editing in emacs for
> speed.
> 
Plans? What's that?-) Seriously though, I probably won't have the time
to do anything about it for a while, particularly since I'm no expert
in any of the technologies involved, so I would likely need to do
some trial-and-error research which takes far longer than I could afford
right now.

> Would be great if it supported some sort of localisation file (so I can
> include the usual bunch of stuff that gives me blue background, yellow
> text, etc etc).
> 
You can customize the variable org-export-latex-classes to do anything
that can be done in the preamble to the document, but I don't know
whether the above can be done there. If it needs to be done after the
\begin{document}, this won't work.  An ugly workaround is to customize
org-export-latex-title-command to be more than just "\\maketitle",
although there might be a less hackish way. A hook could be added to do
that of course, but I tend to agree with you that a localization file
might provide for more flexibility in the long run.

Regards,
Nick

Re: export-latex beamer

[Russell Adams]

> include the usual bunch of stuff that gives me blue background, yellow
> text, etc etc).
> 
> Pete
> 

Couldn't you just insert the raw latex to set the background?


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

Re: FR: date marking in calendar

[Bastien]

Bastien <bzg@altern.org> writes:

>> If I have (setq mark-holidays-in-calendar t), the calendar window will
>> mark all holidays. I am thinking it will be great if we can mark
>> appointments in org-files. 
>
> (require 'diary-lib)
> (add-hook 'diary-display-hook 'fancy-diary-display)
>
> Adding this in your ~/.diary file should do it:
>
> %%(org-diary :scheduled :timestamp :deadline)

A note of caution: If you have *many* appointments in your org agenda
files, then each fancy display of the calendar will be much slower.  

If you just need to use `d' on a calendar date, but don't want the dates
to be fontified, add `&' before the diary sexp:

&%%(org-diary :scheduled :timestamp :deadline)

HTH,

-- 
Bastien

Re: FR: date marking in calendar

[Wanrong Lin]

Bastien,

Thanks a lot for the suggestion. My appointments are in org files are 
agenda are marked with a tag, so using diary as you suggested does not 
work exactly as I wished. But I was not even aware of the existence of 
org-diary and its usage, maybe I can find some other use of it later on.

Also, I did not see any calendar markings in my trial even with 
org-diary, but I suspect it might be because I ran emacs in a text 
terminal, not an X-window or Windows. I will try it later.

Wanrong

Bastien wrote:
>> (require 'diary-lib)
>> (add-hook 'diary-display-hook 'fancy-diary-display)
>>
>> Adding this in your ~/.diary file should do it:
>>
>> %%(org-diary :scheduled :timestamp :deadline)
>>     
>
> A note of caution: If you have *many* appointments in your org agenda
> files, then each fancy display of the calendar will be much slower.  
>
> If you just need to use `d' on a calendar date, but don't want the dates
> to be fontified, add `&' before the diary sexp:
>
> &%%(org-diary :scheduled :timestamp :deadline)
>
> HTH,
>
>   

Re: FR: date marking in calendar

[Bastien Guerry]

Wanrong Lin <wanrong.lin@gmail.com> writes:

> Thanks a lot for the suggestion. My appointments are in org files are
> agenda are marked with a tag, so using diary as you suggested does not
> work exactly as I wished.

Of course, my suggestion only works if you use the usual Org machinery
for appointments...

> Also, I did not see any calendar markings in my trial even with org-diary,
> but I suspect it might be because I ran emacs in a text terminal, not an
> X-window or Windows. I will try it later.

It should be visible in a text terminal with a decent version of Emacs.  

-- 
Bastien

Re: FR: date marking in calendar

[Wanrong Lin]

Hi, Bastien,

Following your suggestion now I can see a pretty list of scheduled 
things when I run "diary", but I don't see any marking of dates in my 
calendar buffer. Is there anything I could have missed? Thank you very much.

Wanrong

Bastien Guerry wrote:
> Wanrong Lin <wanrong.lin@gmail.com> writes:
>
>   
>> Thanks a lot for the suggestion. My appointments are in org files are
>> agenda are marked with a tag, so using diary as you suggested does not
>> work exactly as I wished.
>>     
>
> Of course, my suggestion only works if you use the usual Org machinery
> for appointments...
>
>   
>> Also, I did not see any calendar markings in my trial even with org-diary,
>> but I suspect it might be because I ran emacs in a text terminal, not an
>> X-window or Windows. I will try it later.
>>     
>
> It should be visible in a text terminal with a decent version of Emacs.  
>
>   

Re: FR: date marking in calendar

[Bastien]

Wanrong Lin <wanrong.lin@gmail.com> writes:

> Following your suggestion now I can see a pretty list of scheduled
> things when I run "diary", but I don't see any marking of dates in my
> calendar buffer. Is there anything I could have missed? 

(add-hook 'initial-calendar-window-hook 'mark-diary-entries)

If %%(org-diary :scheduled :timestamp) throws an error, cheat a little
and use this instead:

%%(condition-case nil (org-diary :scheduled :timestamp) (error nil))

-- 
Bastien

Re: FR: date marking in calendar

[Cezar Halmagean]

Bastien <bzg@altern.org> writes:

> Wanrong Lin <wanrong.lin@gmail.com> writes:
>
>> Following your suggestion now I can see a pretty list of scheduled
>> things when I run "diary", but I don't see any marking of dates in my
>> calendar buffer. Is there anything I could have missed? 
>
> (add-hook 'initial-calendar-window-hook 'mark-diary-entries)
>
> If %%(org-diary :scheduled :timestamp) throws an error, cheat a little
> and use this instead:
>
> %%(condition-case nil (org-diary :scheduled :timestamp) (error nil))

Does anyone have a screenshot of how this looks like ? I can't imagine
what it does and how it displays things.

Regards,
Cezar

Re: Re: FR: date marking in calendar

[Bastien Guerry]

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

"Cezar Halmagean" <cezar@mixandgo.com> writes:

>> (add-hook 'initial-calendar-window-hook 'mark-diary-entries)
>>
>> If %%(org-diary :scheduled :timestamp) throws an error, cheat a little
>> and use this instead:
>>
>> %%(condition-case nil (org-diary :scheduled :timestamp) (error nil))
>
> Does anyone have a screenshot of how this looks like ? I can't imagine
> what it does and how it displays things.

See the screenshot.  

The dates in red color are those where there is a diary appointment or
an org agenda scheduled item.


[-- Attachment #2: calendar.jpg --]
[-- Type: image/jpeg, Size: 19300 bytes --]

[-- Attachment #3: Type: text/plain, Size: 13 bytes --]


-- 
Bastien

[-- Attachment #4: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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: FR: date marking in calendar

[Wanrong Lin]

Thanks. It works now. I found I need only set
(setq mark-diary-entries-in-calendar t)
to have the markings show up.

Wanrong

Bastien wrote:
> Wanrong Lin <wanrong.lin@gmail.com> writes:
>
>   
>> Following your suggestion now I can see a pretty list of scheduled
>> things when I run "diary", but I don't see any marking of dates in my
>> calendar buffer. Is there anything I could have missed? 
>>     
>
> (add-hook 'initial-calendar-window-hook 'mark-diary-entries)
>
> If %%(org-diary :scheduled :timestamp) throws an error, cheat a little
> and use this instead:
>
> %%(condition-case nil (org-diary :scheduled :timestamp) (error nil))
>
>   

FR: more options in (org-diary)

[Wanrong Lin]

Hi,

This is branched off from the previous thread "FR: date marking in 
calendar". I got the marking working now with the help from Bastien. My 
intention was to mark calendar with important "hard schedule" 
(appointments) that can not be conflicted with. However, I could not do 
it with current org-diary function, as detailed in the following:

1. Apparently, I can not use %%(org-diary :scheduled), as a lot of 
"SCHEDULED" items are just "softly scheduled". I would like to do those 
things at specified time, but do not HAVE TO do them.
2. If I use %%(org-diary :timestamp), and use plain active time stamps 
for all my appointments, all my appointments will be marked, however, 
entries like this will get marked too:

***** Payday
      <2007-11-02 Fri +2w>

The above entry is just a reminder so I will know it is a payday by 
checking today's agenda. But this does not require any action and hence 
is not an appointment. I can not change the above plain time stamp to 
"SCHEDULED" because that will make it show up as a "past due" task in my 
everyday agenda.

3. My way of indicating that a task is an appointment is as following:

* TODO See Doctor 
Smith                                                   :APPOINT:
  SCHEDULED: <2008-03-05 Wed 09:00>

I use a tag to indicate an appointment. This makes it easy to search and 
list all appointments and clears the ambiguity around "what exactly is 
an appointment". Also I use "SCHEDULED" instead of a plain time stamp 
because if for some reason I missed an appointment (say because I took a 
3-week vacation), I want the appointment to show up in my agenda as a 
past due task instead of being silently passed by.

4. I am reluctant to put my appointments in the diary file, as I want to 
have all my planning information in org files. Org file entries provide 
much more than diary entries. For example, I can group my health related 
appointments in a sub-tree. I can archive my previous dental 
appointments so I know when I should see my dentist next time, and etc.

It seems if we can enhance (org-diary) function a little bit by doing 
the following, my problem can be solved:

1. add options to limit search to "TODO" items only (I can compromise by 
using plain time stamp in my appointments)
2. and/or, add options to limit search to items with certain tags (my 
appointment set up will work very well with this option)

Any comments?  Thank you very much.

Wanrong