emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Putting the value of page-delimiter in some outline regexps?
Date: Thu, 03 Sep 2020 11:09:31 +0200	[thread overview]
Message-ID: <87wo1bw7jo.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877dtcakrb.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 01 Sep 2020 21:02:48 -0700")


Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I've been trying to find a way to cordon off the bottom of my Org files,
> to create an area for file-local variables and "LocalWords" and what
> have you that Org doesn't consider part of the file's final heading.
> The usual Emacs thing to do seems to be using the value of
> page-delimiter to demarcate the end of content, and the beginning of
> meta data. I stuck that into the value of `org-outline-regexp', and also
> hard-coded it into the "true heading" branch of `org-end-of-subtree'.
> Over the past day this has worked fine for interactive use, and some
> automatic Org-based tools. But I'm not so naive as to think that
> catastrophic breakage couldn't be right around the corner as a result of
> this!
> Anyway, I wanted to see if anyone else had tried this, or had any ideas
> about it.

I think Org already puts some care into preserving file-local variables
at the end of the buffer, e.g., when moving around headlines. Maybe the
issues you're encountering can be fixed the same way.

Adding page delimiter in `org-outline-regexp' is clearly not subtle
enough in any case, as it would affect every headline, not only the last
one in the buffer.

Nicolas Goaziou

  reply	other threads:[~2020-09-03  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  4:02 Putting the value of page-delimiter in some outline regexps? Eric Abrahamsen
2020-09-03  9:09 ` Nicolas Goaziou [this message]
2020-09-03 16:43   ` Eric Abrahamsen

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:

  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=87wo1bw7jo.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \


* 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


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).