From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Draft mode
Date: Fri, 09 Oct 2015 10:07:29 +0200 [thread overview]
Message-ID: <87vbagqxby.fsf@gmx.us> (raw)
In-Reply-To: 87a8rtkrej.fsf@alphaville.usersys.redhat.com
Nick Dokos <ndokos@gmail.com> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> 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
next prev parent reply other threads:[~2015-10-09 8:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 9:38 [RFC] Draft mode Nicolas Goaziou
2015-09-27 11:37 ` Nicolas Goaziou
2015-09-27 16:31 ` Charles C. Berry
2015-09-28 20:56 ` Aaron Ecay
2015-10-07 20:22 ` Nicolas Goaziou
2015-09-27 18:39 ` Rasmus
2015-09-27 20:01 ` Marcin Borkowski
2015-10-07 20:12 ` Nicolas Goaziou
2015-10-08 14:23 ` Rasmus
2015-10-08 16:36 ` Thomas S. Dye
2015-10-08 16:54 ` Rasmus
2015-10-08 16:57 ` Eric Abrahamsen
2015-10-08 17:00 ` Nicolas Goaziou
2015-10-08 19:38 ` Eric S Fraga
2015-10-08 20:59 ` Nick Dokos
2015-10-09 8:07 ` Rasmus [this message]
2015-10-10 14:21 ` Nicolas Goaziou
2015-10-11 12:34 ` Rasmus
2015-10-17 12:54 ` Nicolas Goaziou
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=87vbagqxby.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).