emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Mats Kindahl <mats.kindahl@oracle.com>,
	Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: [PATCH] Resolve regexp ambiguity for item headers
Date: Wed, 19 Sep 2012 14:14:52 -0400	[thread overview]
Message-ID: <3042.1348078492@alphaville> (raw)
In-Reply-To: Message from Bastien <bzg@altern.org> of "Wed\, 19 Sep 2012 18\:51\:10 +0200." <87ehlyhs75.fsf@bzg.ath.cx>

Bastien <bzg@altern.org> wrote:

> Hi Nicolas,
> 
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
> 
> > There's room from improvement, though: I find strange that "**** " is
> > a valid empty headline while "****" isn't.
> 
> This I find natural.  
> 
> The prefix for headlines includes the whitespace, so the whitespace
> is needed for empty headlines too.  Also, people might want to use 
> lines matching "^*+$" (to separate paragraphs or whatever.)
> 
> 2 cts of course,
> 

The trouble of course is that the space is almost invisible, so it leads
to hair-pulling: "why the (&^&^$%&bleep*(^()*^* doesn't this work?"

OTOH, if it happens to you once, you tend to remember it for ever after :-)

I see your 2¢ and lower you to 1.5¢,
Nick

  reply	other threads:[~2012-09-19 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 13:20 [PATCH] Resolve regexp ambiguity for item headers Mats Kindahl
2012-09-10 18:24 ` Nicolas Goaziou
2012-09-10 19:35   ` Mats Kindahl
2012-09-12 14:49     ` Nicolas Goaziou
2012-09-19  9:14       ` Bastien
2012-09-19  9:19         ` Mats Kindahl
2012-09-19 13:58           ` Nicolas Goaziou
2012-09-19 16:51             ` Bastien
2012-09-19 18:14               ` Nick Dokos [this message]
2012-09-21  8:56                 ` Bastien

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=3042.1348078492@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mats.kindahl@oracle.com \
    --cc=n.goaziou@gmail.com \
    /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).