emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: newline at start of buffer
Date: Sat, 3 Oct 2009 09:24:30 +0200	[thread overview]
Message-ID: <E8677E75-C85C-43FF-A9BC-3A3BD7F33926@gmail.com> (raw)
In-Reply-To: <87hbuhp2wr.fsf@stats.ox.ac.uk>

Hi Dan,

this was a stupid hack to get the headline away from the first
buffer line which can cause problems in Org under some circumstances
which are hard to consistently remove.  It looks a the empty buffer
case because this is what will happen when people open a new buffer
and immediately create a headline in this way.  When there is already
something in the buffer, even a space, I am assuming the user wants
to be in control.

If it is not bothering you a lot, I'd like to keep it this way.

- Carsten

On Oct 3, 2009, at 5:33 AM, Dan Davison wrote:

> In a completely empty buffer, org-insert-heading inserts a newline
> before the first heading. However, if there is (e.g.) a single space
> character in the buffer (after point), the heading goes on the first
> line. I admit it's trivial, but that doesn't seem right -- there
> presumably isn't a reason for the newline in the first case and not in
> the second, right? (My preference would be no automatic blank line.)
>
> Dan
>
> diff --git a/lisp/org.el b/lisp/org.el
> index 73ef6c5..4883a2f 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -5754,7 +5754,7 @@ current headline.  If point is not at the  
> beginning, do not split the line,
> but create the new headline after the current line."
>   (interactive "P")
>   (if (= (buffer-size) 0)
> -      (insert "\n* ")
> +      (insert "* ")
>     (when (or force-heading (not (org-insert-item)))
>       (let* ((empty-line-p nil)
>             (head (save-excursion
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-10-03  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03  3:33 newline at start of buffer Dan Davison
2009-10-03  7:24 ` Carsten Dominik [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=E8677E75-C85C-43FF-A9BC-3A3BD7F33926@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --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).