From: Bernt Hansen <bernt@norang.ca>
To: Umesh P N <umesh.p.nair@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question on org-mode adding extra blank line
Date: Fri, 04 Feb 2011 20:25:07 -0500 [thread overview]
Message-ID: <87mxmbgtn0.fsf@norang.ca> (raw)
In-Reply-To: <AANLkTikaqDLUs5shMpJ5uTGkSxy1k+TtTN7hpij1qRWS@mail.gmail.com> (Umesh P. N.'s message of "Wed, 2 Feb 2011 10:26:02 -0800")
Umesh P N <umesh.p.nair@gmail.com> writes:
> Hi,
>
> Sometimes (I don't know when), when I press M-return (org-meta-return) at the end of a heading, the next heading
> line (at the same level) is added after a blank line rather than on the next line. Looks like it is a feature and
> not a bug.
>
> Like this.
>
> * heading 1 (I press M-return here.)
>
> * heading 2
>
> I expected
>
> * heading 1 (I press M-return here.)
> * heading 2
>
> instead.
>
> When does this happen, and how can I control that?
>
> My gtd configurations below:
>
> # -*- mode: org; -*-
> # 2011-Q1.org: org-mode data for Umesh Nair for 2011 Q1
> #+STARTUP: overview
> #+STARTUP: hidestars
> #+STARTUP: odd
> #+TITLE: Work GTD file for 2011 Q1 (Umesh Nair)
> #+OPTIONS: toc:nil H:3
> #+TAGS: ICU4C(c) ICU4J(j) CLDR(C) III(i) Documentation(d) OCR(o) READING(r) PHONE(p)
> #+TAGS: EMAIL(e) INTERVIEW(I) TODAY(t)
> #+TAGS: Q1(1) Q2(2) Q3(3) Q4(4) NOW(n) LATER(l)
>
> Thanks,
>
> - Umesh
Hi Umesh,
This is controlled by the variable org-blank-before-new-entry. Normally
this is set to 'auto' by default to try to make the following entry for
lists and headings the same as the current one -- if it has a blank line
then the next entry will also.
You can customize this variable to always or never include blank lines
before new entries.
HTH,
Bernt
prev parent reply other threads:[~2011-02-05 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 18:26 Question on org-mode adding extra blank line Umesh P N
2011-02-05 1:25 ` Bernt Hansen [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=87mxmbgtn0.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=umesh.p.nair@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).