[EMAIL PROTECTED]:offset:length} problem with non-blank IFS
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2
uname output: Linux fly 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
GNU/Linux
Machine Type: i486-pc-linux-gnu
Bash Version: 3.1
Patch Level: 17
Release Status: release
Description:
When IFS does not contain the blank character, var="([EMAIL PROTECTED])"
works fine, but var="([EMAIL PROTECTED]:offset:length})" does not (it creates
a single-element array).
Repeat-By:
IFS=$'\n'
a=(A B C D)
b=("[EMAIL PROTECTED]")
echo "[EMAIL PROTECTED]", "[EMAIL PROTECTED]" # 4, A B C D -- OK
b=("[EMAIL PROTECTED]:2}")
echo "[EMAIL PROTECTED]", "[EMAIL PROTECTED]" # 1, C D -- bug, should be 2, C D
Sub-arrays do not work with non-blank IFS
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib
-g -O2
uname output: Linux fly 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007
i686 GNU/Linux
Machine Type: i486-pc-linux-gnu
Bash Version: 3.1
Patch Level: 17
Release Status: release
Description:
If the IFS does not contain a blank, copying an array using
("[EMAIL PROTECTED]") works, but creating a sub-array using
("[EMAIL PROTECTED]:offset:length}") does not work.
Repeat-By:
IFS=$'\n'
a=(A B C D)
b=("[EMAIL PROTECTED]")
echo "[EMAIL PROTECTED]", "[EMAIL PROTECTED]" # 4, A B C D -- OK
b=("[EMAIL PROTECTED]:2}")
echo "[EMAIL PROTECTED]", "[EMAIL PROTECTED]" # 1, C D -- bug, should be 2, C D
Re: ESC . vs. ^R, ^P again
C> "\M-.":"\M->\M-_" Thanks but that doesn't work. $ : 1 $ : 2 $ : 3 $ : 4 $ I want now typing ^R 2 ^E M-. to put a 4 at the end of the line but the above macro does not.
Re: ESC . vs. ^R, ^P again
[EMAIL PROTECTED] wrote: > C> "\M-.":"\M->\M-_" > Thanks but that doesn't work. > $ : 1 > $ : 2 > $ : 3 > $ : 4 > $ > I want now typing ^R 2 ^E M-. to put a 4 at the end of the line but > the above macro does not. Try bind '"\e.":"\e>\e_"' That worked for me when I used it, since I use ESC as the meta-prefix. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: ESC . vs. ^R, ^P again
$ bind '"\e.":"\e>\e_"' $ : 1 $ : 2 $ : 3 $ : 4 $ >> I want now typing ^R 2 ^E M-. to put a 4 at the end of the line... ...and not wipe out the 2, which is what the above bind did. BASH_VERSION='3.1.17(1)-release'
Re: ESC . vs. ^R, ^P again
[EMAIL PROTECTED] wrote: > $ bind '"\e.":"\e>\e_"' > $ : 1 > $ : 2 > $ : 3 > $ : 4 > $ >>> I want now typing ^R 2 ^E M-. to put a 4 at the end of the line... > ...and not wipe out the 2, which is what the above bind did. OK, you're not going to be able to do that, since you're moving away from the line containing the `2'. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
bug kde kubuntu v7.10
Bonjour, de France : Après installation de Kubuntu, puis téléchargement et installation de 79 mises à jour , puis install de ClamAV et Firestarter , blocage de ADEPT. Kmail sous root seulement avec impossibilité d'ouvrir Kontact et donc de configurer Kmail. J'ai désinstallé Adept puis réinstallé Adept avec le terminal. OK j'ai modifél es permissions du dossier et sous-dossiers Kmail avec le terminal . OK tout semble rentré dans l'ordre ( je n'ai pas eu ce problème avec Ubuntu 7.10 ) horiane (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1235720512 (LWP 14962)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xe410 in __kernel_vsyscall () #7 0xb65e1875 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb65e3201 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb67ed6e0 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #10 0xb67eaf65 in ?? () from /usr/lib/libstdc++.so.6 #11 0xb67eafa2 in std::terminate () from /usr/lib/libstdc++.so.6 #12 0xb67eb0ca in __cxa_throw () from /usr/lib/libstdc++.so.6 #13 0x0812b916 in ?? () #14 0x0812be8a in ?? () #15 0x0812bee8 in ?? () #16 0x0812c735 in ?? () #17 0x0812a22d in ?? () #18 0x08114379 in ?? () #19 0x080951ed in ?? () #20 0x0807378d in ?? () #21 0x0807408e in ?? () #22 0xb6e31893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #23 0xb71bd8ec in QSignal::signal () from /usr/lib/libqt-mt.so.3 #24 0xb6e51842 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #25 0xb6e59258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #26 0xb6dc8af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #27 0xb6dca91f in QApplication::notify () from /usr/lib/libqt-mt.so.3 #28 0xb758eca2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #29 0xb6d5b209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #30 0xb6dbb53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #31 0xb6d6fd49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #32 0xb6de31ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #33 0xb6de2fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #34 0xb6dca699 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #35 0x0806f75e in ?? () #36 0xb65cd050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #37 0x0806f401 in ?? ()
Re: bug kde kubuntu v7.10
Bonjour, Cependant ce mail semble assez hors sujet sur cette liste, adresse toi plutôt à une liste concernant kubuntu, ou envoie un e-mail au maintainer d'adept pour kubuntu. Pierre. On Jan 7, 2008 11:12 PM, sibelius <[EMAIL PROTECTED]> wrote: > Bonjour, > de France : > > Après installation de Kubuntu, puis téléchargement et installation de > 79 mises à jour , puis install de ClamAV et Firestarter , blocage de ADEPT. > > Kmail sous root seulement avec impossibilité d'ouvrir Kontact et donc de > configurer Kmail. > > J'ai désinstallé Adept puis réinstallé Adept avec le terminal. OK > j'ai modifél es permissions du dossier et sous-dossiers Kmail avec le > terminal . OK > > tout semble rentré dans l'ordre ( je n'ai pas eu ce problème avec Ubuntu > 7.10 ) > > horiane >
