[Feature suggestion] (related to what I described in the last post of this thread):<div><br></div><div>Keep configuration options for an org file in a separate file. Could be:</div><div> * nameoftheorgfile.conf</div><div><br>
</div><div>I know it seems awkward, but I think it&#39;d be nice if we could keep org file configurations outside of the org file, of course, as an optional feature. Now, this wouldn&#39;t be complicated to implement, I&#39;m sure, and I could even try to hack it as part of some much needed elisp exercise. </div>
<div><br></div><div>Would that make sense?</div><div><br></div><div>Cheers,</div><div><br></div><div>Marcelo.</div><div><br><br><div class="gmail_quote">On Thu, Jul 7, 2011 at 10:51 AM, Marcelo de Moraes Serpa <span dir="ltr">&lt;<a href="mailto:celoserpa@gmail.com">celoserpa@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It&#39;s obvious, but here&#39;s the snippet to promote the headline for your convenience:<div><br></div><div><div><br>
</div><div>(defun ngz-move-headline-up ()</div><div>  &quot;Move current headline to the top of the tree&quot;</div><div class="im">
<div>  (interactive)</div><div>  (unless (org-at-heading-p) (error &quot;Not at an headline&quot;))</div></div><div>  (save-excursion (while (ignore-errors (org-move-subtree-up)))))</div><div><br></div><div><br></div><div>
The only minor issue I have now is with my org file conf section. It&#39;s supposed to be the last item in the file, but when I send the item to the bottom, it starts pilling up as I add more. </div>
<div><br></div><div>It would be nice if we could setup a special tag for the conf section of the org file, i.e:</div><div><br></div><div>* conf  :HIDDEN:</div><div>#+STARTUP: overview</div><div>...</div><div><br></div><div>

HIDDEN items would be hidden unless show-hidden-items toggles. Does that make sense?</div><div><br></div><div>Cheers,</div><div></div><div>Marcelo.</div><div><div></div><div class="h5"><br><div class="gmail_quote">On Mon, Jul 4, 2011 at 10:27 PM, Marcelo de Moraes Serpa <span dir="ltr">&lt;<a href="mailto:celoserpa@gmail.com" target="_blank">celoserpa@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I definitely need to get my head around elisp. Thank you very much.<div><div></div><div><br><br><div class="gmail_quote">

On Sun, Jul 3, 2011 at 4:39 AM, Nicolas Goaziou <span dir="ltr">&lt;<a href="mailto:n.goaziou@gmail.com" target="_blank">n.goaziou@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hello,<br>
<br>
Marcelo de Moraes Serpa &lt;<a href="mailto:celoserpa@gmail.com" target="_blank">celoserpa@gmail.com</a>&gt; writes:<br>
<br>
</div><div>&gt; Nicolas, the function works quite well!  Thanks. Just one last request: Is<br>
&gt; it possible to not follow the item until the bottom? The issue is that, once<br>
&gt; running it and when the item is sent to the bottom of the file, the pointer<br>
&gt; is also put there and the buffer scrolls down with it.<br>
<br>
<br>
</div>Sure, it&#39;s simple as packing it into a (save-excursion ...)<br>
<br>
#+begin_src emacs-lisp<br>
<div>(defun ngz-move-headline-at-bottom ()<br>
  &quot;Move current headline to the last position in the same tree&quot;<br>
  (interactive)<br>
  (unless (org-at-heading-p) (error &quot;Not at an headline&quot;))<br>
</div>  (save-excursion (while (ignore-errors (org-move-subtree-down)))))<br>
<div><div></div><div>#+end_src<br>
<br>
Regards,<br>
<br>
--<br>
Nicolas Goaziou<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div>