-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable Indentation #90
Comments
Use haskell-simple-indent? Though you shouldn't have TAB insert literal tab characters; whilst the Haskell spec allows for it (with a tab character being the width of 8 spaces), most Haskellers agree on using spaces rather than tabs (and Cabal disallows literal tab characters in .cabal files). |
Yes, you can disable haskell-mode's indentation behavior with: ; Haskell {{{
; adopted from http://sequence.complete.org/node/365
(load-library "haskell-site-file")
(add-to-list 'auto-mode-alist '("\\.hs\\'" . haskell-mode))
(remove-hook 'haskell-mode-hook 'turn-on-haskell-indent)
; 4-space tabs
(add-hook 'haskell-mode-hook
(lambda ()
(setq tab-width 4)
(setq indent-tabs-mode t)
)
) This version makes each literal TAB character become 4 spaces wide. |
@ivan-m haskell-simple-indent does more than just inserting tabs. |
The fix mentioned in #90 (comment) did not work for Emacs 24.5.1 and haskell-mode 20160117.1345. The default hook does not have The following alternative worked for me -- it explicitly disables the
|
Hi, I've tried everything listed here but cannot get haskell-indentation-mode to turn off by default. Any other ideas? |
|
@gracjan I'm afraid that doesn't work |
Too bad that the fix I mentioned does not work any more; I have since moved on to my own minor mode called "kakapo-mode" (it's on MELPA) that handles indentation for me, so I cannot really comment how/why my fix from 3 years ago (yikes!) doesn't work any more. |
Hi,
Is there anyway you can disable the haskell-mode indentation, so why you hit TAB it inserts a tab characters, no spaces, no aligning with previous line?
The text was updated successfully, but these errors were encountered: