Re: [Wickedshell-user] Prompt not behaving normally after command

[Grzegorz G. <spe...@op...>]

Hi, Stefan,

I have this behaviour with default bash prompt. After this e-mail, I 
tried to set the prompt to something different based on your 
documentation, but the result is the same.
My default bash prompt in gnome-terminal looks like this: 
'astral@astral-laptop:~$ ' (with space, without the apostrophes), So the 
'>' character is not a part of default prompt. Of course, as I said, 
it's not about some character missing:), but that I can't use 
completions, history etc. until I press some button that produces 
printable character (then both '>' and that character are displayed).

Regards,
Grzegorz
> Hi Grzegorz,
>
> the prompt is usually provided by the underlaying shell. If a command is executed, Wicked Shell 'only' transfers the text output from the underlaying shell to the Widget. Wicked Shell expects the last character(s) sent to be the prompt though i cannot identify the content as being a prompt. Do you use the default Shell (bash) or did you write a custom descriptor via preferences?
>
> - Stefan
>
>
> ----- original Nachricht --------
>
> Betreff: [Wickedshell-user] Prompt not behaving normally after command
> Gesendet: Do, 13. Sep 2007
> Von: Grzegorz Galezowski<spe...@op...>
>
>   
>> Hello,
>>
>> I'd like to report a bug (or not? Anyway, it isn't the way I would 
>> Wicked Shell to act).
>>
>> I didn't check it on Windows, but it occurs on my Linux system running 
>> eclipse 3.3.
>>
>> When I'm in the shell and execute a command like 'ls' (or even pressing 
>> Enter button with bare prompt),
>> after the execution the prompt appears again, but it's not complete. For 
>> example:
>>
>> ----------------------
>> astral@astral-laptop:~/Desktop$ > ls
>> GrzegorzGalezowski - 2007 Internship Ending presentation.ppt
>> Img0009.jpg
>> invite.ics
>> notes.txt~
>> report-thunderbird~
>> rest.pdf
>> astral@astral-laptop:~/Desktop$
>> -------------------
>>
>> As you can see, next time there's no '>' character in the prompt. It 
>> appears after I press some printable character.
>> It's a bit frustrating, because I can't then use my history ('up' key) 
>> to execute previous command straight away.
>> I have to press something printable (like spacebar for example) and then 
>> keys like tab, up etc. begin to work.
>>
>> Best Regards, and keep up the good work,
>> Grzegorz Galezowski
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Wickedshell-user mailing list
>> Wic...@li...
>> https://lists.sourceforge.net/lists/listinfo/wickedshell-user
>>
>>     
>
> --- original Nachricht Ende ----
>
>
>