Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

2015-04-12 Thread Rasmus
Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Rasmus ras...@gmx.us writes:

 Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Eventually, we could introduce a `org-return-hook' where an user could
 add, e.g.,

   (lambda () (when (org-at-heading-p) (org-end-of-meta-data) (insert
   \n)))

 Opinions?

 +1.

 I'd also like a hook on C-RET.

 Actually, a hook isn't even needed if you use `advice-add'.

There's also org-metareturn-hook.

I had a patch a while ago adding support for M-RET on keywords.  This
could be pushed together with a documentation on how to use it with
add-function (is nadvice.el too new for us to assume when writing
documentation?) or the mentioned hook.

—Rasmus

-- 
However beautiful the theory, you should occasionally look at the evidence




Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

2015-04-12 Thread Nicolas Goaziou
Rasmus ras...@gmx.us writes:

 Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Eventually, we could introduce a `org-return-hook' where an user could
 add, e.g.,

   (lambda () (when (org-at-heading-p) (org-end-of-meta-data) (insert
   \n)))

 Opinions?

 +1.

 I'd also like a hook on C-RET.

Actually, a hook isn't even needed if you use `advice-add'.


Regards,



Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

2015-04-10 Thread Rasmus
Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Eventually, we could introduce a `org-return-hook' where an user could
 add, e.g.,

   (lambda () (when (org-at-heading-p) (org-end-of-meta-data) (insert
   \n)))

 Opinions?

+1.

I'd also like a hook on C-RET.


-- 
Not everything that goes around comes back around, you know




Re: [O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

2015-04-09 Thread Marcin Borkowski

On 2015-04-09, at 18:16, Subhan Michael Tindall subh...@familycareinc.org 
wrote:

 Summary: [ENTER] on a headline line should move point to the next valid line 
 for entering general text in order to preserve correct drawer syntax

+1

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



[O] [Feature Request] [ENTER] or [C-Alt ENTER] while on headline skip over drawers automatically

2015-04-09 Thread Subhan Michael Tindall
I use drawers a lot, some of which are set up by hooks when I'm entering 
headlines (most notably TODO keywords)
Given the new syntax that requires no text between drawers  headlines (if I'm 
recalling that correctly), I think it would be very usefull to have either 
[ENTER] (bound to org-return)(C-Alt ENTER is an alternate keybinding 
possibility) move point to start of line FOLLOWING any drawers, DEADLINE, or 
SCHEDULE lines, like this:

,** TODO this is a new headline[ENTER]
,point is now here, potentially breaking syntax
,:PROPERTIES:
,:MyProps: value
,:END:

,** TODO this is a new headline[ENTER]
,point is now here, potentially breaking syntax
,:PROPERTIES:
,:MyProps: value
,:END:
,point should may be here, maintaining syntax

Complication:
,** TODO this is a new headline[ENTER]
,:PROPERTIES:
,:MyProps: value
,:END:
,Is this text allowed here under new drawers syntax?
,:TIMELOGS:
,  CLOCK: [2015-04-08 Wed 08:05]--[2015-04-08 Wed 09:18] =  1:13
,:END:
,point should may be here, maintaining syntax

In above scenario, if drawers are allowed to be separated by text, [ENTER] 
should move point to following first drawer


Summary: [ENTER] on a headline line should move point to the next valid line 
for entering general text in order to preserve correct drawer syntax



This message is intended for the sole use of the individual and entity to which 
it is addressed and may contain information that is privileged, confidential 
and exempt from disclosure under applicable law. If you are not the intended 
addressee, nor authorized to receive for the intended addressee, you are hereby 
notified that you may not use, copy, disclose or distribute to anyone the 
message or any information contained in the message. If you have received this 
message in error, please immediately advise the sender by reply email and 
delete the message.  Thank you.