From: Thomas Morgan <tlm@ziiuu.com>
To: emacs-orgmode@gnu.org
Subject: Item scheduled in agenda based on Org player link's start time
Date: Sat, 24 May 2014 18:36:09 +0200 [thread overview]
Message-ID: <87ppj3rv5y.fsf@azha.ziiuu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
Dear Org mode hackers,
This is a recipe for a bug involving Org player, though the bug
might be in Org mode itself.
1. Start Emacs with `emacs -Q -l setup.el'. This opens the day agenda,
which looks like this.
,----
| Day-agenda (W21):
| Friday 23 May 2014
| test-case: 1:23...... Scheduled: TODO Buckle my shoe
| 8:00...... ----------------
| 10:00...... ----------------
| 12:00...... ----------------
| 14:00...... ----------------
| 14:12...... now - - - - - - - - - - - - - - - - - - - - - - - - -
| 16:00...... ----------------
| 18:00...... ----------------
| 20:00...... ----------------
`----
I did not expect the TODO item to be scheduled for 1:23am.
That time is part of the link and is intended for Org player's use.
The text of the TODO item is this:
,----
| Buckle my [[file://shoe.ogg::1:23][shoe]]
`----
This is the format Org player uses to specify where in the media file
to start playback. From `org-player.el':
,----
| ;;; Links can also specify track positions. When a link contains a track
| ;;; position, playback will start at that position in the track. For example:
| ;;;
| ;;; [[file:/path/to/song.mp3::2:43]] Starts playback at 2 min 43 sec.
`----
Best,
Thomas
[-- Attachment #2: setup.el --]
[-- Type: application/emacs-lisp, Size: 238 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: test-case.org --]
[-- Type: text/x-org, Size: 79 bytes --]
* TODO Buckle my [[file://shoe.ogg::1:23][shoe]]
SCHEDULED: <2014-05-23 Fri>
next reply other threads:[~2014-05-25 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 16:36 Thomas Morgan [this message]
2014-05-26 5:35 ` Item scheduled in agenda based on Org player link's start time 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=87ppj3rv5y.fsf@azha.ziiuu.com \
--to=tlm@ziiuu.com \
--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).