From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: SETUPFILE: file open failure hardly noticeable Date: Fri, 5 Apr 2013 18:29:29 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO9W8-0005Iz-Q8 for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:29:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UO9W7-0004Al-Pd for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:29:32 -0400 Received: from mail-la0-x229.google.com ([2a00:1450:4010:c03::229]:48279) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO9W7-0004AS-IV for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:29:31 -0400 Received: by mail-la0-f41.google.com with SMTP id fo12so3669522lab.14 for ; Fri, 05 Apr 2013 09:29:29 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode Hi all I had to experience that a #+SETUPFILE: pointing to a nonexisting file results in not more than two times a (message) "Cannot read file [...]" in the messages buffer which I didn't notice in the first place. Only when I noticed that my custom todo keywords configuration was missing I started to realize what happened. (The minibuffer replaces those messages already after opening the file and I never examine the Messages buffer at that time without reason.) In the Org source code I found noerror for the two corresponding calls of org-file-contents. I tried to make the load failure more prominent but have to give up for the moment: When changing the (message) to (error) or when adding a (ding) to the (message), in my case both trigger new problems like hooks not called and messed up org-emphasis or fontify. And the (error) is noticeable only hardly again because it seems to me like catched by "File mode specification error", a behavior by design which I don't understand. Is there any opinion or help on how to improve this? Michael