[Orgmode] Can't get tasks [%] and [/] to work
Dear All, I probably miss something here, but I really cannot get subtasks stats to work (i.e. what's described in the manual at "5.5 Breaking tasks down into subtasks"). For instance, in the snippet below : *** Cage [%] DONE Redesign motherboard SCHEDULED: <2009-07-29 mer.> - State "DONE" from "TODO" [2009-09-01 mar. 10:59] DONE Solder motherboard SCHEDULED: <2009-07-30 jeu.> - State "DONE" from "TODO" [2009-09-01 mar. 10:59] DONE Write code SCHEDULED: <2009-07-31 ven.> - State "DONE" from "TODO" [2009-09-01 mar. 10:59] All subentries are marked DONE, but the [%] next to cage stays empty. If I try to force an update with 'C-c #', I get : *** Cage [0%] which is also wrong. Another example is here : DONE Web interface [100%] - [X] Fix lang page - Implement buttons in web interface [0/1] - [ ] Refresh Medias (content) 100% is wrong, since "Refresh Medias" isn't checked. (org-hierarchical-todo-statistics is set globally). I probably messed up things somewhere. If anyone has an idea... Thanks for reading, M -- Michel Blanc - Systèmes/Réseaux Erasme Erasme/CG69/Saint Clément les Places/FR69930 T +33-474706840 http://reseau.erasme.org FA67 4EDA D648 9E50 BFA4 3F29 FDF5 4971 24B3 5C22 ___ 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] bad habit (deleting elipses in folded tree)
I have a bad habit. How can I defeat it?
Often an elipsis ("...") is seen at the bottom of a new entry from a
remember template. I find myself deleting them, compulsively. I'm not so
sure, but I THINK that sometimes this is ok, and I now am afraid I have
discovered that at some times a whole bunch of pre-exiisting entries are
deleted when I delete the elipsis.
What's the scoop about elipses? Which variables are relevant? Can I defeat
this habit by reconfiguring, or do I have to force myself to have better
habits?
Thank you,
Alan Davis
You can know the name of a bird in all the languages of the world, but when
you're finished, you'll know absolutely nothing whatever about the bird...
So let's look at the bird and see what it's doing---that's what counts.
Richard Feynman
___
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] Release 6.30
Hi Carsten, thanks for another great release of my favorite mode! > Allow LaTeX export to use the listings package I will definitively test this one extensively :) We always wanted to have this, but... Thanks Eric! I hope to get rid of all that weired stuff I used to typeset source code as seen in http://orgmode.org/img/screenshots/vmap-org-export-to-pdf2.jpg Best wishes 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] Can't get tasks [%] and [/] to work
Michel Blanc writes: > Dear All, > > I probably miss something here, but I really cannot get subtasks stats > to work (i.e. what's described in the manual at "5.5 Breaking tasks down > into subtasks"). > > For instance, in the snippet below : > > *** Cage [%] > DONE Redesign motherboard > SCHEDULED: <2009-07-29 mer.> > - State "DONE" from "TODO" [2009-09-01 mar. 10:59] > DONE Solder motherboard > SCHEDULED: <2009-07-30 jeu.> > - State "DONE" from "TODO" [2009-09-01 mar. 10:59] > DONE Write code > SCHEDULED: <2009-07-31 ven.> > - State "DONE" from "TODO" [2009-09-01 mar. 10:59] > > > All subentries are marked DONE, but the [%] next to cage stays empty. > If I try to force an update with 'C-c #', I get : > > *** Cage [0%] > > which is also wrong. `C-c #' is what doesn't work here (not sure why). But moving to some subheading and pressing `S-LEFT S-RIGHT' will update the top headline here. > Another example is here : > > DONE Web interface [100%] > - [X] Fix lang page > - Implement buttons in web interface [0/1] > - [ ] Refresh Medias (content) > > 100% is wrong, since "Refresh Medias" isn't checked. > (org-hierarchical-todo-statistics is set globally). > > I probably messed up things somewhere. If anyone has an idea... How should Org-mode know, that there is a nested task? The task `Web interface' has only children marked as DONE. This is, how it should look like: DONE Web interface [50%] - [X] Fix lang page - [ ] Implement buttons in web interface [0/1] - [ ] Refresh Medias (content) There might be a variable I'm not aware of, that changes this behavior though. HTH, 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] bad habit (deleting elipses in folded tree)
I would NEVER EVER EVER delete naked ellipses, this is dangerous.
Press `C-c C-r' in their vicinity, this should hopefully fix the
problem. Otherwise, `M-x show-all' will always do the trick.
- Carsten
On Sep 1, 2009, at 11:32 AM, Alan E. Davis wrote:
I have a bad habit. How can I defeat it?
Often an elipsis ("...") is seen at the bottom of a new entry from a
remember template. I find myself deleting them, compulsively. I'm
not so sure, but I THINK that sometimes this is ok, and I now am
afraid I have discovered that at some times a whole bunch of pre-
exiisting entries are deleted when I delete the elipsis.
What's the scoop about elipses? Which variables are relevant? Can
I defeat this habit by reconfiguring, or do I have to force myself
to have better habits?
Thank you,
Alan Davis
You can know the name of a bird in all the languages of the world,
but when you're finished, you'll know absolutely nothing whatever
about the bird... So let's look at the bird and see what it's
doing---that's what counts.
Richard Feynman
___
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] bad habit (deleting elipses in folded tree)
> I would NEVER EVER EVER delete naked ellipses, this is dangerous. If Carsten's capital letters don't cure you of the habit, I don't know what will. :-) Seriously, try to train yourself to think of those ellipses, as code for "everything productive you did in Emacs over the last excruciating hour" 'cause that's what they (sometimes) stand for. Always glad to be of help. ___ 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] Can't get tasks [%] and [/] to work
Sebastian Rose a écrit : > `C-c #' is what doesn't work here (not sure why). But moving to some > subheading and pressing `S-LEFT S-RIGHT' will update the top headline > here. Yes, it works ! Thanks ! > > >> Another example is here : >> >> DONE Web interface [100%] >> - [X] Fix lang page >> - Implement buttons in web interface [0/1] >> - [ ] Refresh Medias (content) >> > How should Org-mode know, that there is a nested task? Oh well, if I had any clue how OrgMode works internally, I probably wouldn't post noob questions here ;) > This is, how it should look > like: > > DONE Web interface [50%] > - [X] Fix lang page > - [ ] Implement buttons in web interface [0/1] > - [ ] Refresh Medias (content) Again, you spotted the problem. Thanks a lot for your help Sebastian ! M -- Michel Blanc - Systèmes/Réseaux Erasme Erasme/CG69/Saint Clément les Places/FR69930 T +33-474706840 http://reseau.erasme.org FA67 4EDA D648 9E50 BFA4 3F29 FDF5 4971 24B3 5C22 ___ 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: Release 6.30
Carsten Dominik writes: > New command to submit a bug report > --- > > There is now a special command `M-x org-submit-bug-report'. This > command will create a mail buffer with lots of useful details. > In particular, it contains complete version information for Emacs > and Org-mode. It will also (if you agree to it) contain all > non-standard settings of org-mode and outline-mode related > variables. Even if you do not sent your emails from within > Emacs, please still use this command to generate the information > and then copy it into your mail program. > > The command will not generate and include a `*Backtrace*' buffer, > please do this yourself if you have hit an error. For more > information, see the [feedback section] of the manual. > > [feedback section]: http://orgmode.org/manual/Feedback.html#Feedback > This is cool. There's a minor typo in the mail text - patch follows. -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
[Orgmode] [PATCH] Fix typo in org-submit-bug-report mail text
--- This patch is available at git://git.norang.ca/org-mode for-carsten lisp/org.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index c851dc1..113925f 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -15493,7 +15493,7 @@ such private information before sending the email.") list)) nil nil "Remember to cover the basics, that is, what you expected to happen and -what in fact did happen. You don't know hoe to make a good report? See +what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback -- 1.6.4.2.363.g2d6e ___ 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: make update error
Nick Dokos writes: > Thomas S. Dye wrote: > >> git pull counts, compresses, receives objects, resolves deltas, >> updates and fails with this message: >> >> error: Entry 'Makefile' not uptodate. Cannot merge. >> >> As far as I know Makefile is up-to-date. >> > You might also want to have a local branch, where you can keep any local > modifications, e.g. if the changes to the Makefile were deliberate and > you wanted to keep them, then you could save the Makefile temporarily > (mv Makefile /tmp/Makefile), do the above commands, then create the local > branch: > >git branch local > > change to it: > >git checkout local > > (note that checkout has a couple of related but different meanings). > Move the modified Makefile back and commit the changes: > >mv /tmp/Makefile . >git commit -a > > When it it time to pull again, you can change back to the (pristine) > master branch and pull: > >git checkout master >git pull > > Then you can rebase your local changes on top of the new bits: > >git rebase master local > > It's a good way to keep a few local modifications and carry them forward > to any new version of org (of course, if the new version and your changes > change the same area of a file, you might end up with merge conflicts that > you'll have to resolve: but most of the time, it just works). There's a description of how to do this local branch with rebase automagically at http://orgmode.org/worg/org-faq.php#keeping-local-changes-current-with-Org-mode-development There's not need to change back to the master branch - just pull (with rebase) into your local branch. -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
[Orgmode] git and possibly 6.30 xemacs bug
The select-frame-set-input-focus function doesn't exist in xemacs, which was recently added in org-eval-in-calendar. This seems to be a common problem as gnus defines this to get around it: (defun gnus-select-frame-set-input-focus (frame) "Select FRAME, raise it, and set input focus, if possible." (cond ((featurep 'xemacs) (if (fboundp 'select-frame-set-input-focus) (select-frame-set-input-focus frame) (raise-frame frame) (select-frame frame) (focus-frame frame))) ;; `select-frame-set-input-focus' defined in Emacs 21 will not ;; set the input focus. ((>= emacs-major-version 22) (select-frame-set-input-focus frame)) (t (raise-frame frame) (select-frame frame) (cond ((memq window-system '(x ns mac)) (x-focus-frame frame)) ((eq window-system 'w32) (w32-focus-frame frame))) (when focus-follows-mouse (set-mouse-position frame (1- (frame-width frame)) 0) -- \ Wes Hardaker http://pontifications.hardakers.net / \_ "In the bathtub of history the truth is harder to hold than / \___ the soap, and much more difficult to find." ___/ \_ -- Terry Pratchett __/ \__/ ___ 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] [Feature request/proposal] Pinkie finger saving/amateur mode & alternate org-mode-keymap
Hi, I've been using org, but it is starting to bug me that it relies so heavily on control-c this and control-u control-c that. It is now also the case that there is a bewildering array of key strokes to memorise. You only need to look at the org-mode reference card to see that. In my personal config i have the common things that i use re-mapped to make it easier on me. For example org-ctrl-c-ctrl-c is mapped to meta-o and org-remember is meta-r. So this latest release with the agenda keymap change got me thinking about the org keymapings, and I'd like to propose something a bit different. This is an idea that will work as a reference for beginners, a dynamic built in org-mode reference card, and a pinkie finger saver. Essentially it is this. There is a - meta-o or ctrl-c-ctrl-c-ctrl-h or whatever. When you press this key it brings up a menu like the remember mode and agenda mode front ends. This menu is the top of a tree like structure that gives access to all of the org-mode key-mappable things. Below is an example created from headings in the org-mode reference card. * Pressing brings up a menu buffer with: [v]isibility cycling [m]otion [s]tructure editing ar[c]hiving [f]iltering and sparse trees [t]ables [l]inks [c]ompletion t[o]do items and checkboxes ta[g]st[i]mestamps [a]genda views late[x] and cdlatex-mode [e]xporting and publishing[d]ynamic blocks [u]ser functions * Pressing 'v' for [v]isibility, brings up the next menu: === Visibility Cycling == Menu option: org-keymap: [r]otate current subtree between states TAB rotate [e]ntire buffer between states S-TAB restore [p]roperty-dependent startup visibility C-u C-u TAB show the [w]hole file, including drawersC-u C-u C-u TAB reveal [c]ontext around point C-c C-r This creates an inbuilt help system and a pinkie saving mode. because C-u C-u C-u TAB is also v w It should also be extendible enough for users to add their own functions, and org-mode extensions to add any new keys. Comments/Opinions? Tim. ___ 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: make update error
Bernt Hansen wrote: > Nick Dokos writes: > > > Thomas S. Dye wrote: > > > >> git pull counts, compresses, receives objects, resolves deltas, > >> updates and fails with this message: > >> > >> error: Entry 'Makefile' not uptodate. Cannot merge. > >> > > > > > There's a description of how to do this local branch with rebase > automagically at > > http://orgmode.org/worg/org-faq.php#keeping-local-changes-current-with-Org-mode-development > > There's not need to change back to the master branch - just pull (with > rebase) into your local branch. > Nice! Thanks for pointing that out (the document *and* the method). 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] Org-mode version 6.30 (release_6.30.dirty); must be an empty tag
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know hoe to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. There is no in XHTML. This patch fixes it: diff --git a/lisp/org-html.el b/lisp/org-html.el index 197e186..0968776 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -1642,7 +1642,7 @@ lang=\"%s\" xml:lang=\"%s\"> (push (mapconcat (lambda (x) (setq gr (pop org-table-colgroup-info)) - (format "%s%s" + (format "%s%s" (if (memq gr '(:start :startend)) (prog1 (if colgropen "\n" "") Best wishes Sebastian Emacs : GNU Emacs 23.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.1) of 2009-08-18 on beteigeuze Package: Org-mode version 6.30 (release_6.30.dirty) ___ 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: Keyword completion.
On Sun, Aug 23, 2009 at 6:19 AM, Nick Dokos wrote: > Noorul Islam wrote: > >> On Sat, Aug 22, 2009 at 7:19 PM, Matt Lundin wrote: >> > Noorul Islam wrote: >> >> >> >> On Sat, Aug 22, 2009 at 6:48 PM, Matt Lundin wrote: >> >> > Noorul Islam writes: >> >> > >> >> >> In an org-file I typed in #+A followed by ESC-Tab. I got a completion >> >> >> list window in which I clicked on AUTHOR using mouse . It actually >> >> >> replaced everything in the line with AUTHOR. I think it should have >> >> >> inserted AUTHOR after #+ which is the behavior when we try to complete >> >> >> with ESC-TAB. >> >> > >> >> > I can't replicate this. With completion, >> >> > >> >> > #+A >> >> > >> >> > becomes >> >> > >> >> > #+AUTHOR >> >> >> >> Did you use the mouse for selection? >> > >> > Yes. I tried it both with the mouse and with RET. >> > >> >> I tried again, >> >> My emacs version. >> >> GNU Emacs 23.0.60 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of >> 2008-06-21 on noorul >> >> Did anyone else face the same problem? >> > > I can't reproduce this either: > > #+A bcd > > put the cursor after A, hit Esc-TAB, click on AUTHOR, I get > > #+AUTHOR: bcd > > I tried both with and without the bcd part - works fine in either case. > > Version info: > > GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-08-09 on > gamaville.dokosmarshall.org > Org-mode version 6.29trans (release_6.29c.55.ga48f) > This works on my work laptop. It looks like something is wrong with my personal laptop setup. Thanks Noorul ___ 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] Repeated Tasks
Hello list, I have a requirement for calculating the time spent on repetitive task. Say for example checking mails. I don't have a specific schedule or deadline for this task. * TODO Check Mail I went through this document, http://orgmode.org/org.html#Repeated-tasks. The methodologies mentioned in the document requires a scheduled date or a deadline which I don't have in this scenario. For time being, I do the following. 1. Change TODO to STARTED 2. Clock-In 3. Check mail. After checking mail return to org file. 4. Clock-out 5. Change STARTED to TODO I have feeling that what I am doing is not a cool method. What you guys do in such situation? Thanks and Regards Noorul ___ 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: [Feature request/proposal] Pinkie finger saving/amateur mode & alternate org-mode-keymap
"Tim O'Callaghan" writes: > I've been using org, but it is starting to bug me that it relies so > heavily on control-c this and control-u control-c that. It is now also > the case that there is a bewildering array of key strokes to memorise. > You only need to look at the org-mode reference card to see that. An aside: Swapping caps-lock and control makes C-c a very convenient key combination. > So this latest release with the agenda keymap change got me thinking > about the org keymapings, and I'd like to propose something a bit > different. > > This is an idea that will work as a reference for beginners, a dynamic > built in org-mode reference card, and a pinkie finger saver. > > Essentially it is this. There is a - meta-o or > ctrl-c-ctrl-c-ctrl-h or whatever. When you press this key it brings up > a menu like the remember mode and agenda mode front ends. This menu is > the top of a tree like structure that gives access to all of the > org-mode key-mappable things. Below is an example created from > headings in the org-mode reference card. You can already do something like this with tmm-menubar. You could bind something like (tmm-menubar 50) to a key to get a browseable menu. Note: the 50 should be replaced by the the "x-position" of the org menu in your own menubar. Here's the result: , | Press PageUp key to reach this buffer from the minibuffer. | Alternatively, you can use Up/Down keys (or your History keys) to change | the item in the minibuffer, and press RET when you are done, or press the | marked letters to pick up your choice. Type C-g or ESC ESC ESC to cancel. | Click on a completion to select it. | In this buffer, type RET to select the completion near point. | | Possible completions are: | s==>Show/Hide n==>New Heading | N==>Navigate Headings e==>Edit Structure | E==>Editing a==>Archive | h==>Hyperlinkst==>TODO Lists | T==>TAGS and Properties d==>Dates and Scheduling | l==>Logging work A==>Agenda Command... | S==>Set Restriction Lock f==>File List for Agenda | v==>Special views current filep==>Export/Publish... | L==>LaTeX D==>Documentation | c==>Customize b==>Send bug report | r==>Refresh/Reload ` Obviously, this would not aid in learning keyboard shortcuts. > It should also be extendible enough for users to add their own > functions, and org-mode extensions to add any new keys. You might also want to checkout CategoryMenus on the Emacs Wiki: http://www.emacswiki.org/emacs/CategoryMenus OneKey, LaCarte, Icicles, etc. all look like they might be useful. 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] Repeated Tasks
Hi Noorul, Noorul Islam writes: > Hello list, > > I have a requirement for calculating the time spent on repetitive > task. Say for example checking mails. I don't have a specific schedule > or deadline for this task. > > * TODO Check Mail > > I went through this document, > http://orgmode.org/org.html#Repeated-tasks. The methodologies > mentioned in the document requires a scheduled date or a deadline > which I don't have in this scenario. > > For time being, I do the following. > > 1. Change TODO to STARTED > 2. Clock-In > 3. Check mail. After checking mail return to org file. > 4. Clock-out > 5. Change STARTED to TODO > how about: 1. On the `TODO Check Mail' headline, clock in: C-c C-x C-i 2. Check mail 3. On the `TODO Check Mail' headline, clock out: C-c C-x C-o Note, that you can use the menu from the clock display in the modeline to clock out again. Best wishes 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] org-todo-keywords prompt for note
Hello, When marking an item as DONE, I would like to be able to press "n" if I want to leave a note, and press "d" to just mark the item as DONE. I've tried using this trick: (setq org-todo-keywords '( (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)" "DONE(d!)") I also tried this: (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)") (sequence "TODO(t)" "STARTED(s)" "|" "DONE(d!)") But neither kludge would prompt me for a note when I press Ctrl-C Ctrl-T n I realize this is picky, because I can manually insert a note before marking an item as DONE. I'm just wondering if anyone knows a way that two shortcuts can be defined for the same TODO state, with one of the shortcuts prompting for a note. Thanks, --Nate ___ 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: [Feature request/proposal] Pinkie finger saving/amateur mode & alternate org-mode-keymap
Matt Lundin imapmail.org> writes: > > An aside: Swapping caps-lock and control makes C-c a very convenient > key combination. > If things come that one can also configure e.g. the right control key as a special prefix key which makes such combinations even more convenient, because unlike "C-c a" you can press "Rctrl a" with two hands. In case of right handed people the right control key is usually unused, so it's practical to use it for something else than it's original purpose. ___ 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-todo-keywords prompt for note
Nathan Neff writes:
> Hello,
>
> When marking an item as DONE, I would like to be able to press "n"
> if I want to leave a note, and press "d" to just mark the item as DONE.
>
> I've tried using this trick:
>
> (setq org-todo-keywords '(
> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)" "DONE(d!)")
>
>
> I also tried this:
>
> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)")
> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(d!)")
>
> But neither kludge would prompt me for a note when I press Ctrl-C Ctrl-T n
>
> I realize this is picky, because I can manually insert a note before marking
> an item as DONE. I'm just wondering if anyone knows a way that two
> shortcuts can be defined for the same TODO state, with one of the
> shortcuts prompting for a note.
(setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE@")))
works here. Note, that org chooses the first letter of the todo keyword
in lowercase automatically if you press C-c C-t, so there's no need for
"TODO(t)" et al.
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] org-todo-keywords prompt for note
> Nathan Neff writes:
>> Hello,
>>
>> When marking an item as DONE, I would like to be able to press "n"
>> if I want to leave a note, and press "d" to just mark the item as DONE.
>>
>> I've tried using this trick:
>>
>> (setq org-todo-keywords '(
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)" "DONE(d!)")
>>
>>
>> I also tried this:
>>
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)")
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(d!)")
>>
>> But neither kludge would prompt me for a note when I press Ctrl-C Ctrl-T n
>>
>> I realize this is picky, because I can manually insert a note before marking
>> an item as DONE. I'm just wondering if anyone knows a way that two
>> shortcuts can be defined for the same TODO state, with one of the
>> shortcuts prompting for a note.
>
>
>
>
> (setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE@")))
>
> works here. Note, that org chooses the first letter of the todo keyword
> in lowercase automatically if you press C-c C-t, so there's no need for
> "TODO(t)" et al.
I just found I use the trick including the keydefinition in my own setup
:) which is superfluous:
(setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE" "CANCELED(c@)")))
___
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-todo-keywords prompt for note
Hi Nathan,
Sorry for my typo (see below).
Sebastian Rose writes:
> Nathan Neff writes:
>> Hello,
>>
>> When marking an item as DONE, I would like to be able to press "n"
>> if I want to leave a note, and press "d" to just mark the item as DONE.
>>
>> I've tried using this trick:
>>
>> (setq org-todo-keywords '(
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)" "DONE(d!)")
>>
>>
>> I also tried this:
>>
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(n@/@)")
>> (sequence "TODO(t)" "STARTED(s)" "|" "DONE(d!)")
>>
>> But neither kludge would prompt me for a note when I press Ctrl-C Ctrl-T n
>>
>> I realize this is picky, because I can manually insert a note before marking
>> an item as DONE. I'm just wondering if anyone knows a way that two
>> shortcuts can be defined for the same TODO state, with one of the
>> shortcuts prompting for a note.
>
>
>
>
> (setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE@")))
Pardon me, this should be:
(setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE(@)")))
I found you'll have to close and open the Org file in question again to
make it work.
BTW: What's your value of the variable `org-todo-interpretation' ?
Maybe add these lines to your setup:
(setq org-todo-interpretation (quote sequence))
(setq org-todo-keywords (quote ("TODO" "STARTED" "|" "DONE(@)")))
HTH
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] Org-mode version 6.30 (release_6.30.dirty); must be an empty tag
WOW! The first bug report with the new function!!! :-) Applied, thanks. - Carsten On Sep 1, 2009, at 4:42 PM, Sebastian Rose wrote: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know hoe to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. There is no in XHTML. This patch fixes it: diff --git a/lisp/org-html.el b/lisp/org-html.el index 197e186..0968776 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -1642,7 +1642,7 @@ lang=\"%s\" xml:lang=\"%s\"> (push (mapconcat (lambda (x) (setq gr (pop org-table-colgroup-info)) - (format "%s%s" + (format "%s%s" (if (memq gr '(:start :startend)) (prog1 (if colgropen "\n" "") Best wishes Sebastian Emacs : GNU Emacs 23.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.16.1) of 2009-08-18 on beteigeuze Package: Org-mode version 6.30 (release_6.30.dirty) ___ 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] Usability idea: color coding items with priorities in agenda
The agenda list would be easier to parse with the eye if each priority level (A, B, C) had its own face. This way the user could optionally set a background color for these priorities, so priority items would stand out from the todo list. ___ 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: make update error
On Sep 1, 2009, at 4:07 AM, Bernt Hansen wrote: Nick Dokos writes: Thomas S. Dye wrote: git pull counts, compresses, receives objects, resolves deltas, updates and fails with this message: error: Entry 'Makefile' not uptodate. Cannot merge. As far as I know Makefile is up-to-date. You might also want to have a local branch, where you can keep any local modifications, e.g. if the changes to the Makefile were deliberate and you wanted to keep them, then you could save the Makefile temporarily (mv Makefile /tmp/Makefile), do the above commands, then create the local branch: git branch local change to it: git checkout local (note that checkout has a couple of related but different meanings). Move the modified Makefile back and commit the changes: mv /tmp/Makefile . git commit -a When it it time to pull again, you can change back to the (pristine) master branch and pull: git checkout master git pull Then you can rebase your local changes on top of the new bits: git rebase master local It's a good way to keep a few local modifications and carry them forward to any new version of org (of course, if the new version and your changes change the same area of a file, you might end up with merge conflicts that you'll have to resolve: but most of the time, it just works). There's a description of how to do this local branch with rebase automagically at http://orgmode.org/worg/org-faq.php#keeping-local-changes-current-with-Org-mode-development There's not need to change back to the master branch - just pull (with rebase) into your local branch. -Bernt Aloha Nick and Bernt, Thanks for the very useful advice and the pointer to the FAQ that deals specifically with my situation. I very much appreciate not receiving a RTFM reply. It turns out I had edited the top of the Makefile, per the instructions, to configure it to my Mac setup. To my mind, this edit was a "configuration" and not a "local change." When I looked through the FAQ I didn't stop to read "How can I keep local changes and still track Org mode development" because I hadn't made any changes to the lisp source of org-mode, so thought I couldn't possibly have made a "local change." I think I can see now how the distinction I was making between a "local change" and a "configuration" isn't sensible from a developer's point of view, but I'm not sure I would have been able to do so without falling back on my graduate school training in linguistic anthropology! I'm looking forward to isolating my local changes from the master branch, a task I am scheduling now with C-c r ... All the best, Tom ___ 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] Repeated Tasks
On Tue, Sep 1, 2009 at 8:45 PM, Sebastian Rose wrote: > Hi Noorul, > > > > > > > > Noorul Islam writes: >> Hello list, >> >> I have a requirement for calculating the time spent on repetitive >> task. Say for example checking mails. I don't have a specific schedule >> or deadline for this task. >> >> * TODO Check Mail >> >> I went through this document, >> http://orgmode.org/org.html#Repeated-tasks. The methodologies >> mentioned in the document requires a scheduled date or a deadline >> which I don't have in this scenario. >> >> For time being, I do the following. >> >> 1. Change TODO to STARTED >> 2. Clock-In >> 3. Check mail. After checking mail return to org file. >> 4. Clock-out >> 5. Change STARTED to TODO >> > > how about: > > > 1. On the `TODO Check Mail' headline, clock in: > > C-c C-x C-i > > 2. Check mail > > 3. On the `TODO Check Mail' headline, clock out: > > C-c C-x C-o > > > Note, that you can use the menu from the clock display in the modeline > to clock out again. > > Thanks for the suggestion. Sometimes I do that also. But that won't change the mod-line status saying that I am Checking Mails. Thanks Noorul ___ 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] RSI
Orgers, Repetitive strain injury is real and important. One thing that you can do is to ensure that you have a keyboard that has modifier keys on both sides. You should pound a new habit into your cerebellum: use two hands. For example, c-c c-o should look like this: r hand presses ctrl l hand presses c let go l hand presses ctrl r hand presses o let go This is obviously inefficient, but it is the correct thing. Ideally, the most important c-c and c-x operations would be on the lhs. That way, you can hold down ctrl and press the two keys. Many (maybe even most) will find this idea strange. But I urge all of you to try it for a few months. On 2009-09-01, PT wrote: > Matt Lundin imapmail.org> writes: >> >> An aside: Swapping caps-lock and control makes C-c a very convenient >> key combination. >> > > If things come that one can also configure e.g. the right control > key as a special prefix key which makes such combinations even > more convenient, because unlike "C-c a" you can press "Rctrl a" > with two hands. > > In case of right handed people the right control key is usually > unused, so it's practical to use it for something else than it's > original purpose. > > > > > > ___ > 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 > -- Myalgic encephalomyelitis causes death (Jason et al. 2006) and severe suffering. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. 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
[Orgmode] Re: RSI
Clarification. On 2009-09-01, Samuel Wales wrote: > Ideally, the most important c-c and c-x operations would be on the > lhs. That way, you can hold down ctrl and press the two keys. I mean c-c c-letter not c-c letter here. -- Myalgic encephalomyelitis causes death (Jason et al. 2006) and severe suffering. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. 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
Re: [Orgmode] RSI
Emacs can definitely lead to RSI - Richard Stallman, the creator, developed it. I am quite prone to RSI, which led me to VIM due to its modal operation (very few modifier key combos). I used VIM for quite a while and did not have any issues, but org-mode pulled me to emacs. I now use a kinesis keyboard and have no RSI issues. The keyboard combined with the idea expressed below that you use different hands when pressing control key combinations has really helped. The Kinesis puts all the control keys (control, meta, command) on your thumbs. Its expensive, but worth every penny to me at least. Check them out at http://www.kinesis-ergo.com/ Keith On Sep 1, 2009, at 1:11 PM, Samuel Wales wrote: Orgers, Repetitive strain injury is real and important. One thing that you can do is to ensure that you have a keyboard that has modifier keys on both sides. You should pound a new habit into your cerebellum: use two hands. For example, c-c c-o should look like this: r hand presses ctrl l hand presses c let go l hand presses ctrl r hand presses o let go This is obviously inefficient, but it is the correct thing. Ideally, the most important c-c and c-x operations would be on the lhs. That way, you can hold down ctrl and press the two keys. Many (maybe even most) will find this idea strange. But I urge all of you to try it for a few months. On 2009-09-01, PT wrote: Matt Lundin imapmail.org> writes: An aside: Swapping caps-lock and control makes C-c a very convenient key combination. If things come that one can also configure e.g. the right control key as a special prefix key which makes such combinations even more convenient, because unlike "C-c a" you can press "Rctrl a" with two hands. In case of right handed people the right control key is usually unused, so it's practical to use it for something else than it's original purpose. ___ 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 -- Myalgic encephalomyelitis causes death (Jason et al. 2006) and severe suffering. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. 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 Keith Lancaster klancaster1...@mac.com ___ 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: RSI
Samuel Wales gmail.com> writes: > > One thing that you can do is to ensure that you have a keyboard that > has modifier keys on both sides. You should pound a new habit into > your cerebellum: use two hands. > > ... > > Many (maybe even most) will find this idea strange. But I urge all of > you to try it for a few months. I agree it's a good idea. For those who think this approach is too radical I recommend trying out sticky keys as an alternative which also alleviates a bit the effects of the finger killing C-x/C-c and similar combinations: http://www.emacswiki.org/emacs/StickyModifiers ___ 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] Usability idea: color coding items with priorities in agenda
Try c-h v org-priority-faces. -- Myalgic encephalomyelitis causes death (Jason et al. 2006) and severe suffering. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. 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
[Orgmode] Re: Usability idea: color coding items with priorities in agenda
Samuel Wales gmail.com> writes: > > Try c-h v org-priority-faces. > Silly me, I forgot to check if a later version has that feature. I'm still on 6.21b. Thanks. ___ 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] Release 6.30
Hi Carsten, Thanks for the release! The dedicated frame patch does not actually appear to be in this release, though. On Tue, Sep 1, 2009 at 12:20 AM, Carsten Dominik wrote: > Hi, > > I am releasing Org-mode version 6.30. > > Enjoy! > > - Carsten > > Changes in Version 6.30 > === > > Inconsistent changes > ~ > > Agenda now uses `f' and `b' to move through time > = > > Up to now, the Org-mode agenda used the cursor keys `left' and > `right' to switch the agenda view forward an backward through > time. However, many people found this confusing, and others > wanted to be able to do cursor motion in the agenda, for example > to select text. Therefore, after an extensive discussion on > `emacs-orgm...@gnu.org', it was decided to use the `b' and > `f' keys instead, and to let the cursor keys do cursor motion > again. > > Agenda follow mode is now on the `F' key > = > > This was necessary to free up the `f' key, see above. > > Details > > > Maintenance > > > New command to submit a bug report > --- > > There is now a special command `M-x org-submit-bug-report'. This > command will create a mail buffer with lots of useful details. > In particular, it contains complete version information for Emacs > and Org-mode. It will also (if you agree to it) contain all > non-standard settings of org-mode and outline-mode related > variables. Even if you do not sent your emails from within > Emacs, please still use this command to generate the information > and then copy it into your mail program. > > The command will not generate and include a `*Backtrace*' buffer, > please do this yourself if you have hit an error. For more > information, see the [feedback section] of the manual. > > [feedback section]: http://orgmode.org/manual/Feedback.html#Feedback > > New contributed package org-track.el > - > > This package allows to keep up-to-date with current Org > development, using only Emacs on-board means. So if you don't > want or cannot use `git', but still want to run the latest and > hottest Org-mode, this is for you. > > Thanks to Sebastian Rose for this contribution. > > Agenda > === > > Agenda now uses `f' and `b' to move through time > - > > Up to now, the Org-mode agenda used the cursor keys `left' and > `right' to switch the agenda view forward an backward through > time. However, many people found this confusing, and others > wanted to be able to do cursor motion in the agenda, for example > to select text. Therefore, after an extensive discussion on > `emacs-orgm...@gnu.org', it was decided to use the `b' and > `f' keys instead, and to let the cursor keys do cursor motion > again. > > Agenda follow mode is now on the `F' key > - > > This was necessary to free up the `f' key, see above. > > The agenda can be put into a dedicated frame > - > > When the variable `org-agenda-window-setup' has the value > `separate-frame', then the new frame created to show the agenda > will now have the window marked as /dedicated/. As a > consequence, exiting the agenda while the agenda is the only > window on the frame will kill that frame. > > This was a request by Henry Atting. > > New mode to show some entry body text in the agenda > > > There is now a new agenda sub-mode called > `org-agenda-entry-text-mode'. It is toggled with the `E' key. > When active, all entries in the agenda will be accompanied by a > few lines from the outline entry. The amount of text can be > customized with the variable `org-agenda-entry-text-maxlines'. > > This was a request by Anthony Fairchild, Manish, and others. > > Improve following links from the agenda > > > `C-c C-o' in the agenda will now offer all links in the headline > and text of an entry. If there is only a single link, it will be > followed immediately. > > Avoid some duplicate entries > - > > There is a new variable that can be used to avoid some duplicate > agenda entries: `org-agenda-skip-scheduled-if-deadline-is-shown' > If that is set, it avoids that an entry shows up in the agenda for > today for both a scheduling and a deadline entry. See the > docstring of the variables for more details. > > This partially addresses a request by Samuel Wales. > > Mark the running clock in the agenda. > -- > > If the entry currently being clocked is present in the agenda, it > will be highlighted with the face `org-agenda-clocking'. > > This was a request by Rainer Stengele. > > > Export > === > > Allow LaTeX export to use the listings package > ---
[Orgmode] Re: RSI
Samuel Wales writes: > Repetitive strain injury is real and important. > > One thing that you can do is to ensure that you have a keyboard that > has modifier keys on both sides. You should pound a new habit into > your cerebellum: use two hands. > > For example, c-c c-o should look like this: > > r hand presses ctrl > l hand presses c > let go > l hand presses ctrl > r hand presses o > let go > > This is obviously inefficient, but it is the correct thing. > > Ideally, the most important c-c and c-x operations would be on the > lhs. That way, you can hold down ctrl and press the two keys. > > Many (maybe even most) will find this idea strange. But I urge all of > you to try it for a few months. This is no doubt the correct method, but it is not realistic for many users given the idiosyncratic layouts of keyboards today. Many of the laptops I've used have had a misplaced or non-existent right control key. Thus, short of using viper, the only solution that works for me is to use the Caps Lock key as Control. With that slight modification, I find emacs controls *very* comfortable (perhaps even as comfortable than vim). Once I made that switch, RSI issues disappeared virtually overnight. Now, any RSI issues I experience come from using n and p or j and k repeatedly. Needless to say, YMMV. 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] bad habit (deleting elipses in folded tree)
El mar, sep 01 2009 a les 11:32, Alan E. Davis va escriure: > What's the scoop about elipses? Which variables are relevant? Can I defeat > this habit by reconfiguring, or do I have to force myself to have better > habits? You can change how the ellipsis look so that you are more careful and don't confuse them with 3 normal dots which could appear anywhere... For instance: (setq org-ellipsis "〖 ✎ 〗") Or just give it a more visible face, like in: (setq org-ellipsis (quote org-column)) I use another face and I don't attempt anymore to delete hidden text. [1] In addition I use … to write ellipsis myself, thus I notice the difference between … and ... -- Daniel [1] I only do it when I hit some org-mode bug which allows you to edit invisible text while it still shows the ellipsis; this happens specially at the end of buffers (narrowed or not). ___ 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] Org-mode version 6.30 (release_6.30); Batch archiving needs to be more clever
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know hoe to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Batch archiving mode appears to just try the most obvious thing: take
each tagged member and archive it. However, it always runs into
problems, because it will archive a parent node, then try and archive
the children. Not finding the children anymore, it errors out.
Probably an easy solution would be to just gracefully handle this error
by ignoring it and pretending the item was archived. Alternatively,
updating the list after every operation could also work.
Ideal solution, IMHO: always archive parents first, then clear the
children from the list automatically.
Emacs : GNU Emacs 23.1.50.2 (x86_64-unknown-linux-gnu, X toolkit)
Package: Org-mode version 6.30 (release_6.30)
current state:
==
(setq
org-log-done 'time
org-link-frame-setup '((gnus . gnus) (file . find-file-other-window))
org-clock-string-limit 50
org-agenda-custom-commands '(("w" todo #("WAITING" 0 7 (face org-warning)) nil)
("n" tags-todo #("-live" 0 5 (face org-warning))
((org-show-hierarchy-above nil)
(org-agenda-todo-ignore-with-date t)
(org-agenda-tags-todo-honor-ignore-options t))
)
("l" "Agenda and live tasks" ((agenda "")
(tags-todo "+live"
org-agenda-files '("~/org/work.org")
org-agenda-include-diary t
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent
org-depend-block-todo)
org-completion-use-ido t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-agenda-todo-ignore-scheduled t
org-agenda-start-with-log-mode t
org-clock-out-switch-to-state '(lambda (prev-state) (if (member prev-state
org-done-keywords) "DONE" "STARTED"))
org-deadline-warning-days 1
org-agenda-skip-scheduled-if-done t
org-trigger-hook '(org-depend-trigger-todo)
org-export-preprocess-hook '(org-export-blocks-preprocess)
org-tab-first-hook '(org-hide-block-toggle-maybe)
org-src-mode-hook '(org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-todo-keywords '((sequence "TODO(t)" "STARTED(s)" "WAITING(w@/!)" "|"
"DONE(d)" "OBSOLETE(o)"))
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-dim-blocked-tasks 'invisible
org-agenda-tags-todo-honor-ignore-options t
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-block-all
append local] 5]
)
org-agenda-ndays 1
org-refile-targets '((nil :maxlevel . 3))
org-emphasis-regexp-components '(" ('\"{" "- .,:!?;'\")}" "
.\n,\"'" "." 1)
org-confirm-elisp-link-function nil
org-agenda-mode-hook '((lambda nil (hl-line-mode 1)))
org-enforce-todo-dependencies t
org-agenda-skip-deadline-if-done t
org-occur-hook '(org-first-headline-recenter)
org-from-is-user-regexp "\\"
org-drawers '("PROPERTIES" "CLOCK" "LOGBOOK" "NOTES")
)
___
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: Usability idea: color coding items with priorities in agenda
PT wrote: > Samuel Wales gmail.com> writes: > > > > > Try c-h v org-priority-faces. > > > > I installed the latest org and tried it. It helps a bit, but it's > not really what I thought of. The full header text of the prority > todo item should have a distinct background color in the agenda > buffer (if the user configures it this way), not just the > priority marker. > You missed the *other* variable :-) C-h v org-agenda-fontify-priorities , | org-agenda-fontify-priorities is a variable defined in `org-agenda.el'. | Its value is cookies | | Documentation: | Non-nil means, highlight low and high priorities in agenda. | When t, the highest priority entries are bold, lowest priority italic. | However, settings in org-priority-faces will overrule these faces. | When this variable is the symbol `cookies', only fontify the | cookies, not the entire task. | This may also be an association list of priority faces, whose | keys are the character values of `org-highest-priority', | `org-default-priority', and `org-lowest-priority' (the default values | are ?A, ?B, and ?C, respectively). The face may be a named face, | or a list like `(:background "Red")'. | | You can customize this variable. ` HTH, 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] bad habit (deleting elipses in folded tree)
Well noted. Alan You can know the name of a bird in all the languages of the world, but when you're finished, you'll know absolutely nothing whatever about the bird... So let's look at the bird and see what it's doing---that's what counts. Richard Feynman > > ___ 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] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Fri 05:45AM +, 24 Jul 2009, Tang, Hsiu-Khuern (hsiu-khuern.t...@hp.com) wrote: > * On Fri 01:22AM +, 24 Jul 2009, Bastien (bastiengue...@googlemail.com) > wrote: > > Hi Hsiu-Khuern, > > > > I've just pushed a fix for this: when the "src" switch is present, > > including a file won't escape org-like lines. With a bare #+include > > we still escape lines starting with * or #. > > > > Please test it and report any problem. > > It works beautifully now. Thank you very much for the fix! It looks Org has reverted to the old behavior: inserting a comma at a beginning of every line in the #INCLUDE'd file that starts with whitespace followed by #. For example, if you export this as ascii (see http://article.gmane.org/gmane.emacs.orgmode/15718): File 1: a.org == * test #+INCLUDE: "a.sh" src sh == File 2: a.sh == #!/bin/sh ## shell comment echo "This is a test" == the output contains the line ", ## shell comment". Related question: what git commands does one use to obtain all the commits that changed a particular range of lines in a file? I'm quite lost with git. -- Best, Hsiu-Khuern. ___ 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] Unnecessary comma escapes in HTML export of #+INCLUDE files
Hsiu-Khuern Tang wrote: > * On Fri 05:45AM +, 24 Jul 2009, Tang, Hsiu-Khuern > (hsiu-khuern.t...@hp.com) wrote: > > * On Fri 01:22AM +, 24 Jul 2009, Bastien (bastiengue...@googlemail.com) > > wrote: > > > Hi Hsiu-Khuern, > > > > > > I've just pushed a fix for this: when the "src" switch is present, > > > including a file won't escape org-like lines. With a bare #+include > > > we still escape lines starting with * or #. > > > > > > Please test it and report any problem. > > > > It works beautifully now. Thank you very much for the fix! > > It looks Org has reverted to the old behavior: inserting a comma at a > beginning > of every line in the #INCLUDE'd file that starts with whitespace followed by > #. > > For example, if you export this as ascii (see > http://article.gmane.org/gmane.emacs.orgmode/15718): > > File 1: a.org > == > * test > > #+INCLUDE: "a.sh" src sh > == > > File 2: a.sh > == > #!/bin/sh > > ## shell comment > echo "This is a test" > == > > the output contains the line ", ## shell comment". > > Related question: what git commands does one use to obtain all the commits > that > changed a particular range of lines in a file? I'm quite lost with git. > There was some churn for this particular functionality, but since I don't really understand what is *supposed* to happen, I'll just refer you (and Carsten and Bastien, both of whom made -possibly conflicting- changes to this functionality) to the following exchange in the archive, hoping it will shed some light and lead to a satisfactory resolution for all involved: http://thread.gmane.org/gmane.emacs.orgmode/16244/focus=16259 The relevant commits are 68b65e8f480c17cfe1024001c236eb4065893f4d and dfd3749a273cc9f9a1d954363ea6de87049d17a7 Thanks, 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] Unnecessary comma escapes in HTML export of #+INCLUDE files
* On Tue 10:47PM +, 01 Sep 2009, Dokos, Nicholas (nicholas.do...@hp.com) wrote: > Hsiu-Khuern Tang wrote: > > It looks Org has reverted to the old behavior: inserting a comma at a > > beginning > > of every line in the #INCLUDE'd file that starts with whitespace followed > > by #. > > > > For example, if you export this as ascii (see > > http://article.gmane.org/gmane.emacs.orgmode/15718): > > > > File 1: a.org > > == > > * test > > > > #+INCLUDE: "a.sh" src sh > > == > > > > File 2: a.sh > > == > > #!/bin/sh > > > > ## shell comment > > echo "This is a test" > > == > > > > the output contains the line ", ## shell comment". > > > > Related question: what git commands does one use to obtain all the commits > > that > > changed a particular range of lines in a file? I'm quite lost with git. > > > > There was some churn for this particular functionality, but since I > don't really understand what is *supposed* to happen, I'll just refer > you (and Carsten and Bastien, both of whom made -possibly conflicting- > changes to this functionality) to the following exchange in the archive, > hoping it will shed some light and lead to a satisfactory resolution for > all involved: > >http://thread.gmane.org/gmane.emacs.orgmode/16244/focus=16259 > > > The relevant commits are > > 68b65e8f480c17cfe1024001c236eb4065893f4d > > and > > dfd3749a273cc9f9a1d954363ea6de87049d17a7 > > Thanks, > Nick Thanks for pointing me to the relevant commits, both of which changed the org-get-file-contents function. I'm not sure what the correct behavior for that function is, since it may ultimately be used for different purposes, e.g., to generate an agenda and for exporting. For exporting to various formats, is there any reason to escape Org-like lines -- headers and comments -- of an #INCLUDE'd file, since the file contents are indented in the output anyway and so there can be no confusion? I'm not sure that the indentation occurs for all export formats, but it seems to be the case for ASCII and HTML export. At any rate, the docstring of org-get-file-contents is inconsistent with the behavior: "If MARKUP, don't protect org-like lines, the exporter will take care of the block they are in." It is actually protecting org-like lines when the markup is "src" or "example". -- Best, Hsiu-Khuern. ___ 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: small emacs for using org on Android
"Sven Bretfeld" writes: > writes: > >>can anyone recommend a small emacs implementation that will run org? >>I have Debian running on my G1 phone (see here: >>http://www.emacswiki.org/emacs/EmacsOnAndroid), >>and have been running Emacs 22 on it successfully. >>However it doesn't leave me much memory for other apps. > > If you have a flatrate and if you don't mind to have a computer > constantly running at home, you can use the Android app ConnectBot (or > normal ssh on Debian) to do your Emacs work including org stuff. This is > much easier and faster than running Emacs on the phone itself. > Actually I find it significantly slower using ssh - there is a noticeable lag. I only really want to use it for org-mode so I don't need any heavy computation. However I must admit I get a more reliable cursor position using SSH (with a local connection it is sometimes off by a line). -- aleblanc ___ 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] small emacs for using org on Android
Hi, please remember a org-file is still (and thankfully and amazingly) a plain text file. As long as you are not going to make big changes, any other (smaller) text editor will do, e.g., nano, pico, *cough* vim *cough*. I found myself comfortable to export the org-file to html and display it in my E-ink Ebook reader. Not able to edit it but reading my notes and thought like on printed paper is nice :) Greetings Totti ___ 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: Usability idea: color coding items with priorities in agenda
Nick Dokos hp.com> writes: > > You missed the *other* variable > > C-h v org-agenda-fontify-priorities > Damn! Org is again a step ahead of me. :D Thanks. ___ 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] Unnecessary comma escapes in HTML export of #+INCLUDE files
Hi Hsiu-Khuern, I am not able to reproduce the problem. - Carsten On Sep 2, 2009, at 12:03 AM, Hsiu-Khuern Tang wrote: * On Fri 05:45AM +, 24 Jul 2009, Tang, Hsiu-Khuern (hsiu-khuern.t...@hp.com ) wrote: * On Fri 01:22AM +, 24 Jul 2009, Bastien (bastiengue...@googlemail.com ) wrote: Hi Hsiu-Khuern, I've just pushed a fix for this: when the "src" switch is present, including a file won't escape org-like lines. With a bare #+include we still escape lines starting with * or #. Please test it and report any problem. It works beautifully now. Thank you very much for the fix! It looks Org has reverted to the old behavior: inserting a comma at a beginning of every line in the #INCLUDE'd file that starts with whitespace followed by #. For example, if you export this as ascii (see http://article.gmane.org/gmane.emacs.orgmode/15718): File 1: a.org == * test #+INCLUDE: "a.sh" src sh == File 2: a.sh == #!/bin/sh ## shell comment echo "This is a test" == the output contains the line ", ## shell comment". Related question: what git commands does one use to obtain all the commits that changed a particular range of lines in a file? I'm quite lost with git. -- Best, Hsiu-Khuern. ___ 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] Org-mode version 6.30 (release_6.30); Batch archiving needs to be more clever
Hi Andrew,
Org does take care of this possibility. All I get in my simple
test case is the following message:
Acted on 1 entries, skipped 2 (disappeared before their turn)
That is not an error, it is just feedback.
Or are you really getting an error?
- Carsten
On Sep 1, 2009, at 9:06 PM, Andrew Hyatt wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know hoe to make a good report?
See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Batch archiving mode appears to just try the most obvious thing: take
each tagged member and archive it. However, it always runs into
problems, because it will archive a parent node, then try and archive
the children. Not finding the children anymore, it errors out.
Probably an easy solution would be to just gracefully handle this
error
by ignoring it and pretending the item was archived. Alternatively,
updating the list after every operation could also work.
Ideal solution, IMHO: always archive parents first, then clear the
children from the list automatically.
Emacs : GNU Emacs 23.1.50.2 (x86_64-unknown-linux-gnu, X toolkit)
Package: Org-mode version 6.30 (release_6.30)
current state:
==
(setq
org-log-done 'time
org-link-frame-setup '((gnus . gnus) (file . find-file-other-window))
org-clock-string-limit 50
org-agenda-custom-commands '(("w" todo #("WAITING" 0 7 (face org-
warning)) nil)
("n" tags-todo #("-live" 0 5 (face org-
warning))
((org-show-hierarchy-above nil) (org-
agenda-todo-ignore-with-date t)
(org-agenda-tags-todo-honor-ignore-
options t))
)
("l" "Agenda and live tasks" ((agenda
"") (tags-todo "+live"
org-agenda-files '("~/org/work.org")
org-agenda-include-diary t
org-blocker-hook '(org-block-todo-from-children-or-siblings-or-
parent org-depend-block-todo)
org-completion-use-ido t
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-agenda-todo-ignore-scheduled t
org-agenda-start-with-log-mode t
org-clock-out-switch-to-state '(lambda (prev-state) (if (member prev-
state org-done-keywords) "DONE" "STARTED"))
org-deadline-warning-days 1
org-agenda-skip-scheduled-if-done t
org-trigger-hook '(org-depend-trigger-todo)
org-export-preprocess-hook '(org-export-blocks-preprocess)
org-tab-first-hook '(org-hide-block-toggle-maybe)
org-src-mode-hook '(org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-todo-keywords '((sequence "TODO(t)" "STARTED(s)" "WAITING(w@/!)"
"|" "DONE(d)" "OBSOLETE(o)"))
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-
drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-agenda-dim-blocked-tasks 'invisible
org-agenda-tags-todo-honor-ignore-options t
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook org-show-
block-all append local] 5]
)
org-agenda-ndays 1
org-refile-targets '((nil :maxlevel . 3))
org-emphasis-regexp-components '(" ('\"{" "- .,:!?;'\")}" " .\n,
\"'" "." 1)
org-confirm-elisp-link-function nil
org-agenda-mode-hook '((lambda nil (hl-line-mode 1)))
org-enforce-todo-dependencies t
org-agenda-skip-deadline-if-done t
org-occur-hook '(org-first-headline-recenter)
org-from-is-user-regexp "\\"
org-drawers '("PROPERTIES" "CLOCK" "LOGBOOK" "NOTES")
)
___
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
