Telescope broken on Windows 10 after latest update

[rkakkar123]

Description

After the latest update, Telescope is adding a ^M at the end of every file and hence opening a blank file

Neovim version

NVIM v0.5.0

Operating system and version

Microsoft Windows 10 Enterprise

Steps to reproduce

1. nvim -nu minimal.lua
2. ...

Expected behavior

No response

Actual behavior

As described above

Minimal config

vim.cmd [[set runtimepath=$VIMRUNTIME]]
vim.cmd [[set packpath=/tmp/nvim/site]]
local package_root = '/tmp/nvim/site/pack'
local install_path = package_root .. '/packer/start/packer.nvim'
local function load_plugins()
  require('packer').startup {
    {
      'wbthomason/packer.nvim',
      {
        'nvim-telescope/telescope.nvim',
        requires = {
          'nvim-lua/plenary.nvim',
          { 'nvim-telescope/telescope-fzf-native.nvim', run = 'make' },
        },
      },
      -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. '/plugin/packer_compiled.lua',
      display = { non_interactive = true },
    },
  }
end
_G.load_config = function()
  require('telescope').setup()
  require('telescope').load_extension('fzf')
  -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
end
if vim.fn.isdirectory(install_path) == 0 then
  print("Installing Telescope and dependencies.")
  vim.fn.system { 'git', 'clone', '--depth=1', 'https://github.com/wbthomason/packer.nvim', install_path }
end
load_plugins()
require('packer').sync()
vim.cmd [[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]]

[dhruvmanila]

You have not filled out the Steps to reproduce section. It would make the maintainers life really easy if you could reproduce using the minimal config they have provided adding in all the necessary information.

[Conni2461]

I am pretty sure this is caused by this part

telescope.nvim/lua/telescope/_.lua

Lines 168 to 178 in 364d795

	local start = index
	index = string.find(text, "\n", index, true)
	if index == nil then
	text = get_next_text(string.sub(text, start or 1))
	return next_value()
	end
	index = index + 1
	return string.sub(text, start or 1, index - 2)

Its a new implementation of the previous job implementation and i think we need to remove \r\n for windows and only \n for everyone else.

I am thinking about a good realization of this but maybe on new we pick either this function of a different one based on OS

[tjdevries]

Does this fix it? #1169 I don't have an easy way to test at the moment

[Remoat]

Fixes it for me at least.

[tjdevries]

OK, I've merged. Please let me know if any of you sees something going wrong here.