mhinz / mhinz/vim-tree

Weird character sequence appears if run from ~/.vim folder

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
60
Forks
2
PR merge metrics
No merged PRs in 30d

Description

This does not happen so far in any other folder... If I run ``:Tree`` from ~/.vim folder, then instead of clean box drawing lines, I see the following weird character sequence. This happens even if vim-tree is the only plugin I load, and happens with both vim and neovim.

```
├── UltiSnips/
│  ├── mail.snippets
│  └── tex.snippets
├── after/
│  └── ftplugin/
│  ├── mail.vim
│  ├── qf.vim
│  ├── rust.vim
│  ├── tex.vim
│  └── vimwiki.vim
├── autoload/
│  ├── AnsiEsc.vim
│  ├── plug.vim
│  └── plug.vim.old
├── bundle/
│  ├── autoload/
│  │  └── vimwiki/
│  │  ├── base.vim
```

And here's the screenshot:

![Screen Shot 2021-06-24 at 1 46 07 PM](https://user-images.githubusercontent.com/71736629/123330278-a9bf6900-d4f2-11eb-93a0-b8f9dc0d6549.png)

Relevant information:
```
Vim 8.2 patches 1-2890 ARM64
NeoVim v0.5.0-dev+nightly-356-gb28d458f8 ARM64
macOS BigSur 11.4 ARM64
$TERM xterm-256color
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the :Tree entry point and reproduce the output from ~/.vim in both Vim and Neovim, then compare it with running from another folder. Use the reported macOS, ARM64, terminal, and version details while checking that box-drawing characters render correctly; done means the clean tree output is restored in ~/.vim.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.