From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [RFC] Draft mode Date: Fri, 09 Oct 2015 10:07:29 +0200 Message-ID: <87vbagqxby.fsf@gmx.us> References: <87io6w9p7y.fsf@nicolasgoaziou.fr> <87io6vd7vl.fsf@gmx.us> <87r3l6jv55.fsf@nicolasgoaziou.fr> <87oag95thw.fsf@gmx.us> <87d1wpi9cx.fsf@nicolasgoaziou.fr> <87wpuxw3pb.fsf@ucl.ac.uk> <87a8rtkrej.fsf@alphaville.usersys.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkSiR-0000Po-RM for emacs-orgmode@gnu.org; Fri, 09 Oct 2015 04:07:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkSiO-0007v2-Hq for emacs-orgmode@gnu.org; Fri, 09 Oct 2015 04:07:47 -0400 Received: from plane.gmane.org ([80.91.229.3]:57380) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkSiO-0007ur-BL for emacs-orgmode@gnu.org; Fri, 09 Oct 2015 04:07:44 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZkSiM-0001d3-AU for emacs-orgmode@gnu.org; Fri, 09 Oct 2015 10:07:42 +0200 Received: from 62.80.108.14 ([62.80.108.14]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Oct 2015 10:07:42 +0200 Received: from rasmus by 62.80.108.14 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Oct 2015 10:07:42 +0200 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: emacs-orgmode@gnu.org Nick Dokos writes: > Eric S Fraga writes: > >> On Thursday, 8 Oct 2015 at 19:00, Nicolas Goaziou wrote: >> >> [...] >> >>> I think I will go with the straight to the point >>> `org-export-barf-on-invalid-link' variable. >>> >>> However, not sure about the OPTIONS item. >>> >>> #+OPTIONS: ???:t >> >> #+options: barf:t >> >> ;-) >> >> More seriously, I'm a big fan of longer is better if more clear so how >> about "invalidlinksok:t" or "allowdanglinglinks:t" or some variation >> thereof? > > Can option names contain dashes? > If so, combine these two ideas to make a name as similar as possible > to the variable name: > > #+options: barf-on-invalid-link:t While I agree that options such as 't:·', '^:·', 'h:·' are bad, I think 'barf:·' is nice. It's short and precise, much like 'num:·'. Something like 'barf-on-invalid-link' is very easy to mistype or forget. And yes, I mostly type options by hand. Rasmus -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone