emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-insert-heading
Date: Sat, 16 Oct 2010 07:30:51 +0200	[thread overview]
Message-ID: <6079A7F4-8CF4-4658-8D9D-9EFEAE5AA586@gmail.com> (raw)
In-Reply-To: <4CB891AE.1050204@easy-emacs.de>

Hi Andreas,

On Oct 15, 2010, at 7:38 PM, Andreas Röhler wrote:

>
> Hi,
>
> doku of `org-insert-heading' says:
>
> ,----
> | If point is not at the beginning, do not split the line,
> | but create the new headline after the current line.
> `----
>
> which sounds wisely.

>
> Unfortunately function behaves different, splits line
> uses it's following part to create the new headline
> from, an inconvenience, resp. bug IMHO.
>
> Also tex-info endorses that:
>
> ,----
> | When this command is used in
> | the middle of a line, the line is split and the rest of the line  
> becomes
> | the new headline@footnote{If you do not want the line to be split,
> | customize the variable
> `----
>

In fact, splitting the line is the intended behavior, and there is a  
variable
to change that.

I have updated the docstring of the command.

- Carsten


> Seems something across anyway.  Suggest to restore/enable the
> behaviour of the doku-string. Could send a patch.
>
> Interesting to read the reason for this change/difference anyway, so  
> maybe I change my opinion too...
>
> Thanks all
>
>
> Andreas
>
> --
> https://code.launchpad.net/~a-roehler/python-mode/python-mode- 
> components
> https://code.launchpad.net/s-x-emacs-werkstatt/
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-10-16  5:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 17:38 org-insert-heading Andreas Röhler
2010-10-16  5:30 ` Carsten Dominik [this message]
2010-10-16  6:14   ` org-insert-heading Andreas Röhler
  -- strict thread matches above, loose matches on Subject: below --
2013-11-13  1:49 org-insert-heading Thomas S. Dye
2013-11-13  8:58 ` org-insert-heading Bastien
2013-11-13 13:06   ` org-insert-heading Thomas S. Dye
2013-11-13 14:15     ` org-insert-heading Bastien
2013-11-14 17:46       ` org-insert-heading Nicolas Goaziou
2013-11-14 22:53         ` org-insert-heading Bastien
2013-11-15  6:42           ` org-insert-heading Carsten Dominik
2013-11-15  8:08             ` org-insert-heading Bastien
2014-11-12  0:10 org-insert-heading Luke Crook
2014-11-12  0:13 ` org-insert-heading Luke Crook
2014-11-13 20:01 ` org-insert-heading Nicolas Goaziou
2014-11-14  3:14   ` org-insert-heading Luke Crook
2014-11-14  4:18     ` org-insert-heading Luke Crook
2014-11-16 14:52     ` org-insert-heading Nicolas Goaziou

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=6079A7F4-8CF4-4658-8D9D-9EFEAE5AA586@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=andreas.roehler@easy-emacs.de \
    --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).