emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manish <mailtomanish.sharma@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-remember: Skip creation of the default '* Notes' task
Date: Tue, 14 Apr 2009 12:11:16 +0530	[thread overview]
Message-ID: <e7cdbe30904132341m4cebf8f2xc2fc7a7f20ece83b@mail.gmail.com> (raw)
In-Reply-To: <1239311972-3362-3-git-send-email-bernt@norang.ca>

  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

  reply	other threads:[~2009-04-14  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 21:19 [PATCH] Report org-version after reloading Bernt Hansen
2009-04-09 21:19 ` [PATCH] Document more org-refile related variables in the docstring Bernt Hansen
2009-04-09 21:19 ` [PATCH] org-remember: Skip creation of the default '* Notes' task Bernt Hansen
2009-04-14  6:41   ` Manish [this message]
2009-04-14 12:30     ` Bernt Hansen
2009-04-10  8:28 ` [PATCH] Report org-version after reloading Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7cdbe30904132341m4cebf8f2xc2fc7a7f20ece83b@mail.gmail.com \
    --to=mailtomanish.sharma@gmail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).