emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rebel Neurofog <rebelneurofog@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Local subtree view (analysis of a fundamental issue with subtree narrowing)
Date: Sun, 3 Jun 2012 10:18:02 +0400	[thread overview]
Message-ID: <CAJsLN0K4hOVZmUXQn4qw2=-Pf1z4=m2VhSmu9Tmady11t=_AFg@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8s0kyvdsj7n1rc899Q=bNS9_ggzVcHD58b=6OLVQw69Tw@mail.gmail.com>

On Sun, Jun 3, 2012 at 6:51 AM, Samuel Wales <samologist@gmail.com> wrote:
> Hi Rebel,
>
> On 6/2/12, Rebel Neurofog <rebelneurofog@gmail.com> wrote:
>> The closest thing I'd like to have is (org-tree-to-indirect-buffer),
>> but, first, there's a bug in it (I use Emacs 23.4.2 - latest official):
>> - When I edit the last empty line in indirect buffer, the new text
>> gets into next entry (inside original buffer) like this:
>
>> ** TODO Go shoping
>> Some new text** TODO Finish Line Edit widget
>
> What version of Org are you running?  My version works.  That
> apparently empty line is possibly the beginning of the next line.  It
> might need a newline.  That is expected.

I've installed org-7.8.11
Now there's no flooding up of next line.
But original buffer is still edited incorrectly.

I even found org-indirect-buffer-display variable.
But still when I kill indirect buffer I have to press Tab several times
to make Org-mode specific things look fine.

I believe the problem is about indirect buffer editing:
modified part is inserted into view-precomposed data incorrectly.

      reply	other threads:[~2012-06-03  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03  2:51 Local subtree view (analysis of a fundamental issue with subtree narrowing) Samuel Wales
2012-06-03  6:18 ` Rebel Neurofog [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='CAJsLN0K4hOVZmUXQn4qw2=-Pf1z4=m2VhSmu9Tmady11t=_AFg@mail.gmail.com' \
    --to=rebelneurofog@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /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).