[PATCH] Report org-version after reloading

[PATCH] Report org-version after reloading

[Bernt Hansen]

---
I'm always typing 'M-x org-version' after reloading the compiled or uncompiled
org files using 'M-x org-reload'.  This just saves me typing that extra
command each time.  Yes I'm lazy ;)

This and the following patches are available on my for-carsten branch.

-Bernt


 lisp/org.el |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index c17a694..249f843 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -14774,7 +14774,8 @@ With prefix arg UNCOMPILED, load the uncompiled versions."
 		  (file-exists-p (concat f ".elc")))
 	     (load (concat f ".elc") nil nil t)
 	   (load (concat f ".el") nil nil t))))
-     files)))
+     files))
+  (org-version))
 
 ;;;###autoload
 (defun org-customize ()
-- 
1.6.2.2.485.ge37347

[PATCH] Document more org-refile related variables in the docstring

[Bernt Hansen]

Make it easier to find variables related to refiling by just reading
the docstring.
---
I found it took a few minutes to look up these variables that change how
org-refile works.  I just added them to the docstring so next time I can
find them faster :)

 lisp/org.el |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index 249f843..1e8c706 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8241,7 +8241,9 @@ below it are allowed.
 With prefix arg GOTO, the command will only visit the target location,
 not actually move anything.
 With a double prefix `C-u C-u', go to the location where the last refiling
-operation has put the subtree."
+operation has put the subtree.
+
+See also `org-refile-use-outline-path' and `org-completion-use-ido'"
   (interactive "P")
   (let* ((cbuf (current-buffer))
 	 (regionp (org-region-active-p))
-- 
1.6.2.2.485.ge37347

[PATCH] org-remember: Skip creation of the default '* Notes' task

[Bernt Hansen]

Remember and refile processing does not require a task.  This change
removes the unneeded default task.

This supports a workflow where new remember tasks and notes go into a
mostly empty file which just has #+FILETAGS: at the top and nothing
else.

This workflow has a minimal number of remember templates
  - one for new tasks and (filed in tasks.org)
  - one for new notes (filed in notes.org)
  - one for phone calls (filed in phone.org)

New tasks are added as top-level tasks to the end of these files and
the #+FILETAGS: REFILE header causes each task to be easy to find.
All tasks in these files are refiled to a more appropriate org file at
a later time.
---
Carsten, (and list)

I've started using this new workflow just this week and org remember insisted
on creating an annoying '* Notes' task before my #+FILETAGS: line since there
were no tasks in the file yet.  I'm refiling as top-level tasks at the end
of the file and the '* Notes' task was just in the way.  I couldn't find any 
good reason to keep this so this patch removes the requirement.  I find tasks
to refile with a custom agenda tag search looking for the tag REFILE and this
change gets rid of the bogus 'Notes' task that kept showing up.

Let me know if I missed some reason you really need this '* Notes' default
task.

-Bernt



 lisp/org-remember.el |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/lisp/org-remember.el b/lisp/org-remember.el
index 6895340..926da74 100644
--- a/lisp/org-remember.el
+++ b/lisp/org-remember.el
@@ -860,10 +860,6 @@ See also the variable `org-reverse-note-order'."
 	(save-excursion
 	  (save-restriction
 	    (widen)
-	    (and (goto-char (point-min))
-		 (not (re-search-forward "^\\* " nil t))
-		 (insert "\n* " (or (and (stringp heading) heading)
-				    "Notes") "\n"))
 	    (setq reversed (org-notes-order-reversed-p))
 
 	    ;; Find the default location
-- 
1.6.2.2.485.ge37347

Re: [PATCH] Report org-version after reloading

[Carsten Dominik]

Hi Bernt,

I have applied all three patches, thanks.

- Carsten

On Apr 9, 2009, at 11:19 PM, Bernt Hansen wrote:

> ---
> I'm always typing 'M-x org-version' after reloading the compiled or  
> uncompiled
> org files using 'M-x org-reload'.  This just saves me typing that  
> extra
> command each time.  Yes I'm lazy ;)
>
> This and the following patches are available on my for-carsten branch.
>
> -Bernt
>
>
> lisp/org.el |    3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/lisp/org.el b/lisp/org.el
> index c17a694..249f843 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -14774,7 +14774,8 @@ With prefix arg UNCOMPILED, load the  
> uncompiled versions."
> 		  (file-exists-p (concat f ".elc")))
> 	     (load (concat f ".elc") nil nil t)
> 	   (load (concat f ".el") nil nil t))))
> -     files)))
> +     files))
> +  (org-version))
>
> ;;;###autoload
> (defun org-customize ()
> -- 
> 1.6.2.2.485.ge37347
>
>
>
> _______________________________________________
> 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: [PATCH] org-remember: Skip creation of the default '* Notes' task

[Manish]

  On Fri, Apr 10, 2009 at 2:49 AM, Bernt Hansen wrote:
  [snip (17 lines)]
  > Carsten, (and list)
  >
  > I've started using this new workflow just this week and org
remember insisted
  > on creating an annoying '* Notes' task before my #+FILETAGS: line
since there
  > were no tasks in the file yet. I'm refiling as top-level tasks at the end
  > of the file and the '* Notes' task was just in the way. I couldn't find any
  > good reason to keep this so this patch removes the requirement. I find tasks
  > to refile with a custom agenda tag search looking for the tag
REFILE and this
  > change gets rid of the bogus 'Notes' task that kept showing up.

If I may ask a question about your workflow.  Once you have constructed the
agenda view with all tasks tagged "REFILE", how do you go and start refiling
them?  Do you have any way to do refile from the agenda view itself or do you
visit the org file containing the task?

Thanks
-- 
Manish

Re: [PATCH] org-remember: Skip creation of the default '* Notes' task

[Bernt Hansen]

Manish <mailtomanish.sharma@gmail.com> writes:

>   On Fri, Apr 10, 2009 at 2:49 AM, Bernt Hansen wrote:
>   [snip (17 lines)]
>   > Carsten, (and list)
>   >
>   > I've started using this new workflow just this week and org
> remember insisted
>   > on creating an annoying '* Notes' task before my #+FILETAGS: line
> since there
>   > were no tasks in the file yet. I'm refiling as top-level tasks at the end
>   > of the file and the '* Notes' task was just in the way. I couldn't find any
>   > good reason to keep this so this patch removes the requirement. I find tasks
>   > to refile with a custom agenda tag search looking for the tag
> REFILE and this
>   > change gets rid of the bogus 'Notes' task that kept showing up.
>
> If I may ask a question about your workflow.  Once you have constructed the
> agenda view with all tasks tagged "REFILE", how do you go and start refiling
> them?  Do you have any way to do refile from the agenda view itself or do you
> visit the org file containing the task?

Hi Manish!

I visit the file containing the task and refile from there.  I just use
the agenda to verify that all tasks to be refiled are done.

I collect tasks for up to a week.  One of the items in my weekly review
checklist is to find tasks to refile and that's what I use the agenda
view for.

I'll reorder the tasks to group things together and then refile them as
a group to the target task in another file.

My main reason for switching to this workflow is to speed up my remember
usage - I don't want to think about where the task is going when I
create the remember task.  It's either a phone call (which starts the
clock immediately), or a task or a note.  Nothing else is really
important at the time I'm entering it.  I used to have tons of remember
templates to file things directly into the appropriate client org file
but then I found I needed to refile them again from there anyway and
thinking about which template I need to use before throwing the details
in the remember task wasn't buying me anything useful.

My reason for refiling everything is client phone calls are clocked and
contribute to billable hours at the end of the month.  I need to make
sure that clocked time is in the correct client org file and project so
it doesn't get lost when I invoice the client.  I found the easiest way
to do that is just get used to refiling everything away so my remember
task buckets (tasks.org, notes.org, phone.org) are empty.

HTH,
Bernt