emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: org-mode <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Bug on file publish
Date: Sun, 26 Oct 2008 23:10:09 +0100	[thread overview]
Message-ID: <4904EAC1.40602@gmx.de> (raw)
In-Reply-To: <98ECED6C-E9C1-48EA-B858-E580557834BF@uva.nl>

Hi,

in org-publish-get-base-files-1


(car (file-attributes "~/notes/.#index.org"))

gives sebastian@orgon.4849:1225047914

!!!

So we have to test, if fd-p is the name of an existing file in
base-dir. That's it.

	    (if (and fd-p --HERE--  recurse
		     (not (string-match "^\\.+$" fnd))
		     (if skip-dir (not (string-match skip-dir fnd)) t))

Regards,

   Sebastian



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 -> 
>> shamrock@development.mydomain.net.21672:1224638771
>> | shamrock@development:~/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
> 

  parent reply	other threads:[~2008-10-26 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25  0:09 Bug on file publish Richard Riley
2008-10-26  6:42 ` Carsten Dominik
2008-10-26 21:56   ` Sebastian Rose
2008-10-26 22:10   ` Sebastian Rose [this message]
2008-10-26 23:55     ` Sebastian Rose
2008-10-27  5:24       ` Carsten Dominik
2008-10-27  7:22       ` 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=4904EAC1.40602@gmx.de \
    --to=sebastian_rose@gmx.de \
    --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).