From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 22 Apr 2016 11:07:55 -0700 From: Endre Bakken Stovner Reply-To: kyleam/snakemake-mode Message-ID: In-Reply-To: References: Subject: Re: hs-special-modes-alist not working (#14) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_571a687b21f72_269e3fcb7da432a01911a"; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: kyleam/snakemake-mode List-Archive: https://github.com/kyleam/snakemake-mode List-Post: List-Unsubscribe: , To: kyleam/snakemake-mode Cc: Kyle Meyer , Comment ----==_mimepart_571a687b21f72_269e3fcb7da432a01911a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks! On Fri, Apr 22, 2016 at 7:57 PM, Kyle Meyer wrote: > > I am guessing it is because I have neither defined an end for my > > block, nor a `forward-sexp-function`. Only the latter is possible, so > > that must probably be done first. > > Thanks for looking into setting up `hs-special-modes-alist`. Your guess > sounds right. > > I was going to suggest you check snakemake-in-rule-or-subworkflow-block-p > to see how rule blocks are recognized. But, revisiting that function, I > think there are at least a couple cases that aren't handled correctly > (rule blocks that are indented under, say, an if statement; the function > relies on no blanks between rule lines even though this is legal > syntax). I should rewrite it, and then the forward-sexp-function should > pretty much fall out of that. > > However, I don't think I'll find time to do that for another week or > two. (In the meantime, I'll probably be pretty unresponsive in general, > aside from merging #13.) > > =E2=80=94 > You are receiving this because you modified the open/close state. > Reply to this email directly or view it on GitHub > > --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kyleam/snakemake-mode/issues/14#issuecomment-213535002= ----==_mimepart_571a687b21f72_269e3fcb7da432a01911a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks!

On Fri, Apr 22, 2016 at 7:57 PM, Kyle Meyer <notifications@github.com>= ;
wrote:

> > I am guessing it is because I have neither defined an end for my<= br> > > block, nor a `forward-sexp-function`. Only the latter is possible= , so
> > that must probably be done first.
>
> Thanks for looking into setting up `hs-special-modes-alist`. Your gues= s
> sounds right.
>
> I was going to suggest you check snakemake-in-rule-or-subworkflow-bloc= k-p
> to see how rule blocks are recognized. But, revisiting that function, = I
> think there are at least a couple cases that aren't handled correc= tly
> (rule blocks that are indented under, say, an if statement; the functi= on
> relies on no blanks between rule lines even though this is legal
> syntax). I should rewrite it, and then the forward-sexp-function shoul= d
> pretty much fall out of that.
>
> However, I don't think I'll find time to do that for another w= eek or
> two. (In the meantime, I'll probably be pretty unresponsive in gen= eral,
> aside from merging #13.)
>
> =E2=80=94
> You are receiving this because you modified the open/close state.
> Reply to this email directly or view it on GitHub
> <https://github.com/kyleam/snakemake-mode/issues/14#issuecomment-21= 3530196>
>

&mda= sh;
You are receiving this because you commented.
Reply to this e= mail directly or view it on GitHub3D""

----==_mimepart_571a687b21f72_269e3fcb7da432a01911a--