emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: Possible bug - shifting headline - hashmark and what	follows is considered part of headline that is shifted
Date: Fri, 23 May 2014 12:23:48 -0400	[thread overview]
Message-ID: <537F7614.3090209@verizon.net> (raw)
In-Reply-To: <87ppj4wlvj.fsf@bzg.ath.cx>

Hi, again, Bastien,
Bastien wrote:
> Hi Charles,
>
> Charles Millar <millarc@verizon.net> writes:
>
>> If I attempt to move headline 2b above 2a (M-up)
>>
>> * 1
>> ** 2a
>> ** 2b
>>
>> #  LocalWords:  XXXXXXXX YYYYYYYY
>>
>> the result is
>>
>> * 1
>> ** 2b
>>
>> #  LocalWords:  XXXXXXXX YYYYYYYYY
>> ** 2a
>
> Yes, #  LocalWords:  XXXXXXXX YYYYYYYYY is part of the ** 2b headline.
>

I now realize that since # LocalWords is considered part of a previous 
headline, any refile to a file that contains # LocalWords (or possibly 
any similar special construct) is placed after # LocalWords.

I would expect that the refile, at the very least, would be placed 
between the last headline and # LocalWords.

Possibly this situation could cause errors would be in exporting.

Best, Charlie

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

  parent reply	other threads:[~2014-05-23 16:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 15:28 Possible bug - shifting headline - hashmark and what follows is considered part of headline that is shifted Charles Millar
2014-05-23 15:33 ` Bastien
2014-05-23 16:00   ` Charles Millar
2014-05-23 16:30     ` Brian van den Broek
2014-05-23 16:23   ` Charles Millar [this message]
2014-05-23 17:27     ` Bastien
2014-05-23 17:51       ` Charles Millar
2014-05-23 19:21         ` Bastien
2014-05-23 20:13           ` Charles Millar
2014-05-24  7:41           ` Sebastien Vauban
2014-05-24  7:59             ` Bastien
2014-05-24 13:19               ` Charles Millar
2014-05-24 14:54                 ` Bastien

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=537F7614.3090209@verizon.net \
    --to=millarc@verizon.net \
    --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).