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 13:51:02 -0400	[thread overview]
Message-ID: <537F8A86.6060206@verizon.net> (raw)
In-Reply-To: <87lhtsv21c.fsf@bzg.ath.cx>

Bastien and all,

Bastien wrote:
> Hi Charles,
>
> There will be no problem with comments at export time since comments
> are not exported.

Thanks for the pointer concerning that # is comment in all exporting 
situations.

>
> The way it works now is deeply into the ADN of Org, *everything*
> within a subtree moves with this subtree, and nothing is *not* part
> of a subtree (except text before the first headline.)
>

I am only now teaching myself emacs lisp and common lisp, mostly so I 
can at least try to understand the code. Based on Brian van den Broeck's 
message and my observation following his message, is it possible, 
actually is it worth the time and effort, for Org Mode only, to make "# 
LocalWords:" into a "#+ LocalWords:" into a top level buffer setting, 
and furthermore any additions would be placed into the top level setting 
and not at the end of the buffer?

Charlie

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

  reply	other threads:[~2014-05-23 17:51 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
2014-05-23 17:27     ` Bastien
2014-05-23 17:51       ` Charles Millar [this message]
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=537F8A86.6060206@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).