You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #2154: ArgumentError: invalid byte sequence in UTF-8

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter Marius Gedminas
Tags no tags

Description

When I press \t in my home directory, I see this:

GoToFile [-]                                                                                                                          [0:0]    [buf 2]
>>  
Error detected while processing function <SNR>34_CommandTShowFileFinder:                                                                    
line    2:
ArgumentError: invalid byte sequence in UTF-8
Press ENTER or type command to continue

I think this may mean that there's a file somewhere under ~ with a non-UTF-8 filename. I've no idea what it might be.

Could command-t display it by showing <XX>, or U+FFFD REPLACEMENT CHARACTER, or a question mark? Instead of emitting that error, I mean.

Comments

  1. Marius Gedminas

    Note that this breaks command-t completely: the choice list is empty, and if I press a key like <Down>, I get a new error:

    Error detected while processing function CommandTSelectNext: line 1: NoMethodError: undefined method length' for nil:NilClass

  2. Greg Hurrell

    Out of interest, which version of Ruby us Vim linked against?

    You can check with:

    :ruby puts RUBY_VERSION
  3. anonymous

    I met this error too. I guess it's a encoding problem cause I have a Japanese character in my path name.

  4. anonymous

    I can confirm this problem. My Vim is linked against ruby 2.1.2

  5. Greg Hurrell

    I can fix this if someone can give me a minimal repro case for it (could be a specific filename, or a zip with a bad filename in it etc).

  6. Greg Hurrell

    I'm about to merge the proposed workaround from https://github.com/wincent/command-t/pull/113 so I'm going to mark this one as closed.

  7. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu