On 3/30/2014 10:55 PM, Bastien wrote:
Hi Brady,
Brady Trainor writes:
For `org-insert-heading' (M-RET), I wanted the following action on empty
headlines:
"* " |--> "* \n* ", rather than "*\n* ".
I'm not sure I understand this, can you make it more explicit?
Thanks!
I mean that if I us
Hi Brady,
Brady Trainor writes:
> For `org-insert-heading' (M-RET), I wanted the following action on empty
> headlines:
>
> "* " |--> "* \n* ", rather than "*\n* ".
I'm not sure I understand this, can you make it more explicit?
Thanks!
--
Bastien
Bastien gnu.org> writes:
> ---does the Org version that comes from the maint branch
> still needs a fix? If so, can you describe the problem
> again?
I did test the `maint` branch today. The behavior was not ideal for my
funny use-case.
For `org-insert-heading' (M-RET), I wanted the follow
Hi Brady,
Brady Trainor writes:
> Thanks again!
you're welcome---does the Org version that comes from the maint
branch still needs a fix? If so, can you describe the problem
again?
Here is how to use Org from maint
~$ git clone git://orgmode.org/org-mode.git
~$ git checkout maint
~$ make aut
Bastien gnu.org> writes:
>
> Hi Brady,
>
> Brady Trainor uw.edu> writes:
> > (when respect-content
> > (and (looking-at "[ \t]+") (replace-match ""))
> > I thought to try substituting "[ \t]+" with "[\t]+", and byte compiled the
> > file. But this did not solve.
> What you w
Hi Brady,
Brady Trainor writes:
> So, I started trying to read the org.el file. I thought I had found
> the "offending" line, (my L7614,) finding
>
> ;; If we insert after content, move there and clean up whitespace
> (when respect-content
> (org-end-of-subtree nil t)
I am revisiting a workflow that I have a hard time letting go of, despite
it's unintended use in Org-mode.
That is, I like to visually separate groups of headlines by simply having a
couple of empty headlines. This allows more nimble and simple use-case of
manually sorting buildup of headlin
