discussion and development of Emacs Snakemake mode
 help / color / mirror / code / Atom feed
From: Kyle Meyer <notifications@github.com>
To: kyleam/snakemake-mode <snakemake-mode@noreply.github.com>
Cc: Kyle Meyer <kyle@kyleam.com>,
	Your activity <your_activity@noreply.github.com>
Subject: Re: indentation problems (#26)
Date: Mon, 12 Feb 2018 03:20:05 +0000 (UTC)	[thread overview]
Message-ID: <kyleam/snakemake-mode/issues/26/364820394@github.com> (raw)
In-Reply-To: <kyleam/snakemake-mode/issues/26@github.com>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

> Since updating to the newest version

Do you happen to recall what version(-ish) you upgraded from?

> Any suggestions on what might be causing this?

Hmm, I'm not having any luck reproducing this (Emacs 25.3, GNU/Linux).
Starting with point in front of "message", TAB indents it four spaces.

You could try debugging `snakemake--calculate-indentation`,
particularly

https://github.com/kyleam/snakemake-mode/blob/6cf6d20db2e5253ce3f86e302651faa28f220aa7/snakemake-mode.el#L258-L269

That should return the value of `snakemake-indent-field-offset` (4 by
default).

> I did upgrade a bunch of things at once, of course, so the cause might be somewhere else.

You could also try testing with emacs -Q, and then just loading
snakemake-mode and its dependencies (dash, magit-popup).

If you have a local clone of the repo, running `make test` would tell
you if the indentation tests (ran with emacs -Q) are passing for you.

What version of Emacs are you using?


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kyleam/snakemake-mode/issues/26#issuecomment-364820394

[-- Attachment #2: Type: text/html, Size: 4117 bytes --]

  reply	other threads:[~2018-02-12  3:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  2:27 indentation problems (#26) Elmar Pruesse
2018-02-12  3:20 ` Kyle Meyer [this message]
2020-04-13 23:52 ` Kyle Meyer

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://git.kyleam.com/snakemake-mode

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=kyleam/snakemake-mode/issues/26/364820394@github.com \
    --to=notifications@github.com \
    --cc=kyle@kyleam.com \
    --cc=reply+0013cd7c3f575cf17f869df0151c609c7e1b0709c78db89f92cf000000011698c9e492a169ce11a87176@reply.github.com \
    --cc=snakemake-mode@noreply.github.com \
    --cc=your_activity@noreply.github.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.kyleam.com/snakemake-mode/

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).