On Do, 2009-06-18 at 16:14 -0700, Jindan Zhou wrote:
> I am a bash beginner, just started to build a script that does:
>
> 1. Check if a BBS type site has any new posts, the new thread URL pattern is
> http://www.example.com/bbsviewer.php?trd_id=123456
>
> 2. If 1 is true, go into that URL, find
Am Montag, den 19.01.2009, 10:14 -0800 schrieb Alex Reed:
> Should the globstar (**) syntax allow for partial parameter matching
> (i.e. **.c to find all *.c files in the current directory and its sub-
> directories)?
>
> Currently this can be implemented like this:
> for i in **; do if [[ ${i} =~
Am Mittwoch, den 26.11.2008, 09:51 +0800 schrieb [EMAIL PROTECTED]:
> There are many times one has not planned ahead, and forgets the &:
> $ emacs -nw important.txt #then after a half an hour of editing:
> ^Z
> [1]+ Stopped emacs -nw important.txt
> $ compact_disk_burner_GUI_applic
> Sebastian Kapfer wrote:
>
>> I'm not quite getting the changes in bash's handling of escape
>> sequences.
>
> I can't reproduce your results:
[...]
> I suspect that you have echo defined as a function or alias, or
> something in $PROMPT_COMMAND or $
Hi Chet, hi bug-bash readers,
I'm not quite getting the changes in bash's handling of escape
sequences.
[EMAIL PROTECTED](~)> echo '\a'
'\a
Ouch? This is not related to escape sequence handling:
[EMAIL PROTECTED](~)> echo -E '\a'
'\a
[EMAIL PROTECTED](~)> echo -e '\a'
'
And yet, it is:
[EM
Hello dear bash-bug readers,
I'm quite sure I have found a micro-bug in the bash which should take
about two lines of code to fix -- if you know where to put them. I
tried to locate the problem myself, but the innards of bash traps remain
a mystery to me. Anyway, the description is here:
https
