Skip to content
This repository was archived by the owner on Apr 1, 2020. It is now read-only.

Conversation

akinsho
Copy link
Member

@akinsho akinsho commented Jul 16, 2018

@CrossR following our discussion a little while ago on discord I've tweaked the indent lines so they don't render a guide for the first level of indentation and the last resulting in:

screen shot 2018-07-16 at 23 32 07

Not sure if the image conveys the change correctly but the aim was to have indents render more in line with the way that sublime or vscode renders them as they seem not to render the first and the deepest level of indentation per line

@codecov
Copy link

codecov bot commented Jul 16, 2018

Codecov Report

Merging #2433 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2433   +/-   ##
=======================================
  Coverage   38.28%   38.28%           
=======================================
  Files         300      300           
  Lines       12539    12539           
  Branches     1651     1651           
=======================================
  Hits         4801     4801           
  Misses       7483     7483           
  Partials      255      255

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cdd2224...4713fe9. Read the comment docs.

Copy link
Member

@CrossR CrossR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a quick test, looks great! The lines seem to be the same as in VSCode now for me. (Actually from a second check....VSCode does have one for column 0. Though I'm less sure why that is useful? Unless I guess for files with a single class in so almost everything is indented)

One question though(which if needs action we can do in a separate PR!), is there a reason we have a list of allowed file-types for this? I think perhaps it was something to do with comment style, though I think that might not be needed now. I've tested this with LaTeX code as well with no issues, so wasn't sure.

@akinsho
Copy link
Member Author

akinsho commented Jul 17, 2018

@CrossR thanks for the review re. the 0 column tbh I was thinking that that would have to be configurable at some point as I can very easily see it being raised as an issue down the line since that behaviour isn't going to be universally expected I think users will probably want the option of choosing.

Re. the file types I started off working off of how vim-indent-guides works and it gives a user the option to select per filetype tbh that list can probably be greatly expanded although I think its still very useful to be able to select where you want them to show as for example you might not want them in markdown (I know I wouldn't) or some other file for some other reason, without an option a user is stuck either turning them on or off with no more granular control

@akinsho akinsho merged commit a335ce4 into onivim:master Jul 17, 2018
@akinsho akinsho deleted the feature/omit-initial-deep-indents branch July 17, 2018 07:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants