Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#9738 closed bug (invalid)

Terminal: extreme lag when trying to tab complete a non exsiting string

Reported by: rossi Owned by: nobody
Priority: normal Milestone: R1
Component: Applications/Command Line Tools Version: R1/alpha4.1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Terminal exhibits a very long lag before returning to normal, when tab completition is used and accidentially the string cannot be completed, e.g. because there is no file with the given starting string.

Change History (8)

comment:1 Changed 6 years ago by anevilyak

Component: Applications/TerminalApplications/Command Line Tools
Owner: changed from jackburton to nobody

That's actually up to bash, not Terminal.

comment:2 Changed 6 years ago by anevilyak

I might further note, I've seen much the same happen on Linux/FreeBSD depending on what completion rules bash had installed.

comment:3 Changed 6 years ago by axeld

I've actually only seen this in Linux and Windows so far. In any case, it doesn't sound like a bug within Haiku. So I would suggest closing this as invalid, and if you really care, file it with bash instead.

comment:4 Changed 6 years ago by anevilyak

Resolution: invalid
Status: newclosed

comment:5 Changed 6 years ago by axeld

rossi: BTW have you bash completion installed?

comment:6 Changed 6 years ago by rossi

Hi Axel,

I don't think so, as I didn't install any extras related to bash, at least not consciously. I mostly replicated for my current builds the optional packages, which were also part of the Alpha4.1 release.

Also the issue doesn't seem to happen with the Alpha release, only on the current revisions.

Anyhow, as it doesn't seem to be an Haiku issue, I'll just live with it and try to avoid to complete non-existing terms ;-)

Thanks, Rossi

comment:7 Changed 6 years ago by siarzhuk

what is the way to reproduce it? BTW, I have observed such lags using zsh trying to complete git add/commit commands that can be obviously explained but not with bash.

comment:8 Changed 6 years ago by rossi

steps to reproduce (on fresh install, current revisions):

  • enter terminal
  • start typing a directory path with at least the initial directory existing
  • finish with the beginning letters of a non-existing directory
  • hit tab to complete
  • lag (app. 1-2 minutes, in which terminal/bash doesn't do anything

add. if you close terminal (window close button), the sub processes don't quit properly, it is nescessary to actually kill terminal

Note: See TracTickets for help on using tickets.