aditya siram writes:
> I've included new versions of both patches with most of the changes you
> suggested. I guess you'll apply the longer one when you've been notified by
> the FSF?
>
Once you receive your confirmation from the FSF please let Bastien or
Carsten know, and they'll add you to the
aditya siram writes:
> Thanks for your feedback and your work on org-babel!
>
I'm happy you're finding it useful.
>
> Oops, the maintain-point was a hold-over and isn't actually used in the
> code. I'll remove it.
>
> I will incorporate your suggestions.
>
> However, regarding the cascading if
I've included new versions of both patches with most of the changes you
suggested. I guess you'll apply the longer one when you've been notified by
the FSF?
Is this a one-time deal that covers future patches or do I have to do this
with every patch that's over 15 lines long?
Thanks!
-deech
On S
Thanks for your feedback and your work on org-babel!
Oops, the maintain-point was a hold-over and isn't actually used in the
code. I'll remove it.
I will incorporate your suggestions.
However, regarding the cascading if statements, how would I use `cond` when
the predicates are `and`ed and when
aditya siram writes:
> Attached is a patch that fixes a bug with jumping from source block back to
> the Org file. The problem is that the current detangling behavior does not
> take the :padlline flag into account. This stopped.
>
> Hopefully this is helpful to others ...
> -deech
>
Hi deech,
Attached is a patch that fixes a bug with jumping from source block back to
the Org file. The problem is that the current detangling behavior does not
take the :padlline flag into account. This stopped.
Hopefully this is helpful to others ...
-deech
src_block_jump_fix.patch
Description: Binary d
