Skip to content
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

Flycheck unnecessary line marks #2234

Closed
xged opened this issue Jul 5, 2015 · 6 comments
Closed

Flycheck unnecessary line marks #2234

xged opened this issue Jul 5, 2015 · 6 comments

Comments

@xged
Copy link

xged commented Jul 5, 2015

Flycheck line marks (dots at the left side) are unnecessary and distracting at least to my eyes. Lower underscores are enough IMO. Couple that with difficulty to configure Flycheck (casual) warnings and absence of #2134 you usually get an ugly looking buffer.

@syl20bnr
Copy link
Owner

syl20bnr commented Jul 9, 2015

I propose to improve the flycheck fringe indicator support in spacemacs with a layer variable syntax-checking-fringe-indicators taking 3 possible values nil, default and dot.

@ghost
Copy link

ghost commented Jul 10, 2015

I was thinking of looking into this for another reason: in bzg-big-fringe-mode, the fringe is widened so the flycheck marks cover ~25% of the screen.

Anyways, this does not look too hard to achieve; all the neccessary changes are just in spacemacs/contrib/syntax-checking/packages.el, I guess.

Does dot mean that only the dot should show? I imagine just setting the values fringe-bitmap and fringe-face to nil should remove the flycheck fringe completely.

@ghost
Copy link

ghost commented Jul 10, 2015

After playing around it seems as trivial as I outflined above both to achieve dot and nil.

@swsnr
Copy link
Contributor

swsnr commented Oct 26, 2015

@xged Set flycheck-indication-mode to nil to prevent Flycheck from creating fringe indicators. See Reporting results in the Flycheck manual for more information.

@TheBB
Copy link
Collaborator

TheBB commented Oct 26, 2015

That seems to close this issue. :-)

@TheBB TheBB closed this as completed Oct 26, 2015
@swsnr
Copy link
Contributor

swsnr commented Oct 26, 2015

@endrebak I mean no offense, but please do not guess. Please read the manual: Flycheck already provides an option for this purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants