From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois_Pinard?= <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: non-existent agenda file ~/file.txt. [R]emove from list or [A]bort?
Date: Mon, 21 May 2012 11:43:07 -0400 [thread overview]
Message-ID: <23435.1337614987@alphaville> (raw)
In-Reply-To: Message from =?utf-8?Q?Fran=C3=A7ois_Pinard?= <pinard@iro.umontreal.ca> of "Mon\, 21 May 2012 11\:28\:16 EDT." <86bolhr1tb.fsf@mercure.progiciels-bpi.ca>
François Pinard <pinard@iro.umontreal.ca> wrote:
> Bastien <bzg@gnu.org> writes:
>
> > "Sebastien Vauban"
> > <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
> >> These last days, I've observed that, whenever creating a new Org file
> >> (to be precise, when saving it), I'm asked:
> >>
> >> non-existent agenda file ~/file.txt. [R]emove from list or [A]bort?
> >>
> >> I'm then forced to answer `R' for the save to be done. Do you see
> >> that behavior as well?
>
> > Nope. Any help on how to reproduce this? Since which commit do you
> > see this?
>
> I'm not fully sure, but I think I saw this diagnostic already. It was
> quite a while ago, and the problem disappeared by upgrading. Could it be
> that, by some operational error, Sebastien is using some old Org code?
>
The message is generated from org-check-agenda-file, so just
edebug-defun this function (C-u M-C-x), try the operation and when (if)
it stops, get a backtrace with ``d''.
Nick
PS. I don't see this bahavior at all.
next prev parent reply other threads:[~2012-05-21 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 11:52 non-existent agenda file ~/file.txt. [R]emove from list or [A]bort? Sebastien Vauban
2012-05-21 13:26 ` Bastien
2012-05-21 15:28 ` François Pinard
2012-05-21 15:43 ` Nick Dokos [this message]
2012-05-21 16:05 ` Nick Dokos
2012-06-04 12:58 ` Sebastien Vauban
2012-06-04 13:35 ` Nick Dokos
2012-06-04 14:29 ` Sylvain Rousseau
2012-06-04 14:34 ` Sebastien Vauban
2012-06-04 16:13 ` Nick Dokos
2012-06-04 16:45 ` Sebastien Vauban
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=23435.1337614987@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).