emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Problems with missing newline on last line of	narrowd subtree [6.33trans (release_6.33f.129.g904a)]
Date: Mon, 04 Jan 2010 11:55:27 -0300	[thread overview]
Message-ID: <4b420167.0703c00a.522c.7615@mx.google.com> (raw)
In-Reply-To: <3C141607-5EDF-4766-8178-3EB4231A69B9@gmail.com>


Because of this problem I usually create a dummy headline at the end of the
subtree when I work in a narrowed subtree for a long time. If I avoid changing
anything after this dummy headline I know that nothing strange will happen. Not
elegant, I know, but its a work around for now.

- Darlan Cavalcante Moreira

At Mon, 4 Jan 2010 14:55:11 +0100,
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> 
> Hi David,
> 
> On Dec 17, 2009, at 9:47 PM, David Maus wrote:
> 
> >
> > Remember to cover the basics, that is, what you expected to happen and
> > what in fact did happen.  You don't know how to make a good report?   
> > See
> >
> >     http://orgmode.org/manual/Feedback.html#Feedback
> >
> > Your bug report will be posted to the Org-mode mailing list.
> > ------------------------------------------------------------------------
> >
> > If you narrow the buffer to a subtree, insert some content and widen
> > again the content below the subtree moves into the subtree if there
> > was no newline on the last line of the narrowed subtree.
> >
> > example.org
> > ,----
> > | * Headline 1
> > |
> > | * Headline 2
> > `----
> >
> > Narrow the buffer to "Headline 1", entere some text and remove all
> > empty lines below the entered text.
> >
> > example.org (narrowd)
> > ,----
> > | * Headline 1
> > | Hello World!
> > `----
> >
> > example.org (widened again)
> > ,----
> > | * Headline 1
> > | Hello World!* Headline 2
> > `----
> >
> > I do know that this behaviour makes absolutely sense as removing the
> > newlines in the narrowed subtree equals to removing the newlines in
> > the whole buffer.
> >
> > But as you can imagine this behaviour can be disastrous in Orgmode: I
> > stumpled upon this just because I remembered to have a todo item on my
> > list but Orgmode didn't know about it -- it was sucked into
> > another item.
> >
> > Maybe Orgmode should use a function `org-widen' that ensures a newline
> > at the end of a narrowed buffer before calling the Emacs' `widen'.
> 
> 
> That does make sense if the narrowing was done by org-narrow-to-subtree.
> But if it was done by another command, maybe even narrowing to part of  
> a line,
> than adding a newline can be equally destrucive. I don't think there  
> is a "good" solution to this issue.
> 
> Regards
> 
> - Carsten
> 
> >
> > Regards,
> >
> >  -- David
> >
> >
> > Emacs  : GNU Emacs 23.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.18.3)
> > of 2009-11-28 on elegiac, modified by Debian
> > Package: Org-mode version 6.33trans (release_6.33f.129.g904a)
> >
> >
> > _______________________________________________
> > 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
> 
> - Carsten
> 
> 
> 
> 
> 
> _______________________________________________
> 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-01-04 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 20:47 Bug: Problems with missing newline on last line of narrowd subtree [6.33trans (release_6.33f.129.g904a)] David Maus
2010-01-04 13:55 ` Carsten Dominik
2010-01-04 14:55   ` Darlan Cavalcante Moreira [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=4b420167.0703c00a.522c.7615@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=carsten.dominik@gmail.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 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).