fasd backends #5

Closed
pearofducks opened this Issue Apr 10, 2012 · 6 comments

Comments

Projects
None yet
2 participants
@pearofducks

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?

@clvv

This comment has been minimized.

Show comment Hide comment
@clvv

clvv Apr 11, 2012

Owner

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"
Owner

clvv commented Apr 11, 2012

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"
@pearofducks

This comment has been minimized.

Show comment Hide comment
@pearofducks

pearofducks Apr 11, 2012

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.

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.

@clvv

This comment has been minimized.

Show comment Hide comment
@clvv

clvv Apr 11, 2012

Owner

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?

Owner

clvv commented Apr 11, 2012

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?

@pearofducks

This comment has been minimized.

Show comment Hide comment
@pearofducks

pearofducks Apr 11, 2012

.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

.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

clvv pushed a commit that referenced this issue Apr 11, 2012

@clvv

This comment has been minimized.

Show comment Hide comment
@clvv

clvv Apr 11, 2012

Owner

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.

Owner

clvv commented Apr 11, 2012

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.

@pearofducks

This comment has been minimized.

Show comment Hide comment
@pearofducks

pearofducks Apr 11, 2012

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.


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

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.


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment