From: Carsten Dominik <carsten.dominik@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] org-narrow-to-subtree: prevent prepending text to the next headline while narrowed
Date: Mon, 1 Feb 2010 09:11:32 +0100 [thread overview]
Message-ID: <47EB340A-1D49-44F3-8293-BFAA47532B5E@gmail.com> (raw)
In-Reply-To: <20524da71001220850m5cba19dfncd458d994f0ec2b0@mail.gmail.com>
Hi Samuel,
this remains a contriversial issue. However, since I made the change,
I have not received any concrete reports of problems - so I guess it
is working pretty well the way it is now.
Case closed - until the next bug report :-)
- Carsten
On Jan 22, 2010, at 5:50 PM, Samuel Wales wrote:
> I'm not so sure about this patch.
>
> Are you sure this will work with sorting headlines? Swallowed
> headlines occur if end of narrowed region is at eol. What about other
> operations, including user-written commands? Can we be sure that they
> will not to swallowed headlines?
>
> IMO the behavior described as a bug by the OP is correct -- the user
> should insert a newline after xyz (or org could detect that and insert
> a newline depending on mode-require-final-newline or
> require-final-newline).
>
> I think opinions might vary on this.
>
> --
> Q: How many CDC "scientists" does it take to change a lightbulb?
> A: "You only think it's dark." [CDC has denied a deadly disease for
> 25 years]
> ==========
> Retrovirus: http://www.wpinstitute.org/xmrv/index.html
- Carsten
next prev parent reply other threads:[~2010-02-01 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 11:13 [PATCH] org-narrow-to-subtree: prevent prepending text to the next headline while narrowed Jan Böcker
2010-01-22 10:30 ` Carsten Dominik
2010-01-22 16:50 ` Samuel Wales
2010-02-01 8:11 ` Carsten Dominik [this message]
2010-02-01 17:26 ` Samuel Wales
2010-02-02 6:17 ` Carsten Dominik
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=47EB340A-1D49-44F3-8293-BFAA47532B5E@gmail.com \
--to=carsten.dominik@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).