From mboxrd@z Thu Jan 1 00:00:00 1970 From: Reuben Thomas Subject: Re: Bug: Setting system command org-file-apps does not allow other settings to refer to it [8.2.5h (release_8.2.5h-620-g7fd183 @ /home/rrt/.emacs.d/el-get/package/elpa/org-20140210/)] Date: Mon, 17 Mar 2014 12:18:41 +0000 Message-ID: References: <87d2hos6xc.fsf@sc3d.org> <87mwgpk214.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf303ea6348464f504f4cc6b17 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPWV8-0001cK-PW for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:18:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPWV7-0001zW-UZ for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:18:42 -0400 Received: from mail-yh0-x235.google.com ([2607:f8b0:4002:c01::235]:36208) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPWV7-0001zO-OI for emacs-orgmode@gnu.org; Mon, 17 Mar 2014 08:18:41 -0400 Received: by mail-yh0-f53.google.com with SMTP id v1so5061845yhn.40 for ; Mon, 17 Mar 2014 05:18:41 -0700 (PDT) In-Reply-To: <87mwgpk214.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org --20cf303ea6348464f504f4cc6b17 Content-Type: text/plain; charset=ISO-8859-1 On 17 March 2014 02:11, Bastien wrote: > Hi Reuben, > > I'm confused and can't get what's the problem: is it a bug? > Is it a documentation bug? I don't know, because I don't know whether it's the behavior or documentation that is wrong. -- http://rrt.sc3d.org --20cf303ea6348464f504f4cc6b17 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 1= 7 March 2014 02:11, Bastien <bzg@gnu.org> wrote:
Hi Reuben,

I'm confused and can't get what's the problem: is it a bug?
Is it a documentation bug?

I don't know= , because I don't know whether it's the behavior or documentation t= hat is wrong.

--
http://rrt.sc3d.org
--20cf303ea6348464f504f4cc6b17--