Re: cp command will copy to subdirectory without appending /

2009-10-19 Thread Bob Proulx
Todd Partridge wrote: > The cp command will copy to a subdirectory without an appending / You have reached bug-bash, not bug-coreutils. The 'cp' program is in the GNU Coreutils project and so bug reports for 'cp' should go to bug-coreut...@gnu.org and not to bug-bash. The bug-bash list is for bu

cp command will copy to subdirectory without appending /

2009-10-19 Thread Todd Partridge
The cp command will copy to a subdirectory without an appending / mkdir test test2 touch abc test touch bcd test2 cp -R test2 test ls test test2 abc Since the cp command can also rename I think the proper behavior here for 'cp -R test2 test' would be to error and print that 'Folder already exists

read: error setting terminal attributes: Interrupted system call

2009-10-19 Thread change
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='ba

Small script that sometimes elicits a memory error

2009-10-19 Thread change
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='ba

bug-bash@gnu.org

2009-10-19 Thread Sitaram Chamarty
On Tue, Oct 20, 2009 at 2:22 AM, Bob Proulx wrote: > Certainly yank-last-arg (M-.,M-_) is useful but don't forget about > yank-nth-arg (M-C-y) which yanks the first argument.  Most of the time > that you are doing something like 'edit filename.c &' then you can use > the still quite convenient M-C

Re: Prompt - cursor position - command history display problem

2009-10-19 Thread Chet Ramey
Timothy James Erlenmeyer wrote: > > Configuration Information [Automatically generated, do not > change]: > > Machine: x86_64 > > OS: linux-gnu > > Compiler: gcc > > Compilation > CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' > -DCONF_MACHTYPE='x86_64-unknown-linu

bug-bash@gnu.org

2009-10-19 Thread Bob Proulx
Sitaram Chamarty wrote: > Chet Ramey wrote: > > Sitaram Chamarty wrote: > >> When the previous command was backgrounded (say "gvim > >> filename.c &") and then you try some other command using > >> Alt-., it expands to "&" and not "filename.c". > >> > >> Is this considered a bug? Or correct behavi

Re: another problem with bash PS1 handling

2009-10-19 Thread Chet Ramey
> Whether POSIX applies or not, from a logical standpoint history number > and custom bash escape expansion should be last, after parameter > expansion and command substitution because doing it first breaks > command substitution (see my earlier post) or using variables in a > prompt (a='!'; PS1='

Re: another problem with bash PS1 handling

2009-10-19 Thread Nils
On 19 Okt., 02:56, Chet Ramey wrote: > Second, there are a couple of problems with Posix and this construct. > You can make an argument that Posix doesn't apply, since it only > calls for parameter expansion on the value of PS1, and that does not > include command substitution.  Even if it does ap

bug-bash@gnu.org

2009-10-19 Thread Sitaram Chamarty
On Mon, Oct 19, 2009 at 6:08 AM, Chet Ramey wrote: > Sitaram Chamarty wrote: >> Hello, >> >> When the previous command was backgrounded (say "gvim >> filename.c &") and then you try some other command using >> Alt-., it expands to "&" and not "filename.c". >> >> Is this considered a bug?  Or corre