From: Neil Jerram <neil@ossau.homelinux.net>
To: emacs-orgmode@gnu.org,
David Masterson <dsmasterson@outlook.com>"emacs-orgmode@gnu.org"
<emacs-orgmode@gnu.org>
Subject: Re: Standard Format for Org Outlines?
Date: Sat, 24 Nov 2018 09:04:24 +0000 [thread overview]
Message-ID: <BEB6E9BB-E416-45CB-A2B3-5951B6174CAA@ossau.homelinux.net> (raw)
In-Reply-To: <SN1PR0701MB1853547757A3018667191377A5D40@SN1PR0701MB1853.namprd07.prod.outlook.com>
On 23 November 2018 23:23:27 GMT, David Masterson <dsmasterson@outlook.com> wrote:
>Probably a dumb question, but is there a standard format for Org
>outlines. I'm particularly wondering about the use of blank lines. I
>prefer to have blank lines before my headings for readability, but I
>think a lot of other people work without the blank lines. I recently
>ran into a case with BeOrg where it, in fact, removed the blank lines
>when it synced my change back to my original file. That led me to
>think
>what is the standard format for an Org outline. Should I expect the
>tools to adjust to me or should I adjust to them?
>--
>David
Great question; I've seen and wondered the same thing. In my case it's Orgzly that seems to like removing some blank lines - although happily it doesn't seem to mind when I add some of them back again.
Best wishes,
Neil
next prev parent reply other threads:[~2018-11-24 9:04 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BEB6E9BB-E416-45CB-A2B3-5951B6174CAA@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=dsmasterson@outlook.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.