From: Kaushal <kaushal.modi@gmail.com>
To: Pip Cet <pipcet@gmail.com>,
Andreas Leha <andreas.leha@med.uni-goettingen.de>,
tjolitz@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: outorg issue
Date: Wed, 19 Aug 2015 19:08:46 +0000 [thread overview]
Message-ID: <CAFyQvY1ufHM_vqXSDagZvXMRuB_D-nvxm7dbHCm4x+roJ0+-tw@mail.gmail.com> (raw)
In-Reply-To: <CAOqdjBfcKYbPkLW+iKvkM15FSqB6+e9yKfgHoCQ7vaDfQgXRhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
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
outshine package on github. Or do you have anyone in mind you would take
this up? Thanks.
On Wed, Aug 19, 2015 at 2:26 PM Pip Cet <pipcet@gmail.com> wrote:
> On 8/19/15, Andreas Leha <andreas.leha@med.uni-goettingen.de> 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 empty org file, I can still
> produce the error message with M-x outline-hide-sublevels).
>
> I'd also like to second Bastien's suggestion, it would be excellent to
> see this useful extension maintained again.
>
>
[-- Attachment #2: Type: text/html, Size: 1482 bytes --]
next prev parent reply other threads:[~2015-08-19 19:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 21:51 outorg issue Andreas Leha
2015-08-13 14:30 ` John Kitchin
2015-08-13 14:37 ` Andreas Leha
2015-08-18 16:28 ` Bastien
2015-08-18 19:53 ` Andreas Leha
2015-08-18 20:11 ` Kaushal
2015-08-18 22:26 ` Bastien
2015-08-19 7:53 ` Andreas Leha
2015-08-18 20:35 ` Pip Cet
2015-08-19 8:10 ` Andreas Leha
2015-08-19 14:23 ` Pip Cet
2015-08-19 19:08 ` Kaushal [this message]
2015-09-08 20:09 ` Thorsten Jolitz
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY1ufHM_vqXSDagZvXMRuB_D-nvxm7dbHCm4x+roJ0+-tw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
--cc=pipcet@gmail.com \
--cc=tjolitz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).