Hi Ian, > - I changed 'functions -e vi_mode_user' to 'functions -q' - I assume > that is what you meant. Sure. Funny typo.
> The idea here being to distinguish between functions/variables that we > expect a user to access (prefixed with vi_mode_) vs. internal only > functions (prefixed with __vi_mode_). What is your take on this > matter? I never saw this documented. But I agree with you. Usually I prefix functions which are not to be run manually. > I'd certainly appreciate any further feedback you have :) Sure I will have. Working in vi mode is like a breath of fresh air (: By the way, are you going to implement also: ^ - first non-space character j/k - to go up/down when editing multiline? When I start new fish and try to use undo, fish inserts the copy of current commandline instead of the right part of the commandline and prints the number of characters before the cursor. After that undo works ok. regards, Maxim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
