emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Marco Wahl <marcowahlsoft@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Is it generally better practice to specify local variables at the first line for Org files?
Date: Wed, 5 Oct 2016 07:35:32 -0400	[thread overview]
Message-ID: <CAJ51EToujw_t+u3rQhyHV3z_GCe5QWjYzd_+9XkzZgNmP8AnYQ@mail.gmail.com> (raw)
In-Reply-To: <87shsbnnsh.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]

I usually just put a headline at the end, titled "end" or "local
variables", etc.., and tagged noexport,


John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Wed, Oct 5, 2016 at 5:33 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Marco Wahl <marcowahlsoft@gmail.com> writes:
>
> > I have the same issue.  Currently I try to have an extra eye on the
> > bottommost org tree.  I also use an extra tag to mark the org tree which
> > should be bottommost.  I also use the idea stated in
> > http://www.mail-archive.com/emacs-orgmode@gnu.org/msg106940.html which
> sorts
> > the wanted org tree to the bottom when sorting.
> >
> > For me this works reasonably well.
> >
> > When you put the local variables to the top of the file you are on the
> > save side AFAICT.
> >
> > I try to avoid too much information in the first line.  I prefer to have
> > the variables at the bottom.
>
> 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? 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.
>
> Regards,
>
> --
> Nicolas Goaziou
>
>

[-- Attachment #2: Type: text/html, Size: 2602 bytes --]

  reply	other threads:[~2016-10-05 11:35 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 [this message]
2016-10-05 13:50     ` Marco Wahl

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=CAJ51EToujw_t+u3rQhyHV3z_GCe5QWjYzd_+9XkzZgNmP8AnYQ@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@gmail.com \
    /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).