From: David Masterson <dsmasterson@outlook.com>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Standard Format for Org Outlines?
Date: Thu, 29 Nov 2018 00:22:01 +0000 [thread overview]
Message-ID: <SN1PR0701MB1853E17D35706F6CBF88A326A5D20@SN1PR0701MB1853.namprd07.prod.outlook.com> (raw)
In-Reply-To: <874lc2taxc.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 27 Nov 2018 23:25:51 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> David Masterson <dsmasterson@outlook.com> writes:
>
>> * Header 1
>>
>> * Header 2
>>
>> Position the cursor on '1' and M-return will create a new header with a
>> blank line before and after it, but C-return will create a new header
>> with a blank line before, but not after it.
> I see. I pushed a fix in master branch. Please let me know if it <C-RET>
> behaves better there.
Good try, but I think you got it backwards. I pulled down a daily
development snapshot tarball from yesterday (not good with git yet) and
tried it again. This time, it broke M-return by adding an extra blank
line after the header (ie. two blank lines), but still did not put in a
blank line after the header on C-return.
--
David
next prev parent reply other threads:[~2018-11-29 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 23:23 Standard Format for Org Outlines? David Masterson
2018-11-24 9:04 ` Neil Jerram
2018-11-24 9:20 ` Nicolas Goaziou
2018-11-25 20:53 ` David Masterson
2018-11-25 22:25 ` Nicolas Goaziou
2018-11-26 0:23 ` David Masterson
2018-11-26 9:52 ` Nicolas Goaziou
2018-11-26 17:29 ` David Masterson
2018-11-27 8:32 ` Nicolas Goaziou
2018-11-27 17:20 ` David Masterson
2018-11-27 22:25 ` Nicolas Goaziou
2018-11-29 0:22 ` David Masterson [this message]
2018-11-29 14:10 ` Nicolas Goaziou
2018-11-29 16:46 ` David Masterson
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=SN1PR0701MB1853E17D35706F6CBF88A326A5D20@SN1PR0701MB1853.namprd07.prod.outlook.com \
--to=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=neil@ossau.homelinux.net \
/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).