From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@altern.org>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Move to item to the bottom
Date: Wed, 20 Jul 2011 11:05:05 -0500 [thread overview]
Message-ID: <CACHMzOGZdEN=dMXY6FuKg5uiy5HbisPwpfNiPfi9uZaFzcg9oA@mail.gmail.com> (raw)
In-Reply-To: <CACHMzOFjPw3ZVPMyZO+qXHjnNkvwfs70rZa3-UpThcTK=5oOKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2568 bytes --]
[Feature suggestion] (related to what I described in the last post of this
thread):
Keep configuration options for an org file in a separate file. Could be:
* nameoftheorgfile.conf
I know it seems awkward, but I think it'd be nice if we could keep org file
configurations outside of the org file, of course, as an optional feature.
Now, this wouldn't be complicated to implement, I'm sure, and I could even
try to hack it as part of some much needed elisp exercise.
Would that make sense?
Cheers,
Marcelo.
On Thu, Jul 7, 2011 at 10:51 AM, Marcelo de Moraes Serpa <
celoserpa@gmail.com> wrote:
> It's obvious, but here's the snippet to promote the headline for your
> convenience:
>
>
> (defun ngz-move-headline-up ()
> "Move current headline to the top of the tree"
> (interactive)
> (unless (org-at-heading-p) (error "Not at an headline"))
> (save-excursion (while (ignore-errors (org-move-subtree-up)))))
>
>
> The only minor issue I have now is with my org file conf section. It'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.
>
> It would be nice if we could setup a special tag for the conf section of
> the org file, i.e:
>
> * conf :HIDDEN:
> #+STARTUP: overview
> ...
>
> HIDDEN items would be hidden unless show-hidden-items toggles. Does that
> make sense?
>
> Cheers,
>
> Marcelo.
>
> On Mon, Jul 4, 2011 at 10:27 PM, Marcelo de Moraes Serpa <
> celoserpa@gmail.com> wrote:
>
>> I definitely need to get my head around elisp. Thank you very much.
>>
>>
>> On Sun, Jul 3, 2011 at 4:39 AM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
>>
>>> Hello,
>>>
>>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>>
>>> > Nicolas, the function works quite well! Thanks. Just one last request:
>>> Is
>>> > it possible to not follow the item until the bottom? The issue is that,
>>> once
>>> > running it and when the item is sent to the bottom of the file, the
>>> pointer
>>> > is also put there and the buffer scrolls down with it.
>>>
>>>
>>> Sure, it's simple as packing it into a (save-excursion ...)
>>>
>>> #+begin_src emacs-lisp
>>> (defun ngz-move-headline-at-bottom ()
>>> "Move current headline to the last position in the same tree"
>>> (interactive)
>>> (unless (org-at-heading-p) (error "Not at an headline"))
>>> (save-excursion (while (ignore-errors (org-move-subtree-down)))))
>>> #+end_src
>>>
>>> Regards,
>>>
>>> --
>>> Nicolas Goaziou
>>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 3896 bytes --]
next prev parent reply other threads:[~2011-07-20 16:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 16:13 Move to item to the bottom Marcelo de Moraes Serpa
2011-06-30 18:55 ` Nicolas Goaziou
2011-07-01 6:35 ` Nicolas Goaziou
2011-07-01 8:57 ` Bastien
2011-07-01 9:10 ` Nicolas Goaziou
2011-07-01 9:32 ` Bastien
2011-07-02 19:25 ` Nicolas Goaziou
2011-07-03 2:02 ` Marcelo de Moraes Serpa
2011-07-03 9:39 ` Nicolas Goaziou
2011-07-05 3:27 ` Marcelo de Moraes Serpa
2011-07-07 15:51 ` Marcelo de Moraes Serpa
2011-07-20 16:05 ` Marcelo de Moraes Serpa [this message]
2011-07-27 11:22 ` Bastien
2011-07-27 23:12 ` Marcelo de Moraes Serpa
2011-07-01 9:34 ` Carsten Dominik
2011-07-01 9:46 ` Bastien
2011-07-01 10:25 ` Carsten Dominik
2011-07-01 16:07 ` Bastien
2011-07-01 16:59 ` Marcelo de Moraes Serpa
2011-07-01 19:25 ` Nicolas Goaziou
2011-07-01 22:58 ` Marcelo de Moraes Serpa
2011-07-02 8:05 ` Nicolas Goaziou
2011-07-02 9:06 ` Bastien
2011-07-01 10:14 ` Eric S Fraga
2011-07-01 10:27 ` Carsten Dominik
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='CACHMzOGZdEN=dMXY6FuKg5uiy5HbisPwpfNiPfi9uZaFzcg9oA@mail.gmail.com' \
--to=celoserpa@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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 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.