Fix text sent as input to rufo

[13k]

The text being sent to rufo is incorrectly formed with lines joined by the actual characters \n, instead of an actual single-char newline.

This fixes #17 and fixes #18.

[13k]

It still breaks with code containing \, like:

var2 = \
  case var1
  end

Removing the \ escaping works, but I'm not sure if will break on other scenarios.

[13k]

I've added a commit to remove the escaping, since shellescape should already escape everything needed when passing as a shell argument to echo.

[splattael]

@13k Thank again!

I have trouble to make @blasterpal's code from #17 to work.

This code still give an error - even with your patch:

Code

module JIRA
  class Client
    def find!(*args)
      begin
        self.find(*args)
      rescue JIRA::HTTPError
        puts "Object not found"
        nil
      end
    end
  end
end

Result

@13k Any ideas?

[13k]

I think this is related to #19, which I fixed again. I've merged #19 and this one and that snippet formats correctly for me.

[13k]

[lucerion]

Could you, please, recheck #12?

[13k]

@lucerion It looks correct:

My reasoning here is, essentially, that the correct approach is to always send the unmodified input to rufo, emulating cat <file> | rufo. The command should receive \ chars as \ chars, newlines as actual newlines, and so on.

I tried to research a way to avoid echoing the contents and piping to the program's stdin, but looks like vim doesn't support it. The examples I found use python to spawn a child process and directly emit the text to the child's stdin. Despite it being common for modern vim plugins to require +python, I'm not sure if the added complexity/dependencies are worth the benefits here.