Re: [Orgmode] Re: OrgmodeWiki Support
Hi Paul, On Dec 18, 2009, at 9:35 PM, Paul Sexton wrote: Carsten Dominik carsten.dominik at gmail.com writes: [snip] I think it would be useful to discuss this proposal first in a broader sense. Let me try to make a start. A few days ago, Paul Sexton submitted his proposal for simple file-to-file links based on etags. He wanted to make [[sometext]] be a link to sometext where the target definition sometext can be in a different file. Furthermore, his proposal uses an external program to do the indexing of the tags, and following the links uses the etags code shipped with Emacs. Finally, Paul's proposal also contains a way to automatically create new topics when a link is called that does not yet have a target. Now we are talking about WikiWords, or CamelCase links. Here the idea is that any such mixed-case word automatically is treated as a link. Traditionally these links to a separate file with name given by the link text directly. But I suppose it could also got to a target somewhere in a file? For a couple of reasons it seems to me that it would be useful to look at these proposals together. For one thing, I am not a huge fan of the zillions of files that will be created when using the one-file-per-word approach. Since Org-mode is outline based, it seem to make a lot of sense to have many topics per file. One way to move into this direction would be to still use etags to index the possible targets, and then to turn specific words (like CamelCase words) directly into links without the need to surround them with [[...]]. But of course, we could also have an implementation as Adam proposes it, with CamelCase words linking to files, and then [[target]] linking to targets. Can we discuss this for a bit? - Carsten Hi Carsten, In the other thread, you say you have implemented a hook whose function(s) are run when attempting to open a link. From your description it sounds like the hook is run FIRST, and org's default behaviour only happens if the hook functions don't override it. That is correct, because the default behavior not only searches for target, but also for plain text searches, and this may disrupt the workings of your code. Since all targets in the current file should also be in your tags file, I think they will be fond without any problem in the current file as well. So it is early enough to fall back to full text search by the time your ctags search has *not* returned a successful match. Or am I missing something here? However, both the link-to-file-of-same-name proposal and my etags functionality would be more easily implemented with a hook function that is called only when org can't find a specific target for [[plain link]]. At the moment org defaults to performing a full-text search for plain link. Both the wikiwords and the etags behaviours need to happen instead of that default behaviour, but neither needs to override the rest of org's link-opening behaviour. Well, all the normal link stuff like http: links and file: links is still does before calling the hook! Re the WikiWords idea -- this could be done in 2 independent parts: 1. Option to tell org to interpret all CamelCase words as plain links (this might be behaviour that some people want by itself) 2. Function, called when org can't find target for plain link, that tries to open and visit a file with the same name as the link. I think a hook to change the default behaviour of org when it can't find an explicit target for a plain link is a very good idea and would probably lead to other useful stuff. Personally I don't find the default behaviour of full-text search to be useful. Exactly. So why does your org-ctags still need a patch? I am confused. Paul P.S. My wishlist includes using a different colour to fontify links whose targets don't exist (a la wikipedia with its undefined links in red). Can be done, but not sure how to do it efficiently. Indeed, this would be relatively hard to do efficiently. - but not impossible. - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please 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 format control - emphasis and radio link
Hi Baptiste,
first of all, why don't you just use not-a-lint instead of not_a_link?
Using underscore sort-of asks for problems in this context.
Also, why do you want the links to be in typewriter font? This is
unusual. Maybe instead of modifying org-emph-alist, you'd want to add
to it and create a new emphasis with is texttt but not verbatim?
Finally,
other_radio_link
it is indeed a bug that this is not exported with escaped underscores.
I have fixed this issue.
- Carsten
On Dec 23, 2009, at 3:27 PM, Baptiste Fouques wrote:
Hi,
I am using Org for a while, and I actually do like it a lot. I'd like
to extend my usage a bit, but I have some difficulties with export
format.
Basically, my point is about expanding/escaping control sequences in
latex output.
My sample org file is :
#+TITLE: Org Test
#+AUTHOR:Baptiste Fouques
#+EMAIL: b...@m4tp.org
#+DESCRIPTION: org mode link test
#+OPTIONS: ^:nil
* org-export-latex-emphasis-alist difficutlies
# link_radio
=link_radio=
=not_a_link=
* Radio Link format
other_radio_link
EOF-
What I would expect as a Latex export would be :
\section{org-export-latex-emphasis-alist difficutlies}
\label{sec-1}
\label{link_radio}
\texttt{\hyperref[link_radio]{link\_radio}}
\texttt{not\_a\_link}
\section{Radio Link format}
\label{sec-2}
\label{other_radio_link}other\_radio\_link
EOF
But, I naturally get
...
\texttt{[[link\_radio][link\_radio]]} {1}
...
\label{other_radio_link}other_radio_link {2}
which does not work at all as {1} is just a no-sense for LaTeX, and
{2} has not escaped the _ in plain text output (also the org header
has #+OPTIONS: ^:nil ).
I can manage to get {1} quite correct, manipulating
org-export-latex-emphasis-alist : ( ... (= \\texttt{%s} nil) ... )
...
\texttt{\hyperref[link_radio]{link\_radio}}
...
but then, =not_a_link= became naturally broken ( _ are no more
escaped ... )
And I found no such parameter that can be used to manipulate radio
link export format (to get oher_radio_link beeing exported as
\label{other_radio_link}other\_radio\_link .
If you could help me on this issue, I will be able to use Org mode
more widely in my everyday work (and propose it to my co-worker).
Thanks a lot,
---Bat
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Replace the string in project setting
Carsten Dominik carsten.domi...@gmail.com writes: On Dec 24, 2009, at 3:12 AM, Water Lin wrote: I set publishing project by -- (require 'org-publish) (setq org-publish-project-alist - and I also want to embed css sheetstyle by setting :style style.../style But the style is too long and I want to use a string to replace it. So I set a string by --- (setq waterstyle style/style) --- and replace the :style like following: --- :style waterstyle --- But while I publish the project, Emacs prompts an error about this. I am not very familiar with elisp. Can I embed the style by a string like this? Hi, you need to do this: (setq waterstyle .) (setq org-publish-project-alist `((.. .. :style ,waterstyle ))) (note the *backquote* instead of a normal quote to quote the value of org-publish-project-alist, and note the comma before waterstyle to interpolate the value into the quoted list. HTH - Carsten Thanks, I think I am not just know how to do it but also know why I need to do this. Thanks Water Lin Thanks Water Lin -- Water Lin's notes and pencils: http://en.waterlin.org Email: water...@ymail.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten -- Water Lin's notes and pencils: http://en.waterlin.org Email: water...@ymail.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Contracts in Orgmode
At Tue, 22 Dec 2009 13:49:07 -0800, Markus Heller wrote: After some more googling and having a closer look at the org manual, I came up with a solution that might work. It uses dependencies and org-depend.el. I've pasted it below, and as usual, I'd appreciate any comments/improvement :) I realize that this is not exactly an elegant solution, but it might work for me. I'd still like to see a way in orgmode to allow clocking in on certain tasks only during a specific period of time, maybe something like ** Contract for Client A :PROPERTIES: :START: 01-01-2010 :EXPIRY: 03-31-2010 :END: Then, when the START date is reached, the task state gets changed to the TODO or STARTED, and once the expiry date is reached, it gets marked DONE, and cannot be clocked in anymore. I'm not sure if this is a feature that would be of general interest ... But what do the experts think? With regards to closing expired items you may take a look at org-expiry.el in the contrib directory. It provides a function to check for and act upon entries that are past their expiration date. What I am not quite understanding is the wish to be unable to clock in a closed item: Isn't clocking in something you do deliberately? Regards -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. maus.da...@gmail.com ICQ... 241051416 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] custom agenda view
I try to make custom agenda view with todo keyword STARTED and tag @HOME I wrote this code (setq org-agenda-custom-commands (quote ((w work tasks tags-todo +start...@work ((org-agenda-todo-ignore-with-date nil))) (h home tasks tags-todo +start...@home ((org-agenda-todo-ignore-with-date nil))) (n Notes tags NOTE nil but it's not work. -- Highlink Ltd. St-Peterburg, Russia +7 812 3341212 http://www.hl.ru ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] custom agenda view
On Thu, Dec 24, 2009 at 4:40 PM, Yuri Goncharov wrote: I try to make custom agenda view with todo keyword STARTED and tag @HOME I wrote this code (setq org-agenda-custom-commands (quote ((w work tasks tags-todo +start...@work ((org-agenda-todo-ignore-with-date nil))) (h home tasks tags-todo +start...@home ((org-agenda-todo-ignore-with-date nil))) (n Notes tags NOTE nil but it's not work. I will and run your scenario later but may be this can be of help too http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.php -- Manish ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: custom agenda view
Yuri Goncharov g...@hl.ru writes: I try to make custom agenda view with todo keyword STARTED and tag @HOME I wrote this code (setq org-agenda-custom-commands (quote ((w work tasks tags-todo +start...@work ((org-agenda-todo-ignore-with-date nil))) (h home tasks tags-todo +start...@home ((org-agenda-todo-ignore-with-date nil))) (n Notes tags NOTE nil but it's not work. Does the following work? Since STARTED is a todo state, it needs to be specified with a different syntax. (setq org-agenda-custom-commands (quote ((w work tasks tags-todo @WORK/!STARTED ((org-agenda-todo-ignore-with-date nil))) (h home tasks tags-todo @HOME/!STARTED ((org-agenda-todo-ignore-with-date nil))) (n Notes tags NOTE nil Best, Matt ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] blogging org files
andrea wrote: Since I'm using org-mode I started to write really a lot, and many of those things could easily become articles to blog somewhere. I got sick of wordpress and all php related stuff, and I found this: http://metajack.im/2009/01/23/blogging-with-git-emacs-and-jekyll/ Which is what I wanted. It doesn't support natively org-mode (textile and markdown), but I think I can just set up some hooks to auto convert my files. What do you think? I've seen there are already many packages to blog with org-mode, which ones are you using? Hi Andrea, I recently wrote a tutorial for Worg, which shows how to use Jekyll to blog with native org files. The org site seems to be timing out for me at the moment, so I can't give you the direct url. Best wishes, Ian. ___ Emacs-orgmode mailing list Please 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 format control - emphasis and radio link
Hi, thank you for having answered quickly my questions On Thu, Dec 24, 2009 at 9:31 AM, Carsten Dominik carsten.domi...@gmail.com wrote: first of all, why don't you just use not-a-lint instead of not_a_link? Using underscore sort-of asks for problems in this context. Guess that I am not really looking for problems (I am not this type of guy ;) ), but where I work, symbol names are defined with underscores as word separators, and I need a tool that handle it ... And I prefer facing the the problems when they come (well, first trying to find the correct way, before asking for help). Also, why do you want the links to be in typewriter font? still, it is about symbol names ... so the typewriter font, Then they are defined once, then any reference should link to the definition ... This is unusual. Maybe instead of modifying org-emph-alist, you'd want to add to it and create a new emphasis with is texttt but not verbatim? It do work, thanks for the advice. Also now I have to handle to prefix for word that are radio-linked and those who are not ... other_radio_link it is indeed a bug that this is not exported with escaped underscores. I have fixed this issue. Thank you. Got it and confirm that it works. Have a good Christmas --- Bat ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Contracts in Orgmode
On 12/24/2009 1:22 AM, David Maus wrote: At Tue, 22 Dec 2009 13:49:07 -0800, Markus Heller wrote: After some more googling and having a closer look at the org manual, I came up with a solution that might work. It uses dependencies and org-depend.el. I've pasted it below, and as usual, I'd appreciate any comments/improvement :) I realize that this is not exactly an elegant solution, but it might work for me. I'd still like to see a way in orgmode to allow clocking in on certain tasks only during a specific period of time, maybe something like ** Contract for Client A :PROPERTIES: :START: 01-01-2010 :EXPIRY: 03-31-2010 :END: Then, when the START date is reached, the task state gets changed to the TODO or STARTED, and once the expiry date is reached, it gets marked DONE, and cannot be clocked in anymore. I'm not sure if this is a feature that would be of general interest ... But what do the experts think? With regards to closing expired items you may take a look at org-expiry.el in the contrib directory. It provides a function to check for and act upon entries that are past their expiration date. Thanks. I'll have a look at it. What I am not quite understanding is the wish to be unable to clock in a closed item: Isn't clocking in something you do deliberately? Work should only be done if a valid contract exists (no valid contract, no payment, right? :) ). Right now, my work flow is to bring up an agenda view with all STARTED items, and then I'd clock in on the Contract. I'm not aware of how to check if the contract is valid or not, so I might be clocking in on an expired contract. Is there a way to include an expiry flag in the agenda view? Maybe there can be a regexp in the PROPERTIES that checks if the actual date is before the expiry date? If that was the case, then that would let me see right away in the agenda view if I'm about to clock in on an expired contract. I hope I'm not too confusing in my description of what I'm trying to achieve ... In any case, merry xmas to all of you! Markus ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Selective Export Question
So, no Christmas present for me? :)
Merry Christmas everyone. Thanks for all the hard work and
the help over the last year. Congratulations for working
together to produce such a fantastic tool.
Mark
Mark Elston wrote:
I have been making progress on my use of org-mode to manage both
my teaching notes and handouts in a single document. However, there
is something I still have not been able to make happen. That is
selective exporting of text *without* exporting a headline along with
it.
Here is a sample of what I would like. In this example I have sections
with common text (should be in both teaching notes and handouts) and
sections that are specific to each individual output format. What I
have below is set up to export the notes. What I would like is to
have the text (only) of the non-excluded sections and not the headlines.
--
#+TITLE: Test
#+LaTeX_CLASS: ClassNotes
#+OPTIONS: toc:nil H:8 tags:nil
#+EXPORT_EXCLUDE_TAGS: handouts
* Headline 1
some text
** Headline 1-1
even more text
* Headline 2
some more text
** Headline 2-1
Common text 1. Should be followed by handout or notes text.
* should be handouts only:handouts:
handout text
* should be notes only :notes:
notes text
** Headline 2-2
Common text 2. Should be followed by handout or notes text.
*:handouts:
handout text again
*:notes:
notes text again
--
The relevant material from my org-export-latex-classes is:
(ClassNotes \\documentclass[letter,twoside,openright]{memoir}
...
(\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(%% Level 5 . %% Level 5)
(%% Level 6 . %% Level 6)
(%% Level 7 . %% Level 7)
(%% Level 8 . %% Level 8))
...
I was hoping to allow all levels of heading to be exported but only
write comments for the levels below level 4. It didn't work out that
way.
With the above I don't get *any* of the :notes: or :handouts:
sections written out. However, if I include empty level three and four
headlines (the stars followed by a mandatory space) I get the :notes:
and :handouts: sections just fine. Except now I also get empty
\subsection{} and \subsubsection{} blocks in my latex output. I have
attached the resulting .tex file with comments pointing out the
extra heading lines I would like to *not* see...
The net result is a lot of blank space in the resulting .pdf file
between the 'common' text and the note- or handout-specific text. This
is *definitely* not what I had in mind.
Is there any way of working around this or correcting this behavior?
Mark
___
Emacs-orgmode mailing list
Please 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
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Contracts in Orgmode
On 12/24/2009 10:35 AM, Markus Heller wrote: On 12/24/2009 1:22 AM, David Maus wrote: At Tue, 22 Dec 2009 13:49:07 -0800, Markus Heller wrote: After some more googling and having a closer look at the org manual, I came up with a solution that might work. It uses dependencies and org-depend.el. I've pasted it below, and as usual, I'd appreciate any comments/improvement :) I realize that this is not exactly an elegant solution, but it might work for me. I'd still like to see a way in orgmode to allow clocking in on certain tasks only during a specific period of time, maybe something like ** Contract for Client A :PROPERTIES: :START: 01-01-2010 :EXPIRY: 03-31-2010 :END: Then, when the START date is reached, the task state gets changed to the TODO or STARTED, and once the expiry date is reached, it gets marked DONE, and cannot be clocked in anymore. I'm not sure if this is a feature that would be of general interest ... But what do the experts think? With regards to closing expired items you may take a look at org-expiry.el in the contrib directory. It provides a function to check for and act upon entries that are past their expiration date. Thanks. I'll have a look at it. What I am not quite understanding is the wish to be unable to clock in a closed item: Isn't clocking in something you do deliberately? Work should only be done if a valid contract exists (no valid contract, no payment, right? :) ). Right now, my work flow is to bring up an agenda view with all STARTED items, and then I'd clock in on the Contract. I'm not aware of how to check if the contract is valid or not, so I might be clocking in on an expired contract. Is there a way to include an expiry flag in the agenda view? Maybe there can be a regexp in the PROPERTIES that checks if the actual date is before the expiry date? If that was the case, then that would let me see right away in the agenda view if I'm about to clock in on an expired contract. Please disregard the last paragraph here. David already answered this question already. Looks like I'm already in Christmas mode ... Markus ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Selective Export Question
Merry Christmas Mark,
One way to create two LaTeX documents in the same org file using
common elements and keeping fine control over the LaTeX output is to
use Org-babel.
Here's an example from the Uses section of the Org-babel documentation
on Worg:
** Example
*** TODO Your name
- Enter your full name on the open line below.
#+srcname: your-name
#+begin_src latex
Tom Dye
#+end_src
*** TODO Your email address
- Enter your email address on the open line below.
#+srcname: your-email
#+begin_src latex
tsd at tsdye dot com
#+end_src
*** No data entry below this line
- The two source blocks here each produce a LaTeX document after
they are tangled with a call to =org-babel-tangle=.
#+begin_src latex :noweb :tangle dist-form.tex
\documentclass[12pt]{article}
\begin{document}
\section{Distribution Form}
\begin{description}
\item[Name] your-name
\item[Email] your-email
\end{description}
\end{document}
#+end_src
#+begin_src latex :noweb :tangle file-form.tex
\documentclass[10pt]{article}
\begin{document}
\section{File Form}
your-name can be reached at your-email.
\end{document}
#+end_src
To my mind, using Org-babel this way is kind of like using the Org-
mode Agenda. It frees the organization of your org file from the
organization of some external model, leaving you to organize it in the
way that makes the most sense to you.
That said, I'm relatively confident that there is some way to do what
you want in Org-mode using the built-in LaTeX exporter, but I don't
know what it might be.
All the best,
Tom
On Dec 24, 2009, at 8:43 AM, Mark Elston wrote:
So, no Christmas present for me? :)
Merry Christmas everyone. Thanks for all the hard work and
the help over the last year. Congratulations for working
together to produce such a fantastic tool.
Mark
Mark Elston wrote:
I have been making progress on my use of org-mode to manage both
my teaching notes and handouts in a single document. However, there
is something I still have not been able to make happen. That is
selective exporting of text *without* exporting a headline along with
it.
Here is a sample of what I would like. In this example I have
sections
with common text (should be in both teaching notes and handouts)
and
sections that are specific to each individual output format. What I
have below is set up to export the notes. What I would like is to
have the text (only) of the non-excluded sections and not the
headlines.
--
#+TITLE: Test
#+LaTeX_CLASS: ClassNotes
#+OPTIONS: toc:nil H:8 tags:nil
#+EXPORT_EXCLUDE_TAGS: handouts
* Headline 1
some text
** Headline 1-1
even more text
* Headline 2
some more text
** Headline 2-1
Common text 1. Should be followed by handout or notes text.
* should be handouts only:handouts:
handout text
* should be notes only :notes:
notes text
** Headline 2-2
Common text 2. Should be followed by handout or notes text.
*:handouts:
handout text again
*:notes:
notes text again
--
The relevant material from my org-export-latex-classes is:
(ClassNotes \\documentclass[letter,twoside,openright]{memoir}
...
(\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(%% Level 5 . %% Level 5)
(%% Level 6 . %% Level 6)
(%% Level 7 . %% Level 7)
(%% Level 8 . %% Level 8))
...
I was hoping to allow all levels of heading to be exported but only
write comments for the levels below level 4. It didn't work out that
way.
With the above I don't get *any* of the :notes: or :handouts:
sections written out. However, if I include empty level three and
four
headlines (the stars followed by a mandatory space) I get the :notes:
and :handouts: sections just fine. Except now I also get empty
\subsection{} and \subsubsection{} blocks in my latex output. I have
attached the resulting .tex file with comments pointing out the
extra heading lines I would like to *not* see...
The net result is a lot of blank space in the resulting .pdf file
between the 'common' text and the note- or handout-specific text.
This
is *definitely* not what I had in mind.
Is there any way of working around this or correcting this behavior?
Mark
___
Emacs-orgmode mailing list
Please 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
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Feature request: Prompt to remove deadline/scheduled dates
On Wed, Dec 23, 2009 at 07:14:44PM -0500, Matt Lundin wrote: Paul Holcomb pholc...@cpoint.net writes: Its great that there is a log when the DEADLINE or SCHEDULED value changes for an entry. It would also be nice if you could remove the deadline or scheduled value using the same interface so it could be logged. I'm not entirely sure if this is what you are asking for, but you can remove SCHEDULED and DEADLINE metadata by adding a prefix argument to C-c C-s and C-c C-d. That's my fault; I wasn't very clear. Here's the problem: When you remove a deadline or schedule with the prefix argument, it doesn't make an entry about the removed deadline or schedule if you have the variable org-log-redeadline or org-log-reschedule set to 'note, respectively. From a quick glance, it looks like an easy patch to org-deadline and org-schedule as well. Turns out I was just thinking about it the wrong way yesterday. Thanks for your followup here. -- Paul Holcomb *pholcomb\@ cpoint net* GPG key fingerprint 2B62 05AE EE74 845A 705F D716 28C4 FE1C 088F CFAC ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] OT Happy Christmas
Thanks to Carsten and all the helpful people on the list, for all their work on making org such a great piece of software. I am just off to the barn to get some hay for Rudolph. Ian. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: custom agenda view
В Thu, 24 Dec 2009 06:21:23 -0500 Matt Lundin m...@imapmail.org пишет: Does the following work? Since STARTED is a todo state, it needs to be specified with a different syntax. (setq org-agenda-custom-commands (quote ((w work tasks tags-todo @WORK/!STARTED ((org-agenda-todo-ignore-with-date nil))) (h home tasks tags-todo @HOME/!STARTED ((org-agenda-todo-ignore-with-date nil))) (n Notes tags NOTE nil Thanks! It's work. -- С уважением Юрий Гончаров Системный администратор Highlink Ltd. St-Peterburg, Russia +7 812 3341212 http://www.hl.ru ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-ctags released
Happy Xmas everyone. I have updated org-ctags to use an existing hook which has recently been added to the development version of org-mode by Carsten. So now, no patch is needed. I have also fixed a couple of bugs. Latest version can be downloaded at: http://bitbucket.org/eeeickythump/org-ctags/ Paul ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
