From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Alekseyev Subject: Re: Capitalisation and good taste ? Date: Fri, 20 Jan 2012 22:00:24 -0600 Message-ID: References: <87k4509rc1.fsf@iro.umontreal.ca> <87aa5wcitv.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:47404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RoS7v-0003QV-H7 for emacs-orgmode@gnu.org; Fri, 20 Jan 2012 23:00:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RoS7u-000763-HS for emacs-orgmode@gnu.org; Fri, 20 Jan 2012 23:00:27 -0500 Received: from mail-pw0-f41.google.com ([209.85.160.41]:50735) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RoS7u-00074y-7p for emacs-orgmode@gnu.org; Fri, 20 Jan 2012 23:00:26 -0500 Received: by pbdu6 with SMTP id u6so805266pbd.0 for ; Fri, 20 Jan 2012 20:00:25 -0800 (PST) In-Reply-To: <87aa5wcitv.fsf@norang.ca> 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 > A long time ago all capitals was the only way these keywords were > supported. =A0Since then they have become case insensitive and I use all > lowercase for most of my keywords now (#+begin_src:, #+begin_example: > etc) > > With fontification these stand out enough now and the capitalization can > be removed. So I'm kind of late to this party, but like Bernt, I've been favoring lowercase #+ keywords; I believe it looks cleaner and easier on the eyes. However, if functions that autogenerate keywords (e.g. #+results from code blocks and easy templates) default to a particular case, forcing a different case as a user becomes unappealing (consistency trumps aesthetics). If we want to keep org truly keyword-case-agnostic, then there should be a user-customized variable that easy templates and org-babel result blocks would follow. --Leo