Andreas Schwab wrote:
"Joachim Schmitz" writes:
But prevent others from having the benefit of this protection...
Which is highly questionable.
Well, I deliberatly didn't comment on whether I find it useful or not ;-)
Andreas Schwab wrote:
Chet Ramey writes:
It's a cheap and easy way to protect yourself from `rm *'.
If you put it in gitignore you don't need to clutter up the
repository.
But prevent others from having the benefit of this protection...
Hi Chet
Here's my 2nd batch of fixes to the devel branch, it is mainly about //
comments vs. /* */ ones
diff --git a/lib/readline/colors.c b/lib/readline/colors.c
index 7a271f2..ebf9e42 100644
--- a/lib/readline/colors.c
+++ b/lib/readline/colors.c
@@ -34,17 +34,17 @@
#include
-#include "po
Hi Chet
OK, so I've now switched to the devel branch and found a couple problems,
here's my 1st batch of fixes to them:
ofifo_list = copy_fifo_list (&osize);
^
".../execute_cmd.c", line 701: error(252): argument of type
"volatile int *" is i
> From: Chet Ramey [mailto:chet.ra...@case.edu]
> Sent: Friday, September 14, 2012 8:15 PM
...
> I don't typically patch the examples. The newer code is in the devel
> branch of the git tree on savannah.
Ah, I didn't notice there were branches, thanks.
> From: Chet Ramey [mailto:chet.ra...@case.edu]
> Sent: Friday, September 14, 2012 7:49 PM
> To: Joachim Schmitz
> Cc: Joachim Schmitz; Bug-bash@gnu.org; chet.ra...@case.edu
> Subject: Re: Portability patch: S_IWRITE and S_IEXEC
>
> On 9/14/12 11:37 AM, Joachim Schmitz w
Hi Chet
Here's a portability patch, S_IWRITE and S_IEXEC are obsolete since long and
got replaced by S_IWUSR and S_IXUSR respectivly
diff --git a/examples/loadables/mkdir.c b/examples/loadables/mkdir.c
index f41f171..f5c105e 100644
--- a/examples/loadables/mkdir.c
+++ b/examples/loadables/mkd
Hi Chet
Could you add this? Prevents us from having to remember to
use --without-bash-malloc
diff --git a/configure.in b/configure.in
index d7e0998..af72223 100644
--- a/configure.in
+++ b/configure.in
@@ -87,6 +87,7 @@ sparc-linux*)opt_bash_malloc=no ;;# sparc running
linux; r
*-beo
Petr Sumbera wrote:
Hi,
we are running Bash 3.2.38 on Solaris 10 where asprintf() isn't
available. Thus code in snprintf.c is used.
There is a problem with following command:
bash -c 'printf "x%10.0fx\n" 123'
x000123x
Where correct output should be:
x 123x
It seems that '0' after '
Joachim Schmitz wrote:
From: Mike Frysinger [mailto:vap...@gentoo.org]
Sent: Tuesday, March 27, 2012 5:23 PM
To: bug-bash@gnu.org
Cc: Pierre Gaston; Joachim Schmitz; gnu-bash-...@moderators.isc.org
Subject: Re: UTF-8 regression in bash version 4.2
On Tuesday 27 March 2012 08:08:33 Pierre Gaston
> From: Mike Frysinger [mailto:vap...@gentoo.org]
> Sent: Tuesday, March 27, 2012 5:23 PM
> To: bug-bash@gnu.org
> Cc: Pierre Gaston; Joachim Schmitz; gnu-bash-...@moderators.isc.org
> Subject: Re: UTF-8 regression in bash version 4.2
>
> On Tuesday 27 March 2012 08:08:3
dennis.birkh...@rwth-aachen.de wrote:
>
Bash Version: 4.2
Patch Level: 24
Release Status: release
Interesting, seems the announcements dor patches 21-24 have gotten lost?
bye, Jojo
Chet Ramey wrote:
I spent a little while messing around with git over the past couple of
days, and ended up updating the bash git repository on savannah
(http://git.savannah.gnu.org/cgit/bash.git to browse the sources).
Bash-4.2 patch 20 is the head of the tree, and there's a branch
containing th
Jan Schampera wrote:
On 22.07.2011 18:12, the mad doctor kaeding wrote:
is this a bug?
echo goodbye\ cruel\ world\!
goodbye cruel world!
echo "goodbye cruel world!"
bash: !": event not found
echo "goodbye cruel world\!"
goodbye cruel world\!
No, this is a specific history expansion in
>Eric Blake wrote:
>>Joachim Schmitz writes:
>> Or did something break in forwarding mails to bug-bash to the news group?
>
>Probably during the mail server move, gnu.emacs.help broke as well.
Is there something being done to get it fixed?
Bye, Jojo
Eric Blake wrote:
>On 05/13/2011 04:54 AM, Joachim Schmitz wrote:
>> Hi folks
>>
>> Just found Bash-4.2 patches 9 and 10, strange that they never got
>> announced?
>
>Yes they did:
>
>http://lists.gnu.org/archive/html/bug-bash/2011-05/msg00014.html
>
Hi folks
Just found Bash-4.2 patches 9 and 10, strange that they never got announced?
---
Bye, Jojo
Pierre Gaston wrote:
On Tue, Aug 24, 2010 at 10:25 AM, Joachim Schmitz
wrote:
Chris F.A. Johnson wrote:
On Mon, 23 Aug 2010, Dennis Williamson wrote:
If you're writing a Bash-specific script then it's preferable to
use double square brackets (see
http://mywiki.wooledge.org/B
Edward Peschko wrote:
All,
I've been working lately at upgrading my debugging tools and
procedures, and have come to looking how I can improve debugging
bash.
I know about bash -x , but its terribly annoying because, even though
it shows the evaluated text, there is no explicit way to tie th
Chris F.A. Johnson wrote:
On Mon, 23 Aug 2010, Dennis Williamson wrote:
If you're writing a Bash-specific script then it's preferable to use
double square brackets (see http://mywiki.wooledge.org/BashFAQ/031).
if [[ -f $file ]]
then
do something
fi
I'd avoid non-portable syntax unless
Chet Ramey wrote:
On 5/21/10 1:00 PM, Roman Rakus wrote:
There are patches 6 and 7 available for bash-4.1.
I don't see any announce, are they official? I just want to be sure
:)
I usually put patches on the ftp sites around a week before I announce
them on bug-bash, to give myself time to fix
Greg Wooledge wrote:
On Fri, May 21, 2010 at 01:32:26AM -0700, Linda Walsh wrote:
Does something need to happen for case to be ignored in wildcards,
on this file
system?
Have you tried shopt -s nocaseglob yet?
That would switch if of for all file systems, woulödn't it? Not what the OP
was lo
Greg Wooledge wrote:
On Thu, May 06, 2010 at 09:30:20AM -0500, Chuck Remes wrote:
The standard .bashrc contains a line of code that precludes certain
scripts from executing. It has to do with the logic for checking if
the session is interactive.
There's no such thing as a "standard .bashrc",
Bob Proulx wrote:
Peng Yu wrote:
My grep is aliased to "grep --color=auto".
I then use grep "", where is a tab character. But the
result is not colored. How to make the tabs colored?
You might try asking that question on bug-grep. This is bug-bash and
your issue does not seem to be with bas
Greg Wooledge wrote:
On Sat, Jan 30, 2010 at 03:17:22PM +0100, Joachim Schmitz wrote:
Clark J. Wang wrote:
Hi all,
I want to write my own built-in bash commands but I cannot find any
info about that in bash manual. Anyone has any idea?
Have a look into the .def files in the builtins
Greg Wooledge wrote:
On Sat, Jan 30, 2010 at 03:17:22PM +0100, Joachim Schmitz wrote:
Clark J. Wang wrote:
Hi all,
I want to write my own built-in bash commands but I cannot find any
info about that in bash manual. Anyone has any idea?
Have a look into the .def files in the builtins
Clark J. Wang wrote:
Hi all,
I want to write my own built-in bash commands but I cannot find any
info about that in bash manual. Anyone has any idea?
Have a look into the .def files in the builtins directory of bash's source
tree.
Add your .def file (start with a copy of an existing one chang
Greg Wooledge wrote:
> On Thu, Nov 19, 2009 at 06:32:49PM +0100, Joachim Schmitz wrote:
>> In siglist.c the compiler complained bitterly about having to
>> convert the reseult of _() into a char * (sometimes comming from
>> int, somtimes coming from const char *) My nasty
Hi folks
When trying to port bash 4 (actually 4.0.35) to NonStop Kernel, I stumbled
accross lib/readline/rltty.c to use ECHOCTL, which that platform doesn't
seem to provide.
My fix:
diff -u ./lib/readline/rltty.c.orig ./lib/readline/rltty.c
--- ./lib/readline/rltty.c.orig 2008-10-05 04:39:2
29 matches
Mail list logo
