emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: FR: toggling timestamps active/inactive
Date: Wed, 17 Oct 2007 18:18:33 +0100	[thread overview]
Message-ID: <20071017171833.GD10874@atlantic.linksys.moosehall> (raw)
In-Reply-To: <93a50cd52fdb50d8da9a08743318e38c@science.uva.nl>

On Tue, Oct 16, 2007 at 06:13:41PM +0200, Carsten Dominik wrote:
> On Oct 16, 2007, at 16:19, Adam Spiers wrote:
> > Another simple idea - subject line is pretty much self-explanatory I
> > think: would be great to be able to toggle timestamps between [] and
> > <>.
> >
> > Why?  Say I have an event in my diary.org file, and am subsequently
> > told my presence at the event is no longer necessary.  Consequently I
> > would like to keep it in the file for reference, to track colleagues'
> > movements or in case my presence is re-required, but I don't want the
> > event to appear in the agenda.
> 
> Writing the command is simple - finding a keybinding is harder.
> I will make so that using S-up or S-down on one of the brackets
> will switch the type.  If you have a good proposal for another
> key, come forward.

How about making it so that C-c ! over an active timestamp will
deactivate it, and C-c . over an inactive one will activate it?

> > By the way, I probably could have coded this in the time it took to
> > write the mail, but I thought that until I've sent a piece of paper to
> > the FSF assigning rights for code contributed to org-mode and emacs,
> > it would be better to let Carsten write it.  Is that correct or flawed
> > thinking?
> 
> Well, I cannot officially take your code, but if you show me an
> "example" implementation, it will probably be faster still.

Now that I am beginning to get really serious about implementing the
review component of GTD, new ideas for org-mode tweaks are continually
popping into my head; apologies for spamming the list recently as a
result :-)  Several of the tweaks would require >15 LoC to implement,
so I am thinking it might be worth sorting out copyright assignment.
How should I go about this - would the following be sufficient?

http://mirrors.wikifusion.info/gnu/elisp-archive/FSF-Copyright-Assignment

  reply	other threads:[~2007-10-17 17:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 14:19 FR: toggling timestamps active/inactive Adam Spiers
2007-10-16 16:05 ` Rick Moynihan
2007-10-16 16:22   ` Adam Spiers
2007-10-16 16:46     ` Rick Moynihan
2007-10-17  4:44     ` Carsten Dominik
2007-10-17  9:08       ` Rick Moynihan
2007-10-18 16:08         ` Carsten Dominik
2007-10-18 17:36           ` Bastien
2007-10-18 17:42             ` Bastien
2007-10-16 16:13 ` Carsten Dominik
2007-10-17 17:18   ` Adam Spiers [this message]
2007-10-19  5:36     ` Carsten Dominik
2007-10-19 18:18       ` Adam Spiers
2007-10-16 23:01 ` Christian Egli
2007-10-17  0:47   ` Bastien

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=20071017171833.GD10874@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --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).