Auto-complete on osx when specifying the DB adds extra spaces #136

Closed
wwood opened this Issue Feb 20, 2015 · 7 comments

Projects

None yet

3 participants

@wwood
Contributor
wwood commented Feb 20, 2015
Database dir not set.

SequenceServer needs to know where your FASTA files or BLAST+ databases are.
Please enter the path to the relevant directory (default: current directory).

Press Ctrl+C to quit.

>>/Users/ben/Downlo

then press tab becomes

/Users/ben/Downloads 

Note the extra space after downloads, even though I intended to specify a subfolder of Downloads.

This is on OSX 10.9.5, Ubuntu did not have this problem

@yeban
Contributor
yeban commented Feb 23, 2015

Could you try this one @wwood? We use readline for autocompletion. The code for this is in bin/sequenceserver.

@wwood
Contributor
wwood commented Feb 24, 2015

Hmm, I'm pretty busy for the next 4 weeks or so, not sure I will have the time. I will try though.

@yeban
Contributor
yeban commented Feb 24, 2015

Ok. It's just that I can't reproduce this issue or I would have taken care of it.

@wwood
Contributor
wwood commented Feb 24, 2015

Sure. This isn't the biggest problem though I'd say.

On 24 February 2015 at 13:44, Anurag Priyam notifications@github.com
wrote:

Ok. It's just that I can't reproduce this issue or I would have taken care
of it.


Reply to this email directly or view it on GitHub
#136 (comment)
.

Ben Woodcroft
http://ecogenomic.org/users/ben-woodcroft http://www.ecogenomic.org/

@yeban yeban added the bug label Mar 19, 2015
@yeban yeban added the bite-sized label Sep 15, 2015
@yannickwurm
Contributor

@wwood is this still an issue?

@wwood
Contributor
wwood commented Jan 29, 2016

Yes, seems so I'm afraid. I just updated all my gems (including seqserv to 1.0.6), and got the same issue. Is this not reproducible by others?

I can also just reproduce with readline itself outside of seqserv using system ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]

Clearly not our fault, seems an issue either with ruby itself or OSX packaging it. What to do? Not really our fault.. I suggest we do nothing.

@yannickwurm
Contributor

Agreed - can you add this as an FAQ?

@yannickwurm yannickwurm closed this Feb 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment