From: Alexandros Prekates <aprekates@posteo.net>
To: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: [BUG] phantom newlines while moving headings [9.6-pre ( @ /home/chomwitt/.config/emacs/elpa/org-9.6pre0.20221110.85807/)]
Date: Mon, 14 Nov 2022 00:00:08 +0000 [thread overview]
Message-ID: <20221114020008.03f40695@enous> (raw)
In-Reply-To: <87pmdu9qd0.fsf@localhost>
On Fri, 11 Nov 2022 02:28:27 +0000
Ihor Radchenko <yantar92@posteo.net> wrote:
Indeed testing the latest version my previous example didnt create
ghost newlines . But with a small diffefence that example that i
post below creates a ghost newline.
> chomwitt@posteo.eu writes:
>
> > It follows a possible org chunk that reproduce the phantom newlines
> > that are created while trying to move a headline from a state where
> > there are no newlines between the headers.
>
> Could you please provide more information?
> Which headline should I move to reproduce the problem?
>
> I tried to move headlines randomly in the attached file (your example)
> but I do not see any newlines created.
>
Creaete 1st level headlines -------
* a$
* b$
* c$
* d$
@
Move point after headline c ------
* a$
* b$
* c@$
* d$
Press enter ---------------------
* a$
* b$
* c$
@$
* d$
Creating subheading -----
* a$
* b$
* c$
** c1@$
* d$
Press enter -----
* a$
* b$
* c$
** c1$
@$
* d$
Fold c heading -----
* a$
* b$
* @c...$
* d$
move c heading all the way down -----
* a$
* b$
* d$
* @c...$
<---- a yellow rectancle appears!
move c heading up -----
* a$
* b$
* @c...$
<--- ghost newline
* d$
move c heading again up -----
* a$
* @c...$
* b$
* d$
prev parent reply other threads:[~2022-11-14 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 0:16 [BUG] phantom newlines while moving headings [9.6-pre ( @ /home/chomwitt/.config/emacs/elpa/org-9.6pre0.20221110.85807/)] chomwitt
2022-11-11 2:28 ` Ihor Radchenko
2022-11-11 9:22 ` Alexandros Prekates
2022-11-12 13:07 ` Ihor Radchenko
2022-11-14 0:00 ` Alexandros Prekates [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221114020008.03f40695@enous \
--to=aprekates@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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.