@alexandrudima in the end I am passing a Range to the editor with start line number and start column (https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/quickopen/browser/gotoLineHandler.ts#L98). Are you saying that this API talks about characters and not columns?

@bpasero I haven't seen a screenshot, but apparently there is somewhere some UI string the widget shows that mentions "column". That UI string should mention "character" instead of "column".

@mgerner Can you please include a screenshot.

@alexandrudima it is this one:

So when I pass a startColumn to the editor it will actually put it at the character position I give it?

@bpasero Please change your nls string such that it shows:
"Go to line 45 and character 34"

I fixed the one in goto line quick open but I still see more places where we talk about column when it should maybe be character?

Bouncing back to you to decide if those are valid. I think they are in markers land mainly.

Thank you. The editor configurations talk about the correct columns. i.e. a ruler at column 4 will be rendered possibly after character 1 if that character is a tab (and tabs are configured to be equal 4). Same is for wrappingColumn.

giving to @dbaeumer and @sandy081 to think about their use-cases.

Makes sense to me to use character consistently.

To me too.

Changed it for markers panel.

Fixed except for the cases where the doc was referring to properties. Since these properties are API and I didn't want to break the API I left them with column.

gotoLine.ts has 3 occurrences of 'column'. argv.ts has 3 related to 'go to line'. Reopening.

As discussed assigning to you.