fasd backends

Created on 10 Apr 2012  ·  7Comments  ·  Source: clvv/fasd

The documentation for setting fasd backends isn't explicit, but in my tests I'm unable to get it to read viminfo at all.

Setting:
$_FASD_BACKENDS="viminfo" or to
$_FASD_BACKENDS=viminfo

in ~/.fasdrc doesn't seem to parse the file at all. This is confirmed by moving the .fasd file which then seems to wipe all data.

Any advice or pointers for something I should try?

Most helpful comment

please add it to the doc that for using multiple locations we should separate them by space, I was imagining it was by : like in $PATH variable.
_FASD_BACKENDS="native viminfo"

All 7 comments

I think this is a syntax issue. .fasdrc should be a shell script. Variable assignment in posix shell script does not include the leading $ sign.

Assuming you want to use the content in your .viminfo file in addition to what fasd already has, try:

_FASD_BACKENDS="native viminfo"

Sounds good, thanks for the response! Is there any way to tell its successfully importing viminfo data? I open quite a few files from within vim that fasd would otherwise never see. Right now if I just have viminfo as the backend, it still gives no results.

That is weird. Try fasd -tb viminfo. Anything at all? If not also try fasd --backend viminfo. Is there anything special about your setup? Is you .viminfo file in $HOME? Are there lines that start with > in you .viminfo file?

.viminfo is in $HOME. No output from fasd -tb viminfo, here's the output from the other command.

$ fasd --backend viminfo
sed: 1: "/^>/{s@~@/Users/pear@;p}": extra characters at the end of p command

I do have lines starting with > in .viminfo, but github markdown keeps eating the > :D

/usr/local/bin/fasd
20 " 1 16
21 ^ 1 17

The problem is that your sed does not like the command fasd gave. I've pushed a quick fix for you, on branch issue-5.

Which OS are you using? What sed does it come with? I think the code fasd gave to sed is perfectly posix compliant, though I might be wrong.

Yeah I just caught that too. MacOS doesn't like the {'s in sed. Thanks for the quick fix. Alternatively its probably reasonable to recommend users (with Homebrew installed) running into this problem install a non-MacOS sed.

```brew install gnu-sed --default-names

I just did that and everything is happy. Thanks for the help!

please add it to the doc that for using multiple locations we should separate them by space, I was imagining it was by : like in $PATH variable.
_FASD_BACKENDS="native viminfo"

Was this page helpful?
0 / 5 - 0 ratings

Related issues

simendsjo picture simendsjo  ·  6Comments

ixil picture ixil  ·  5Comments

rosshadden picture rosshadden  ·  6Comments

sypl picture sypl  ·  12Comments

rendybjunior picture rendybjunior  ·  14Comments