From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joon Ro Subject: The error "Opening input file: No such file or directory" should show the source org file Date: Fri, 13 Oct 2017 16:55:53 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_BY2PR15MB0421E0B2CE8EE6AB69CF6F89EB480BY2PR15MB0421namp_" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51684) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e33Ff-0002J1-Lk for emacs-orgmode@gnu.org; Fri, 13 Oct 2017 12:56:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e33Fc-0005f4-FU for emacs-orgmode@gnu.org; Fri, 13 Oct 2017 12:55:59 -0400 Received: from mail-oln040092011101.outbound.protection.outlook.com ([40.92.11.101]:29344 helo=NAM04-SN1-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e33Fc-0005dt-0y for emacs-orgmode@gnu.org; Fri, 13 Oct 2017 12:55:56 -0400 Content-Language: en-US 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" To: "emacs-orgmode@gnu.org" --_000_BY2PR15MB0421E0B2CE8EE6AB69CF6F89EB480BY2PR15MB0421namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I often see the error message: "Opening input file: No such file or directo= ry" for one of the org files that has wrong file path for a #+SETUPFILE. It= usually happens when I change the path of the setup file which is used by = multiple org files. However, currently it is hard to locate the file where the error is origina= ted from. I think it would be great if the error message shows the location= of the file as well. Best Regards, Joon --_000_BY2PR15MB0421E0B2CE8EE6AB69CF6F89EB480BY2PR15MB0421namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,

I often see the error message: "Opening input file: No such file = or directory" for one of the org files that has wrong file path for a = #+SETUPFILE. It usually happens when I change the path of the setup fil= e which is used by multiple org files. 

However, currently it is hard to locate the file where the error is origina= ted from. I think it would be great if the error message shows the location= of the file as well.

Best Regards,
Joon

--_000_BY2PR15MB0421E0B2CE8EE6AB69CF6F89EB480BY2PR15MB0421namp_-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: The error "Opening input file: No such file or directory" should show the source org file Date: Sat, 14 Oct 2017 11:02:16 +0200 Message-ID: <87a80u3xwn.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45443) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e3IL4-0003nK-Ut for emacs-orgmode@gnu.org; Sat, 14 Oct 2017 05:02:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e3IKq-0005DG-0t for emacs-orgmode@gnu.org; Sat, 14 Oct 2017 05:02:34 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:55358) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e3IKp-0005C8-Q1 for emacs-orgmode@gnu.org; Sat, 14 Oct 2017 05:02:19 -0400 In-Reply-To: (Joon Ro's message of "Fri, 13 Oct 2017 16:55:53 +0000") 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" To: Joon Ro Cc: "emacs-orgmode@gnu.org" Hello, Joon Ro writes: > I often see the error message: "Opening input file: No such file or > directory" for one of the org files that has wrong file path for > a #+SETUPFILE. It usually happens when I change the path of the setup > file which is used by multiple org files. > > However, currently it is hard to locate the file where the error is > originated from. I think it would be great if the error message shows > the location of the file as well. Fixed. Thank you. Note that you can also use M-x org-lint to find wrong SETUPFILE keywords in the document. Regards, -- Nicolas Goaziou