Kaushal writes:
Hi all, Hi Bastien,
> I don't know the outshine and outorg code in and out. But I wouldn't
> mind keeping it maintained with the pull requests I get.
>
> That said, adding Thorsten Jolitz to this discussion.
> @Thorsten Would you mind making me (
> https://github.com/tj64/outshi
I don't know the outshine and outorg code in and out. But I wouldn't mind
keeping it maintained with the pull requests I get.
That said, adding Thorsten Jolitz to this discussion.
@Thorsten Would you mind making me (
https://github.com/tj64/outshine/pull/46 ) a temporary maintainer of your
outshin
On 8/19/15, Andreas Leha wrote:
> Thank you for your patch! It seems as it breaks global visibility
> cycling, though.
Sorry about that, I really messed up there. Kaushal's patch should
work better, as long as there is at least one valid heading in the
file (if I try running it on an entirely em
Hi Pip,
Pip Cet writes:
> Hi,
> can you confirm the issue only appears when the first line of the
> buffer isn't an outline heading? I think it's easy enough to fix then,
> and if you like you might want to try the patch I've attached.
>
> It's bugged me for a while that `org-back-to-heading' et
Hi Kaushal,
Kaushal writes:
> I had submitted a pull request to solve this issue on that author's outshine
> package page a couple of months back but as Andreas noted, the author hasn't
> been able to maintain this stuff
> due to personal reasons.
>
> You can fix this issue by manually making c
Hi Kaushal,
thanks for sharing your solution.
Kaushal writes:
> You can fix this issue by manually making changes in your copy of
> outshine as per this PR: https://github.com/tj64/outshine/pull/46/
> files
>
> I use outshine daily and I needed to fix only outshine.el. Probably
> outorg.el need
Hi,
can you confirm the issue only appears when the first line of the
buffer isn't an outline heading? I think it's easy enough to fix then,
and if you like you might want to try the patch I've attached.
It's bugged me for a while that `org-back-to-heading' et al throw
errors when they're used bef
I had submitted a pull request to solve this issue on that author's
outshine package page a couple of months back but as Andreas noted, the
author hasn't been able to maintain this stuff due to personal reasons.
You can fix this issue by manually making changes in your copy of outshine
as per this
Hi Bastien,
Bastien writes:
> Hi Andreas,
>
> Andreas Leha writes:
>
>> For quite some time now, I have to disable outshine/outorg [1] as it
>> does give me "Before first heading" (complete backtrace [2]) whenever I
>> open an org file followed by more issues actually using org mode.
>
> Copying
Hi Andreas,
Andreas Leha writes:
> For quite some time now, I have to disable outshine/outorg [1] as it
> does give me "Before first heading" (complete backtrace [2]) whenever I
> open an org file followed by more issues actually using org mode.
Copying Thorsten as the author of outshine.el, ho
Hi John,
Thanks for the confirmation!
Andreas
John Kitchin writes:
> I can only confirm I have had the same issue for a while. For me it is
> mostly when I press shift-tab. regular tab works fine for cycling.
>
> The problem seems to arise from the point moving to the beginning of the
> buffer
I can only confirm I have had the same issue for a while. For me it is
mostly when I press shift-tab. regular tab works fine for cycling.
The problem seems to arise from the point moving to the beginning of the
buffer when outline-back-to-heading is called, which raises that
error. I don't have ti
Hi all,
For quite some time now, I have to disable outshine/outorg [1] as it
does give me "Before first heading" (complete backtrace [2]) whenever I
open an org file followed by more issues actually using org mode.
I can even reproduce this with emacs -Q and a minimal configuration [3].
My syste
13 matches
Mail list logo
