vi editing mode: shift-x not working properly (char deleted but not yanked)
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 uname output: Linux silmaril 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 GNU/Linux Machine Type: i386-pc-linux-gnu Bash Version: 2.05b Patch Level: 0 Release Status: release Description: In the vi editing mode of the bash the command "X" (shift-x) is not working as expected. Although the character in front of the cursor is deleted it is not yanked. Repeat-By: 1. Change to vi editing mode: 'set -o vi' 2. Type "adsf". 3. Change to command mode by pressing ESC. 4. Move to the "s" and press 'X' (shift-x) to delete the "d". 5. Now press 'p' to insert the deleted "d" after the "s". -> The "d" is not inserted. (If you use 'dh' instead of 'X' it works.) Best regards Beat Wieland ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
WellsFargo Banking
Title: Untitled Document Dear WellsFargo Bank Client, To provide our customers the most effective and secure online access to their accounts, we are continually upgrading our online services. As we add new features and enhancements to our service, there are certain browsers versions which will not support these system upgrades. As many customers already know, Microsoft Internet Explorer has significant 'holes' or vulnerabilities that virus creators can easily take advantage of . In order to further protect your account, we have introduced some new important security standards and browsers requirements. WellsFargo Bank security systems require that you test your browser now to see if meets the requirements to WellsFargo Online Banking. Pleas follow this link in order to verify security update installation. https://www.onlinebanking.wellsfargo.com This security update will be effective immediately . In the meantime some of the Internet Banking services may not be available. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Expansion from home directory
I apologize if this is old hat (I could not find it in the FAQ), but I encounter the annoying problem that if I use path completion starting with my home directory, i.e., ~haselbac/cfd/... then bash puts a space after each directory name, i.e., if there was a directory called 'calcs' below 'cfd', bash would put ~haselbac/cfd/calcs_ where the '_' denotes an empty space. This is annoying because I have to backspace several times when I work through deep directory hierarchies. If I put the complete path to my home directory, i.e., /Users/haselbac/cfd/... then this does not happen. Any explanations/ideas/fixes/etc? Thanks Andreas ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Expansion from home directory
Hi Chet, I'm afraid I'm not quite sure what you mean. I assume it's installed because partial names are being completed. Also, I forgot to mention that I've encountered this problem on both RH Linux 9.0 and OS 10.3. Andreas Chet Ramey wrote: I apologize if this is old hat (I could not find it in the FAQ), but I encounter the annoying problem that if I use path completion starting with my home directory, i.e., ~haselbac/cfd/... Do you have completions installed? Bash doesn't do this by default. Chet -- Andreas Haselbacher Voice: (217) 333-8683 Center for Simulation of Advanced Rockets Fax: (217) 333-1910 University of Illinois at Urbana-Champaign Email: [EMAIL PROTECTED] 2253 Digital Computer Laboratory, MC 278 1304 West Springfield Avenue Urbana, IL 61801 ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Expansion from home directory
> I apologize if this is old hat (I could not find it in the FAQ), but I > encounter the annoying problem that if I use path completion starting > with my home directory, i.e., > > ~haselbac/cfd/... Do you have completions installed? Bash doesn't do this by default. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Expansion from home directory
Andreas Haselbacher wrote: > Hi Chet, > > I'm afraid I'm not quite sure what you mean. I assume it's installed > because partial names are being completed. Also, I forgot to mention > that I've encountered this problem on both RH Linux 9.0 and OS 10.3. Type `complete -p cd'. If there's output, type `complete -r cd' and try the completion again. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Problems delivering your mail
I'm sorry, but we had problems delivering your mail. The errors we encountered appear below. If you have any questions, contact the Cornell Postmaster as <[EMAIL PROTECTED]>. Please include a copy of this message with your correspondence. The following addresses could not be found at all in our Directory. Please make sure you have the correct address. [EMAIL PROTECTED] To help you identify exactly which piece of electronic mail was undeliverable, your original message appears below Received: from cornell.edu ([200.59.230.30]) by soapstone1.mail.cornell.edu (8.12.10/8.12.6) with SMTP id j2ONLRZQ009837 for <[EMAIL PROTECTED]>; Thu, 24 Mar 2005 18:21:28 -0500 (EST) Message-Id: <[EMAIL PROTECTED]> From: bug-bash@gnu.org To: [EMAIL PROTECTED] Subject: Sua saude esta bem? Date: Thu, 24 Mar 2005 20:23:33 -0300 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="68676250" X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.0, Antispam-Data: 2005.3.24.13 --68676250 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit AMA! --68676250 Content-Type: application/x-zip-compressed; name=":(.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=":(.zip" --68676250-- ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Builtin 'read -u fd' does not work with fd other than zero.
Configuration Information [Automatically generated, do not change]: Machine: sparc OS: solaris2.8 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc' -DCONF_OSTYPE='solaris2.8' -DCONF_MACHTYPE='sparc-sun-solaris2.8' -DCONF_VENDOR='sun' -DSHELL -DHAVE_CONFIG_H -I. -I/wamas/tools/haubi/src/toolsbox-4-patches/buildroot/bash/bash-2.05b -I/wamas/tools/haubi/src/toolsbox-4-patches/buildroot/bash/bash-2.05b/include -I/wamas/tools/haubi/src/toolsbox-4-patches/buildroot/bash/bash-2.05b/lib -g -O2 uname output: SunOS sauxch4 5.8 Generic_108528-11 sun4u sparc SUNW,Sun-Fire-280R Machine Type: sparc-sun-solaris2.8 Bash Version: 2.05b Patch Level: 0 Release Status: release Description: When using 'read -u 3' or the like, and the pipe-buf already contains more than one line, the first line is returned, and bytes up to the next multiple of 128 are skipped. This bug quite sure exists in bash-3.0 too. Repeat-By: Send lines to a spawned bash over a pipe with fd!=0 to have more than one line in pipe-buffer when doing the 'read -u'. If you want, you can have a test case with a python program spawning a bash and communicate with it over pipes other than stdin. Fix: diff -ruN bash-2.05b.orig/builtins/read.def bash-2.05b/builtins/read.def --- bash-2.05b.orig/builtins/read.def 2005-03-25 07:53:42.662996304 +0100 +++ bash-2.05b/builtins/read.def2005-03-25 07:55:02.205903944 +0100 @@ -274,7 +274,7 @@ input_is_tty = isatty (fd); if (input_is_tty == 0) #ifndef __CYGWIN__ -input_is_pipe = (lseek (0, 0L, SEEK_CUR) < 0) && (errno == ESPIPE); +input_is_pipe = (lseek (fd, 0L, SEEK_CUR) < 0) && (errno == ESPIPE); #else input_is_pipe = 1; #endif ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
