From: Angus Gibson <darthshrine@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-batch-agenda lock problem
Date: Tue, 9 Jun 2009 22:53:13 +1000 [thread overview]
Message-ID: <0855B524-A126-4E56-B6FF-F9D343A4C6B5@gmail.com> (raw)
In-Reply-To: <679B0691-B585-4B34-9125-26955D8DBF68@gmail.com>
On 09/06/2009, at 22:24 , Carsten Dominik wrote:
>
> On Jun 9, 2009, at 12:40 PM, Angus Gibson wrote:
>
>> I am a recent convert to org-mode, and the ability to export the
>> agenda is very useful. Currently I have a script that runs every 10
>> seconds or so that calls:
>>
>> emacs -batch -l ~/.emacs -eval '(org-batch-agenda "a" org-agenda-
>> ndays 1)' 2>/dev/null
>
> The following may or may not work, depending on what happens in non-
> interactive emacs sessions when a lock is encountered. Maybe this
> would work?
>
> emacs -batch -l ~/.emacs -eval '(progn (defun ask-user-about-lock
> (&rest args) nil) (org-batch-agenda "a" org-agenda-ndays 1))' 2>/dev/
> null
Simple enough solution, thanks. I think it's a bit weird that it is
encountering the lock, but I suppose getting rid of the confirmation
is the easiest step for a completely non-interactive session.
Thanks,
Angus
>
> or
>
> emacs -batch -l ~/.emacs -eval '(progn (defun file-locked-p (&rest
> args) nil) (org-batch-agenda "a" org-agenda-ndays 1))' 2>/dev/null
>
>
> These are bad hacks, but should be OK sice creating an agenda should
> not modify any file buffers...
>
> - Carsten
>
>
>
>
>>
>> In order to put the agenda items on my desktop. This works fine,
>> until I start to edit the org file. From what I have gathered, this
>> causes a lock to be placed, and org-batch-agenda has a collision
>> with this lock, resulting in no output because it's trying to
>> output the message about resolving the collision. Obviously this
>> isn't very useful, so I was wondering why org-batch-agenda would
>> have to modify the file, or possibly the easiest way to resolve
>> this (I'm not amazing with Emacs).
>>
>> Thanks,
>> Angus
>>
>>
>> _______________________________________________
>> 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
>
next prev parent reply other threads:[~2009-06-09 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 10:40 org-batch-agenda lock problem Angus Gibson
2009-06-09 12:24 ` Carsten Dominik
2009-06-09 12:53 ` Angus Gibson [this message]
2009-06-15 10:44 ` 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=0855B524-A126-4E56-B6FF-F9D343A4C6B5@gmail.com \
--to=darthshrine@gmail.com \
--cc=carsten.dominik@gmail.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).