[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
1 Oct 2004 01:55:30 -0000
Configuration Information [Automatically generated, do not change]:
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -g -O2
uname output: Linux Ezekiel 2.6.6 #1 Tue May 25 17:18:41 EDT 2004 i686 unknown
Machine Type: i686-pc-linux-gnu
Bash Version: 3.0
Patch Level: 0
Release Status: release
Ok. Dunno if it's a feature but to me (and I guess I'm not alone) it's
really an annoyance. I just upgraded bash from bash-2.05b-i486-3 to
bash-3.0-i486-1 (on slackware packages yeah and I compiled the sources and it's
the same thing).
It's hard to explain and I'm not a professionnal in bash terms and even
less in english so forgive my ... oh well you will understand :)
When you hit the up arrow in (from now I will call bash-2.05b as 205
and bash-3.0 as 300) 205 like 10 times and you didn't write anything in the
first time, you can hit the down arrow 10 times and you will get your shell
(cursor?) empty, like at the begining. In 300, if your command prompt is
empty, and you hit one time the up arrow, you can hit the down arrow and you
prompt will become again empty. But if you (dare :) hit the up arrow two times
and more, it will stay with the last command you did (the command that appears
when you first hit the up arrow).
In fact I just need a tip to get the behavior of 205 back. If it's not
possible I will simply downgrade to 205. Because to me it's REALLY annoying.
Sry for the caps, but PLEASE WRITE ME BACK TO address@hidden Write me : fuck
you, you will have to contact address@hidden to solve this, I don't care. BUT
WRITE ME SOMETHING PLEASE :)
And BTW, I really think bash is the best shell out there. If I didn't think
so, I would simply change my shell instead of writing this :)
Keep up the good work guys!
|[Prev in Thread]
||[Next in Thread]|