On Tue, Aug 15, 2006 at 01:52:29AM +0200, Axel Liljencrantz wrote:
> [ fish_title ] the information is in the documentation.

indeed it is, i guess i need to read through that again. sorry.
it doesn't mention how to disable it though.


> The point of doing e.g. delete-or-exit as a generic shellscript
> functions is to keep as much as possible outside of the shell proper.

yes, i realize that, and i generally support that goal.
it is one of the things that make fish appealing.

when i am asking for a change, i am not trying to get you to change your
goals. that would be counterproductive. your design goals are what make
fish interresting. i am just trying to work out the things that get in
my way as quickly as possible so that i can go on focusing on my work
with fish doing its job to improve my productivity. 


> I consider the performance of delete-or-exit a bug, but I am not sure
> how to solve the it.

well, one argument would be that sometimes one needs to make exceptions
to the rule.


things to consider:
the redraw code currently (in 1.20.0) wipes the whole line before
rewriting it. maybe instead just jump to the beginning and overwrite
without wiping. that would save the flicker for one, and make the thing
more bearable.

also:
all of this does not explain why in screen the redraw is slower by
several magnitudes. this must be a problem with the interpretation of
screens terminal capabilitis or something like that, because in a normal
xterm or a console, it is much faster.

lastly: 
i looked at the help for bind,
it does not say how to remove a keybinding. is that possible?


> Not using a shellscript, as you suggest, is
> definitely a simple and viable solution. Trouble is, if fish ever
> become popular, I would hope that people start writing their own
> keyboard shortcuts, and those would _have_ to be done as shellscripts,
> so it would simply mean pushing the problem to the future.

yes and no. consider how likely it is that any of these will be run
repeatedly like ctrl-d. using something builtin to delete a key simply
is a standard action that makes sense to be built in, just like
backspace, left/right arrows, and other editing in general.

the only thing special is the ability to use ctrl-d for logout on an
empty line. as much as i like that feature, i'd prefer the ability to
simply disable the keybinding alltogether, and have ctrl-d function as a
regular editing key, if that is the price for avoiding a functioncall on
every keypress. (frankly i don't actually need ctrl-d for logout,
because thanks to screen i rarely log out of shells anyways)

especially since due to the slow redraw using keyrepeat for multiple
deletes is not possible, because you can not control when to stop. you
need to stop way earlier than it seems from the progres of the drawn
deletion because if you keep it up to long you may accidently delete the
whole line and log out. since that is dangerous, the result will be that
i will probably end up not using ctrl-d at all, which means the whole
feature is for nothing.

greetings, martin.
-- 
cooperative communication with sTeam      -     caudium, pike, roxen and unix
offering: programming, training and administration   -  anywhere in the world
--
pike programmer   travelling and working in europe             open-steam.org
unix system-      bahai.or.at                        iaeste.(tuwien.ac|or).at
administrator     (caudium|gotpike).org                          is.schon.org
Martin Bähr       http://www.iaeste.or.at/~mbaehr/

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to