From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Is it generally better practice to specify local variables at the first line for Org files?
Date: Wed, 05 Oct 2016 15:50:15 +0200 [thread overview]
Message-ID: <84fuoaucq0.fsf@gmail.com> (raw)
In-Reply-To: 87shsbnnsh.fsf@nicolasgoaziou.fr
> Local variables at the end of the buffer are, indeed, a bit painful to
> handle under Org. Org Footnote handles them reasonably well, I think,
> but that's about it.
>
> I would welcome a general solution to this, as long as it does not
> impede speed of most basic Org commands.
>
> Do you have an idea about it?
I think it's difficult to find a good way to keep something (e.g. the
local variables) at the bottom of an org file. Up to now the bottommost
tree contains the rest of the file. There is no bottom. A certain
bottom would somehow disturb the tree structure as it is, AFAICS.
For the implementation you need to check for many operations if the
bottom is involved.
The header of an org file on the other side is a save place with regards
to operations in the tree. Personally, if Emacs would allow to place
the local variables block at the beginning of a file, I'd do that.
> Maybe a start would be to have a dedicated
> Org version of `outline-next-heading' that moves before local variables
> when it reaches the end of the buffer.
This sounds like a good idea to me. This step would keep the local
variables a bit saver, AFAICS. I can imagine that the implementation of
this idea (and more ideas like this) could yield an almost pain free
local variable experience for org files.
Ciao,
--
Marco
prev parent reply other threads:[~2016-10-05 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 20:36 Is it generally better practice to specify local variables at the first line for Org files? Jorge Morais Neto
2016-10-05 6:40 ` Marco Wahl
2016-10-05 9:33 ` Nicolas Goaziou
2016-10-05 11:35 ` John Kitchin
2016-10-05 13:50 ` Marco Wahl [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=84fuoaucq0.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--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 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.