emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: Bernt Hansen <bernt@norang.ca>,
	nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Capitalisation and good taste ?
Date: Tue, 10 Jan 2012 10:46:23 -0500	[thread overview]
Message-ID: <31946.1326210383@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) of "Tue\, 10 Jan 2012 09\:59\:52 EST." <87ty4361sn.fsf@iro.umontreal.ca>

François Pinard <pinard@iro.umontreal.ca> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > François Pinard <pinard@iro.umontreal.ca> wrote:
> >> P.P.S. How about amending the manual for consistent capitalization?
> >> 
> 
> > Knock yourself out! ;-)
> 
> I've absolutely nothing against doing that little work myself (that one
> is easy enough!), besides the idea that I might be working against the
> crowd.  If nobody objects that I normalize everything (every #+ thing)
> to lower case, I'll happily do it.  If the only result of a patch would
> be to start a flame war (or just loosing my time), I'd better stay
> quiet...
> 
> Always easier to formally ask permission once you informally got it!
> 

OK - I'm not the one to ask permission from, but I doubt very much that
a flame war will erupt because of a patch to make things in the manual
more uniform (of course, there will have to be a notation somewhere, if
one is not there already, that capitalization does not matter in these
cases: it's easy to infer that when all the examples are in various
forms of capitalization, but harder when everything is uniform - as you
can see, uniformity is not an unmitigated blessing :-) ).

Nick

  reply	other threads:[~2012-01-10 15:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  3:19 Capitalisation and good taste ? François Pinard
2012-01-10  3:55 ` Bernt Hansen
2012-01-10  5:13   ` Nick Dokos
2012-01-10  5:35     ` François Pinard
2012-01-10  7:37       ` Nick Dokos
2012-01-10 14:59         ` François Pinard
2012-01-10 15:46           ` Nick Dokos [this message]
2012-01-10 19:32       ` Bastien
2012-01-10 19:38         ` Eric Schulte
2012-01-10 19:55           ` Bastien
2012-01-10 20:18             ` François Pinard
2012-01-10 20:57               ` Martyn Jago
2012-01-11  7:49               ` Sebastien Vauban
2012-01-14 22:15                 ` François Pinard
2012-01-14 23:01                   ` Sebastien Vauban
2012-01-11 15:40               ` Bastien
2012-01-14 22:25                 ` François Pinard
2012-01-11 15:38             ` Bastien
2012-01-11 20:47               ` Eric Schulte
2012-01-11 20:57                 ` Eric Schulte
2012-01-11 21:26                   ` [PATCH] " Thomas S. Dye
2012-01-11 22:42                     ` Eric Schulte
2012-01-12  7:42                   ` Bastien
2012-01-10  5:22   ` François Pinard
2012-01-10 17:45     ` Tommy Kelly
2012-01-10 21:19     ` Eric S Fraga
2012-01-10 23:41       ` Sankalp
2012-01-21  4:00   ` Leo Alekseyev
2012-01-21 12:16     ` Bernt Hansen
2012-01-21 20:08       ` Eric S Fraga
2012-01-21 23:03         ` Bernt Hansen
2012-01-23  8:49           ` Eric S Fraga
2012-01-24 14:42             ` Bastien
2012-01-10 21:13 ` Eric S Fraga

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=31946.1326210383@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).