emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ob-sed
Date: Sat, 30 May 2015 22:08:59 -0400	[thread overview]
Message-ID: <871thx5whw.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: AB6D1204-921D-4E38-94DA-F5E23509F4A4@infomedia.uib.no

Bjarte Johansen <bjarte.johansen@infomedia.uib.no> writes:

>> On 30 May 2015, at 14:32, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> 
>> Bjarte Johansen <bjarte.johansen@infomedia.uib.no> writes:
>> 
>>> I think I have addressed all of your comments except I didn’t
>>> understand the comment about the spaces. Are there two spaces extra or
>>> do you want me to introduce two spaces somewhere?
>> 
>> As Suvayu Ali pointed out, sentences in comments and docstrings are
>> expected to be separated by two spaces (american english convention).
> I was not aware of this convention. I also don’t really understand it, but I will change it.
>

It dates from the typewriter era (as does the convention of "double
spacing"). In that context, it makes the visual detection of the end of
the sentence easier. But the real reason to follow it now is that the
emacs sentence commands use the convention to determine what a sentence
is.  See

        (info "(emacs) sentences")

Nick

      parent reply	other threads:[~2015-05-31  2:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  8:51 ob-sed Bjarte Johansen
2015-05-27  8:56 ` ob-sed Bjarte Johansen
2015-05-27 21:31   ` ob-sed Nicolas Goaziou
2015-05-28 11:47     ` ob-sed Bjarte Johansen
2015-05-29  9:00       ` ob-sed Nicolas Goaziou
2015-05-29 13:32         ` ob-sed Bjarte Johansen
2015-05-29 17:08           ` ob-sed Suvayu Ali
2015-05-30 12:32           ` ob-sed Nicolas Goaziou
2015-05-30 12:36             ` ob-sed Bjarte Johansen
2015-05-30 13:01               ` ob-sed Nicolas Goaziou
2015-05-31  2:08               ` Nick Dokos [this message]

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=871thx5whw.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).