emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Subhan Michael Tindall <SubhanT@familycareinc.org>
To: "'e.fraga@ucl.ac.uk'" <e.fraga@ucl.ac.uk>,
	Jude DaShiell <jdashiel@shellworld.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: long outline entries
Date: Fri, 23 Jan 2015 17:04:30 +0000	[thread overview]
Message-ID: <8bddf5c045364e67b1259f1eceb43c5e@fcmailsvr2.familycareinc.org> (raw)
In-Reply-To: <87fvb1khbo.fsf@ucl.ac.uk>

> -----Original Message-----
> From: emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org
> [mailto:emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org] On
> Behalf Of e.fraga@ucl.ac.uk
> Sent: Friday, January 23, 2015 12:55 AM
> To: Jude DaShiell
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] long outline entries
> On Thursday, 22 Jan 2015 at 17:06, Jude DaShiell wrote:
> > Is there any way in org-mode to have two things happeautomatically
> > when a long outline entry gets keyed into a file?  First the lines of
> > the outline entry do not go beyond a defined right margin and split on
> spaces.
> > Second, subsequent lines created by above wrapping start on a left
> > margin that makes it clear to org-mode that these additional lines are
> > all part of the original outline entry since they're inside the
> > indents created by the stars and space that started the original
> > outline entry?  A question
> Maybe auto-fill-mode is what you want?
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-717-gd36bd8

Auto-fil-mode doesn't apply to headlines.  AFAIK, there is no way to automatically wrap a headline other than hitting enter, and this moves the rest of what you are typing into the body of the entry.
If I'm recalling correctly, wrapping headlines like you have suggested (which I would like myself!) would break the new more formal drawers format without some significant rewrite.

This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message.  Thank you.

      reply	other threads:[~2015-01-23 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 22:06 long outline entries Jude DaShiell
2015-01-23  8:54 ` e.fraga
2015-01-23 17:04   ` Subhan Michael Tindall [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:

  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=8bddf5c045364e67b1259f1eceb43c5e@fcmailsvr2.familycareinc.org \
    --to=subhant@familycareinc.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=jdashiel@shellworld.net \


* 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


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).