Re: Wrong Character Encoding

2013-08-12 Thread Chet Ramey
On 8/12/13 1:04 PM, Roman Rakus wrote: > This will probably be fixed in next release. For reference: > http://lists.gnu.org/archive/html/bug-bash/2011-08/msg00214.html Maybe, maybe not. I'm assuming yes because it seems like it is command-not-found output he's seeing, but we can't be sure without

Re: Wrong Character Encoding

2013-08-12 Thread Roman Rakus
This will probably be fixed in next release. For reference: http://lists.gnu.org/archive/html/bug-bash/2011-08/msg00214.html RR On 08/12/2013 03:55 PM, Marcus Manning wrote: I hope it is right so to write my bug report to this address in the given format. If I put a "ä"-character in my termina

Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-12 Thread Chet Ramey
On 8/10/13 12:47 AM, Bob Proulx wrote: > John Vincent wrote: >> I find that if I enter the command: >> echo {1..2000} >> it runs, but afterwards whenever I enter another command I get the error: >> -bash: fork: Cannot allocate memory > > You need to allocate more virtual memory space to your m

Wrong Character Encoding

2013-08-12 Thread Marcus Manning
I hope it is right so to write my bug report to this address in the given format. If I put a "ä"-character in my terminal and press Enter, then I will receive an escape-sequence like this: $'\303\244'. The same result by "ü", "ö", "ß", but other sequences. My /etc/inputrc: # do not bell on

Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-12 Thread Greg Wooledge
On Fri, Aug 09, 2013 at 10:47:21PM -0600, Bob Proulx wrote: > John Vincent wrote: > > echo {1..2000} > > it runs, but afterwards whenever I enter another command I get the error: > > -bash: fork: Cannot allocate memory > > You need to allocate more virtual memory space to your machine. You >