Searching is very difficult as nv_directories full path is too long and uses whole window width about notational-fzf-vim

[alok]

Hmm, let me look at this more over the week. I'll get back to you on that.

You don't want to replace the path (in most cases) since bits of the path can be relevant to your search, like ~/wiki/note.md and ~/notes/note.md. Then the path helps to disambiguate them.

[alok]

@borderomm, I asked @junegunn about this and I'm waiting for a reply. Otherwise, this looks like it'll involve a bunch of annoying fiddling.

As a (bad) quick fix, you could symlink your notes directory to something like ~/notes. If it doesn't work, let me know and I can at least fix that quickly.

[alok]

The latest version has g:nv_show_preview and g:nv_show_filepath options to allow you to hide the preview window and filenames. Try let g:nv_show_filepath = 0 to hide the filenames completely.

Let me know if that helped.

[borderomm]

Alok,

Thanks for the changes. Unfortunately none of them work for me:

1. I already have a symlink for the dir, indeed i have ~/notes as you suggested. However, when showing the path, it shows the full path, which is very long and covers the files

2. let g:nv_show_filepath doesn't really work for me as expected. Covering the path completely is very confusing as it also hides the filename. IF it would show the filename, maybe that would work but, as it is now, it's confusing to me.

[alok]

That's odd, it doesn't show the full path when I tested it. It just showed the symlink. Can you try that again and report back? Maybe you have both the full path and the symlink listed in g:nv_directories.

[borderomm]

This is my .vimrc

""" configuration for notational-fzf-vim
let g:nv_directories = ['~/notes']
let g:nv_default_extension = '.md'
let g:nv_main_directory = g:nv_directories[0] " default is first in directory list
let g:nv_show_filepath = 1
let g:nv_show_preview = 1
let g:nv_preview_width = 72
let g:nv_wrap_preview_text = 0

And this is what i see:

/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md
/usr/local/company_name/home/user/notes/reminder_notes.md

> ls -l notes
lrwxrwxrwx 1 user user 56 Jan 29 11:58 notes -> /usr/local/company_name/home/user/GoogleDrive/#MyNotes

NOTE: I modified username and company_name

[alok]

Can you try the latest version of this plugin and see if that helps?

On Sun, Jan 29, 2017 at 4:32 AM borderomm ***@***.***> wrote: This is my .vimrc """ configuration for notational-fzf-vim let g:nv_directories = ['~/notes'] let g:nv_default_extension = '.md' let g:nv_main_directory = g:nv_directories[0] " default is first in directory list let g:nv_show_filepath = 1 let g:nv_show_preview = 1 let g:nv_preview_width = 72 let g:nv_wrap_preview_text = 0 And this is what i see: /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md /usr/local/company_name/home/user/notes/reminder_notes.md > ls -l notes lrwxrwxrwx 1 user user 56 Jan 29 11:58 notes -> /usr/local/company_name/home/user/GoogleDrive/#MyNotes NOTE: I modified username and company_name — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH8KTDVMgyl90MEoDXAkAjx0uvMxZrA8ks5rXIbsgaJpZM4LrmLm> .

-- - Alok

[borderomm]

I just confirmed I'm in the last commit

silent! let g:plugs['notational-fzf-vim'].commit = 'e3f9dfb' 

Without changing anything in my configuration, results seems exactly the same as 8 hours ago.

[alok]

Ok. I was wondering if you maybe had ag aliased to ag -f, which follows symlinks. Can you try running the search manually in the terminal with ag and see if it prints the filenames?

[borderomm]

Mmm,
I haven't touched anything related to ag.

I went inside a folder and ran a simple ag search. Output below:

> ag txt resources
resources/app/README.md
28:  ([MIT License](https://github.com/mootools/mootools-core/blob/master/Source/license.txt))
30:  ([MIT License](https://github.com/jacomyal/sigma.js/blob/master/LICENSE.txt))
36:  ([License](https://github.com/github/octicons/blob/master/LICENSE.txt))

> pwd
/usr/local/company_name/home/user/Downloads/app

I load fzf in zsh as below:

.zshrc

[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh
# don't want to exclude hidden files plus ignore googledrive folder and .git
export FZF_DEFAULT_COMMAND='ag --hidden --ignore .git -g ""'
# To apply the command to CTRL-T as well
export FZF_CTRL_T_COMMAND="$FZF_DEFAULT_COMMAND"

and in .vimrc

let $FZF_DEFAULT_COMMAND= 'ag --hidden --ignore .git -g ""'

[alok]

In any case, I added g:use_short_pathnames just now. See if it works for you.

Scratch that, it doesn't work for anyone since FZF takes the text directly, and it's been modified, so the pathname isn't valid.

[junegunn]

I think I mentioned this before, but you can feed the original path along with the shortened string to fzf, and hide the long one inside the finder using --with-nth option.

echo "/very/long/path:/v/l/p: foobar" | fzf -d: --with-nth 2..

[alok]

@junegunn Thanks for the tip. @borderomm Check the latest commit.

[borderomm]

@alok Thanks for adding a patch.
I added the script in a directory called in $PATH. However I still see the same behavior.

How am I supposed to call the script and/or configure vim to do it?
Thanks

[alok]

Is the script executable?

On Wed, Feb 15, 2017 at 1:17 PM borderomm ***@***.***> wrote: @alok <https://github.com/Alok> Thanks for adding a patch. I added the script in a directory called in $PATH. However I still see the same behavior. How am I supposed to call the script and/or configure vim to do it? Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH8KTLBxf8RCrGuH9Ggm4NI1Jt--8SMlks5rc2tQgaJpZM4LrmLm> .

-- - Alok

[borderomm]

Is the script executable?

Yes

 > ls -l bin/shorten_path_for_notational_fzf.py
-rwxr-x--- 1 user group 37356 Feb 15 22:11 bin/shorten_path_for_notational_fzf.py

[alok]

Well, if it's in your $PATH, and it's not working, then I have no idea what's wrong.

[alok]

Do you have python 3 installed?

[borderomm]

I do but, I was using python2.7 by default.
I added an alias in my .zshrc to point to python3.4
Still no luck.

David

[alok]

Don't do that, just pull the latest commit. If this doesn't work, then you're probably on your own. I really can't see why your computer seems to act differently.

[borderomm]

@alok I just tried in my linux machine at home and I have the same behavior. Nothing changes after having the script in my $PATH.
I'm not sure what I'm supposed to see.
With our without the python script I see the same path names.

Both machines are completely different (ubuntu vs debian), non-related at all and have the same outcome.

How can I know if the script is running?

[alok]

You'll have to send a screenshot or short clip of usage. Try running vim with a different vimrc.

On Thu, Feb 16, 2017 at 2:27 PM borderomm ***@***.***> wrote: @alok <https://github.com/Alok> I just tried in my linux machine at home and I have the same behavior. Nothing changes after having the script in my $PATH. I'm not sure what I'm supposed to see. With our without the python script I see the same path names. Both machines are completely different (ubuntu vs debian), non-related at all and have the same outcome. How can I know if the script is running? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH8KTGfm78rda60JoSj_zNgBmJ7hih6Mks5rdM1egaJpZM4LrmLm> .

-- - Alok