Just thinking aloud:
"Opening directory", "no such file or directory",
>> | "/home/shamrock/webs/mydomain/.#index.org"
is exactly what grep always gives me in such e case (I often use
`grep -lFr string dir').
sh> ls -l /home/sebastian/notes/.#index.org
lrwxrwxrwx 1 sebastian sebastian 31 26. Okt 22:27
/home/sebastian/notes/.#index.org -> [EMAIL PROTECTED]:1225047914
That means .#index.org is a link pointing to a non existent file.
4849 is the process (cat /proc/4849/cmdline), that edits the file
/home/sebastian/notes/.index.org, so it indeed seems to be a locking
mechanism.
Problem seems to be, that the error occurs when ever trying to
access the file, which simply can not work, since it's a link
pointing nowhere.
org-publish-get-base-files-1 excludes files, whos names consist entirely
of dots:
(not (string-match "^\\.+$" fnd))
Maybe exclude files like '[EMAIL PROTECTED]:1225047914'
too - hm - a totaly legal filename though...
Or extend the file-test, so it doesn't simply test for names, but
additionally tests for
'is it a file OR (is it link that points to a real file)'
Carsten Dominik wrote:
Hi Richard,
Maybe this is some file locking mechanism?
I am quite sure that Org does not create this file explicitly.
Can you try to figure out exactly how things happen in
org-publish-get-base-files-1, and which line exactly is causing the
error to be triggered?
- Carsten
On Oct 25, 2008, at 2:09 AM, Richard Riley wrote:
If I modify a file and then publish it using "C-c C-e f" without saving
it I get an error of the form:
,----
| File error: "Opening directory", "no such file or directory",
| "/home/shamrock/webs/mydomain/.#index.org"
`----
I traced it through with edebug (how do you set a watch on a variable? I
couldnt get it through my thick skull from the manual).
Anyway, the error occurs in
org-publish-get-base-files-1
and is a result of a broken link :
,----
| lrwxrwxrwx 1 shamrock shamrock 54 2008-10-25 02:03 .#index.org ->
[EMAIL PROTECTED]:1224638771
| [EMAIL PROTECTED]:~/webs/mydomain$ cat .#index.org
| cat: .#index.org: No such file or directory
`----
The link is created somewhere in the publish process and is not properly
constructed if the file has not been saved prior to publish.
Someone more familiar with the process might know immediately where to
fix it, if not I will have a crack next week.
--
We've arranged a civilization in which most crucial elements
profoundly depend on science and technology. We have also arranged
things so that almost no one understands science and technology. This
is a prescription for disaster. We might get away with it for a
while, but sooner or later this combustible mixture of ignorance and
power is going to blow up in our faces. ~Carl Sagan
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
